ADSP-219x DSP Booting
elfloader -proc ADSP-2191 -b PROM -width 16 app1.dxe
app2.dxe -pdAddrNext 0x20000
elfloader -proc ADSP-2191 -b PROM -width 8 -o flash.ldr -pd
0x20000 -p 0x20000 app3.dxe -pd 0x30000 app4.dxe
!
In cases where the
you may specify
elfloader -proc ADSP-2191 -b PROM -width 16 app1.dxe
app2.dxe -pd 0x20000 -pEqualPD -width8 -o flash.ldr
app3.dxe -pd 0x30000 app4.dxe
With the
-NoDxeAddrHdr
the user loader can still parse the complete boot stream, block by block
until it detects a final-init block. Since the default
zero whenever an
to be explicitly set to
It is very likely that second-stage loaders and similar type of programs exe-
cute directly from the EPROM. Thus, this multiple
often combined with the features discussed in
with No-boot Data" on page
Host Booting
Host booting is performed in either an 8-bit or 16-bit scenario. By
default, little-endian format is used. If configured in Host boot mode, the
DSP does not support the boot process actively. It is the host's responsi-
bility to initialize the DSP memories properly. The DSP passively waits
until the host writes a "
). Then the DSP starts fetching and executing instructions at
0x1CFC
address
0x00 0000
3-10
and
-pd
-p
:
-pEqualPD
switch, this artificial block is not inserted. Then
is specified, the addresses in the Intel hex record has
-o
for
0x20000
flash.ldr
3-16.
" to the Semaphore A register (IO address
1
.
values are expected to be the same,
value is reset to a
-p
.
.DXE
"Enriching Boot EPROMs
VisualDSP++ Loader Manual
for 16-Bit Processors
scenarios are
Need help?
Do you have a question about the VisualDSP++ 3.5 and is the answer not in the manual?