Emisar D4V2 Flash Kit Instructions (Official How To)

149 posts / 0 new
Last post
f0xx
f0xx's picture
Offline
Last seen: 3 days 11 hours ago
Joined: 02/27/2019 - 18:44
Posts: 433
Location: Near Dallas, Texas

I’d suggest re-downloading the firmware. Perhaps your first copy is corrupted?

Maybe try another revision?

EDIT: Spelling error

d_t_a
Offline
Last seen: 10 hours 51 min ago
Joined: 08/04/2017 - 23:58
Posts: 1611
Location: Manila, Philippines

cuberS wrote:
I attempted it again afew times with the attiny85 in the settings in the mobile app. Same result. There’s a pop-up with the message “ operation complete with errors!” The last few lines of the log read:

vrdude: verifying …
avrdude: verification error, first mismatch at byte 0×0000 0xff != 0xa9
avrdude: verification error; content mismatch
avrdude: usbasp_close()

avrdude done. Thank you.

If it’s beneficial, I can post the whole log somehow.

Just curious, how does the setup work? Are you using an SOIC clip or pogo-type pins to flash the D1?

f0xx
f0xx's picture
Offline
Last seen: 3 days 11 hours ago
Joined: 02/27/2019 - 18:44
Posts: 433
Location: Near Dallas, Texas

What happens when you enter this command? -

Quote:
avrdude -p t85 -c usbasp -n
f0xx
f0xx's picture
Offline
Last seen: 3 days 11 hours ago
Joined: 02/27/2019 - 18:44
Posts: 433
Location: Near Dallas, Texas

d_t_a wrote:
Just curious, how does the setup work? Are you using an SOIC clip or pogo-type pins to flash the D1?

D1 would require a clip as it does not have flashing pads (on the current version).
cuberS
Offline
Last seen: 4 months 3 weeks ago
Joined: 11/03/2019 - 09:58
Posts: 6

I have the official flash kit. My D1 has the same pins as my D4V2.

When I put in the command “avrdude -p t85 -c usbasp -n” I get the following:

Quote:
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 = 0×1e9412
avrdude: Expected signature for ATtiny85 is 1E 93 0B Double check chip, or use -F to override this check.

avrdude done. Thank you.

When I put in the command “avrdude -p t1634 -c usbasp -n” I get the following:

Quote:
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 = 0×1e9412

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

avrdude done. Thank you.

I’ve flashed the light with setting combinations of two chips (ATtiny1634 & ATtiny85) and four hex files (anduril.2019-08-05.emisar-d1.hex, anduril.2019-09-28.emisar-d1.hex, anduril.2019-08-05.emisar-d4v2.hex, anduril.2019-09-28.emisar-d4v2.hex), using new downloaded hex files in both windows 10 and the android app. Flashing with the ATtiny85 setting gives errors. No errors in the ATtiny 1634 setting. Flashing with ATtiny85 chip setting and any hex do not give a working light. Flashing with either chip and any D1 hex file do not give a working light.

The combinations of settings of ATtiny 1634 and either D4V2 hex file now give me a working D1, however now the light flickers a lot when screwing on the battery tube and sometimes stays on when battery tube is fully screwed on. Do I have a thread problem now? Anodization looks pretty good. A sliver of anode has worn off Sad

Edit: Or is the flickering/light on due to the software and flashing?

Valynor
Offline
Last seen: 1 hour 34 min ago
Joined: 07/13/2019 - 17:13
Posts: 92
Location: Germany

@cuberS

Couple of things:

-never flash a firmware that you KNOW is for a different device, e.g. D4V2.hex on a D1 - doing this usually means begging for trouble

-your 2nd try with the “avrdude -p t1634 -c usbasp -n” command produced the correct results for the D4V2

-if you can repeat that with "avrdude -c usbasp -p t1634 -u -Uflash:w:FILENAME.hex" and the correct firmware you should be successfull

-make sure to hold your hands really still while the flashing is in progress, maybe get a 2nd person to press the enter key for you

