Implementing a simple INT from stat to finish

[mpgmike]

Maybe the whole book concept needs redefined. Initially it was to be a depository, with filters, and with commentary, of DT's greatest contributions. Under that auspice we are doing exactly what we set out to do. What is being proposed now is an excellent idea, but not what we initially agreed to achieve.

Here is the trade-off; there is much work in making a book out of several forum posts. If that is our goal (initially stated as the intent), it would be up to the reader to filter through everything, read through the references, and do his/her homework. Assembling a "process" in the form of a book that starts the reader at ground zero and walks him/her through step-by-step progressions is a totally different approach.

A compromise might be an Example section with limited examples that may be copy/pasted with minor modifications. In my opinion, Daryl did lots of that with what has already been committed to the Book.

Just how far do we want to take this?

[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.