Flashlight Firmware Repository

configurable, as in, I have a menu option in my FWAA that I can change?

or as in, something needs to be edited and reflashed?

thanks… I honestly do not know what hardware the FWAA uses, nor how many 7135…

where do I see Anduril code?

I have no experience, and most of what you say is outside my comprehension… I can follow directions, but have none of the hardwared needed to connect to a FWAA for reflash…

so forgive if Im not qualified to have an intelligent conversation. I feel like I just walked into a University level Class, and have not met the prerequisites. So if you decide its all too complicated to explain, I will not be offended that you dont have time to hold my hand and walk me through the entire process.

I can live with my FWAA the way it is… not perfect, but parts of it are excellent :wink:

You would put that in your cfg to disable the blink :

#ifdef BLINK_AT_RAMP_MIDDLE
#undef BLINK_AT_RAMP_MIDDLE
#endif

The default settings are in config-default.h so if you want to disable something in there you can do this for any of those.

Ahh, ok. Yes - agree, probably best someone else do this for you. Sounds like a very steep learning curve.

For issue 1., it's configurable by editing and flashing.

thanks for the education :+1:

.

thanks for the reality check
meanwhile, I just use stepped mode, it has no double blink :wink:

OK, I will try.
D4 has Pin #2 for Switch. And the old D4v1 has no Aux/Switch-LED, I think.
And it works with the A17DD Driver with the changes you wrote?

Is the Layout of the BLF Q8 the same as the D4 with aditional Aux-LED on Pin #3?

Where do I find the latest Hex-Files with Anduril or Anduril2? I found the following.

On the older Donwload-Place I found no Anduril-Hex-files:
https://bazaar.launchpad.net/~toykeeper/flashlight-firmware/trunk/files/head:/

You can find the standard/stock basic FET+1 schematic here in DEL's driver thread: https://budgetlightforum.com/t/-/44006/3

It shows the 7135 on pin #5, FET on pin#6. Pin #2 is the switch, pin #3 is the switch/AUX LED, and pin #7 is the voltage divider (not really needed w/Anduril).

Yes - Q8 is same as D4 but with the add switch LED on pin #3.

Not sure about the latest .HEX files.

DEL has the parts list (BOM) in his OSHPark listings, like here: https://oshpark.com/shared_projects/qsbLVgh0 or here: https://oshpark.com/shared_projects/pYGsJoAx

DEL developed the first stable, proper designed driver for the ATTiny85. He designed the Q8 driver. Everyone thereafter copied his design, or I passed along the info to them.

Thanks for the clarification…

Is it possible that Lumintop flashed the wrong firmware (FW3A-219 instead of FWAA) on their FWAA, or just that the model code has a mistake in the cfg-fwaa.h, as you mentioned?

How to check if that is indeed the case? (3-channel program code on a 2-channel physical driver = what kind of issues will happen?)

Does it ramp up and down normally on all 150 levels? Then everything is alright. Wrong channel configuration would result in nonlinear ramp, no turbo, no moon or whatever.

I hope this is an OK place to ask for help. I just updated my KR4 and D4V2 lights to the latest Anduril. However I had the following issue on my K9.3, and after I have not been able to reflash (Or use).

Failed attempt:

Every try since:

I should add that I have tried -F as well

Usually this means it is not physically connected… like the connector slipped during a reflash. Keep trying, and it should work eventually.

It can help to use good lighting and a magnifier or reading glasses to see better, to make sure the pins are making contact. It can also sometimes help to unplug and replug the USB adapter, because some USB adapters are unreliable after one use of avrdude. Also, sometimes it helps to change the angle of the pogo pins against the pads.

Toykeeper,

Thank you so much for your time. Unfortunately I do not believe that is what I have going on here. I have a steady hand and good eyes with plenty of quality light. I have been able to update other lights since, and have attempted this one over 30 times with the same result. I had previously used multiple versions on the 9.3, however as soon as that failed upload occurred there have been no signs of life.

Update:

Have rebooted my pc, and left the adapter unplugged for half an hour. Reflashed a D4V2 first try. Then attempted 20 additional times, carefully repositioning and verifying connection each time with no success. Then to verify the adapter status I reflashed the D4V2 again in 1 try.

