VisualDSP++ 4.5 Loader and Utilities Manual - Analog Devices

Introduction
Download the loadable file into the processor’s PROM space on an
EZ-KIT Lite ® board via the Flash Programmer plug-in. Refer to
VisualDSP++ Help for information on the Flash Programmer.
Use VisualDSP++ to simulate booting in a simulator session (currently
supported on ADSP-21060, ADSP-21061, ADSP-21065L,
ADSP-21160, and ADSP-21161 processors). Load the loader file
and then reset the processor to debug the booting routines. No
hardware is required: just point to the location of the loader file,
letting the simulator to do the rest. You can step through the boot
kernel code as it brings the rest of the code into memory.
Store the loader file in an array for a multiprocessor system. A master
(host) processor has the array in its memory, allowing a full
control to reset and load the file into the memory of a slave
processor.
Non-bootable Files Versus Boot-loadable Files
A non-bootable file executes from an external memory of the processor,
while a boot-loadable file is transported into and executes from an internal
memory of the processor. The boot-loadable file is then programmed into
an external memory device (burned into EPROM) within your target system.
The loader utility outputs loadable files in formats readable by most
EPROM burners, such as Intel hex-32 and Motorola S formats. For
advanced usage, other file formats and boot modes are supported. (See
“File Formats” on page A-1.)
A non-bootable EPROM image file executes from an external memory of
the processor, bypassing the built-in boot mechanisms. Preparing a
non-bootable EPROM image is called splitting. In most cases (except for
Blackfin processors), developers working with floating- and fixed-point
processors use the splitter instead of the loader utility to produce a
non-bootable memory image file.
VisualDSP++ 4.5 Loader and Utilities Manual 1-9