Segment naming, Linker command files for c programs, Segment naming linker command files for c programs – Zilog ZUSBOPTS User Manual
Page 216: Table 15, Segments

Segment Naming
UM017105-0511
188
Zilog Developer Studio II – ZNEO™
User Manual
Segment Naming
The compiler places code and data into separate segments in the object file. The different
segments used by the compiler are listed in Table 15.
Linker Command Files for C Programs
This section describes how the ZNEO linker is used to link a C program. A C program
consists of compiled and assembled object module files, compiler libraries, user-created
libraries, and special object module files used for C run-time initializations. These files are
linked based on the commands given in the linker command file.
The default linker command file is automatically generated by the ZDS II IDE whenever a
build
command is issued. It has information about the ranges of various address spaces
for the selected device, the assignment of segments to spaces, order of linking, and so on.
The default linker command file can be overridden by the user.
The linker processes the object modules (in the order in which they are specified in the
linker command file), resolves the external references between the modules, and then
locates the segments into the appropriate address spaces as per the linker command file.
Table 15. Segments
Segment
Description
NEAR_DATA
_Near initialized global and static data
NEAR_BSS
_Near un-initialized global and static data
NEAR_TEXT
_Near constant strings
FAR_DATA
_Far initialized global and static data
FAR_BSS
_Far un-initialized global and static data
FAR_TEXT
_Far constant strings
ROM_DATA
_Rom global and static data
ROM_TEXT
_Rom constant strings
EROM_DATA
_Erom global and static data
EROM_TEXT
_Erom constant strings
CODE
_Erom code
__VECTORS
_Rom interrupt vectors
STARTUP
_Rom C startup