Hi John
That all makes sense and explains the strange behavior I was seeing except
why one works high (by itself) but not the other one.
Telling my compiler my high was low and resetting the GIEH in the ISR sounds
tricky but doable but there is no reason for that kind of heroics here.

I think the moral of the story is to only put one of my ISRs as high
priority and move on with my life.

I'm not sure why when I tried to put the handle_chars_gps() high and the
handle_chars_cntrl() low it didn't work...no doubt I missed setting
something correctly.
I will fool around with it the morning because given my druthers the GPS
receiver is the more important of the two devices.

Thanks so much for the help John 


Phillip
Things should be as simple as possible but no simpler
 
 
 
Phillip Coiner
CTO, GPS Source, Inc.
 
 
Your source for quality GNSS Networking Solutions and Design Services, Now!

-----Original Message-----
From: piclist-bounces@mit.edu [mailto:piclist-bounces@mit.edu] On Behalf Of
John Temples
Sent: Monday, September 18, 2006 8:46 PM
To: Microcontroller discussion list - Public.
Subject: RE: FW: [PIC] Trouble getting my ISR high

On Mon, 18 Sep 2006, Phillip wrote:

> So what you are saying is that if I'm in a high priority interrupt and
> another one happens I'm toast????

If another interrupt flag becomes set while you're in the ISR, you
will not normally re-enter the ISR, because the PIC has cleared GIEH.
You would only re-enter if you had set GIEH in the ISR, which is not
something that is normally done.

--
John W. Temples, III
-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist

-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist