Fri 18 Dec 2009 10:24:29 PM UTC, original submission:
The chip_erase delay for four AVRs in WinAVR-20090313\bin\avrdude.conf is too short, so the chip erase command times out and avrdude prints an error message. The error is not fatal; it doesn't prevent the user from programming the chip. This bug should be very easy to fix.
<h3>Solution:</h3>
In avrdude.conf, change the chip_erase_delays to the following values:
Part chip_erase_delay
ATmega324P: 45000 (us)
ATmega644: 55000
ATmega644P: 55000
ATmega1284P: 55000
Currently they are all 9000, which is too short. The values listed above were taken from the parts description files installed by AVR Studio:
C:\Program Files (x86)\Atmel\AVR Tools\Partdescriptionfiles\*.xml
<h3>Example output reproducing the problem:</h3>
<pre>
C:\>avrdude -P\\.\USBSER000 -pm324p -F -c avrisp2 -e
avrdude: AVR device initialized and ready to accept instructions
Reading | ################################################## | 100% 0.02s
avrdude: Device signature = 0x1e9511
avrdude: Expected signature for ATMEGA324P is 1E 95 08
avrdude: erasing chip
<b>avrdude: stk500v2_command(): unknown status 0x80</b>
avrdude: stk500v2_command(): command failed
avrdude: stk500v2_command(): unknown status 0xc9
avrdude: stk500v2_program_enable(): cannot get connection status
avrdude: safemode: Fuses OK
avrdude done. Thank you.
</pre>
Fixing the chip_erase_delays will not fix all the error messages here, but it will fix the one highlighted in bold.
|