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.

TigerSHARC <strong>Loader</strong> Guide<br />

Using TigerSHARC <strong>Loader</strong> Comm<strong>and</strong> Line<br />

The TigerSHARC loader utility uses the following comm<strong>and</strong>-line syntax.<br />

For a single input file:<br />

elfloader inputfile -proc processor [-switch …]<br />

For multiple input files:<br />

elfloader inputfile1 inputfile2 … -proc processor [-switch …]<br />

where:<br />

� Comm<strong>and</strong>-line<br />

inputfile—Name of the executable file (.dxe) to be processed<br />

into a single boot-loadable or non-bootable file. An input file name<br />

can include the drive <strong>and</strong> directory.<br />

For multiprocessor or multi-input systems, specify multiple input<br />

.dxe files. Use the -id#exe= switch, where # is the ID number<br />

(from 0 to 7) of the processor. Enclose long file names within<br />

straight quotes, “long file name”.<br />

-proc processor—Part number of the processor (for example,<br />

ADSP-TS101) for which the loadable file is built.<br />

-switch …—One or more optional switches to process. Switches<br />

select operations <strong>and</strong> modes for the loader utility.<br />

switches may be placed on the comm<strong>and</strong> line in<br />

any order. For a multi-input system, the loader utility processes the<br />

input executable files in the ascending order from the -id#exe=<br />

switch presented on the comm<strong>and</strong> line.<br />

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

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

Saved successfully!

Ooh no, something went wrong!