Peter Onion wrote :

> No.  There is nothing in the "main ISR"
> 
routine other than the context save.
> 
> Each module's isr checks the 
appropriate PIR
> bit and jumps to the next handler in the chain
> if 
there is nothing to do.

I guess that what it realy does, is to jump to
its own "end", and that the PIC then just
"falls through" to the next 
ISR, becuse they
happens to be stuffed together physicaly in
memory, 
right ?

And each handler doesn't realy knows about
the others, do they 
?

I see what you are doing (with the init codes also),
but I'm not 
sure that it's "safe"...

Another way (that also makes sure that all 
ISR code
is held together, would be to #include the modules
from the 
ISR-stub.

> ....really easy to use an device from my
> library of 
drivers.

Are you takling about *pre-assembled* library ?
(Either as .O 
files or as a .LIB) ?

It seems as pre-assembled code isn't used
very 
much with the PICs, mainly becuse you
miss all assembly time 
calculations and
conditional assembly that can make the
"library 
routines" realy flexible. Most seems
to keep theirs "code libs" as 
source code...

Jan-Erik.



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