AVR-Chat

Changed vector names from ZCINT0 to EXT_INT0 and PBINT1 to EXT_INT1 per the 
168 data manual. Still the same results. More head banging.
D
----- Original Message ----- 
From: "Mark Nowell" <mark@dicam.co.uk>
To: <AVR-Chat@yahoogroups.com>
Sent: Sunday, August 21, 2005 1:39 AM
Subject: Re: [AVR-Chat] mega 168


> Dennis
>
> FWIW I'm using both INT0 and INT1 on M168 with no problems ... now. I did
> spend several hours banging my head against these interrupts because a) 
> I'd
> used the wrong vector names; b) more than one of the bit defs in the
> avr-libc headers were wrong. The latest WinAVR appears to correct the bit
> defs but it sounds as though you're using asm anyway?
>
> Mark
>
> ----- Original Message ----- 
> From: "Dennis" <dkazar@sbcglobal.net>
> To: <AVR-Chat@yahoogroups.com>
> Sent: Sunday, August 21, 2005 5:31 AM
> Subject: Re: [AVR-Chat] mega 168
>
>
>> 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
>
>
>
>
>
> Yahoo! Groups Links
>
>
>
>
>
>
>