Great, that is the info I was missing. Nick, it would be great if you could add that stuff about the masking to your writeup.
I don't really have a problem ... (which is to say, I haven't tried it yet ...)
Good deal. All Things Are In The Datasheet XD
Some details I would add:Other reasons to use interrupts: - to wake up from sleep mode (you mention it but not so prominently).- super agressive performance optimization, not checking loop conditions but using timer interrupts to terminate loops thus allowing to optimize the check condition out of the code into the hardware
The interrupt event queues will hold at most 1 event per eventsource
The ones that set a flag could be regarded as being queued, as the interrupt flag remains set until such time as the interrupt routine is entered, at which time the processor clears the flag. Of course, since there is only one flag, if the same interrupt condition occurs again before the first one is processed, it won't be serviced twice.