Phillip wrote:
> My reasoning goes like this as I call getcUSART1 again and again if I
> don't allow the last getcUSART1 to finish before my next ISR happens
> eventually I'll over flow the stack and strange things will start to
> happen.

First, calling a C routine in the interrupt handler just to get a byte from
the UART sounds like bad idea.  Why not just do a normal interrupt driven
UART with FIFO, and drop the byte if the FIFO is full?

But the real issue is that your statement makes no sense.  If you are
calling the C GET routine from the ISR, then how can it be called
recursively since interrupts are off?  If you're calling it from outside the
ISR then how can it be called recursively at all?


******************************************************************
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