Man Without Shadow
Man Without Shadow's picture
Offline
Last seen: 34 min 21 sec ago
Joined: 02/20/2017 - 18:17
Posts: 455
Location: Wisconsin

Ok…curiosity piqued…

Afraid to try before…but flashed my D1 with 9.28.19 D1 anduril…

Popped out the driver…no problem…unsoldered the black wire…spun the driver around…set up my SOIC clip, used Android phone for flashing…

Failed like 10 times…checked my wiring…wiggled all my wires…some came loose a few times…still errors…FINALLY reseated the clip just right…was always missing a prong or two…

Successful flash!

I did get “operation failed” like 10x though…in the end…was a bad clip on chip connection…

Mine is an ATtiny85 chip…says so right on the chip…so used that setting…

Look closely at your chip to identify it…

Hope you get results soon!

Peace!

When I'm spending mony foolishly, I like to do it wi$ely...

I have all the flashlights I need, but not as many as I want...

 

brewster
Offline
Last seen: 3 hours 16 min ago
Joined: 07/19/2019 - 23:29
Posts: 41
Location: Australia

Everything you say indicates that your D1 has a D4V2 driver in it. I don’t think there is a proper file for that combination available, although I don’t know the precise differences between D1 and D4V1 drivers for instance (that is, those using the same MCU).

Your other problem of the light flashing as the tube is tightened suggests a physical problem, most likely some wires are pinched between the driver and the body.

f0xx
f0xx's picture
Offline
Last seen: 3 days 11 hours ago
Joined: 02/27/2019 - 18:44
Posts: 433
Location: Near Dallas, Texas
cuberS wrote:

I agree with the above, it looks like Hank is now using a new driver in the D1 based on your findings. (Flashing pads, 1634 works, 85 doesn’t, D1 firmware doesn’t work, etc…). This is cool and exciting, but kind of a bummer right now in your situation.

My guess is that you have the newer MCU (ATtiny1634) and your firmware files are for the older MCU (ATtiny85). If the D4v2 firmware doesn’t work (most likely not the exact same driver as the D4v2), you will need to obtain a version of the D1 firmware suitable for use with the new MCU. I would reach out to Hank and see if all this is true, and if he can provide you with the proper firmware (to get you going).

ToyKeeper would be another good resource as she is likely the one to have written the code for the newer driver (unless Hank just modified the D4v2 Firmware, but this seems unlikely).

d_t_a
Offline
Last seen: 10 hours 51 min ago
Joined: 08/04/2017 - 23:58
Posts: 1611
Location: Manila, Philippines

Does that mean the new D1 now uses ATTiny1634 MCU instead of ATTiny85? And it has the same flashing pad as D4v2 (which uses ATTiny1634)?

Can you take a picture of the D1 flashlight?

cuberS
Offline
Last seen: 4 months 3 weeks ago
Joined: 11/03/2019 - 09:58
Posts: 6
d_t_a wrote:
Can you take a picture of the D1 flashlight?

Man Without Shadow
Man Without Shadow's picture
Offline
Last seen: 34 min 21 sec ago
Joined: 02/20/2017 - 18:17
Posts: 455
Location: Wisconsin

Ulp…

That’s different than mine…

I had to open mine up and use a clip on the chip, no flashing pads.

When I'm spending mony foolishly, I like to do it wi$ely...

I have all the flashlights I need, but not as many as I want...

 

d_t_a
Offline
Last seen: 10 hours 51 min ago
Joined: 08/04/2017 - 23:58
Posts: 1611
Location: Manila, Philippines

Thanks, cuberS.

Has Hank Wang confirmed that the Emisar D1 now uses ATTiny1634 and has the same flashing arrangement (similar to D4v2)?
Or is this just an “honest error” (D4v2 board installed on a D1 flashlight)?

ThirDegree
ThirDegree's picture
Offline
Last seen: 1 day 13 hours ago
Joined: 10/20/2019 - 11:08
Posts: 7

