RE: [Avr-libc-corelib] Mappings from pins to capabilities?

[Weddington, Eric]

Hi David,

[Please subscribe to the list, so your posts don't have to be moderated.]

There have been a bunch of good ideas, and this is also one of them.

But ideas have to be implemented by someone, and we are always in need of good 
volunteers to help in this area. Do you have the time and the skills to be able 
to devote to implementing your idea?

Eric Weddington

> -----Original Message-----
> From: 
> address@hidden 
> [mailto:address@hidden
> gnu.org] On Behalf Of David A. Mellis
> Sent: Tuesday, August 03, 2010 8:18 AM
> To: address@hidden
> Subject: [Avr-libc-corelib] Mappings from pins to capabilities?
> 
> Hi,
> 
> I'm the lead software developer for Arduino, an ATmega8, 168, 328, and
> 1280 based development platform.  One of the issues we struggle with
> is mapping, across multiple cpu's, the port / bit of a pin to the
> other capabilities of the pin (i.e. the labels in the pin
> configurations section of the datasheet) - for example, in order to
> write a function to both set a pin as an output and enable PWM on that
> pin.  Right now, that requires maintaining a mapping between, say, PG5
> and 0C0B.  This seems like it would be a great thing to include in the
> corelib in some form.  The ideal would be a way to go in both
> directions.  One possibility is to define this as a series of macros,
> which could run at compile-time if the parameters are known.  But
> really, any implementation would be fine.  I know there are a lot of
> complications in doing this across the whole AVR line, but that's one
> of the reasons that it seems to make sense in the corelib: it would be
> a chance to resolve all the tricky issues once in a way that other
> developers could take advantage of.  Certainly, it would be a big help
> for Arduino.
> 
> What do you think?
> 
> David
> 
>