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 />

Similar to the ADSP-BF531/BF532/BF533 processor, the<br />

ADSP-BF561/BF566 boot ROM uses the interrupt vectors to stay in<br />

supervisor mode.<br />

The boot ROM code transitions from the RESET interrupt service routine<br />

into the lowest priority user interrupt service routine (Int 15) <strong>and</strong><br />

remains in the interrupt service routine. The boot ROM then checks<br />

whether it has been invoked by a software reset by examining bit 4 of the<br />

system reset configuration register (SYSCR).<br />

If bit 4 is not set, the boot ROM presumes that a hard reset has occurred<br />

<strong>and</strong> performs the full boot sequence. If bit 4 is set, the boot ROM underst<strong>and</strong>s<br />

that the user code has invoked a software reset <strong>and</strong> restarts the user<br />

program by jumping to the beginning of core A’s L1 memory<br />

(0xFFA0 0000), bypassing the entire boot sequence.<br />

When developing an ADSP-BF561/BF566 processor application, you<br />

start with compiling <strong>and</strong> linking your application code into an executable<br />

(.dxe) file. The debugger loads the .dxe file into the processor’s memory<br />

<strong>and</strong> executes it. With two cores, two .dxe files can be loaded at once. In<br />

the real-time environment, there is no debugger which allows the boot<br />

ROM to load the executables into memory.<br />

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

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

Saved successfully!

Ooh no, something went wrong!