Adsp-Bf561 Multiple .Dxe Booting - Analog Devices VisualDSP++ 3.5 Manual

Blackfin Processor Booting

ADSP-BF561 Multiple .DXE Booting

A typical dual-core application is separated into two executable files; one
for each core. The default linker description files (LDFs) for the
ADSP-BF561 processor creates two separate executable files (
) and some shared memory files (
p1.dxe
ing the LDF, it is possible to create a dual-core application that combines
both cores into a single
application is a simple assembly language program which does not link
any C runtime libraries. When using shared memory and/or C runtime
routines on both cores, it is best to generate a separate
core. The loader combines the contents of the shared memory files
( ,
sml2.sm sml3.sm
The boot ROM only loads one single executable before the ROM jumps
to the start of core A instruction SRAM (
must be loaded, a second stage loader should be used. The second stage
boot loader must start at
the second stage loader. A default second stage loader is provided for each
boot mode and can be customized by the user.
Unlike the initialization block, the second-stage loader takes full control
over the boot process and never returns to the boot ROM.
The second-stage loader can use the
cific s in external memory.
.DXE
The default second stage loader uses the last 1024 bytes of L2 memory.
The area must be reserved during booting but can be reallocated at
runtime.
2-36
file. This is not recommended unless the
.DXE
) into the file for core A (
.DXE
0xFFA0 0000
and
sml2.sm sml3.sm
p0.dxe
). When two
0xFFA0 0000
. The boot ROM loads and executes
byte count blocks to find spe-
.DXE
VisualDSP++ Loader Manual
for 16-Bit Processors
and
p0.dxe
). By modify-
file for each
.DXE
).
.DXEs