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.

File Searches<br />

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

-bspiflash—Specifies SPI flash port booting as the boot type for<br />

the boot-loadable file.<br />

-proc ADSP-21262 —Specifies ADSP-21262 as the target<br />

processor.<br />

File searches are important in loader processing. The loader utility supports<br />

relative <strong>and</strong> absolute directory names, default directories, <strong>and</strong><br />

user-selected directories for file search paths. File searches occur as<br />

described on page 1-16.<br />

File Extensions<br />

Some loader switches take a file name as an optional parameter.<br />

Table 5-17 lists the expected file types, names, <strong>and</strong> extensions.<br />

Table 5-17. File Extensions<br />

Extension File Description<br />

.dxe Executable files <strong>and</strong> boot kernel files. The loader utility recognizes overlay memory<br />

files (.ovl) <strong>and</strong> shared memory files (.sm), but does not expect these files on the<br />

comm<strong>and</strong> line. Place .ovl <strong>and</strong> .sm files in the same directory as the .dxe file that<br />

refers to them. The loader utility finds the files when processing the .dxe file. The<br />

.ovl <strong>and</strong> .sm files may also be placed in the .ovl <strong>and</strong> .sm file output directory<br />

specified in the .ldf file.<br />

.ldr <strong>Loader</strong> output file.<br />

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

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

Saved successfully!

Ooh no, something went wrong!