Debugging unhandled interrupts

Go To Last Post
3 posts / 0 new
Author
Message
#1
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Is there a good way to identify which interrupt is occurring that is not being handled? I'm using Atmel Studio 6.2 with a AT32UC3C part.

Walt

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Have a separate handler for each interrupt :?:

Top Tips:

  1. How to properly post source code - see: https://www.avrfreaks.net/comment... - also how to properly include images/pictures
  2. "Garbage" characters on a serial terminal are (almost?) invariably due to wrong baud rate - see: https://learn.sparkfun.com/tutorials/serial-communication
  3. Wrong baud rate is usually due to not running at the speed you thought; check by blinking a LED to see if you get the speed you expected
  4. Difference between a crystal, and a crystal oscillatorhttps://www.avrfreaks.net/comment...
  5. When your question is resolved, mark the solution: https://www.avrfreaks.net/comment...
  6. Beginner's "Getting Started" tips: https://www.avrfreaks.net/comment...
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Are you using the ASF INTC interrupt handler ?
It sends unhandled interrupts to a common routine _unhandled_interrupt() that then stall there.
If you have a debugger you could examine the INTC IRRx registers to find the pending interrupt group and line and then refer to the Interrupt Request Signal Map diagram to find the actual device.

It will probably be easier to just go through the source code and find where interrupts are being enabled.