Analog Devices VisualDSP++ 3.5 Manual page 61

Linker and utilities manual for 16-bit processors
Hide thumbs Also See for VisualDSP++ 3.5:
Table of Contents

Advertisement

{ TYPE(RAM) START(0xF0000000) END(0xF002FFFF) WIDTH(8) }
MEM_HEAP
{ TYPE(RAM) START(0xF0030000) END(0xF0037FFF) WIDTH(8) }
MEM_STACK
{ TYPE(RAM) START(0xF0038000) END(0xF003DFFF) WIDTH(8) }
MEM_SYSSTACK
{ TYPE(RAM) START(0xF003E000) END(0xF003FDFF) WIDTH(8) }
MEM_ARGV
{ TYPE(RAM) START(0xF003FE00) END(0xF003FFFF) WIDTH(8) }
}
Listing 2-2. ADSP-2191 DSPs -- MEMORY{} Command
MEMORY /* Define and label system memory
{
/* List of global memory segments
seg_rth
{TYPE(PM RAM) START(0x000000) END(0x000241) WIDTH(24)}
seg_code
{TYPE(PM RAM) START(0x000242) END(0x007fff) WIDTH(24)}
seg_data1 {TYPE(DM RAM) START(0x008000) END(0x00ffff) WIDTH(16)}
}
The above examples apply to the preceding discussion of how to
write a
SECTIONS{}
can be interspersed with other directives, including location
counter information. You can define new symbols within the
file.
These example define the starting stack address, the highest possi-
ble stack address, and the heap's starting location and size. These
newly created symbols are entered in the executable's symbol table.
VisualDSP++ 3.5 Linker and Utilities Manual
for 16-Bit Processors
command and to the following discussion of the
MEMORY{}
command. The
*/
*/
command is not atomic; it
SECTIONS{}
Linker
.LDF
2-25

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the VisualDSP++ 3.5 and is the answer not in the manual?

Subscribe to Our Youtube Channel

Related Products for Analog Devices VisualDSP++ 3.5

Table of Contents