Running out of interrupt events

If you're working with interrupts, you might see an Out of Interrupt Events error. This happens when the system is no longer able to run user code and is stuck in the kernel, most frequently because:

• The interrupt load is too high for the CPU (it's spending all of the time handling the interrupt).

  Or:

• There's an interrupt handler — one connected with InterruptAttach(), not InterruptAttachEvent() — that doesn't properly clear the interrupt condition from the device (leading to the case above).

If you call InterruptAttach() in your code, look at the handler code first and make sure you're properly clearing the interrupt condition from the device before returning to the OS.

If you encounter this problem, even with all hardware interrupts disabled, it could be caused by misuse or excessive use of software timers.