Re: [avr-libc-dev] Nice to have: XCK Definition

[Frédéric Nadeau]

Hi

Does anyone know of a better source for part description that the xml
provided with AVR Studio?

As far as I can tell, they are:
- Inconsistent: In <PACKAGE> some use a string <NAME> and others use a
combination of  <PIN_NAME> and <ALT_NAME> to describe all posible pin
name.
- Incomplete: AT90USB82 does not have <PACKAGE> information, many
others also miss package information, thus making impossible to guess
pin names.
- Miss formatted: for ATmega1280, line 550 PB5 is written as "[PB5",
missing the "]" as an example, found 5 error in that file with an "eye
survey".

I was thinking about writing a program to parse the xml entry and add
them to the .h and then do a manual cleaning(like combining entry in
iom1280.h and iomxx0_1.h)

So if you know of any better source(Data sheet of course, a little
harder to atomise though), please let me know

Frédéric




On Mon, Mar 9, 2009 at 3:18 PM, Weddington, Eric
<address@hidden> wrote:
>
>
>> -----Original Message-----
>> From:
>> address@hidden
>> [mailto:address@hidden
>> org] On Behalf Of Frédéric Nadeau
>> Sent: Monday, March 09, 2009 1:12 PM
>> To: address@hidden
>> Subject: [avr-libc-dev] Nice to have: XCK Definition
>>
>> Hi there,
>>
>> For what I can tell, the pin XCK is not define for, at least, ATmega8
>> and 16. This pin definition would facilitate portage of code between
>> ATmega8 and 16 since XCK is not on the same pin for both device(PD4
>> for one and PD0 for the other).
>>
>> My suggestion is adding the following:
>>
>> #define XCK_DDR DDRD
>> #define XCK_DDRx DDD4
>>
> Hi Frédéric
>
> AFAIK, we haven't discussed yet whether we should add *pin* descriptions to 
> the I/O header files. This would be a big task because it has to be done on 
> all of the header files, and for all the various pin names, for it to be 
> useful. And it would have to be automated in the future.
>
> At this point, you'll just have to define those yourself for your project. 
> Unless you're willing to provide a patch to implement it as described above.
>
> Eric
>