That is unfortunate. I have a couple lights which are extremely difficult to flash, so I don’t do it very often because each time takes dozens of attempts. In one case, I had to try over 200 times before it finally worked. I never did figure out why exactly it has issues while others don’t, though.

It’s also possible that the flash could have sent exactly the wrong data, causing it to underclock itself or something at boot time, which would make reflashing fail. But in several years of reflashing chips rather a lot, I haven’t seen that happen.

OTOH, I have an old FW3A dev host here which was fine for years, and worked fine last time I reflashed it… it even boots up and runs Anduril normally. But I can’t get it to flash any more. It acts like it’s not connected. I haven’t tried cleaning it yet though; it could just have dirty contacts.

I suppose I will give it some more attempts each day until I break down and order a replacement. Wife is not enthused that I broke “her torch”.

My sympathies. If I ever find a practical way to revive it, I’ll let you know… but so far, the only method I’m aware of is to unsolder the MCU and use a high-voltage programmer on it. Or just keep retrying and hope. :frowning:

It might help to twiddle the 3.3V/5V jumper, but it’s kind of a long shot.

Thujone, I have a spare D4V2 driver board that I can sell you for what I paid for it ($12 I think). But, I am told that replacing it is difficult because of having to solder a lot of wires in a small space. ToyKeeper’s idea of unsoldering the MCU to do the HV (high voltage = 12V) reflash method might be easier. I have never done this and don’t know whether you’d really have to unsolder the entire MCU or just the relevant pin. It’s disappointing to hear that this can’t be done through the 6 pin interface without removing the MCU from the board. What a pain.

I notice illumn.com has some D4V2 in stock in California if your wife doesn’t want to wait for a replacement to arrive from China. They ship pretty fast.

There are probably people on this board who can fix your light by unsoldering the MCU etc .if you’re not up for that yourself. It will definitely be quicker to get a new light, but if you fix the old one afterwards, then you have a spare. I’d offer to give it a try, but I don’t have the tools for it (SMT hot air rework gizmo).

That doesn’t help.

About the high-voltage thing, it’s almost certainly not an option. It requires special equipment to do the reflashing, and getting the MCU off/on is rather difficult due to its form factor. Even just getting the K9.3 driver out is difficult, since there is so much hardware packed into a tiny space.

If reflashing via pogo adapter fails to revive it, Thujone doesn’t have any good options.

Ah whoops, somehow I got confused and forgot what model of light this was. It’s a real pain if the HV reflash can’t be done in-circuit. I guess the pogo pin programmer doesn’t have the 12 volt output anyway. Thujone, don’t throw out your light, it is likely repairable with some expense and hassle. Meanwhile though, yeah, it sounds like you better buy another one. Illumn does have some Noctigons in stock, and fwiw my D4v2 took only around 2 weeks to arrive from China, much faster than I expected.

I’d say the K9.3 is one of the less difficult Emisar/Noctigon to repair, driver cavity has a lot of depth (~10mm) compared to the ~2.5mm of the D4v2/D4Sv2/KRx, which allows to use longer wires, the solder pads on the MCPCB and AUX PCB being more spread out makes soldering the wires significantly easier than on a D4v2.
Still not exactly an easy job and it depends a lot on one’s skills.

Hank sells drivers as spare parts.

I would need to reflash a driver to use only the FET. Is there any FET only Anduril HEX file? How would it be possible to compile one?

Hhmm, I think I did this a while back. Depends on your driver/hardware and what issue(s) you can live with, or not. If it's like a FET+1 but without the FET (i.e. direct drive FET), then at low PWM the smooth ramping is not so smooth, so if you could live with it being rough, or raise the low end of the ramping. I think even the lowest possible ramping level for a FET is still not that low. I don't know if TK's new "better low modes" changes could make this work better or not.

It's fairly easy to generate Anduril / Anduril 2 for 1 channel, and create a FET only ramping table - that's basically all you need to do. I don't have a working, tested version handy. Again, at a minimum, I/we would need specifics on the driver - I/O pin assignment for the FET channel, etc.