Analog Devices VisualDSP++ 3.5 Manual page 95

tion may have the same name. In this example, the memory
segment and output section are named as
because the memory holds both program (
( ) information.
data1
• Each
PROCESSOR{}
cutable file.
• The
OUTPUT()
( ) file and specifies its file name.
.DXE
In this example, the argument to the
$COMMAND_LINE_OUTPUT_FILE
names the executable file according to the text following the
switch (which corresponds to the name specified in the Project
Options dialog box when the linker is invoked via the
VisualDSP++ IDDE).
>
linker ... -o outputfilename
SECTIONS{}
data in physical memory. The linker maps input sections (in object
files) to output sections (in executables), and maps the output sec-
tions to memory segments specified by the
The
INPUT_SECTIONS()
uses as an input to resolve the mapping to the appropriate memory
segment declared in the
The
INPUT_SECTIONS
linker uses as an input to resolve the mapping to the appropriate
MEMORY
two input sections (
ory segment (L2), as shown below.
VisualDSP++ 3.5 Linker and Utilities Manual
for 16-Bit Processors
command
command (on page
(on page 3-42) specifies the placement of code and
statement specifies the object file the linker
.LDF
statement specifies the object file that the
segment declared in the LDF. For example, in
program
Linker Description File
MEM_L2
program
(on page 3-39) generates a single exe-
3-39) produces an executable
OUTPUT()
macro (on page 3-21). The linker
MEMORY{}
file.
and ) are mapped into one mem-
data1
and
DXE_L2
) and data
command is the
-o
command.
Listing 3-1,
3-9