Analog Devices VisualDSP++ 3.5 Manual page 95

Loader manual for 16-bit processors
Hide thumbs Also See for VisualDSP++ 3.5:
Table of Contents

Advertisement

Output file (
-o
page
Opmode for the current and following .
-opmode
The Intel hex offset for the current loader file (see
-p
Width for the current and following
-width
The number of wait states for this and following
-wait
page
Clkdivide for this and following
-clkdivide
Address bits to be masked off for this and following
-maskaddr
page
There are four executable files (streams):
• Application 1 (
• Application 2 (
• Application 3 (
• Application 4 (
The task is to create two loader files, one is 16-bit ROM from
and one is 8-bit Flash from
0x01FFFF
There are two different ways to accomplish the task:
1. Use VisualDSP++ Flash Programmer plug-in to burn the Flash. In
this scenario, the real byte address is expected:
elfloader -proc ADSP-2191 -b PROM -width 16 app1.dxe
app2.dxe -pd 0x20000 -p 0x20000 -width8 -o flash.ldr
app3.dxe -pd 0x30000 app4.dxe
!
Since the
addresses in the Intel hex record starts at zero for
2. Equivalently, invoke the loader twice:
VisualDSP++ Loader Manual
for 16-Bit Processors
) for the current and following
.LDR
3-22).
3-24).
3-22).
) starts at byte address
app1.dxe
) appends to Application 1 (ROM)
app2.dxe
) starts at
app3.dxe
) starts at
app4.dxe
value is reset to a zero whenever an
-p
ADSP-219x DSP Loader/Splitter
s (see
.DXE
s (see
"-opmode #" on page
DXE
"-p address" on page
s (see
"-width #" on page
.DXE
s (see
.DXE
s (see
"-clkdivide #" on page
.DXE
.DXE
0x000000
(flash page 1)
0x020000
(flash page 2)
0x030000
to
0x020000
0x03FFFF
"-o filename" on
3-22).
3-22).
3-24).
"-waits #" on
3-21).
s (see
"-maskaddr #" on
(ROM)
to
0x000000
.
is specified, the
-o
.
flash.ldr
3-9

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the VisualDSP++ 3.5 and is the answer not in the manual?

Subscribe to Our Youtube Channel

Related Products for Analog Devices VisualDSP++ 3.5

Table of Contents