Each segment declaration must contain a
or
LENGTH()
END()
described as:
•
segment_name
Identifies the memory region. The
letter, underscore, or point, and may include any letters, under-
scores, digits, and points, and must not conflict with LDF
keywords.
•
START(address_number)
Specifies the memory segment's start address. The
must be an absolute address.
•
TYPE()
Identifies the architecture-specific type of memory within the
memory segment.
Note: Not all target processors support all types of memory. The
linker stores this information in the executable file for use by other
development tools.
• For Blackfin processors, use
hardware locus (RAM or ROM). The RAM declarator specifies
segments that need to be booted. ROM segments are not
booted; they are executed/loaded directly from off-chip PROM
space.
• For ADSP-218x/9x DSPs, use
ters: memory usage (PM for program memory or DM for data
memory), and functional or hardware locus (RAM or ROM, as
described above). In addition, in ADSP-218x LDFs, the
PM/DM declarator specifies the memory type; and in
ADSP-219x LDFs, it is used only to distinguish between a
16-bit or 24-bit logical data width.
VisualDSP++ 3.5 Linker and Utilities Manual
for 16-Bit Processors
, and a
. Parts of a segment declaration are
WIDTH()
Linker Description File
,
segment_name
TYPE()
must start with a
segment_name
to specify the functional or
TYPE()
to specify two parame-
TYPE()
,
,
START()
address_number
3-31
Need help?
Do you have a question about the VisualDSP++ 3.5 and is the answer not in the manual?