Loader Tasks
Loader Tasks
Common tasks perform by the loader include:
• Processing loader option settings or command-line switches.
• Formatting the output
Supported formats are binary, ASCII, hex-32, and more. Valid file
formats are described in Appendix A
• Packing the code for a particular data format: 8- or 16-bit.
• If specified, adding a boot kernel on top of the user code.
• If specified, preprogramming the location of the
PROM space.
• Specifying processor IDs for multiple input
cessor system.
Loader Files
The loader/splitter output is essentially the same executable code as in the
input
file. The loader repackages the executable, as illustrated in
.DXE
Figure
1-1.
Processor code in a loader file is split into blocks. Each code block is
marked with a tag that contains information about the block, such as a
number of words or destination in processor's memory. Depending on the
processor family, there may be additional information in the tag. Com-
mon block types are "zero" (memory is filled with 0s); non-zero (code or
data); and final (code or data). Depending on the processor family, there
may be other block types.
1-8
file according to user specifications.
.LDR
on page
VisualDSP++ 3.5 Loader Manual
A-1.
file in
.LDR
for a multipro-
.DXEs
for 16-Bit Processors
Need help?
Do you have a question about the VisualDSP++ 3.5 and is the answer not in the manual?