Ok, I figured out finally I need the w: option set in the -U command.
so I entered
C:\Users\swide>avrdude -c usbasp -p t85 -U flash:w:anduril.2020-09-27.blf-lantern.hex
and the flashing began. It seemed to be going fine until the end, when I got the message:
avrdude: verifying …
avrdude: verification error, first mismatch at byte 0x0000
0x00 != 0x60
avrdude: verification error; content mismatch
avrdude: safemode: lfuse changed! Was e2, and is now 0
Would you like this fuse to be changed back? [y/n]
I entered y, and hit return. Now the MHV AVR Tools window is not responding.
I don’t see being able to do anything but close the window and try to establish connection again, as its been a few minutes since this happened and no further activity in the MHV AVR window.
I bit the bullet and closed the window, and then opened it again. It seems ok I think? LFuse seems set back to E2
C:\Users\swide>avrdude -c usbasp -p t85
avrdude: warning: cannot set sck period. please check for usbasp firmware update.
avrdude: AVR device initialized and ready to accept instructions
Reading | ################################################## | 100% 0.02s
avrdude: Device signature = 0x1e930b
avrdude: safemode: Fuses OK (H:FF, E:DE, L:E2)
avrdude done. Thank you.
But the light usually flashes or comes on when its done, and that didn’t happen. And when I apply power, nothing happens. But I still can read the memory.
Try again . . .
this time with the -u command added
Get a verification error, similar to the one documented here, except its 0x60 instead of 0x50
This time it only took 3 tries to get it, not a million.