Analog Devices ADSP2192-12 EZ-KIT LITE, Руководство пользователя

Страница: 23 / 50

ADSP2192-12 EZ-KIT Lite Evaluation System Manual
3-12
The two interrupts used by the monitor are:
•
Kernel interrupt (bit 2 in IMASK)
•
Mailbox interrupt (bit 4 in IMASK)
The memory ranges used by the monitor are:
•
0x7800 - 0x7FFF (16-bit Data Memory)
•
0x10008 - 0x1000B (kernel interrupt vector)
•
0x10010 - 0x10013 (mailbox interrupt vector)
•
•
0x13A00 - 0x13FFF (24-bit Program Memory)
The debugger will catch any user attempt to overwrite the reserved regions of memory should a write
be attempted with a debugger command such as a load or fill. It cannot stop user code from
overwriting these regions.
After a program is loaded, the interrupt vectors used by the monitor are automatically filled so you
need not include these vectors in their source code.
3.2.1.2 Restrictions
Observe the following restrictions to ensure proper operation of the monitor:
•
Only one ADSP2192-12 EZ-KIT Lite may be plugged into the PC at one time. Plugging in
more than one EZ-KIT Lite at one time may cause unpredictable behavior.
•
Do not press the reset button on the EZ-KIT Lite with the debugger open. See the section
below for more information on hard reset. Pressing this button will reset the DSP and cause it
to lose communication with the PCI interface on the PC. You can reset each core through the
Reset command in the Debugger if necessary. This will reset the core without resetting the
PCI configuration of the DSP.
•
Disabling global interrupts will cause Vi+ to lose all communication with the
monitor. Executing the "
DIS INT; " instruction will disable global interrupts on the core. If
user code executes this instruction while running, it must enable global interrupts with the
"
ENA INT; " instruction in order for Vi+ to regain communication. Do not use code
to disable global interrupts.
•
Disabling the kernel interrupt will cause Vi+ to lose communication with the
monitor. Clearing bit 2 in the IMASK register will disable this interrupt. While disabled, you
will not be able to single-step or use software breakpoints. Do not use code to disable kernel
interrupts.
• •
Disabling the mailbox interrupt will cause Vi+ to lose communication with the
monitor. Clearing bit 4 in the IMASK register will disable this interrupt. While disabled, you
cannot halt the core. Do not use code to disable mailbox interrupts.
•
Disabling interrupt nesting will cause Vi+ to lose communication with the monitor if
the user code uses interrupts. Clearing bit 4 in the ICNTL register will disable interrupt
nesting.
•
Do not use code to disable nesting if you intend to use interrupts in your code.
•
Do not push more than 30 values onto the PC stack. This stack is used for temporary storage
upon entering the monitor. It is highly unlikely that user code will ever need more than 30
stack locations. Pay close attention when debugging C programs as the PC stack may grow
without your knowledge due to function calls and library routines.
www.BDTIC.com/ADI