Flashlight Firmware Repository

Thanks pd, that would be great.

I know I have to learn a lot about the codes work but it takes time… even to see which change will lead to an effect is one step forward

If you’re in a hurry, you could probably find the answer in the STAR thread a few pages back. I had to ask for help doing it about a year ago(?).

I´m not in a hurry but in the meawhile I found it, changed it and it works :smiley:

Now it fits my needs and I have one more nice light with a great UI. Thank you!!!

Cool. That’s what I use in all of my e-switch lights (so far). I also shorten up the long press so that it’s only about 0.3 seconds.

It’s just a small step toward giving it a more normal code layout. Putting everything in one file is pretty unusual, and frowned on in most software development. Instead of using a single code file to represent the state of a project (like saving the build for a specific light), snapshots are more often taken in the form of a code branch or repository tag or a tarball or some other complete snapshot of the entire project.

So… Common functions, things which don’t usually change from project to project, were moved into shared headers. When one project gets an improvement to these bits, all the others benefit too. The individual projects have less boilerplate code and focus more on the parts which make them unique. And if there’s a common component you like to do differently (such as hardware calibration), you can swap out one file and it’ll apply to every project automatically.

I limited this to only my directory though, since other people manage their code in different ways. And I added ‘tk-’ to the beginning of each file to avoid name collisions. C doesn’t have real namespaces, so I basically kludged one together in flat space instead.

I’ve still tried to avoid a lot of typical C idioms though, like depending on a specific build system or external libraries or anything else which makes it significantly harder to use in WinAVR or OSX. These projects are still simple enough to be manageable without a massive complex internal structure.

Oh, right. I tried a whole lot of different code while making the soft start ramp-up/down code, and it looks like I missed a few things when cleaning it up afterward. You could also make the ramp slower by increasing the number of steps instead of the delay between steps. This way it’d be smoother.

On some later firmware, the same code should be able to provide smooth transitions between levels on an e-switch light… but that ability isn’t really used much in bistro.

Just to make sure, what is the link for the most recent working version?
I’d prefer to add that one instead of an earlier one which didn’t work. :slight_smile:

Perhaps this should be added too?

I just did a quick check, and I don’t think anything in the repository matches all of the following:

  • e-switch
  • dual PWM
  • single-click off
  • attiny13a

I see everything except tiny13 in one of Tom E’s projects, and everything except dual PWM in one of my projects, and everything except single-click off in JonnyC’s code… but nothing with all of them in one place. Unless I missed something.

That sounds like it’s definitely a hardware difference. You can measure some hardware traits using the files under ToyKeeper/battcheck/* , but that’s just one option.

One possibility is that maybe the fast_presses variable on that exact MCU happens to decay to a useless value. This would be rare, but is possible. You could try changing around the order of variable definitions to maybe align that with a different part of RAM… or try dumping out its value on boot in order to check if it’s even relevant.

Anyway, it’s hard to say for sure what the issue is.

The one in the post is the most recent version, I have it installed in the S8 in my sig line. I was going to ask though, can one of you wizards take a look at the LVP code? I’ve experienced some strange behavior that I haven’t totally found a pattern for. It’s almost like mode cycling stops working when LVP is kicking in. Like you’ll be in turbo/fet mode, lvp will step down to medium, then you can jump back up to turbo, but you can’t cycle past turbo to low. No matter how many “short presses” you do it stays in turbo until lvp starts to step it down again.

Yes, I couldn’t find a matching FW too, that’s why I was asking.

But after the changes I’m satisfied with it so far. The next time the light is opened I’m going to set the long press to about .3s as well. And delete the first mode which is off. I think pd’s solution should be the best. BTW then it is exactly the same UI that Nitecore is using e.g. in their HC30.

The only thing I’m not happy so far is that the turbo stepdown is happening in PWM-channel 1 only (where are my AMCs) and not in PWM-channel 2 (where is the FET). This has to be changed but I want to find out myself first. If I can’t do it I will ask again.

sub

Ok firmware wizards, I can’t remember if I have asked this before or not. I’m looking for a firmware to use in a dual-switch light. I’ll list what I’m looking for, and hopefully there’s already something close or a more advanced FW that I can dumb down or something. If it runs on a 13 that’s preferred, but I could use a 25 or 85 if need be.

- on/off by tail power switch only
—- always comes back on in last mode

- side switch changes modes
—- click forward, hold for backward

  • precise control of two pwm channels

That’s the main stuff, other nice things would be a shortcut to a certain mode by holding the side switch while applying power, or double click then hold enters a second mode group.

So what’s out there?

There’s not a lot out there for dual switch.

I think, at the moment, there may be only STAR_dual_switch (tiny13) and Tom E’s Narsil (eswBrOutCfg, tiny45/85). I haven’t gotten to try either one, but Narsil is pretty full-featured.

I keep wanting to make something, but I don’t actually have a dual-switch light and I keep putting it off. I’ve only got one test driver with an e-switch, and it’s a FET-only board.

What’s a good way to rig up an e-switch to a floating driver without making it fragile or blocking SOIC8 clip access?

Sometimes I use a Forward clicky with leads soldered to OTC pads, but usually I just take a wire, solder one end to the pad that connects to pin 2, then tap the free end to the ground ring to simulate button presses

I always thought Ferrero Rocher constantly displayed battery level with secondary led’s through that little window in the Roche F6, but I don’t see any mention of that in the .text file. Am I thinking of a different firmware? I’d really like something that can do this and use a clicky switch to control the main LED. It’s for a rather complicated project I’m working on.

edit: one more question, does baton keep it’s mode memory if power is removed? Or does that totally reset it?

I can’t help with the firmware, but that sounds very interesting…

Boy, haven't been keep'n up here. Lot more attractive drama in the GB threads Smile.

I bought off of eBay a ton (maybe 100) of e-switch's, the kind similar to those mounted in a SRK - very small, very thin. I wired up 2 wires, maybe 26 AWG, to the contacts and use this rig as my e-switch test. I usually use pin #2 so can take advantage of the OTC pad on our drivers, the other wire to a grnd point. Not the most stable and easiest think to use, because the tiny switch is floating in air, but worked out for me. Mostly I don't need a test switch because I'm attaching my driver in piggyback fashion to the stock driver, and making use of the stock driver mounted switch.

if you need this mainly for testing firmware, my absolute best setup was using Richard's SupFire M2-Z lights - cheap, simple, and use extra long LED wires so you can easy re-program. It fits a 22 mm driver -- better still, because a 22 is easier to work with as well. Just wire up the switch and use the real switch - sooo much easier, nicer setup. Mostly I tested without re-assembling the light - simply wired up a cell with alligator clips.

PD68 post #739 - Narsil won't do exactly that, but kind of sort of close. Narsil will have a turn OFF from the side switch (small parasitic drain), and it does sort of use hold for back -- well a short hold goes back one mode, keep holding and you get strobed.

It does have mode memory on the tail power switch, though it uses the brown out feature for doing this, and allows full mode switching on the tail, not just power. Mode changes made on the e-switch are not "remembered".

Thanks Tom. I’ve been meaning to install Narsil in my 7G3CS, but other projects keep taking priority. One day it will happen.

Does anyone else remember a firmware with active battery monitoring on little SMD led’s? I really thought it was written for the Roche F6.

Edit: i didn’t see anything about it in the .txt file, but now that I look at the .c file I’m convinced ferrero rocher is the one I was thinking of. Can anyone explain how the voltage monitoring works with the red and green leds? I see it has dual-pwm support, but how does that mesh? There aren’t enough mcu pins for all of it to work, are there?