Flashlight Firmware Repository

[f0xx]

On this thread HERE it seems that Hank has put a new driver in the D1.

User cuberS seems to have a D1 with an ATtiny1634 (he has flashing pads and the MCU signature matches the ATtiny1634), but I haven’t find any firmware in the repository for such a light. He flashed the ATtiny85 firmware and it does not work. Is there a firmware he can flash to rescue his light?

[dropman]

Probably asked before, but I cant find answer. I am pretty sure I even saw that TK said that this will be included as an option soon… I am trying to figure out how to disable FET mode on FW3A completely. Will writing zeroes to PWM3_LEVELS help? Or its more complicated?
Another useful option would be PWMx_LEVELS settings and steps settings for faster (someone will prefer slower also) ramping. I know its done with levels_calc.py but testing on FW3A is not so easy (soldering every time).
Last question is about battcheck mode option. I see

//#define BATTCHECK_8bars // FIXME: breaks build and //#define BATTCHECK_4bars // FIXME: breaks build

in source but this probably dont work yet, right?
Thanks.

EDIT:
Ok, I tried this:

#define RAMP_LENGTH 90
#define PWM1_LEVELS 1,1,2,2,3,4,5,7,8,10,12,14,17,20,23,27,31,36,40,46,51,58,64,71,79,87,96,105,115,126,137,149,161,174,188,203,218,234,251,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,0
#define PWM2_LEVELS 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,3,6,10,13,17,21,25,29,33,38,42,47,52,57,63,68,74,80,86,92,99,106,113,120,127,135,143,151,159,167,176,185,194,204,213,223,234,244,255,255,255,255,255,255,255,255,255,255,255,255,255
#define PWM3_LEVELS 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
#define MAX_1x7135 40
#define MAX_Nx7135 90
#define HALFSPEED_LEVEL 10
#define QUARTERSPEED_LEVEL 3

It seems that its working. Ramping is faster. Ramping stops after Nx7135 blip. Double click while on works. Only thing that bothers me is slight variation in brightness at the moment when starting ramping down from Nx7135. Maybe its because I had to put 255 instead of 0 at the end of PWM1_LEVELS?

[Dr.Phillip]

Hi guys, I have a question regarding flashing firmware. I am a total noob when it comes to flashing and I reached dead end when I decided to flash my Astrolux MF01 mini to correct some voltage reading problems (There is a large voltage difference between the actual battery voltage and the blinked out voltage). I managed to find some instruction and I did this:

I downloaded the branch “lp:~toykeeper/flashlight-firmware/fsm” from: Flashlight Firmware Repository in Launchpad because it had the code for Astrolux/Mateminco MF01 MINI. I Unzipped the tarball and found the file I needed to adjust to correct the Voltage measurement:

File: hwdef-Mateminco_MF01-Mini
Lines:
#ifndef VOLTAGE_FUDGE_FACTOR
#define VOLTAGE_FUDGE_FACTOR 5 // add 0.25V
#endif

I changed the VOLTAGE_FUDGE_FACTOR to 10 to add another 0.25V.
Now that I have it, how do I run the make command in the fsm\ToyKeeper\spaghetti-monster\anduril folder?

Do I need a special compiler (I am using windows)? The instructions I found said: “the code can then be built by going into the anduril directory and running “make”. This compiles one .hex file for each cfg-*.h file it finds.”

Could anyone please recommend me the best and the easiest way to do this?

[contactcr]

The short answer is you need to download Atmel Studio and load your edited files in there then choose “compile for size” in the properties. It will create a hex file that you can flash with a SOIC clip and some shady USB drivers.

[0-8-15_User]

I recently got my hands on a used Sofirn SP36 Anduril and found that the temperature limit is exceeded by more than 10 K, although the measured temperature is relatively accurate. This made me curious, especially since I recently ordered some Emisar D4V2s. So I wrote a little simulation to test the thermal regulation code.

Thermography:

https://abload.de/img/heatup_sp36_16x_60fpsgbkwn.gif

Measurement result:

Simulation result (revision 388):

Simulation result (revision 454):

Simulation result (mockup of how it could look like):

https://abload.de/img/anduril_temp_regulatikzk6h.png

What I found so far:

• This might lead to an out of bounds memory access: https://bazaar.launchpad.net/~toykeeper/flashlight-firmware/fsm/view/454/ToyKeeper/spaghetti-monster/anduril/anduril.c#L993
• The "crude lowpass filter" does not seem to do too well: https://bazaar.launchpad.net/~toykeeper/flashlight-firmware/fsm/view/454/ToyKeeper/spaghetti-monster/fsm-adc.c#L291
• The temperature prediction is not what one would expect from a prediction: https://bazaar.launchpad.net/~toykeeper/flashlight-firmware/fsm/view/454/ToyKeeper/spaghetti-monster/fsm-adc.c#L352
• There is a lot of magic involved to prevent the current thermal regulation from exploding, I think there is need for another rewrite. I'll probably give it a try once my D4V2 arrives.

