[Top][All Lists]

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

RE: [avr-gcc-list] xmega support

From: larry barello
Subject: RE: [avr-gcc-list] xmega support
Date: Tue, 6 Jan 2009 22:37:15 -0800

Thanks for the response.  I dug a bit further into the manual and I see that
EEPROM can be mapped to SRAM space eliminating the need for library EEPROM
support in GCC. 

Ironically, since writing AvrX I have not really used it for anything.  I
have no plans to upgrade AvrX for the bigger chips.  A lot of other people
use it and I suppose someone will eventually add things like RampZ, etc. to
the task state and a third word to the call & return stack.


-----Original Message-----
From: Weddington, Eric [mailto:address@hidden 
Sent: Tuesday, January 06, 2009 5:40 PM
To: larry barello; AVR GCC List
Subject: RE: [avr-gcc-list] xmega support


> -----Original Message-----
> From: 
> address@hidden 
> [mailto:address@hidden
> org] On Behalf Of larry barello
> Sent: Tuesday, January 06, 2009 5:33 PM
> To: AVR GCC List
> Subject: [avr-gcc-list] xmega support
> I am trying to bring a project developed on a mega128  up on 
> an xmega128A1.
> Aside from the very different I/O structure (which is 
> actually pretty nice)
> the non-volatile memory stuff is totally different.
> Is there some libc support for reading/writing the EEPROM?  How about
> self-programming support (aka boot-loader)? Or do I have to 
> roll my own?
> Hmm, a search through the 1205 release for 
> "__AVR_ATxmega128a1__" shows only
> the following files having knowledge of the chip:
> Power.h
> Sleep.h
> Wdt.h
> And
> Io.h
> of course.
> I suppose the real question is: what level of support does 
> Libc have for
> these new chips?  

Unfortunately that is it at the moment. Yes, we would certainly like to add
more support for the xmega series in avr-libc. User feedback is particularly
welcomed, whether it is patches, or suggestions for APIs. Tell us what you
would like to see!

Are you thinking about porting AVRX to the xmega?


reply via email to

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