aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Merge branch 'pr52-SiteRelEnby-manual-actions' into trunkSelene ToyKeeper2024-03-291-1/+1
|\ | | | | | | | | * pr52-SiteRelEnby-manual-actions: Allow manually running GitHub actions workflows
| * Merge branch 'manual-actions' of github.com:SiteRelEnby/anduril into ↵Selene ToyKeeper2024-03-291-1/+1
|/| | | | | | | | | | | | | pr52-SiteRelEnby-manual-actions * 'manual-actions' of github.com:SiteRelEnby/anduril: Allow manually running GitHub actions workflows
| * Allow manually running GitHub actions workflowsSiteRelEnby2024-02-291-1/+1
| | | | | | | | https://docs.github.com/en/actions/using-workflows/manually-running-a-workflow
* | Merge branch 'pr46-SiteRelEnby-bugfix-tacmode-without-momentary' into trunkSelene ToyKeeper2024-03-282-6/+8
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | Allows user to disable Momentary Mode at compile time, while keeping Tactical Mode. * pr46-SiteRelEnby-bugfix-tacmode-without-momentary: fixed Tactical Mode's strobes when Momentary Mode not enabled Bugfix: Tactical mode has a dependency on momentary mode
| * | fixed Tactical Mode's strobes when Momentary Mode not enabledSelene ToyKeeper2024-03-281-3/+5
| | |
| * | Merge branch 'bugfix-tacmode-without-momentary' of ↵Selene ToyKeeper2024-03-282-3/+3
|/| | | | | | | | | | | | | | | | | | | | github.com:SiteRelEnby/anduril into pr46-SiteRelEnby-bugfix-tacmode-without-momentary * 'bugfix-tacmode-without-momentary' of github.com:SiteRelEnby/anduril: Bugfix: Tactical mode has a dependency on momentary mode
| * | Bugfix: Tactical mode has a dependency on momentary modeSiteRelEnby2024-02-022-3/+3
| |/ | | | | | | | | | | | | Use case 1: Updating a t85 light, where tactical mode is useful but takes some squeezing, and momentary is less useful Use case 2: Custom builds for people who don't like/want momentary mode
* | Merge branch 'pr49-SiteRelEnby-tactical-mode-3c-fix' into trunkSelene ToyKeeper2024-03-281-0/+5
|\ \ | | | | | | | | | | | | | | | | | | | | | Fixes [bug #40](https://github.com/ToyKeeper/anduril/issues/40) Don't change channel during 3C in Tactical Mode. * pr49-SiteRelEnby-tactical-mode-3c-fix: Bugfix: Prevent switching channel modes when in tactical mode
| * | Merge branch 'tactical-mode-3c-fix' of github.com:SiteRelEnby/anduril into ↵Selene ToyKeeper2024-03-281-0/+5
|/| | | | | | | | | | | | | | | | | | | | pr49-SiteRelEnby-tactical-mode-3c-fix * 'tactical-mode-3c-fix' of github.com:SiteRelEnby/anduril: Bugfix: Prevent switching channel modes when in tactical mode
| * | Bugfix: Prevent switching channel modes when in tactical modeSiteRelEnby2024-02-141-0/+5
| |/ | | | | | | Fixes issue https://github.com/ToyKeeper/anduril/issues/40
* | increased voltage precision from 0.025V to 0.02VSelene ToyKeeper2024-03-2715-86/+87
| | | | | | | | (so 0 to 255 now goes from 0.00V to 5.10V)
* | fixed inaccurate comment (thanks to xikteny for spotting it)Selene ToyKeeper2024-03-231-1/+1
| |
* | enabled eeprom read/write stabilization by default on recent MCUs,Selene ToyKeeper2024-02-022-4/+12
| | | | | | | | | | | | | | | | | | | | | | to prevent corrupt data This was enabled on more build targets before, but the *_ENABLE_PIN definition names changed and the eeprom code didn't, so it was not compiled in for a few months on some lights which probably needed it. To fix that, it's now enabled by default on everything bigger than attiny85, since it doesn't really hurt anything if it's enabled when not needed.
* | thefreeman-avr32dd20-devkit: enable boost bypass at boot, so AA/NiMH can bootSelene ToyKeeper2024-02-021-0/+1
|/
* avr32dd20-devkit: use unimplemented "CH" pin as a boost bypass controlSelene ToyKeeper2024-01-302-2/+33
| | | | | | | For 3V LEDs on a boost/buck dual fuel driver, this allows routing power around the boost converter in li-ion mode, to reduce resistance and increase maximum output. The AA/NiMH mode is unaffected, and boosts as normal.
* added "emisar-2ch-fet-joined" build, for D4S w/ lighted switchSelene ToyKeeper2024-01-106-0/+512
| | | | (it's an odd case with a 2 channel driver which only uses 1 set of LEDs)
* documented FW3X swapped pins betterSelene ToyKeeper2023-12-171-3/+7
|
* documented Wurkkos TS25/TS11/FC13 distinctionsSelene ToyKeeper2023-12-174-6/+44
|
* build.sh: don't require DFPs, newer avr-libc doesn't need themSelene ToyKeeper2023-12-151-6/+8
|
* use BLIP_LEVEL instead of 0 for "blip"sSelene ToyKeeper2023-12-153-2/+7
| | | | | This helps when using a regulator which doesn't like being turned off and back on quickly.
* clarified which-hex-file.md a bit; make sure the model number matchesSelene ToyKeeper2023-12-111-4/+7
|
* fw3x: reduced pulsing on low modesSelene ToyKeeper2023-12-101-2/+2
|
* moved version string calculation to bin/version-string.shSelene ToyKeeper2023-12-053-13/+63
| | | | | | Also updated the format slightly, so this rev is: `2023-12-03+2#1` +N for commits since tag #1 for dirty
* forgot one item in the ChangeLogSelene ToyKeeper2023-12-051-0/+2
|
* ChangeLog: added 2023-12-03 release notes, converted @modelname to &modelnameSelene ToyKeeper2023-12-031-52/+115
| | | | | (because the @ was causing people to get tagged when their username happened to be the same as a brand or model name)
* docs: expanded / reorganized info on Version Check formatsSelene ToyKeeper2023-12-032-44/+63
|
* updated MODELS, bin/models.py, and hw/BRANDS...Selene ToyKeeper2023-12-033-81/+112
| | | | | | | | - changed column order to (model, mcu, name) - changed column sizes (auto-sized w/ 2 spaces between columns) - made it handle hex digits in model numbers - reserved 1900 to 2199 for years only, not model numbers - noted gChart and thefreeman sharing a brand ID
* fw3x: document how it ships with the wrong fuse values, and how to fix itSelene ToyKeeper2023-12-031-0/+5
|
* Merge branch 'github-ci-fix-version-tags' into trunkSelene ToyKeeper2023-12-022-4/+16
|\ | | | | | | | | | | | | | | | | | | | | | | Fixed missing version strings during github CI builds. Made "git describe" work within github's CI environment, so it can detect the most recent release tag and generate a version number for each build. * github-ci-fix-version-tags: github CI: fetch history too, to allow detection of version tags build-all: handle the case where "git describe" can't get any tags run CI on all branches, not just on trunk fetch tags on CI checkout, so 'git describe' can work
| * github CI: fetch history too, to allow detection of version tagsSelene ToyKeeper2023-12-021-1/+2
| | | | | | | | | | | | It needs history to determine which tag precedes the current commit. This could be expensive on large repos, but for Anduril it seems to only increase the checkout size by about 40% or so. (11 MiB -> 15 MiB)
| * build-all: handle the case where "git describe" can't get any tagsSelene ToyKeeper2023-12-021-0/+5
| | | | | | | | Resulting revision is "$MODEL-0.$HASH" where the hash is the commit short ID
| * run CI on all branches, not just on trunkSelene ToyKeeper2023-12-021-4/+7
| |
| * fetch tags on CI checkout, so 'git describe' can workSelene ToyKeeper2023-12-021-0/+3
|/
* added docs/battery-rainbow.png from old repo, since it's still relevantSelene ToyKeeper2023-12-011-0/+0
|
* added bin/make-release.sh to generate a .zip file ready for releaseSelene ToyKeeper2023-12-012-1/+56
|
* build-all.sh: re-indented, started organizing code into functionsSelene ToyKeeper2023-11-301-75/+84
| | | | | (still needs a proper rewrite, but at least the version.h code is in a separate function now)
* changed version number to use the latest release tag instead of build dateSelene ToyKeeper2023-11-303-5/+19
| | | | | | | Before: 2023-11-30 (build date) After: 2023-10-31-98.1 (latest release tag + number of commits since + dirty flag)
* fixed RGB aux turning on in momentary mode when post-off voltage was enabledSelene ToyKeeper2023-11-301-6/+9
|
* oops, flashing script should actually flash ... not just echo a commandSelene ToyKeeper2023-11-301-1/+1
|
* Merge branch 'pr23-digitalcircuit-fix-nofet-bikeflash' into trunkSelene ToyKeeper2023-11-302-4/+10
|\ | | | | | | | | | | | | | | | | Fixed bike mode's default brightness so it won't be wildly miscalibrated on lights with high regulated modes. * pr23-digitalcircuit-fix-nofet-bikeflash: saner defaults for the default biking level bikeflash: Cap default brightness to max, define
| * saner defaults for the default biking levelSelene ToyKeeper2023-11-302-11/+9
| | | | | | | | | | | | | | - set DEFAULT_BIKING_LEVEL in bike mode's header file - use RAMP_SIZE/3 by default - limit to MAX_BIKING_LEVEL if necessary - get rid of any ties to MAX_1x7135 because it's kind of an obsolete symbol
| * Merge branch 'fix-nofet-bikeflash' of github.com:digitalcircuit/anduril into ↵Selene ToyKeeper2023-11-301-1/+9
|/| | | | | | | | | | | | | pr23-digitalcircuit-fix-nofet-bikeflash * 'fix-nofet-bikeflash' of github.com:digitalcircuit/anduril: bikeflash: Cap default brightness to max, define
| * bikeflash: Cap default brightness to max, defineShane Synan2023-11-281-1/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Cap fallback default bike flasher brightness to stay below MAX_BIKING_LEVEL, fixing noFET/boost driver builds where MAX_1x7135 is above MAX_BIKING_LEVEL. Add the optional define DEFAULT_BIKING_LEVEL to set the default bike flasher brightness. This is NOT checked against MAX_BIKING_LEVEL, for simplicity. Alternatively, strobe-modes.c could be updated to check if the value exceeds MAX_BIKING_LEVEL at runtime. However, that might take up more flash space. Migrated from https://code.launchpad.net/~digitalcircuit/flashlight-firmware/anduril2_fix_nofet_bikeflash/+merge/408124
* | sofirn-lt1s-pro: disable memory timer and extended simple UI by defaultSelene ToyKeeper2023-11-301-3/+3
| | | | | | | | | | (users complained, and extended simple UI probably needs to be off by default in all factory builds anyway)
* | minor documentation updatesSelene ToyKeeper2023-11-302-8/+9
| |
* | Merge branch 'avr32dd20-devkit' into trunkSelene ToyKeeper2023-11-3083-1296/+2633
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Added support for AVR DD MCUs, particularly avr32dd20. Also did a bunch of refactoring for how MCU support works, cleaned up the ADC code, switched to consistent internal formats for voltage and temperature, fixed the FW3X, and some other little things. * avr32dd20-devkit: (28 commits) eliminated direct CCP register access from arch/attiny1616 made the avr32dd20 flashing script more universal added a build target for FW3X with manually-fixed RGB aux wiring prevent future issues like the FW3X had fixed FW3X thermal regulation fixed incorrect temperature history for a few seconds after waking fsm/adc: removed dead code FW3X: fixed external temperature sensor FW3X: multiple upgrades... fw3x: fixed swapped red+blue, fixed battery measurements, added police color strobe fixed ADC on sp10-pro fixed ADC on attiny85 and related builds fixed ADC on attiny1634 and related builds more ADC / DAC / MCU progress... avr32dd20-devkit: make the defaults a bit more dev friendly (realtime voltage colors, and no simple UI by default) ADC voltage: battcheck 3 digits, fixed t1616, switched back to 8-bit internal volt unit got ADC voltage+temp working on avrdd... but broke all other builds/MCUs 1.55V AA battery should not show as "white" voltage color, only purple started refactoring fsm/adc.*, but need a checkpoint before continuing added dac-scale.py: short script to calculate avrdd DAC+Vref values from level_calc.py ramp data ...
| * | eliminated direct CCP register access from arch/attiny1616Selene ToyKeeper2023-11-301-2/+2
| | | | | | | | | | | | (the protected write macro exists for a reason, and should be used instead)
| * | made the avr32dd20 flashing script more universalSelene ToyKeeper2023-11-301-5/+32
| | |
| * | added a build target for FW3X with manually-fixed RGB aux wiringSelene ToyKeeper2023-11-303-3/+21
| | |
| * | prevent future issues like the FW3X hadSelene ToyKeeper2023-11-281-4/+5
| | | | | | | | | | | | | | | | | | | | | 1/3rd of the ramp size is probably a more reliable default than MAX_1x7135. The 7135-based reference points need to eventually be removed entirely and replaced by something more universal, but for now at least don't fail when a thermal stepdown isn't defined.
generated by cgit v1.2.3 (git 2.25.1) at 2026-03-28 19:50:23 +0000