cancel
Showing results for 
Search instead for 
Did you mean: 

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

mchahn
Senior

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.

2 REPLIES 2
mchahn
Senior

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.

WilkoL
Senior

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.