[Top][All Lists]

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

RE: [avr-gcc-list] just 2 bytes allocated for uint32_t?

From: Weddington, Eric
Subject: RE: [avr-gcc-list] just 2 bytes allocated for uint32_t?
Date: Sat, 28 Feb 2009 12:09:08 -0700


> -----Original Message-----
> From: 
> address@hidden 
> [mailto:address@hidden
> org] On Behalf Of Radoslav Kolev
> Sent: Saturday, February 28, 2009 11:55 AM
> To: address@hidden
> Subject: [avr-gcc-list] just 2 bytes allocated for uint32_t?
> On Sat, Feb 28, 2009 at 8:09 PM, Weddington, Eric
> <address@hidden> wrote:
> > Are you including <stdint.h> or <inttypes.h>?
> Yes, <inttypes.h> is included. I'm attaching the complete .c file.
> > And please stop using inb() and outb(). They have been 
> removed from avr-libc and are not necessary. Just use a 
> regular assignment.
> I know. I didn't write this file, it's from the Arduino
> (http://arduino.cc) platform that's getting pretty popular lately. It
> hasn't been touched for some time as I can see from the svn logs. I
> just wanted to recompile it to run on a lower frequency crystal.
> I noticed now, that there is even a warning displayed at compile time:
> ATmegaBOOT.c:470: warning: comparison is always false due to limited
> range of data type

- Change <avr/delay.h> to <util/delay.h>
- define BAUD_RATE somewhere
- define F_CPU somewhere (like on the command line below)

Used this command line:
avr-gcc -Os -mmcu=atmega8 -c ATmegaBOOT.c -DF_CPU=8000000UL -o ATmegaBOOT.o

No warnings, no errors.

Using avr-gcc 4.3.2.

reply via email to

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