which resulted in a read verification failure (probably just because I didn’t hold the pins steady enough).
Now when I try to reflash, I get:
avrdude.exe: warning: cannot set sck period. please check for usbasp firmware update.
avrdude.exe: error: programm enable: target doesn’t answer. 1
avrdude.exe: initialization failed, rc=–1
avrdude.exe: AVR device initialized and ready to accept instructions
avrdude.exe: Device signature = 0x6d3430
avrdude.exe: Expected signature for ATtiny1634 is 1E 94 12
avrdude.exe: NOTE: “flash” memory has been specified, an erase cycle will be performed
To disable this feature, specify the -D option.
avrdude.exe done. Thank you.
I have successfully reflashed the light several times before and the programmer still works fine on other lights. I have the tint-ramping version of the D4V2.
Also, normally when I connect the pogo pins, the button LED lights up; now it no longer does that, so I suspect something is pretty wrong.
Do you connect the pogo pins before powering on the USBasp? I’m not sure about the protection of the ATtiny, but I made bad experiences with other controllers when the ground has bad contact and a positive voltage is applied first. That’s why I always connect the pogo pins first and then plug in the USBasp into the USB port.
Just tried that and I keep getting the same error.
For reference, I didn’t ever have to connect the USBasp that way before (i.e. I just leave it plugged in and then connect the pogo pins) and it was working fine.
What happens when you do a tailcap reset and try to flash again?
I had one occasion where I flashed a new version and got a message on the app saying it flashed with errors. The light appeared to work normally, but I reflashed it and this time got no errors.
I also tried to flash a version that was incorrect and the light wouldn’t work at all. So I flashed the correct version and all was well.
Have you verified the version you need to flash?
Edit: I gather you’re using a PC to reflash? I’ve not tried the PC method, but the Android app Zflasher AVR makes the process simple enough that even I had no trouble (other than the above) reflashing my Hank-lights.
I had a similar issue with the light not working at all when I flashed the wrong version. But reflashing with the correct version returned the light to normal operations.
Have you tried flashing a stock version to see if it works?
Ouch. Oh well, at least these aren’t expensive fixes, just inconvenient. I’ll be curious to learn what failed and what you need to do to fix it, if you decide on a repair option.
That should be the right firmware. Every now and then, I get a bad download and the light won’t turn on after a flash. Download it again and try flashing again.
