Oliver, So in general it's the "map of memory available to the cc65 program" what > the .cfg files describes. > Ahhh ... got it! That helps me out a lot! So instead of saying: The cc65 toolset requires a memory configuration file to define the memory > map of the system > I should really say: The cc65 toolset requires a memory configuration file to define the memory > that is available to the cc65 run-time environment > I have modified the text after the memory configuration as follows: ZP defines the available zero page locations, which in this case starts at > $0 and has a length of $100. Keep in mind that certain systems may require > access to some zero page locations, so the starting address may need to be > adjusted accordingly to prevent cc65 from attempting to reuse those > locations. Also, at a minimum, the cc65 run-time environment uses 26 zero > page locations, so the smallest zero page size that can be specified is > $1A. The usable RAM segment begins after the 6502 stack storage in page 1, > so it is defined as starting at location $200 and filling the remaining 4K > of space (4096 - 2 × 256 = 3584 = $0E00). > Does this sound better? Bruce ---------------------------------------------------------------------- To unsubscribe from the list send mail to majordomo@musoftware.de with the string "unsubscribe cc65" in the body(!) of the mail.Received on Thu Feb 18 16:07:53 2010
This archive was generated by hypermail 2.1.8 : 2010-02-18 16:07:55 CET