Linker Description File - Overview - Analog Devices VisualDSP++ 3.5 Manual

• Contiguous addresses on different-width hardware must reside in
different memory segments.
• More than one output section may map to a memory segment if
the output sections fit completely within the memory segment.
Linker Description File — Overview
Whether you are linking C/C++ functions or assembly routines,
the mechanism is the same. After converting the source files into object
files, the linker uses directives in an
an executable file (
Executable file structure conforms to the Executable and Linkable
Format (ELF) standard.
Each project must include one
by defining the target memory and mapping the code and data into that
memory. You can write your own
file; modification is often the easier alternative when there are few changes
in your system's hardware or software. VisualDSP++ provides an
that supports the default mapping of each processor type.
When developing a new project, use the Expert Linker to generate
the project's
Similar to an object (
different segments, called output sections. Input section names are
independent of output section names. Because they exist in different
namespaces, input section names can be the same as output section names.
Refer to Chapter 3,
VisualDSP++ 3.5 Linker and Utilities Manual
for 16-Bit Processors
.LDF
), which may be loaded into a simulator for testing.
.DXE
file that specifies the linking process
.LDF
.LDF
file, as described in Chapter 4,
.LDF
) file, an executable (
.DOJ
"Linker Description File"
file to combine the objects into
file, or you can modify an existing
"Expert
) file consists of
.DXE
for further information.
Linker
file
.LDF
Linker".
2-5