Renamed RAM to MAIN for all disk based targets.
The name RAM doesn't make much sense in general for a memeory area because i.e. the zero page is for sure RAM but is not part of the memory area named RAM. For disk based targets it makes sense to put the disk file more into focus and here MAIN means the main part of the file - in contrast to some header. Only for ROM based targets the name RAM is kept as it makes sense to focus on the difference between RAM and ROM.
This commit is contained in:
@@ -148,7 +148,7 @@ Special locations:
|
||||
($58).
|
||||
|
||||
<tag/Stack/
|
||||
The C runtime stack is located at end of the RAM memory area ($CFFF)
|
||||
The C runtime stack is located at end of the MAIN memory area ($CFFF)
|
||||
and grows downwards.
|
||||
|
||||
<tag/Heap/
|
||||
@@ -561,7 +561,7 @@ The contents of this chunk come from the SYSCHKCHNK memory area of the linker co
|
||||
<item>main program&nl;
|
||||
This load chunk is loaded at the selected program start address (default $2000) and
|
||||
contains all of the code and data of the program.&nl;
|
||||
The contents of this chunk come from the RAM memory area of the linker config file.
|
||||
The contents of this chunk come from the MAIN memory area of the linker config file.
|
||||
</enum>
|
||||
|
||||
|
||||
|
||||
Reference in New Issue
Block a user