> In a message dated 98-03-12 13:18:02 EST, you write:
>
> You certainly can do this on a PIC!  At the start of the interupt
> routine you
> simply check the INTCON reg to see what generated the interupt and
> jump
> accordingly.
> Well, you have to do this, regardless of whether it's in interrupt
> inside an interrupt or not. What I was trying to say was that it is
> this very fact that makes it hard to handle recursive interrupts on a
> pic. Example: Your in an isr routine, you get interrupted, and you
> vector to the same physical spot in the code you were already at. That
> can get snakey with a limited stack if your not careful. You may be
> able to do this on a pic be re-enabling the global interrupt bit. In
> my opinion theres always a better programming solution than doing
> recursive interrupts.
>
> Then Motorolla parts have different kinds of interupts, thus the
> different
> vectors.  One vector for an IRQ and another for the NMI another for
> SWI etc.
> It still won't tell you what device generated the interupt, You have
> to resort
> to polling the devices inside the interupt routine.
> The very fact that you vectored to a certain location (in a Motorola
> device) tells you what generated the interrupt.
>
> Dave Duley
>
>
> Brad Stevenson, CET
> The DPL Group - Telecom Techniques
> 506-635-1055 or 1-800-561-8880
> http://www.dpl.ca
>