PS: On an aside, the project name (sphagetti-monster) hits the nail on the head. :D

[CNCman]

I just purchased a Haikelite MT09 and ordered a new driver from Lexel.

He wants to know what firmware i want.

I have no clue, any suggestions

[f0xx]

Anduril

[Agro]

Anduril

[Quadrupel]

Do we have some soft for red bicycle back light?

[Chatika_vas_Paus]

There is such a thing, but I don’t actually know how it works.
click - tail light

[Lexel]

I am even too stupid to get that Bazaar to open your trunk, the plenty URLs I tried do not work
Anduril does not work properly with temp reading

the Wiki gets it for granted you know which link and how to add and don’t even give any examples

with https://

I downloaded every single file to my PC manually and replaced the old ones, its still reading garbage then it seems to read correctly after running it a while
but testing the driver with heat applied does not adjust output at all

[Agro]

You’re using a website that presents the repository rather than the repository.
The website shows that you should use “bzr branch lp:~toykeeper/flashlight-firmware/fsm” command.
With your UI you may try to enter “lp:~toykeeper/flashlight-firmware/fsm” URL.

[Lexel]

@Agro

You’re using a website that presents the repository rather than the repository.
The website shows that you should use “bzr branch lp:~toykeeper/flashlight-firmware/fsm” command.
With your UI you may try to enter “lp:~toykeeper/flashlight-firmware/fsm” URL.

Those people who write this bazaar wiki seem to think everyone is an expert programmer and know all the basics

with your link I get this error

Please
all I am asking is a zip or similar container with a working Anduril build for AS7

.

I am wasting again now almost 4 hours on this and can’t build drivers in that time for the community and I have not much time at all right now for weeks and its not looking better this year

I am close to quit Anduril with a March build like I did with NarsilM v1.2 and support no newer versions anymore

[Lexel]

Now I seem to got it working but I run into serious code overflow problems using FW3A with Aux LED support

[contactcr]

@Lexel

Now I seem to got it working but I run into serious code overflow problems using FW3A with Aux LED support

IMO, tell buyers they can have AUX support OR muggle mode but not both. Commenting out muggle saves a lot of space

[treellama]

Add -fwhole-program to the CFLAGS in build.sh, and comment out #define USE_VERSION_CHECK from anduril.c (or USE_BIKE_FLASHER_MODE or another mode if you really need the version check)

[Lexel]

@contactcr

@Lexel

Now I seem to got it working but I run into serious code overflow problems using FW3A with Aux LED support

IMO, tell buyers they can have AUX support OR muggle mode but not both. Commenting out muggle saves a lot of space

#ifdef USE_BIKE_FLASHER_MODE
#undef USE_BIKE_FLASHER_MODE
#endif
#ifdef USE_PARTY_STROBE_MODE
#undef USE_PARTY_STROBE_MODE
#endif

disable 2 strobe modes works as well 99.7% full now

@treellama

Add -fwhole-program to the CFLAGS in build.sh, and comment out #define USE_VERSION_CHECK from anduril.c (or USE_BIKE_FLASHER_MODE or another mode if you really need the version check)

I got absolutely no idea how to do that, that file is not even on the dependencies list in my project

This is the code when open in my Editor

#!/bin/sh

UI=anduril

date ‘+#define VERSION_NUMBER “%Y%m%d”’ > version.h

for TARGET in cfg-*.h ; do
NAME=$(echo “$TARGET” | perl ne ’/cfg(.*).h/ && print “$1\n”;‘)
echo “= $NAME =”
ATTINY=$(grep ’ATTINY:’ $TARGET | awk ‘{ print $3 }’)
if [ -z “$ATTINY” ]; then ATTINY=85 ; fi
echo …/…/…/bin/build.sh $ATTINY “$UI” “-DCONFIGFILE=${TARGET}”
…/…/…/bin/build.sh $ATTINY “$UI” “-DCONFIGFILE=${TARGET}”
mv -f “$UI”.hex “$UI”.$NAME.hex
done

I use a simple build “Anduril” project button with my mouse
I use no scripts or make file or other stuff the programmers are always talking of to build 20 versions at once with different settings in them

v

[treellama]

My bad, I should have realized using Atmel Studio doesn’t use that build.sh. You might be able to get back some space by adding the -fwhole-program flag to the miscellaneous flags here:

But I haven’t tried it. I’m not set up to compile for AVR.

[Lexel]

I cant find even that menu you opened

then add “-fwhole-program” ?

PS seems to save 126 Bytes but are there any problems with firmware stability?

[treellama]

Right click on the project in the solution explorer at the right, and choose Properties, to find the menu I showed. Then add the -fwhole-program to that huge list of flags in Miscellaneous (or maybe to the shorter list in Optimization). The flags are separated by spaces, and are what get passed to the compiler I use on the command line instead.

If it still gives you trouble, and you’re willing to wait a few days, I can try to set up Atmel Studio for AVR myself and give it a try.