On Mon, May 3, 2010 at 7:53 AM, Josh Koffman wrote: > I think I need to look at my Interrupt initialization again. > Unfortunately I won't have time until tonight. Dang! Well, I've made some progress. I made a bit of a mistake in my interrupt initialization. That was bad. I've fixed that and it seems to be working closer to what I expected it to. This brings up a few questions that I've been thinking about in regards to interrupt service routines. These are all based on code I've seen other people write. 1. Is it necessary to do go back and poll all the possible interrupt flags after servicing one of them? I always figured if I had an overlapping interrupt that I'd jump right back into the ISR so there wasn't much point in rechecking everything. 2. Do most people check the interrupt enable before checking the flag to determine the source of the interrupt? I've only really seen one person do this consistently, and it was because they were changing the status (enabling and disabling) a few of the interrupts over the course of the program. In my problem above, had I been doing this I would have seen that the cause of my entering the ISR was not what I had thought it was. Thanks everyone for the help! Josh -- A common mistake that people make when trying to design something completely foolproof is to underestimate the ingenuity of complete fools. -Douglas Adams -- http://www.piclist.com PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist