Compiling And Assembling; Linking; Loading And Splitting - Analog Devices VisualDSP++ 3.5 Manual

Program Development Flow

Compiling and Assembling

Input source files are compiled and assembled to yield object files. Source
files are text files containing C/C++ code, compiler directives, possibly a
mixture of assembly code and directives, and, typically, preprocessor com-
mands. Refer to the VisualDSP++ 3.5 Assembler and Preprocessor Manual
or the VisualDSP++ 3.5 C/C++ Compiler and Library Manual for informa-
tion about the assembler and compiler source files.

Linking

Under the direction of the Linker Description File (LDF) and linker set-
tings, the linker consumes separately assembled object and library files to
yield an executable file. If specified, shared memory and overlay files are
also produced. The linker output conforms to the Executable and Link-
able Format (ELF), an industry-standard format for executable files. The
linker also produces map files and other embedded information used by
the debugger (DWARF-2).
These executable files (.
directly. They are neither supposed to be burned onto a EPROM or Flash
memory device. Executable files are consumed by VisualDSP++ debugging
targets, such as the simulator or emulator. Refer to the VisualDSP++ 3.5
Linker and Utilities Manual for 16-Bit Processors and online Help for infor-
mation about linking and debugging.

Loading and Splitting

Upon completing the debug cycle, the processor hardware needs to run on
its own, without any debugging tools connected. After power-up, proces-
sor memories need to be initialized to be booted. Therefore, the linker
output must be transformed to a format readable by the processor. This
process is handled by the loader/splitter utility. The loader/splitter uses
the debugged and tested executable as well as shared memory and overlay
files as inputs to yield a processor-loadable file.
1-2
) are not readable by the processor hardware
DXE
VisualDSP++ 3.5 Loader Manual
for 16-Bit Processors