Emisar D4V2 Flash Kit Instructions (Official How To)

hey all… im currently updating the firmware on my d4v2, im getting a mismatch on byte, anyone have an idea why this is the case? heres the output

Try a couple more times, making sure you're holding the pins steady. I ran into this problem as well. What I did - was flashed the other hex file (non Nichia version), and it worked. Then I went back and flashed the correct hex file for my light (Nichea version), and it also worked. Not sure what causes this error.

okay will continue trying, do you recall if you got the same error as below?

I posted an example of the "verification error" on the instructions. It was slightly different.

hmm yeah, i went to the older version and i get the same error… thinking…hmmmm

oh the usbasp, do i have to change the jp2 jumper? I have it all the way on the right (right being closest to usb port)

Note the jumper location, exactly as I got it from Hank.

trailhunter;

You're using the flash kit from Hank?

Nah, I built my own Imgur: The magic of the Internet

"Nah, I built my own https://imgur.com/a/p2KgwEu"

That shouldn't be a problem, but where did the USBasp board come from?

">Imgur: The magic of the Internet

That shouldn’t be a problem, but where did the USBasp board come from?

[/quote]

amazon, ive been using it to flash fw3’s no problem. let me double check all the wiring one more time. im surprised the first check in passing.

Terry, I found the problem. So thinking this through and looking at my setup, I noticed that my wire leads may be a bit too long at 3v on the usbasp. So what I did is move the pin from 3v to 5v and guess what? That fixed my issue above. So basically, if you run longer leads, you’ll want to bump the voltage up to compensate for that voltage drop :smiley:

As you can see here, it updated just fine now.

Congrats.

@Terry Oregon Huge thanks to you for making the instructions for the community.

Everything worked right at the 1st attempt:

avrdude -c usbasp -p t1634 -u -Uflash:w:anduril.2019-08-05.emisar-d4v2.hex

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

Reading | ################################################## | 100% 0.00s

avrdude: Device signature = 0x1e9412 (probably t1634)
avrdude: NOTE: "flash" memory has been specified, an erase cycle will be performed
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 "anduril.2019-08-05.emisar-d4v2.hex"
avrdude: input file anduril.2019-08-05.emisar-d4v2.hex auto detected as Intel Hex
avrdude: writing flash (9122 bytes):

Writing | ################################################## | 100% 9.20s

avrdude: 9122 bytes of flash written
avrdude: verifying flash memory against anduril.2019-08-05.emisar-d4v2.hex:
avrdude: load data flash data from input file anduril.2019-08-05.emisar-d4v2.hex:
avrdude: input file anduril.2019-08-05.emisar-d4v2.hex auto detected as Intel Hex
avrdude: input file anduril.2019-08-05.emisar-d4v2.hex contains 9122 bytes
avrdude: reading on-chip flash data:

Reading | ################################################## | 100% 4.86s

avrdude: verifying ...
avrdude: 9122 bytes of flash verified

avrdude done. Thank you.

I did the reset afterwards (hold 3 seconds when tightening battery cap) and also tried the other way ("13H") for curiosities sake but I found it next to impossible to get the timing right.

Received my kit yesterday. Reflashed my D4v2 via the Android and OTG method. Couldn’t be easier!

Now what else can I do with this kit? :slight_smile:

Done.

If I can do it (my old eyes needed a magnifying glass), everyone can. Thanks to TK & Hank for resolving the issue.

Now comes the really difficult part … getting my old preferences back into the light.

Kit arrived yesterday and update done to my D4V2 the same day from MacOS. As other oldies have noted, the hardest part is seeing close up to ensure the tiny pins are in place on the pads.

It might help to have a second via cut in the board to position the pins better. That could be done in future without affecting backwards compatability.

The quick reset now in Anduril is great, too. The reset cleaned up a small issue seen after flashing a Q8, where I presume some old configuration data wasn’t cleaned out by flashing.

Thanks to Hank and TK for sorting this - and incidentally for the great leap forward in firmware flashing.

I flashed my two D4v2s this morning without problem; the pogos neutralized my tremor. Thanks Terry for your clear instructions. Thanks TK and Hank for addressing the problem promptly and efficiently.

Also got my reflashing kit ordered from Hank, tested on my D4v2 and at first try, it didn’t succeed, most likely due to the pins not aligning properly with the D4v2 holes (they’re very tiny and my eyesight is a bit poor…) A second try worked successfully. (I have previous experience flashing the BLF/Sofirn Q8 into NarsilM v1.2 and Anduril already, so I sort of knew how the AVRDUDE works on PC… The flashing process seems to take just a little bit longer, maybe by a few seconds, on the D4v2 compared to the Q8, but it could just be my imagination)…

Regarding the 2019-08-05 hex file, aside from eliminating the muggle mode bug, adding a factory reset function, are there any other minor new functions added or changes in behavior (eg. thermal behavior or say candle mode behavior), compared to the June 2019 firmware?

here are some updates listed: