avr-chat
[Top][All Lists]
Advanced

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

[avr-chat] Expanding the ATxmega support in the toolchain


From: Erik Walthinsen
Subject: [avr-chat] Expanding the ATxmega support in the toolchain
Date: Sun, 22 Nov 2009 16:50:39 -0800
User-agent: Thunderbird 2.0.0.23 (X11/20090817)

I've got boards ready to populate for a [paid] prototyping project that
are going to be getting ATxmega16a4's (for lack of anybody selling
64a4's...).  The problem is, even the WinAVR patches don't seem to show
any support for anything other than the 64a1 and 128a1.

I'm going to be adding support for the 16a4, and probably every other
chip actually nominally available at this point, and submitting the
patches soon (since this is the next roadblock for me to blast through
on this contract).

However, I'm *royally* confused by the presence of the avrxmega2-7
"architectures".  There seems to be no correlation between the arch
number and the chip it's supposed to represent, as per the table at
http://www.nongnu.org/avr-libc/user-manual/using_tools.html  Further,
the table refers to a number of chips that don't even exist (the D* series).

>From my understanding of both Atmel's very clearly stated goal, and a
lot of time reading the datasheets, there should be *1* "architecture"
for all the existing chips, that would be the atxmegaA.  The only other
that might make sense could be a <=64KB variant.

Anyone able to shed light on what's up with these architectures and
whether they actually mean anything, or would it make sense to collapse
them down as part of adding full support to all the current chips?

TIA,
   Omega
   aka Erik Walthinsen
   address@hidden




reply via email to

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