[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

From: E. Weddington
Subject: Re: [avr-gcc-list] Problems porting from CodeVisionAVR to WinAVR
Date: Wed, 03 Nov 2004 16:00:24 -0700
User-agent: Mozilla Thunderbird 0.7.3 (Windows/20040803)

Curtis Maloney wrote:


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?


reply via email to

[Prev in Thread] Current Thread [Next in Thread]