| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| | | | | | | |
|
| | | |\ \ \ \
| |_|/ / / /
|/| | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
* trunk:
enabled eeprom read/write stabilization by default on recent MCUs, to prevent corrupt data
thefreeman-avr32dd20-devkit: enable boost bypass at boot, so AA/NiMH can boot
avr32dd20-devkit: use unimplemented "CH" pin as a boost bypass control
added "emisar-2ch-fet-joined" build, for D4S w/ lighted switch
documented FW3X swapped pins better
documented Wurkkos TS25/TS11/FC13 distinctions
build.sh: don't require DFPs, newer avr-libc doesn't need them
use BLIP_LEVEL instead of 0 for "blip"s
clarified which-hex-file.md a bit; make sure the model number matches
fw3x: reduced pulsing on low modes
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
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.
|
| |/ / / / / |
|
| | |/ / /
|/| | |
| | | |
| | | |
| | | |
| | | |
| | | | |
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.
|
| | | | |
| | | |
| | | |
| | | | |
(it's an odd case with a 2 channel driver which only uses 1 set of LEDs)
|
| | | | | |
|
| | | | | |
|
| | | | | |
|
| | |/ /
|/| |
| | |
| | |
| | | |
This helps when using a regulator which doesn't like being turned off
and back on quickly.
|
| | | | |
|
| | |/
|/| |
|
| | |\
| |/
|/|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* trunk:
moved version string calculation to bin/version-string.sh
forgot one item in the ChangeLog
ChangeLog: added 2023-12-03 release notes, converted @modelname to &modelname
docs: expanded / reorganized info on Version Check formats
updated MODELS, bin/models.py, and hw/BRANDS...
fw3x: document how it ships with the wrong fuse values, and how to fix it
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
added docs/battery-rainbow.png from old repo, since it's still relevant
added bin/make-release.sh to generate a .zip file ready for release
build-all.sh: re-indented, started organizing code into functions
changed version number to use the latest release tag instead of build date
|
| | |
| |
| |
| |
| |
| | |
Also updated the format slightly, so this rev is: `2023-12-03+2#1`
+N for commits since tag
#1 for dirty
|
| | | |
|
| | |
| |
| |
| |
| | |
(because the @ was causing people to get tagged when their username
happened to be the same as a brand or model name)
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| | |
- 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
|
| | | |
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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
|
| | | |
| | |
| | |
| | |
| | |
| | | |
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)
|
| | | |
| | |
| | |
| | | |
Resulting revision is "$MODEL-0.$HASH" where the hash is the commit short ID
|
| | | | |
|
| |/ / |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| | |
(still needs a proper rewrite, but at least the version.h code is
in a separate function now)
|
| | |
| |
| |
| |
| |
| |
| | |
Before: 2023-11-30
(build date)
After: 2023-10-31-98.1
(latest release tag + number of commits since + dirty flag)
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| | |
The 0144 model number is reserved for the successor to the Meteor M44.
This is Hank's first AA light, so it's assigned as 0161:
- 01: Emisar
- 6: product line 6
- 1: model 1
|
| |/ |
|
| | |
|
| | |
|
| |\
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
| | |
| |
| |
| |
| |
| |
| | |
- 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
|
| |/|
| |
| |
| |
| |
| |
| | |
pr23-digitalcircuit-fix-nofet-bikeflash
* 'fix-nofet-bikeflash' of github.com:digitalcircuit/anduril:
bikeflash: Cap default brightness to max, define
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
| | |
| |
| |
| |
| | |
(users complained, and extended simple UI probably needs to be off by
default in all factory builds anyway)
|
| | | |
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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
...
|
| | | |
| | |
| | |
| | | |
(the protected write macro exists for a reason, and should be used instead)
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
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.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
It had no minimum thermal stepdown defined, so it used MAX_7135 by default,
which was level 149/150 ... thus virtually no regulation.
I also made it easier to switch between internal and external temperature
sensors by just commenting out a few lines in the hwdef.h.
|
| | | |
| | |
| | |
| | |
| | | |
(it used raw ADC units instead of cooked Kelvin units ...
... which was only noticeable on hardware which has different ADC units)
|
| | | | |
|
| | | |
| | |
| | |
| | | |
(the MCU's internal sensor works too, but external is a bit better I guess?)
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
- upgraded to DSM: lower lows, *much* smoother ramp
- made lows more efficient with underclocking
- fixed party strobe being too blurry
- calibrated UI speed / bogomips multiplier
- added readme to document this hardware's multiple quirks
|
| | | |
| | |
| | |
| | | |
strobe
|