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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>Loader</strong> for ADSP-2126x/2136x/2137x SHARC Processors<br />

in FINAL_INIT (“DO RESET UNTIL EQ;”). When a loop condition<br />

is achieved within the last three instructions of a loop,<br />

the processor branches to the top-of-loop address (PCSTK)<br />

one final time.<br />

5) We manually changed this top-of-loop address 0x80004, <strong>and</strong> so<br />

to conclude the kernel, the processor executes the instruction<br />

at 0x80004 *again*.<br />

6) There’s a new instruction at 0x80004: “PM(0,I8)=PX;”. This<br />

initializes the user-intended instruction at 0x80030 (the vector<br />

for the High-Priority-SPI interrupt).<br />

At this point, the kernel is finished, <strong>and</strong> execution continues<br />

at 0x80005, with the only trace as if nothing happened! */<br />

/* ========================================================== */<br />

ADSP-2136x/2137x Multi-Application (Multi-DXE)<br />

Management<br />

Up to eight ADSP-21367/21368/21389 <strong>and</strong> ADSP-2137x processors can<br />

be clustered together <strong>and</strong> supported by the <strong>VisualDSP++</strong> loader utility. In<br />

PROM boot mode, all of the processors can boot from the same PROM.<br />

The loader utility assigns an input executable (.dxe) file to a processor ID<br />

or to a number of processor IDs, provided a corresponding loader option<br />

is selected on the property page or on the comm<strong>and</strong> line. The loader utility<br />

inserts the ID into the output boot stream using the multiprocessor tag<br />

MULTI_PROC (see Table 5-12). The loader utility also inserts the offset (the<br />

32-bit word count of the boot stream built from the input executable<br />

(.dxe) file) into the boot stream. The MULTI_PROC tag enables the boot kernel<br />

to identify each section of the boot stream with the executable (.dxe)<br />

file from which that section was built. The Figure 5-3 shows the multiprocessor<br />

boot stream structure.<br />

<strong>VisualDSP++</strong> <strong>4.5</strong> <strong>Loader</strong> <strong>and</strong> <strong>Utilities</strong> <strong>Manual</strong> 5-33

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

Saved successfully!

Ooh no, something went wrong!