smcx schrieb:
And here is the output from AVRdude (I was using AVR8-Burn-O-Mat as a GUI)
C:\WinAVR-20071221\bin\avrdude.exe -q -u -C
C:\WinAVR-20071221\bin\avrdude.conf -p m8 -P usb -c usbasp -D -E
noreset,novcc -U flash:w:E:\Labsoft\ATMEGA8\main.hex:a
The -D option your frontend passes to avrdude is the main Problem here I
think. It disables the erase-cycle avrdude normally performs before
writing to the avr. When the old program is only overwritten with the
new one, it is no wonder that the verification fails.
regards,
Peter
_______________________________________________
AVR-chat mailing list
AVR-chat@nongnu.org
http://lists.nongnu.org/mailman/listinfo/avr-chat
