Skip to main content
Explorer
February 6, 2022
Question

How do I find out what IRQ triggered a debug breakpoint at NonHandledInterrupt?

  • February 6, 2022
  • 2 replies
  • 1276 views

I cannot get interrupts to work and I found that NonHandledInterrupt is getting called. How do I find out what IRQ triggered a debug breakpoint at NonHandledInterrupt? I've stared at my code for hours and all it does is stare back.

    This topic has been closed for replies.

    2 replies

    mchahnAuthor
    Explorer
    February 7, 2022

    I figured out one way to do it. I made a number of routines: NonHandledInterrupt1, NonHandledInterrupt2, NonHandledInterrupt3, etc. for sections of interrupt vectors. I was able to identify the guilty interrupt. It would be nice if there was an easier way but there probably isn't.

    Visitor II
    February 10, 2022

    NonHandledInterrupt  means that you enabled some interrupt (timer, uart...) but do not have the corresponding code to handle that interrupt. Just disable one interrupt in your code at a time and you'll see when the NonHandledInterrupts disappear.