Check out toykeeper’s baton FW in the ferrero rocher folder. Not sure if it is 2-channel, but it is for the attiny13a.
Toykeeper’s baton FW is a single channel FW.
Attiny13A Diagram
Not Used - |1 8| - VCC
E-switch - |2 7| - Voltage ADC
Red LED - |3 6| - PWM
GND - |4 5| - Green LED
I’m not sure if that still uses the same firmware or if it’s a newer light with one of LoneOceans’ drivers. If the firmware is recent, you should be able to find out by using the version check function as described here. If it blinks out a product ID, use that. Otherwise, if it doesn’t list a product ID, it’s probably old enough that it uses the firmware you linked.
Gen1 Emisar D4S Driver issue:
Hi all.
I have an older D4S that’s using this driver, with this type of flashing pads:
For some reason i can’t update it beyond “anduril.2019-12-17.emisar-d4s-219c.hex”
New’er builds beyond that, or Anduril2 doesn’t work on this driver.
My best guess is that some pinouts changed ?
Just got this in an email from Microchip/Atmel, EOL notification on our old gem Atmel Tinys:
https://www.microchip.com/product-change-notifications/#/16686/GBNG-14CATI014
Ouch!!!
Ooops! False alarm...
Hello,
I recently upgraded the firmware of a Sofirn SP36 BLF LH351D 4000k (old version without powerbank-functionality) to Anduril 2 (and added two 5.1kohm pulldown resistors to the USB-C CC1 and CC2 pins to “ask” USB-PD compliant chargers for 5V using C-C cables). I also changed the button LED colors to red and yellow instead of red and green. The yellow LED’s seem to have a higher Vf than the green LED’s though, so the button LED is now unfortunately only visible on “high”. I tried decreasing the on-board current-limiting LED from 1k to 500ohm but that didn’t really do much… Is is possible to change something in the firmware to increase the lower button-brightness? Thanks!
(I flashed the “anduril.2021-12-13.sofirn-sp36.hex” file btw, and so far I noticed that SOS is missing from the Sofirn SP36 (Pro) & Q8 (Pro) diagram, but I won’t miss that haha)
No, that’s not possible. The low brightness is determined by the internal pull-up resistor of the microcontroller.
SOS was not enabled for most targets until recently: ~toykeeper/flashlight-firmware/anduril2 : revision 640
I see, thanks for the quick response! Could I change the 1k resistor to maybe 100ohm to get a higher “low” brigness? The lowest I went to was 400ohm I think… Although when changing resistors the “output” voltage didn’t seem to change all that much so I doubt that’s going to give the desired effect, I suppose I just need to find yellow/amber LED’s with a lower Vf…
I see, thank you!
Which anduril 2 file should I use to refresh the FWAA? This is fet+1 with tiny85. Emisar D4 makes the most sense for me.
I’m fairly certain Lumintop has used the fw3a-219 config (based on the firmware version that blinks out, last 4 digits 0312)
Thanks. I didn’t thought about checking it out before disassembly. A bit strange because the original fw3a has fet+7+1. I know that the new ones have fet+1, but I didnt know that the soft has changed too.
You sure?
Back trace T85 pin config to make sure, but its probably D4 config.
Yes it’s the same pin configuration as D4.
Nice if TK could confirm if 0312 is for dual or triple channel. I just checked my FWAA and it shows 0312 (fw3a 219) too.
Correct, fw3a-219 config is for 3 channels and FWAA only has two. It just means that the 3rd channel does nothing and that likely ramp levels 130-150 are all the same (see PWM2_LEVELS): ~toykeeper/flashlight-firmware/anduril2 : contents of ToyKeeper/spaghetti-monster/anduril/cfg-fw3a-219.h at revision 657
Ive been able to download the tarball code in the past.
For quite some time now, I’m unable to download the tarball at all. Anybody else experiencing this?
Thanks!
Impossible to download for half year or longer.
Thank you. Glad to know it isn’t something I’m doing incorrectly.
Does anybody know the reason it can no longer be downloaded?
It is broken and the Launchpad team doesn’t want to fix it for some reason. Just use breezy to clone the repo.