Re: [avr-gcc-list] Problems porting from CodeVisionAVR to WinAVR

[E. Weddington]

Curtis Maloney wrote:

> Greetings,
>
>     We've recently decided to migrate all of our AVR development to 
> avr-gcc, for various reasons.
>
>     We figured as a good exercise we'd port some existing, working 
> code from cvavr.  And weren't there some differences.
>
>     No longer the handy notation of PORTx.y for accessing port pins, 

Yeah, there's been some talk about adding that capability into avr-libc 
as an alternative method of setting/clearing port pins. No work has come 
of it that I know of.

> and declaring interrupts is a little different, but in general the 
> changes have been  simple and minor.

And *that's* due to the C Standard: they don't define a standard way to 
declare interrupts. Everybody does them differently.


>     However, this has not yet resulted in success.  For some reason, 
> whenever we enable the Timer 0 Overflow interrupt, the setup resets.  
> Not immediately, of course, but after the timer expires.
1. What device are you using?
2. How are you declaring the interrupt?

Eric