That, and I'd strongly advise a fleshed out interrupt vector table. They can all be RETIs, or they can be a short bit of code that turns off that interrupt (what I use for all unimplemented ISRs) or a "halt and catch fire", but I would never do what you did there. Imagine the total wierdness if another int is accidentally enabled, and the ISR fires, jumping somewhere into the middle of your code... ICK. [Non-text portions of this message have been removed]
Message
Re: [AVR-Chat] Basic interrupts on ATtiny26
2007-02-17 by David VanHorn