Software Development Flow - Analog Devices VisualDSP++ 3.5 Manual

Software Development Flow

Software Development Flow
The majority of this manual describes linking, a critical stage in the
program development process for embedded applications.
The linker tool (
executable files, which can be loaded onto a simulator or target processor.
The linker also produces map files and other output that contain informa-
tion used by the debugger. Debug information is embedded in the
executable file.
After running the linker, you test the output with a simulator or emulator.
Refer to the VisualDSP++ User's Guide of your target processors and
online Help for information about debugging.
Finally, you process the debugged executable file(s) through the loader or
splitter to create output for use on the actual processor. The output file
may reside on another processor (host) or may be burned into a PROM.
Separate Loader Manual for 16-Bit Processors describes loader/splitter func-
tionality for the target processors.
The processor software development flow can be split into three phases:
1. Compiling and Assembling – Input source files C (
and assembly (
2. Linking – Under the direction of the Linker Description File
( ), a linker command line, and VisualDSP++ Project Options
.LDF
dialog box settings, the linker utility consumes object files (
to yield an executable (
and overlay (
3. Loading or splitting – The executable (
memory (
output file(s). For Blackfin processors, these are boot-loadable
( ) files or non-bootable PROM image files, which execute from
LDR
the processor's external memory.
1-2
) consumes object and library files to produce
linker.exe
) yield object files (
.ASM
) file. If specified, shared memory (
.DXE
) files are also produced.
.OVL
) and overlay (
.SM
VisualDSP++ 3.5 Linker and Utilities Manual
)
.DOJ
), as well as shared
.DXE
) files, are processed to yield
.OVL
), C++ (
.C .CPP
)
.DOJ
.SM
for 16-Bit Processors
),
)