56303 | 563xx | 5680 | 56805 | 5680x | 56F80 | 56F800DEMO | 56F805 | 56f807 | 56F830 | ADC | Bootloader | Codec | CodeWarrior | CW5 | CW6 | Debugger | DSP56303 | DSP56303EVM | DSP563xx | DSP5680 | DSP56800 | DSP56807 | DSP56858 | DSP56858EVM | DSP56F803 | DSP56F805 | DSP56F807 | DSP56F80x | DSP56F826 | DSP56F827 | DSP56F8xx | EVM | FFT | Flash_over_jtag | GPIO | Interrupt | Interrupts | JTAG | LCD | Linker | MCF5307 | Metrowerks | Modulus | MSCAN | PCMaster | PWM | Quad | Rif | RTOS | SDK | SPI

** Help with Interrupts ** Exercise 3c has been created. It is available on the 56800 FAQs. In the future it will be included in the next version of the Training CD. For now, log on to http://e-www.motorola.com/cgi-bin/faq.cgi? kbase=dsp&prod_default=56800 and search using the keywords "Exercise 3c". Abstract: In Exercise 3c we will discuss the details of how SDK supports interrupts. You will learn how to determine the configuration of ISRs in your project's interrupt vector table as well as how to debug interrupt service routines (ISRs). Problem: The Embedded SDK does not implement the interrupt vector table as a table, but rather uses #define tokens in the appconfig.h. Is there a way to build a table of the interrupt service routines (ISRs) installed in a project? What about the priority level used for each ISR? I am getting unhandled interrupts while debugging my code. Is there a way of determining which interrupts are firing?

(You need to be a member of motoroladsp -- send a blank email to motoroladsp-subscribe@yahoogroups.com )