Booting A Different Application - Analog Devices ADSP-BF506F Hardware Reference Manual

Boot Management
others may have a separate application that controls the process, namely a
boot manager.
In a master boot mode where the on-chip boot kernel loads the boot
stream from memory, the boot manager is a piece of Blackfin software
which decides at runtime what application is booted next. This may sim-
ply be based on the state of a GPIO input pin interrogated by the boot
manager, or it may be the conclusion of complex system behavior.
Slave boot scenarios are different from master boot scenarios. In slave boot
modes, the host masters boot management by setting the Blackfin proces-
sor to reset and then applying alternate boot data. Optionally, the host
could alter the
Blackfin processor since the intelligence is provided by the host device.

Booting a Different Application

The boot ROM provides a set of user-callable functions that help to boot
a new application (or a fraction of an application). Usually there is no
need for the boot manager to deal with the format details of the boot
stream.
These functions are:
•
BFROM_MEMBOOT
•
BFROM_SPIBOOT
page 24-47
The user application, the boot manager application, or an initcode can call
these functions to load the requested boot data. Using the
flag the user can control whether the routine simply returns to the calling
function or executes the loaded application immediately.
These ROM functions expect the start address of the requested boot
stream as an argument. For
address, for
BFROM_SPIBOOT
24-38
configuration pins, resulting in little impact to the
BMODE
discussed in
discussed in
BFROM_MEMBOOT
it is a serial address. The SPI function can also
ADSP-BF50x Blackfin Processor Hardware Reference
"Flash Boot Modes" on page 24-45
"SPI Master Boot Modes" on
, this is a Blackfin memory
BFLAG_RETURN