[Top][All Lists]

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

[avr-gcc-list] avr-gcc/avr-binutils/avr-libc and the ATMega168 - what a

From: Victoria Welch
Subject: [avr-gcc-list] avr-gcc/avr-binutils/avr-libc and the ATMega168 - what am I doing wrong, tnx!
Date: Fri, 28 Jan 2005 15:38:33 -0800
User-agent: KMail/1.7.2

Hello Ned and Eric,

Thank you VERY much for the reply!

On Friday 28 January 2005 08:13, Ned Konz wrote:
> On Thursday 27 January 2005 7:58 pm, Victoria Welch wrote:
> > Somehow I had the impression that this would add some
> > of the newer devices, especially for me, the ATMega168.
> > Apparently not or there is something I am missing.
> Fixes for GCC 4.0 were posted in November, as I recall.
> http://www.avr1.org/pipermail/avr-gcc-list/2004-November/
> You could probably apply them to the GCC 3.4 and rebuild.
> Have you tried getting the CVS HEAD or recent snapshot of
> gcc 4.0 and compiling it for the avr target to see?
> You can get a gcc 4.0 snapshot from:
> ftp://gcc.gnu.org/pub/gcc/snapshots/4.0-20050123

Got this and hacked it into an ebuild which seems to work, 
but it is acting odd, not sure if this is the result of not 
having the right version of avr-binutils or not.  I am VERY 
lost and will show why below.

> There is a 1.2.1 version (a bug fix release of 1.2.0) of
> avr-libc available from
> http://savannah.nongnu.org/download/avr-libc/

Fixed up an ebuild for that and emerged it, thanks!

Now as to the confusion.

atmega168 still fails as not valid, however:

{~/projects/wrl/kbc2313} $ avr-gcc --version
avr-gcc (GCC) 4.0.0 20050123 (experimental)

In my makefile:

FLAGS= -g -Os -mmcu=atmega168 -Wall

which results in:

[ ... ]
Known MCU names:
  avr1 avr2 avr3 avr4 avr5 at90s1200 attiny10 attiny11 
attiny12 attiny15
  attiny28 at90s2313 at90s2323 at90s2333 at90s2343 attiny22 
  at90s4433 at90s4414 at90s4434 at90s8515 at90s8535 
at90c8534 at86rf401
  atmega603 atmega103 at43usb320 at43usb355 at76c711 atmega8 
  atmega85 atmega8515 atmega8535 atmega16 atmega161 
atmega162 atmega163
  atmega169 atmega32 atmega323 atmega64 atmega128 at94k
Assembler messages:
Fatal error: unknown MCU: atmega168
[ ... ]

However, if I change the FLAGS line in the makefile to (I 
saw this somewhere):

CFLAGS= -g -Os -mmcu=atmegan68 -Wall

I get:

unknown MCU `atmegan68' specified
Known MCU names:
[ ... ]
[ ... ]

As for the patches at:


I have no idea if these are relevant at this point.

Thoughts or suggestions appreciated!

Just for reference this is the current state of things:

*  dev-embedded/avr-binutils
      Latest version available: 2.15
      Latest version installed: 2.15
      Size of downloaded files: 11,245 kB
      Homepage:    http://sources.redhat.com/binutils
      Description: The GNU binutils for the AVR 
microcontroller architecture
      License:     GPL-2

*  dev-embedded/avr-gcc
      Latest version available: 4.0-r1
      Latest version installed: 4.0-r1
      Size of downloaded files: 27,802 kB
      Homepage:    http://www.avrfreaks.net/AVRGCC
      Description: The GNU C compiler for the AVR 
microcontroller architecture
      License:     GPL-2

Please Note:  this is:

{~/projects/wrl/kbc2313} $ avr-gcc --version
avr-gcc (GCC) 4.0.0 20050123 (experimental)

Just the way I had to name it to make the ebuild maker 
happy :).

*  dev-embedded/avr-libc
      Latest version available: 1.2.1
      Latest version installed: 1.2.1
      Size of downloaded files: 311 kB
      Homepage:    http:////www.nongnu.org/avr-libc/
      Description: Libc for the AVR microcontroller 
      License:     GPL-2

Thanks very *VERY* much & take care, V.
Victoria Welch, WV9K/7.  "Engineering is the art of making 
what you want from things you can get."-  Jerry Avins
"Learning about the U.S. from the mainstream media is like 
learning about plumbing by sitting in a cesspool."  -- 
Michael Phelps

reply via email to

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