25.12.2012 Views

VisualDSP++ 4.5 Loader and Utilities Manual - Analog Devices

VisualDSP++ 4.5 Loader and Utilities Manual - Analog Devices

VisualDSP++ 4.5 Loader and Utilities Manual - Analog Devices

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>Loader</strong>/Splitter for Blackfin Processors<br />

ADSP-BF53x <strong>and</strong> ADSP-BF561/BF566<br />

Multi-Application (Multi-DXE) Management<br />

� This<br />

section does not applies to ADSP-BF535 processors.<br />

This section describes how to boot more than one .dxe file into an<br />

ADSP-BF531/BF532/BF533/BF534/ BF536/BF537/BF538/BF539 <strong>and</strong><br />

ADSP-BF561/BF566 processor. The information presented in this section<br />

applies to all of the named processors. For additional information on the<br />

ADSP-BF561/BF566 processor, refer to “ADSP-BF561/BF566<br />

Dual-Core Application Management” on page 2-50.<br />

The ADSP-BF531/BF532/BF533/BF534/ BF536/BF537/BF538/BF539<br />

<strong>and</strong> ADSP-BF561/BF566 loader file structure <strong>and</strong> the silicon revision of<br />

0.1 <strong>and</strong> higher allow the booting of multiple .dxe files into a single<br />

processor from external memory. As illustrated in Figure 2-32, each executable<br />

file is preceded by a 4-byte count header, which is the number of<br />

bytes within the executable, including headers. This information can be<br />

used to boot a specific .dxe file into the processor. The 4-byte .dxe count<br />

block is encapsulated within a 10-byte header to be compatible with the<br />

silicon revision 0.0. For more information, see<br />

“ADSP-BF531/BF532/BF533/BF534/BF536/BF537/BF538/ BF539<br />

Blocks, Block Headers, <strong>and</strong> Flags” on page 2-33.<br />

Booting multiple executables can be accomplished by one of the following<br />

methods.<br />

Use the second-stage loader switch, “-l userkernel.dxe”. This<br />

option allows the use of your own second-stage loader.<br />

After the second-stage loader gets booted into internal memory via<br />

<strong>VisualDSP++</strong> <strong>4.5</strong> <strong>Loader</strong> <strong>and</strong> <strong>Utilities</strong> <strong>Manual</strong> 2-51

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!