Phillip wrote:
> Below is the code of my timer/button ISR routine below.
> Look at the first line.

No.  I don't do C ISRs, and as I said, I think they're silly.

Don't you need to mutter some magic incantation though to make the compiler
understand that this particular subroutine is meant to be a ISR?  (No, I
don't care about the answer, but it's something you might want to look
into.)

> So I don't believe you when you say that the hardware disables
> interrupts during an ISR event.....

Then why are you asking me for help if you don't believe what I say anyway,
especially when it is something directly stated in the data sheet?

For the record, I said that the hardware disables interrupts on entry to the
ISR, not "during an ISR event", whatever that means.

> I think my problem was that my serial ISR was reading the char and
> clearing the interrupt before control was transferred again by the
> hardware...

But...  Oh never mind.  What's the point.

> at least most times as long as the characters arrived slowly
> enough when I started sending characters relentlessly eventually the
> ISR fell behind and before it could read the last char the hardware
> tried to transfer control to the ISR or some nonsense....as you can see
> I'm much clearer on what fixed it than what was going wrong....

No, you don't have a clue.  You accidentally found something that made the
symptom appear to go away.  Clearly you have very little understanding of
what is actually going on.


******************************************************************
Embed Inc, Littleton Massachusetts, (978) 742-9014.  #1 PIC
consultant in 2004 program year.  http://www.embedinc.com/products
-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist