SOLVED! Something went wrong flashing FW3A (hope not bricked...)

dropman · 2019-08-03T18:10:11.000Z

Was trying to flash newest firmware, but something went wrong and now I get this:

C:\avr\MHV AVR Tools>avrdude -p t85 -c usbasp -Uflash:w:fw3a.hex:a

avrdude: warning: cannot set sck period. please check for usbasp firmware update
.
avrdude: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.05s

avrdude: Device signature = 0x1e930b
avrdude: NOTE: “flash” memory has been specified, an erase cycle will be perform
ed
To disable this feature, specify the -D option.
avrdude: erasing chip
avrdude: warning: cannot set sck period. please check for usbasp firmware update
.
avrdude: reading input file “fw3a.hex”
avrdude: input file fw3a.hex auto detected as Intel Hex
avrdude: writing flash (7682 bytes):

Writing | ################################################## | 100% 8.66s

avrdude: 7682 bytes of flash written
avrdude: verifying flash memory against fw3a.hex:
avrdude: load data flash data from input file fw3a.hex:
avrdude: input file fw3a.hex auto detected as Intel Hex
avrdude: input file fw3a.hex contains 7682 bytes
avrdude: reading on-chip flash data:

Reading | ################################################## | 100% 5.57s

avrdude: verifying …
avrdude: verification error, first mismatch at byte 0x0000
0x00 != 0xef
avrdude: verification error; content mismatch

avrdude: safemode: lfuse changed! Was e2, and is now 80
Would you like this fuse to be changed back? [y/n] n
avrdude: safemode: hfuse changed! Was de, and is now 0
Would you like this fuse to be changed back? [y/n] n
avrdude: safemode: efuse changed! Was ff, and is now fe
Would you like this fuse to be changed back? [y/n] n
avrdude: safemode: Fuses OK (H:FF, E:DE, L:E2)

avrdude done. Thank you.

Not tried to solder driver back and test. What shoud I do?

SammysHP · 2019-08-03T18:40:06.000Z

First of all, check the wiring. If possible, send photos of your setup.

dropman · 2019-08-03T18:49:48.000Z

link to google drive photos
Hope that wiring is wrong, because instructions was not stright forward for me…

SammysHP · 2019-08-03T19:03:31.000Z

The wiring looks to be OK. So next step is to remove the clip and attach it again. There might be bad contact. Then try to read the fuses:

avrdude -p t85 -c usbasp -U lfuse:r:-:h -U hfuse:r:-:h -U efuse:r:-:h

Repeat several times and check that you get consistent results.

dropman · 2019-08-03T19:05:55.000Z

I got 4 times:

C:\avr\MHV AVR Tools>avrdude -p t85 -c usbasp ~~U lfuse:r:~~:h ~~U hfuse:r:~~:h -U e
fuse:r:-:h

avrdude: warning: cannot set sck period. please check for usbasp firmware update
.
avrdude: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.04s

avrdude: Device signature = 0x1e930b
avrdude: reading lfuse memory:

Reading | ################################################## | 100% 0.01s

avrdude: writing output file “”
0xe2
avrdude: reading hfuse memory:

Reading | ################################################## | 100% 0.01s

avrdude: writing output file “”
0xde
avrdude: reading efuse memory:

Reading | ################################################## | 100% 0.01s

avrdude: writing output file “”
0xff

avrdude: safemode: Fuses OK (H:FF, E:DE, L:E2)

avrdude done. Thank you.

SammysHP · 2019-08-03T19:36:18.000Z

That’s strange. Reading the fuses explicitly says L:E2 H:DE E:FF, but the summary is L:E2 H:FF E:DE (high and extended exchanged)

Sounds like a bug in avrdude. I assume that the explicitly read values are correct and they match the default Anduril configuration. So just try to flash it again.

edit: lol, the avrdude bug tracker already has a big warning at the top:

Please stop reporting bug #40085 over and over again.

Which is this bug: Typo fix in fuses report
And it was fixed already 2013…

dropman · 2019-08-03T19:46:57.000Z

