Multi-Dxe Boot Streams - Analog Devices ADSP-BF506F Hardware Reference Manual

accept the code for the GPIO pin that controls the device select strobe of
the SPI memory.

Multi-DXE Boot Streams

If the start addresses of all the boot streams are predefined, the boot man-
ager needs only to call the ROM functions directly. However since the
addresses tend to vary from build to build they may have to be calculated
at runtime.
In the world of the elfloader, a boot stream is always generated from a
DXE file. It is therefore common to talk about multi-DXE or multi-appli-
cation booting. When the elfloader utility accepts multiple DXE files on
its command line, it generates a contiguous boot image by default. The
second boot stream is appended immediately to the first one. Since the
utility updates the
field of a
BFLAG_FIRST
The next-DXE pointer of the first DXE boot stream points relatively to
the start address of the second DXE boot stream. A multi-DXE boot
image can be seen as a linked list of boot streams. The next-DXE pointer
of the last DXE boot stream points relatively to the next free address. This
is illustrated by an example shown in the next two figures.
shows a commented sketch as an example.
of the Blackfin loader file viewer utility for the same example. The
utility is not part of the CrossCore Embedded Studio or Visu-
LdrViewer
alDSP++ tools suite. It is a third-party freeware product available on
www.dolomitics.com.
ADSP-BF50x Blackfin Processor Hardware Reference
field of all
ARGUMENT
block is called next-DXE pointer (NDP).
System Reset and Booting
blocks, the
BFLAG_FIRST
Figure 24-8 shows a screenshot
ARGUMENT
Figure 24-7
24-39