Weddington
-Original Message-
From:
avr-libc-dev-bounces+eric.weddington=atmel@nongnu.org
[mailto:avr-libc-dev-bounces+eric.weddington=atmel@nongnu.
org] On Behalf Of Frédéric Nadeau
Sent: Thursday, March 26, 2009 5:01 PM
To: avr-libc-dev@nongnu.org
Subject: Re: [avr-libc-dev
If you want a sneak preview of what it will look like, heads toward:
http://code.google.com/p/avr-drv/source/browse/trunk/avr_mod/
http://code.google.com/p/avr-drv/source/browse/trunk/avr_mod/iom128.h
it contains a modified copy of the include/avr directory of avr-libc
Some devices are
While I'm at it, should I remove all the
#define SIG_xxx _VECTOR(y)
since they are deprecated?
Ron: Consider it done. Since I don't need it for my project, I won't
update in there, but when I'll commit to avr-libc tree it will be
included. If you do need it, fell free to ask, I'll make a zip
/* External Interrupt Request 5 */
#define INT5_num 6
#define INT5_vect _VECTOR(6)
#define SIG_INTERRUPT5 _VECTOR(6)
Note that SIG_ and _vect are not always aligned. _vect
and
_num however are always aligned.
I posted my patch on bug report:
bug #25300: Additional i/o port names
If applyed againt avr-libc/HEAD it will include the vector and pin
description to most header.
Frédéric
On Thu, Mar 26, 2009 at 6:51 PM, Ron Kreymborg r...@jennaron.com.au wrote:
/* External Interrupt Request 5 */
Hi there,
I'm back from my business travel, so I can now commit my
modifications. One little concern remains:
- Should I add my name at top of headers in the copyright section?
- If yes: What is the encoding scheme used by AVR-libc dev
team(UTF-8, ISO-8859-1) since my name as a diacritic
-Original Message-
From:
avr-libc-dev-bounces+eweddington=cso.atmel@nongnu.org
[mailto:avr-libc-dev-bounces+eweddington=cso.atmel@nongnu.
org] On Behalf Of Frédéric Nadeau
Sent: Monday, March 16, 2009 10:40 AM
To: avr-libc-dev@nongnu.org
Subject: Re: [avr-libc-dev
Hi there,
Hopes everyone had a great weekend :)
Now to be more consistent with the way DDR, PORT, are define across
devices, here is a new sample block:
#define DDR_SCK DDRB
#define PORT_SCK PORTB
#define PIN_SCK PINB
#define SCK_IDX 7
In case we want to match the data sheet exactly, here what
Good news... I finished(or so I think) the modification to the script.
I have include two files. First is a XML generated by the first part of
the script. It use the AVR Studio XML file to do so. Second file is the
actual ioxxx.h to witch vector patch and pin definition patch have been
I don't want to push the discussion to an extreme, but looking around
a few AVR's datasheet, I notice the following:
In C code example, they often refer to defines that I'm currently
working on such as:
DDR_SCK
DDR_XCKx
etc.
Where as I decided arbitrary to named them
SCK_DDR
XCKx_DDR
etc.
I do
I'm looking at the two USB definition that are missing iousbxx2.h and
iousbxx6_7.h to add pin definition by hand. I'm stuck with the
following dilemma:
In data sheet for AT90USB646 as well as the one for AT90USB82, Clock
pin for the SPI module is name in the pin description section as SCLK
where
-Original Message-
From:
avr-libc-dev-bounces+eweddington=cso.atmel@nongnu.org
[mailto:avr-libc-dev-bounces+eweddington=cso.atmel@nongnu.
org] On Behalf Of Frédéric Nadeau
Sent: Friday, March 13, 2009 6:55 AM
To: avr-libc-dev@nongnu.org
Subject: Re: [avr-libc-dev] Nice
-Original Message-
From:
avr-libc-dev-bounces+eweddington=cso.atmel@nongnu.org
[mailto:avr-libc-dev-bounces+eweddington=cso.atmel@nongnu.
org] On Behalf Of Frédéric Nadeau
Sent: Thursday, March 12, 2009 1:32 PM
To: avr-libc-dev@nongnu.org
Subject: Re: [avr-libc-dev
[mailto:avr-libc-dev-bounces+eweddington=cso.atmel@nongnu.
org] On Behalf Of Frédéric Nadeau
Sent: Tuesday, March 10, 2009 7:02 AM
To: avr-libc-dev@nongnu.org
Subject: Re: [avr-libc-dev] Nice to have: XCK Definition
The XMLs I have come from AVR Studio 4.16 build 628.
I forgot to mention
-bounces+eweddington=cso.atmel@nongnu.org
[mailto:avr-libc-dev-bounces+eweddington=cso.atmel@nongnu.
org] On Behalf Of Frédéric Nadeau
Sent: Wednesday, March 11, 2009 11:53 AM
To: avr-libc-dev@nongnu.org
Subject: Re: [avr-libc-dev] Nice to have: XCK Definition
I do agree with you
2009/3/9 Frédéric Nadeau fred.nad...@gmail.com:
My suggestion is adding the following:
#define XCK_DDR DDRD
#define XCK_DDRx DDD4
May be better
#define XCK D,4
or even
#define XCK D,4,H
with dummy High active level symbol? This 'H' not needed for XCK or
MOSI or OC1A but needed for
My original plan was to have something like this:
#define INT0_DDR DDRB
#define INT0_PORT PORTB
#define INT0_PIN PINB
#define INT0_IDX 1
Witch let people use it in a more or less common way:
INT0_DDR |= _BV(INT0_IDX );
Vs. your idea:
#define INT0 B,1
I totally love the idea. I see only one
17 matches
Mail list logo