As another data point, I ordered 2 D1’s from Hank on 10/19. Both utilize the same flashing pads as my D4V2’s. When attempting to flash with anduril.emisar-d1.hex, I end up with a D1 that does not work. When flashing with anduril.emisar-d4v2.hex, I end up with a functioning light.

Agro
Agro's picture
Online
Last seen: 2 min 24 sec ago
Joined: 05/14/2017 - 11:16
Posts: 5768
Location: Ślōnsk

It’s working. Smile
I just flashed my own variant of Andruil.

It’s a really big deal for me because previously I put a lot of effort into making USBASP working – and I failed. Smile

Gst138
Offline
Last seen: 3 months 4 weeks ago
Joined: 03/01/2016 - 04:03
Posts: 11
Location: UK

Sorry if this is a stupid question. I have ordered the reflash kit for my d4sv2. where does one find the latest firmware version to download.

bquinlan
Offline
Last seen: 11 hours 48 min ago
Joined: 04/19/2018 - 01:07
Posts: 100
Location: Madison, Wisconsin, USA
Gst138 wrote:
Sorry if this is a stupid question. I have ordered the reflash kit for my d4sv2. where does one find the latest firmware version to download.

I’m sure it’s in the thread elsewhere, but here is the URL:

http://toykeeper.net/torches/fsm/

Gst138
Offline
Last seen: 3 months 4 weeks ago
Joined: 03/01/2016 - 04:03
Posts: 11
Location: UK

Thank you.

Firelight2
Firelight2's picture
Offline
Last seen: 6 hours 10 min ago
Joined: 04/08/2011 - 15:17
Posts: 3869
Location: California

Just reflashed three D4V2s using this guide. Worked great. Cool

BabyDoc
BabyDoc's picture
Offline
Last seen: 1 day 15 hours ago
Joined: 05/29/2019 - 09:37
Posts: 141
Location: Beachwood, Ohio

What’s new in the 11-24-19 release for the D4v2?

f0xx
f0xx's picture
Offline
Last seen: 3 days 11 hours ago
Joined: 02/27/2019 - 18:44
Posts: 433
Location: Near Dallas, Texas
cuberS wrote:

cuberS,

I posted a question about this in the firmware development thread. It seems that there are a few others that have noticed a new driver in the D1. ToyKeeper’s reply is here:
http://budgetlightforum.com/comment/1595549#comment-1595549

It may be helpful.

Gst138
Offline
Last seen: 3 months 4 weeks ago
Joined: 03/01/2016 - 04:03
Posts: 11
Location: UK

Help please.
I have downloaded Zflasher, I have the reflash kit and have got the latest firmware downloaded onto my phone. I bought the otg adapter from intl outdoors but it was for USB C. I bought this from eBay
Standard Micro USB Host OTG adapter, can be used for connecting devices like memory sticks, hard drives(need external power support), mouse, card reader, keyboard etc. to your compatible phone & tablet.

compatible with modern device:

Samsung Galaxy S2/SII/SIII/S4/i9100

ASUS Google Nexus 7(2nd Gen)/10

HTC One

Tesco HUDL

Galaxy TAB 3

Nokia N810/N9

Most of Android Tablets

When I attempt the download it comes up with “completed with errors”.

Can anyone help.

Unheard
Offline
Last seen: 21 hours 18 min ago
Joined: 01/16/2019 - 11:38
Posts: 395
Location: Germany

BabyDoc wrote:
What’s new in the 11-24-19 release for the D4v2?

Most notably, the light wasn’t always responding to button press. In rare cases, it won’t come on. It now always does.
Man Without Shadow
Man Without Shadow's picture
Offline
Last seen: 34 min 21 sec ago
Joined: 02/20/2017 - 18:17
Posts: 455
Location: Wisconsin

I have had that happen to me, and the simplest answer is maybe you are accidentally wiggling the connector.

If you can hold it very still, and try to flash it again that could work.

