Implementing a simple INT from stat to finish

[MOUNTAIN747]

Mike, you are absolutely right. I proposed the repository to begin with and now I am considering altering the plan. My bad. I found myself digging in a great number of post's on some particular INT that made the whole process seem more and more complex. I realized the majority of our forum members and guest, and that especially includes me, could not implement some of these INT's without a mouth of research and investigation. It would be nice if every INT had a good example but that doesn't seem possible as I can't find an example of many INT's. I'm sure that at some point Darrel just started going through the datasheets and wrote the INT with no intention of using it but to make it available for others to use if needed. I think at some point a step-by-step project example needs to be done. However, it should not be a part of Darrel's BOOK.

[tumbleweed]

It would be nice if every INT had a good example but that doesn't seem possible as I can't find an example of many INT's

The mechanics of interrupts are basically the same for all of them, with a few minor exceptions..

It sounds like you're talking more about how to use all of the various peripherals. That's a tall order.
My suggestion is to keep in mind that for most applications interrupts aren't worth the bother... they just
complicate things and make your code larger and slower.

Keep interrupts for what they're most useful for... things that must happen at a defined interval (ie a timer), scanning a display, or USART receive. Triggering an ADC to read and then waiting for an interrupt to read the data is likely a waste of time and energy.