Adsp-2192 Dsp Rtbl - Analog Devices VisualDSP++ 3.5 Manual

ADSP-2192 DSP Booting
Once the bus configurations have been determined (assuming that a serial
EEPROM exists), the boot kernel calls a function to commence reading
data from the serial EEPROM. Data format of serial EEPROM boot
stream is described in the
Once the kernel has finished reading data from the serial EEPROM, it
proceeds to set up and commit bus configurations for the rest of booting
via the PCI or USB interfaces. For PCI, the configuration registers are set
to be read-only, and the DSP is to respond to PCI requests from the sys-
tem host. For USB, the DSP is to enter an idle loop, allowing the system
host to detect and configure the part.
The final task performed by the kernel after configuring the bus and trans-
ferring control to PCI or USB is to enter an infinite loop, waiting for
instructions. A predefined memory address, DM
checked for commands. Once the PCI or USB device has completed boot-
ing the DSP, they can write an instruction to this predefined location and
have the DSP execute any of supported commands.
!
Refer to the datasheet, ADSP-219x/2192 DSP Hardware Reference
and Application Note EE-124 for further details.

ADSP-2192 DSP RTBL

The VisualDSP++ linker produces files with
sions. Typically, these file are not shipped with your applications. Instead,
the linker's output is run through the loader that repackages the linker
output as an
.H
Figure 4-1. The RTBL output file (
or USB).
Given that booting from PCI or USB involves code running on the PC
host, you must create a program, which executes on the host, to initiate
and conduct the actual PCI or USB transfer. Because of this, the loader
4-4
"ADSP-2192 DSP RTBL" on page
file, which is consumed by an RTBL, as illustrated in
0x000000
,
.DXE .OVL
) is used by a bootable device (PCI
.EXE
VisualDSP++ Loader Manual
4-4.
, is regularly
, and exten-
.SM
for 16-Bit Processors