Re: [avr-gcc-list] AVRdude for ATMega16

[Joerg Wunsch]

Andi Suhandi <address@hidden> wrote:

> avrdude: error: selected device is not supported by programmer: m16

So it's not AVRDUDE which doesn't support the ATmega16 but your
programmer.

The problem here is that AVR910's idea of a "device code" is
completely flawed.  The original appnote AVR910 lists device code 0x75
for the ATmega16, meant as the "boot" code, so the "normal" code is
0x74.  This code doesn't appear in your programmer's device code list,
but instead, a number of device codes appear which are not understood
by AVRDUDE.

The dilemma is, appnote AVR910 has been essentially abandoned by Atmel
(at least, the programming protocol/firmware part), and these device
codes have not been maintained by any kind of authority further on, so
they vastly diverged in the wild.  (This doesn't explain though why
your programmer obviously doesn't use the rather well-defined ATmega16
code number 0x74.)

You have to ask the author of your programmer's firmware about which
of these (unknown to AVRDUDE) device codes is meant to apply to the
ATmega16.  Once you know, let's assume the answer is "0x42", you can
run AVRDUDE with

avrdude -p atmega16 -P com15 -c avr910 -x devcode=0x42 -b 38400 -U 
TalkCounter.hex -U eeprom:w:TalkCounter.eep -U lock:w:0xfc:m

This will override the device code decision which is normally based on
avrdude.conf.

-- 
cheers, J"org               .-.-.   --... ...--   -.. .  DL8DTL

http://www.sax.de/~joerg/                        NIC: JW11-RIPE
Never trust an operating system you don't have sources for. ;-)