diff --git a/doc/customizing.sgml b/doc/customizing.sgml index 1ae49f3c0..29c525e00 100644 --- a/doc/customizing.sgml +++ b/doc/customizing.sgml @@ -81,7 +81,6 @@ SEGMENTS { ZEROPAGE: load = ZP, type = zp, define = yes; DATA: load = ROM, type = rw, define = yes, run = RAM; BSS: load = RAM, type = bss, define = yes; - HEAP: load = RAM, type = bss, optional = yes; STARTUP: load = ROM, type = ro; ONCE: load = ROM, type = ro, optional = yes; CODE: load = ROM, type = ro; @@ -95,7 +94,6 @@ The meaning of each of these segments is as follows.
ZEROPAGE: Data in page 0, defined by ZP as starting at $0 with length $100
DATA: Initialized data that can be modified by the program, stored in RAM
BSS: Uninitialized data stored in RAM (used for variable storage) -
HEAP: Uninitialized C-level heap storage in RAM, optional
STARTUP: The program initialization code, stored in ROM
ONCE: The code run once to initialize the system, stored in ROM
CODE: The program code, stored in ROM
@@ -304,16 +302,17 @@ also forcing a BRK instruction into the CPU.
The next step in customizing the cc65 toolset is creating a run-time
library for the targeted hardware. The recommended way to do this is to
modify the platform-independent standard library of the cc65 distribution.
-It is named "none.lib" in the lib directory of the distribution.
+It is named "no-platform.lib" in the lib directory of the
+cc65 distribution.
-When using "none.lib" we need to supply our own crt0
+When using "no-platform.lib" we need to supply our own crt0
module with custom startup code. This is simply done by first copying the
the library and giving it a new name, compiling the startup code with ca65,
and finally using the ar65 archiver to add the module to the new library.
The steps are shown below: