Lpc2000

On a project I'm working on I have several interrupt service routines.
 All of them work fine except for one of them that is on the external
interrupt 0.  The ISR will be sucessfully called once and the system
hangs upon exiting the ISR.  I have defined a default ISR to see if
spurious interrupts were a problem, and the default ISR never gets
called, so all seems well there.  Any sugestions as to what might be
the problem?

Thanks, 
Reggie McMurtrey

On Monday 15 August 2005 11:52, Nice Guy wrote:
> On a project I'm working on I have several interrupt service routines.
>  All of them work fine except for one of them that is on the external
> interrupt 0.  The ISR will be sucessfully called once and the system
> hangs upon exiting the ISR.  I have defined a default ISR to see if
> spurious interrupts were a problem, and the default ISR never gets
> called, so all seems well there.  Any sugestions as to what might be
> the problem?
>

Two things I can think of:

1) Your interrupt wrapper code is not acknowledging the interrupt properly, or 
perhaps not in the right order.
2) You're using level instead of edge interrupt detection. Make sure you're 
setting this up right.

can I set a breakpoint inside an ISR and use the jtag to see where the
PC is going to upon exciting the ISR?

Thanks,
Reggie

--- In lpc2000@yahoogroups.com, Charles Manning <manningc2@a...> wrote:
> On Monday 15 August 2005 11:52, Nice Guy wrote:
> > On a project I'm working on I have several interrupt service routines.
> >  All of them work fine except for one of them that is on the external
> > interrupt 0.  The ISR will be sucessfully called once and the system
> > hangs upon exiting the ISR.  I have defined a default ISR to see if
> > spurious interrupts were a problem, and the default ISR never gets
> > called, so all seems well there.  Any sugestions as to what might be
> > the problem?
> >
> 
> Two things I can think of:
> 
> 1) Your interrupt wrapper code is not acknowledging the interrupt
properly, or 
> perhaps not in the right order.
> 2) You're using level instead of edge interrupt detection. Make sure
you're 
> setting this up right.