Hi John
This makes sense to me/was my interpretation of that section.  
 
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: Thursday, June 29, 2006 6:16 PM
To: Microcontroller discussion list - Public.
Subject: Re: [PIC] C18 resource remaining metric/test

On Thu, 29 Jun 2006, Gerhard Fiedler wrote:

> Phillip wrote:
>
>> But I did not want to nest my low priority interupts (at least I don't
>> think I do)
>
> The whole point of using two interrupt priorities is nesting them. If you
> don't want the high prio ints interrupting the low prio ints, there's not
> really a point in having high and low prio ints.

The section in the C18 manual entitled "Nesting Interrupts" refers to
re-entrant nesting of interrupts of the same priority level, not
interrupting of low priority interrupts by high priority interrupts.
I.e., you can nest low priority interrupts since their context is
saved on the software stack, but you can't nest high priority
interrupts since they use the fast register stack.

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