Re: [avr-gcc-list] Looking for a spurious interrupt

[Bjarne Laursen]

Trevor White wrote:

> When you say you have a spurious interrupt. I take it you have all the 
> interrupts enabled for everything? Are you able to turn everything off 
> and then start turning interrupts on one by one...

When the interrupt is enabled shouldnt there be a specialised handler 
for it?

If you make your interrupt handler naked, you should be able to get down 
to 2 instructions for each interrupt.
- set some unused i/o bit
- jump to the default handler

> Another thought is could you use a register to identify what routine 
> you were running when the interrupt occurs. For example

You should  be able to get the return adress from the stack, it will 
indicate were the interrupt occured.