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> for ADSP-2126x/2136x/2137x SHARC Processors<br />

The kernel code with the decompression engine is on the top of the loader<br />

file. This section is loaded into the processor first <strong>and</strong> is executed first<br />

when a boot process starts. Once the kernel code is executed, the rest of<br />

the stream is brought into the processor. The kernel code calls the decompression<br />

routine to perform the decompression operation on the stream,<br />

<strong>and</strong> then loads the decompressed stream into the processor’s memory in<br />

the same manner a conventional kernel does when it encounters a compressed<br />

stream.<br />

Figure 5-6 shows the structure of a compressed boot stream.<br />

COMPRESSED BLOCK HEADER<br />

COMPRESSED STREAM<br />

Figure 5-6. Compressed Block<br />

Compressed Block Headers<br />

A compressed stream always has a header, followed by the payload compressed<br />

stream.<br />

The compressed block header is comprised of three 32-bit words. The<br />

structure of a compressed block header is shows in Figure 5-7.<br />

0X00002000 COMPRESSION TAG/FLAG<br />

0XWBIT0PAD WINDOW SIZE/PADDED WORD COUNT<br />

0XBYTEBYTE COMPRESSED BYTE COUNT<br />

Figure 5-7. Compressed Block Header<br />

The first 32-bit word of the compressed block header holds the compression<br />

flag, 0x00002000, which indicates that it is a compressed block<br />

header.<br />

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

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

Saved successfully!

Ooh no, something went wrong!