nop;
nop;
rti;
The page loaders are generated dynamically by the
on the number of overlay pages to be initialized. A page loader sets up
BDMA transfers. Since BDMA transfers cannot target off-chip DM and
PM memories (overlay pages 1 and 2) directly, the corresponding page
loaders first BDMA-load the data into on-chip memory and then copy the
data by core instructions.
The final BDMA sequence has the BCR bit set. It overwrites the preloader
and page loaders resident in internal PM memory and issues a context
reset once it has finished. The program counter resets to
gram execution begins.
Refer to the ADSP-218x DSP Hardware Reference for a detailed descrip-
tion of BDMA capabilities. You can debug the EPROM booting process
using the VisualDSP++ simulator by loading the
ulator) and then resetting (Debug->Reset) the DSP to start booting.
The loader outputs files in industry-standard file formats, Intel hex-32
and Motorola S, which are readable by most EPROM burners. For
advanced usage, other file formats are supported; refer to Appendix A,
"File Formats"
ADSP-218x BDMA Loader Command-Line Reference
This section details the ADSP-218x BDMA loader's command-line
interface.
The syntax for the loader's command line is:
elfspl21 sourcefile [outputfile] -218{x|1} [-switch ...]
VisualDSP++ 3.5 Loader Manual
for 16-Bit Processors
nop; nop; nop;
nop; nop; nop;
nop; nop; nop;
for details. The default file extension is .
ADSP-218x DSP Loader/Splitter
/* 0x0014: 000000 000000 */
/* 0x0018: 000000 000000 */
/* 0x001C: 0A001F 000000 */
elfspl21
file (Settings->Sim-
.BNM
, depending
and pro-
0x0000
BNM.
5-7
Need help?
Do you have a question about the VisualDSP++ 3.5 and is the answer not in the manual?
Questions and answers