VisualDSP++ 4.5 Loader and Utilities Manual - Analog Devices

Blackfin Processor Booting
with the data. The loader utility, however, creates a regular last block if no
data is in that memory range. The space of 0xFF903F00 to 0xFF903FFF is
saved for the boot ROM to use as a data buffer during a boot process.
Initialization Blocks
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
Last Block:
1 = Last Block
0 = Not Last Block
Compressed Block:
1 = Compressed Block
0 = Not Compressed Block
Port Number:
00 = Disabled, 01 =Port F
10 = Port G, 11 = Port H
Programmable Flag:
0 = Default, Selectable from 0–15
Ignore Block: 1 = Ignore Block, 0 = Do Not Ignore Block
Initialization Block: 1 = Init Block, 0 = No Init Block
Processor Type: 1 = ADSP-BF533/534/536/537/538/539
0 = ADSP-BF531/BF532
Zero-Fill: 1 = Zero-Fill Block, 0 = No Zero-Fill Block
Bits 14, 12–11 are reserved for future use
Figure 2-29. Flag Bit Assignments for 2-Byte Block Flag Word
The -init filename option directs the loader utility to produce the initialization
blocks from the initialization section’s code in the named file.
The initialization blocks are placed at the top of a loader file. They are
executed before the rest of the code in the loader file booted into the
memory (see Figure 2-30).
Following execution of the initialization blocks, the boot process
continues with the rest of data blocks until it encounters a final block (see
Figure 2-31). The initialization code example follows in Listing 2-1 on
page 2-38.
2-36 VisualDSP++ 4.5 Loader and Utilities Manual
0