I installed avr tools from MHV_AVR_Tools_20131101.exe
Do I need newer version?
Thanks

SammysHP · 2019-08-03T19:53:26.000Z

It’s an old version, but it should work.

The latest version would be http://download.savannah.gnu.org/releases/avrdude/avrdude-6.3-mingw32.zip (I’m a Linux user and haven’t tested the Windows version.)

dropman · 2019-08-03T20:16:31.000Z

Still no luck.
I have avrdude 6.3 now and still get:

c:\avr\MHV AVR Tools>avrdude -p t85 -c usbasp -Uflash:w:fw3a.hex:a

avrdude: warning: cannot set sck period. please check for usbasp firmware update
.
avrdude: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.03s

avrdude: Device signature = 0x1e930b (probably t85)
avrdude: NOTE: “flash” memory has been specified, an erase cycle will be perform
ed
To disable this feature, specify the -D option.
avrdude: erasing chip
avrdude: warning: cannot set sck period. please check for usbasp firmware update
.
avrdude: reading input file “fw3a.hex”
avrdude: input file fw3a.hex auto detected as Intel Hex
avrdude: writing flash (7682 bytes):

Writing | ################################################## | 100% 8.75s

avrdude: 7682 bytes of flash written
avrdude: verifying flash memory against fw3a.hex:
avrdude: load data flash data from input file fw3a.hex:
avrdude: input file fw3a.hex auto detected as Intel Hex
avrdude: input file fw3a.hex contains 7682 bytes
avrdude: reading on-chip flash data:

Reading | ################################################## | 100% 5.69s

avrdude: verifying …
avrdude: verification error, first mismatch at byte 0x0000
0x00 != 0xef
avrdude: verification error; content mismatch

avrdude: safemode: lfuse changed! Was e2, and is now 80
Would you like this fuse to be changed back? [y/n] n
avrdude: safemode: hfuse changed! Was de, and is now 0
Would you like this fuse to be changed back? [y/n] n
avrdude: safemode: efuse changed! Was ff, and is now fe
Would you like this fuse to be changed back? [y/n] n
avrdude: safemode: Fuses OK (E:FF, H:DE, L:E2)

avrdude done. Thank you.

SammysHP · 2019-08-03T20:47:35.000Z

First try to flash with 3.3 V instead of 5 V by moving the jumper on the programmer one pin to the right (from pin 1+2 to pin 2+3). I had problems flashing with 5 V because the power consumption of the LEDs was too high. Not sure how other people handle this.

If it didn’t work: Don’t know if avrdude detects if the lock bit is set. Please show the output of this command:

avrdude -p t85 -c usbasp -U lock:r:-:b

dropman · 2019-08-04T06:07:34.000Z

Tried with 3.3V

C:\avr\MHV AVR Tools>avrdude -p t85 -c usbasp -Uflash:w:fw3a.hex:a

avrdude: warning: cannot set sck period. please check for usbasp firmware update
.
avrdude: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.04s

avrdude: Device signature = 0x1e930b (probably t85)
avrdude: NOTE: “flash” memory has been specified, an erase cycle will be perform
ed
To disable this feature, specify the -D option.
avrdude: erasing chip
avrdude: warning: cannot set sck period. please check for usbasp firmware update
.
avrdude: reading input file “fw3a.hex”
avrdude: input file fw3a.hex auto detected as Intel Hex
avrdude: writing flash (7682 bytes):

Writing | ################################################## | 100% 8.94s

avrdude: 7682 bytes of flash written
avrdude: verifying flash memory against fw3a.hex:
avrdude: load data flash data from input file fw3a.hex:
avrdude: input file fw3a.hex auto detected as Intel Hex
avrdude: input file fw3a.hex contains 7682 bytes
avrdude: reading on-chip flash data:

Reading | ################################################## | 100% 5.60s

avrdude: verifying …
avrdude: 7682 bytes of flash verified

avrdude: safemode: Fuses OK (E:FF, H:DE, L:E2)

avrdude done. Thank you.

Will try to solder driver back and test.
Edit: Everything works! Thanks for yout help, SammysHP!