When interrupt occurs, EIMSK,1 is set to zero disabling further INT1 interrupts. Interrupt routine loads T1 for 50ms debounce timeout and goes into infinite loop waiting for T1 timeout. It really doesn't matter. As I stated before, if I do an RETI as the first instruction in the interrupt routine, it doesn't return. The vectors are all standard assignments for a 168 with 16k flash. Stack appears to operate properly if INT0 and Timer1 interrupts function. It's a bugger. Have sent code to Atmel FAE to get his opinion. Might, maybe get it on Monday. Otherwise, more head-banging. Thanks Dennis ----- Original Message ----- From: "Peter Gargano" <peter@techedge.com.au> To: <AVR-Chat@yahoogroups.com> Sent: Saturday, August 20, 2005 11:17 PM Subject: Re: [AVR-Chat] mega 168 > Dennis wrote: >> Nebulous question. If all other interrupt vectors work OK why not this >> one? > > Continue to assume the hardware works! Either the vector you think > you're using is wrong, or you do something bad in the correct ISR and > it never returns, or maybe you blow the stack with repeated int calls. > Surely a bit of diag code can work out what's happening? > > Do you know your INT1 ISR gets entered, and via the correct vector? > > INT1 is entered how many times per keypress? (hardware has a knack of > bouncing and producing multiple ints. > > .. > > > Peter. > > > > > > Yahoo! Groups Links > > > > > > >
Message
Re: [AVR-Chat] mega 168
2005-08-21 by Dennis
Attachments
- No local attachments were found for this message.