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.

Boot Streams<br />

Introduction<br />

The loader utility’s output (.ldr file) is essentially the same executable<br />

code as in the input .dxe file; the loader utility simply repackages the executable<br />

as shown in Figure 1-2.<br />

.DXE FILE<br />

CODE<br />

DATA<br />

SYMBOLS<br />

DEBUG<br />

INFORMATION<br />

A .DXE FILE INCLUDES:<br />

- DSP INSTRUCTIONS (CODE AND DATA)<br />

- SYMBOL TABLE AND SECTION INFORMATION<br />

- TARGET PROCESSOR MEMORY LAYOUT<br />

- DEBUG INFORMATION<br />

.LDR FILE<br />

Figure 1-2. A .dxe File Versus an .ldr File<br />

Processor code <strong>and</strong> data in a loader file (also called a boot stream) is split<br />

into blocks. Each code block is marked with a tag that contains information<br />

about the block, such as the number of words <strong>and</strong> destination in the<br />

processor’s memory. Depending on the processor family, there can be<br />

additional information in the tag. Common block types are “zero” (memory<br />

is filled with 0s); nonzero (code or data); <strong>and</strong> final (code or data).<br />

Depending on the processor family, there can be other block types.<br />

Refer to the following chapters to learn more about boot streams.<br />

<strong>VisualDSP++</strong> <strong>4.5</strong> <strong>Loader</strong> <strong>and</strong> <strong>Utilities</strong> <strong>Manual</strong> 1-15<br />

CODE<br />

DATA<br />

SYMBOLS<br />

DEBUG<br />

INFORMATION<br />

AN .LDR FILE INCLUDES:<br />

- DSP INSTRUCTIONS (CODE AND DATA)<br />

- RUDIMENTARY FORMATTING<br />

(ALL DEBUG INFORMATION HAS<br />

BEEN REMOVED)

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

Saved successfully!

Ooh no, something went wrong!