avr-libc-dev
[Top][All Lists]
Advanced

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

RE: [avr-libc-dev] Adding (some) Procyon AVRlibfunctionalitytoavr-libc


From: Weddington, Eric
Subject: RE: [avr-libc-dev] Adding (some) Procyon AVRlibfunctionalitytoavr-libc
Date: Sat, 19 Sep 2009 09:47:53 -0600

 

> -----Original Message-----
> From: 
> address@hidden 
> [mailto:address@hidden
> org] On Behalf Of Mike Perks
> Sent: Saturday, September 19, 2009 9:42 AM
> To: address@hidden
> Subject: Re: [avr-libc-dev] Adding (some) Procyon 
> AVRlibfunctionalitytoavr-libc

> I think one of the areas that is going to cause a lot of work is the 
> different definitions of I/O pins, ports and flags between different 
> processors. I wish Atmel would make things more consistent 
> whenever they 
> come out with a new device. Things aren't even consistent within a 
> particular device family with the possible exception of 
> xmegas. 

Unfortunately, this is just a hisorical problem that we have to live with. Yes, 
Atmel has improved its consistency on newer device families such as xmega and 
the UC3 for the AVR32. However, this doesn't help us with past device releases. 
:-( We just have to accept this fact and move on the best we can.

> For my 
> projects I end up defining some common names and then #defining the 
> particular device configuration to those defines. It would be 
> great if 
> we could do something this automagically from the XML files.

Would you be willing to describe in more detail about what you do to solve this 
problem? I think it would be good if we heard from others' experience. 




reply via email to

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