Add ATMega328 to avrdude.conf (in addition to ATmega328P)

[GoogleCodeExporter]

What change would like to see?
Add native support for the non-Pico Power version of the ATMega328.

Why?
Many users not concerned with power consumption would like to use the 
ATMega328.  The chip is cheaper and readily available.  In order to use the 
chip the AVRDude configuration file must be changes so it believes the 
ATMega328 is actually a ATMega328p.  This not apparent and should not be 
necessary.

Would this cause any incompatibilities with previous versions?  No.
If so, how can these be mitigated?

Original issue reported on code.google.com by Randall....@gmail.com on 29 May 2012 at 6:22

[GoogleCodeExporter]

This would be nice.  To solve this, we'd need to patch or upgrade avrdude (in 
which case it would be good to also solve issue 623).  

Original comment by dmel...@gmail.com on 30 May 2012 at 1:18

• Added labels: Component-Build

[GoogleCodeExporter]

Are you sure you would need to change avrdude.  It appears that avrdude gets 
all of its configuration parameters out of avrdude.conf.
I believe what would need to changes is all the conditional compiles.  Such as 
in .\hardware\tools\avr\avr\include\avr\io.h:
...
#elif defined (__AVR_ATmega3250__)
#  include <avr/iom3250.h>
#elif defined (__AVR_ATmega3250P__)
#  include <avr/iom3250.h>
#elif defined (__AVR_ATmega328P__)
#  include <avr/iom328p.h>
#elif defined (__AVR_ATmega329__)
#  include <avr/iom329.h>
#elif defined (__AVR_ATmega329P__)
#  include <avr/iom329.h>
...

Is there something I can do to help implement this enhancement?

Original comment by Randall....@gmail.com on 4 Jun 2012 at 10:34

[GoogleCodeExporter]

For Mac/Windows, this would also require a compiler upgrade, since 4.3.2 
doesn't include knowledge of the non-picopower 328.

Original comment by wes...@gmail.com on 6 Aug 2012 at 9:11

[GoogleCodeExporter]

Original comment by dmel...@gmail.com on 4 Sep 2012 at 7:43

• Changed title: Add ATMega328 to avrdude.conf (in addition to ATmega328P)