I'm trying to deal with a weird issue where a CAN interrupt is only being triggered after I suspend a debug session.
For instance, I have a break-point at "CAN0_ORed_0_15_MB_IRQHandler()" which is the first function called from the interrupt vector.
Starting the code, I have the following, showing now CAN interrupts have been flagged:
Then, I let the board run, and send a CAN message (verified that this occurs)... and nothing happens. When I suspend the debug session, the register shows there is a CAN interrupt:
After I resume the debug session, I suddenly hit my break-point!!
Why on earth would this happen *only* after pausing a debug session?
Solved! Go to Solution.
Kinda dumb, but still interesting - this happened because interrupts were disabled globally but not re-enabled.
Kinda dumb, but still interesting - this happened because interrupts were disabled globally but not re-enabled.