I tried several times before I got it to complete without errors.

Unless there is more wrong that I don’t know about, you should try this a few times… Just trying to hold the connector pins steady.

When I'm spending mony foolishly, I like to do it wi$ely...

I have all the flashlights I need, but not as many as I want...

 

crazy.about.lights
crazy.about.lights's picture
Offline
Last seen: 3 days 18 hours ago
Joined: 08/20/2019 - 18:19
Posts: 21
Location: Somewhere out there

Took quite a bit of learning and time but it was more than worth it. Thanks Terry Oregon for this guide.

Gabe

radellaf
Offline
Last seen: 1 month 3 weeks ago
Joined: 10/14/2017 - 23:43
Posts: 32
Location: NC

Finally got around to trying this. Used Win10 on the work laptop since I don’t have an android phone and don’t feel like installing Xcode or homebrew on the iMac.

Two verification fail errors using reading glasses and pushing halfway down. Then, using the Optivisor and pushing all the way down on the pogo pins: success. Yay.

Not sure if I did the factory reset properly. Held it down waiting for a flash, but it did a bunch of things and I just kept holding it down until a few seconds after it stopped doing anything different. I hadn’t changed it from defaults apart from aux settings. Those reset, so I guess it all did.

How to do thermal config? Tried the diagram and could get into config mode but failed at setting anything properly. Haven’t played with anything but Zebralights for a long time now. I use the FW3A more than my 3 Emisar D4, but in only the most basic way. The D4V2 has spent the last months in aux high blue mode on top of a clear plastic decoration. It is very pretty. I have the D4S, with cyan aux LEDs on the other side of the decoration. Even prettier. Before that, I mostly used the D4V2 in candle mode with an hour timer to go to sleep. Beautiful, but now I seem to have a large collection of LED candles vs just the one, so not so much need.

Now I see there’s a D4SV2, along with a FW21 I just ordered (bah, no 3000 or 4000K option). Lovely.

So, anyway, had to dig up the text manual for Anduril and now I get it. Wonderful, no more bug in a mode I never use, but since I waited so long I get … some other fixes. And satisfaction. I’ve been playing a lot with an Arduino Mega and the much nicer ESP32 (built in WiFi!) but command line is a bit more hardcore than the Arduino IDE. There is a GUI for avrdude but I haven’t played with it. I’d kinda like to flash my two D4 to Anduril but I’m not taking them apart to get to the chip.

The D4S has pads in a different arrangement I think. And I have no idea if it is D4 type or Anduril type interface. Probably will leave it alone unless I could buy a set of pogos (or a kit thereof) that fit it.

Anyway, thanks to all involved. Cool light, and had fun with the little bit of effort it took to reprogram it.

For anyone else, here’s the bit of instructions I need that wasn’t in this thread (or I didn’t see it):

Every config mode has the same interface. The menu has one or more
options the user can configure, and it will go through them in order.
For each menu item, the light will follow the same pattern:

– Blink one or more times, corresponding to the item number. – Stutter or “buzz” quickly between two brightness levels for a few seconds. This indicates that the user can click one or more times to enter a number. It will keep buzzing until the user stops clicking, so there is no need to hurry. – Pause, and then go to the next option.

After the light has gone through all of the menu options, it should
return to whatever mode the light was in before entering the config
mode.

If the user doesn’t press a button during a menu item’s “buzz” phase,
that item remains unchanged from its previous value.

Hikelite
Offline
Last seen: 2 hours 16 min ago
Joined: 07/13/2011 - 16:18
Posts: 3696
Location: RO

Maybe instead of using commands in Windows maybe something like AVRDUDESS could be used as it has an interface?
https://github.com/zkemble/AVRDUDESS

What do you think?

Quadrupel
Quadrupel's picture
Offline
Last seen: 2 days 23 hours ago
Joined: 12/03/2017 - 10:40
Posts: 190
Location: LT

Just flashed attiny85 with Zflasher, works like a charm

Pages