Analog Devices ADSP-BF506F Hardware Reference Manual page 1130

Advanced Boot Techniques
The elfloader utility provides two different mechanisms to support the
initcode feature.
• The
-init initcode.dxe
• The
-initcall address/symbol
If enabled by the elfloader
initcode is added to the beginning of the boot stream. Here,
refers to the user-provided custom initialization executable— a separate
project. Figure 24-6
lowing steps.
1. Boot initcode into L1 memory.
2. Execute initcode.
3. Overwrite initcode with final application code.
4. Boot data/code into memory.
5. Continue program execution with block n.
Although
initcode.dxe
they differ from standard projects. Initcodes provide only a callable
sub-function, so they look more like a library than an application. Never-
theless, unlike library files (
already been resolved by the linker.
An initcode is always a heading for the regular application code. Conse-
quently whether the initcode consists of one or multiple blocks, it is not
terminated by a
ROM to terminate the boot process.
It is advantageous to have a clear separation between the initcode and the
application by using the
elfloader
-initcall
24-26
command line switch
-init initcode.dxe
shows a boot stream example that performs the fol-
files are built as CCES or VisualDSP++ projects,
file extension), the symbol addresses have
.DLB
bit indicator—this would cause the boot
BFLAG_FINAL
switch. If this separation is not needed, the
-init
command-line switch might be preferred. It enables
ADSP-BF50x Blackfin Processor Hardware Reference
command line switch
command-line switch, the
initcode.dxe