Yeah, avrdude has always supported x86_64, which is what Intel Apple devices use. It seems like it is buildable for arm64, at least, there just isn’t official support yet. It depends how you installed avrdude, if you built it from source or not, but I really don’t know enough about the apple ecosystem to know if it’ll be possible without further changes, because it looks from the issue I linked above that there are some dependency issues.
I’m not sure how ZFlasher AVR does it for Android (which is also arm64), potentially they build a version of avrdude specifically for arm64, but you’re going to need a package for arm64 (aka aarch64), from somewhere that’s compatible with that environment, packages that say x64 or x86_64 (also different names for the same thing) aren’t going to work there.
That’s not particularly hard since it’s just a serial device, avrdude already knows the right protocol, the issue with mobile devices is more likely to be making it accessible in a directly-usable way.
After I noticed that my D4K did in fact have aux issues with 2022.10.21.0273, I compiled multi-channel rev 721 and flashed it. Now the light won’t go warmer than about 31C after a factory reset and has a very aggressive rampdown.
Also… Apologies if I missed it, is there a non compile time option to change how often the battcheck aux readings are taken?
I’m on the edge of levels and the 1 second color strobing is much more annoying than every 8 seconds it was before.
No way to change it easily (would need code changes) AFAIK. Use the light for a few seconds and it should drop enough, I guess.
Did you recalibrate the thermal sensor? If it was cold when it was reflashed that might happen, otherwise it sounds like a regression of that bug from before.
Ah, that’s not a big deal, I’ll hunt it down in the code if it really becomes too annoying.
I did a factory reset at room temp. Light was reading 31C at rampdown and felt ever so slightly warm.
Flashed back to 2022.10.21.0273, factory reset, will hit the 45C limit.
Looks like you’d be looking at adc_deferred() (called from fsm-main.c) - the flag for whether the ADC value is processed or not is adc_deferred_enable, which gets set by an interrupt handler in fsm-standby.c whenever the ADC sends its interrupt (meaning it has a new measurement).
If you added some logic here to set adc_deferred_enable and call adc_deferred() less often (e.g. every other or every nth interrupt), afaik this shuld reduce the measurement frequency.
Note that this will also increase the frequency for temperature checks, so isn’t ideal, and might affect other stuff elsewhere, nothing was immediately obvious to me but not 100% confident on that, but it’s close enough to the hardware that I’d rather provide advice than actual direct usable changes (but happy to look into it more if you’re interested).
Alternatively, you could modify adc_deferred() itself to do something like skip processing if adc_step is 0 (voltage) unless it’s every nth time, while leaving temperature unchanged. Same disclaimer here.
If you do this change I might maybe suggest reducing VOLTAGE_WARNING_SECONDS (default 5) to 1 or 2 because this somewhat reduces the speed of action of LVP, especially if you make it a long delay.
First of all, I want to say thank you for such a great customizable and powerful firmware. Been playing with different versions for a week or so, I’m a fan of multi-channel branch now – new features are quite neat!
I do have some questions, though.
Having two Olight lights, I really dig the smooth turn-on and turn-off effects on those, when the brightness quickly ramps up and down. Are there any plans to implement something like this for Anduril? I’ve found starryalley’s fork with smooth startup mode implemented. I adapted it for multi-channel r721 (can share the patch, but it’s pretty straightforward). Aside from cool-looking effect, it serves another purpose – there is no initial bright blink from turning on when you do clicks from off state (to 4C / 7C / 7H, for example). I’m afraid I don’t yet have enough understanding of how the firmware works internally to correctly implement similar effect for turn-off, though. I have found USE_SET_LEVEL_GRADUALLY macro, but it seems it’s being used only for brightness change due to thermal regulation.
For lights with both backlit non-RGB buttons and AUX LEDs (like Emisar D4K / D2 and many others), It will be nice to have the ability to set the states for them separately, especially with this new post-voltage feature. I’ve found an old mod from TimMcMahon and adapted it for r721, with addition of different settings for off and lockout states (and changing the hotkey to 8C). I can share this patch as well, but again, while it seems to be working fine, I’m not sure I did it the right way.
Anyone know off hand what the last known fully working version of A2 for the dm11/d4 boost driver is?
I think 7/29/2022 was what was on my boost d4 non k initially and it doesn’t have any aux or thermal bugs. But I didn’t start taking notes on versions until after I updated off factory fw.
Managed to get the dopamine machine working again for a bit and found/fixed the bug that was causing post-off voltage to blink red when initially activated (appears to be caused by the ADC not reading the voltage when the switch is pressed?). Here’s a set of builds for the latest version (721) with the fix for anyone who’s interested.
The bug was introduced in revision 670 and fixed in 712. The dm11-boost in the above release (File on MEGA) is based on the latest version (721) with an additional bugfix.
If you’re specifically looking for the last old version (i.e. before the multichannel refactor), it’d be v657 (with tactical mode added). Here’s a build: 27.1 KB file on MEGA
Noticed a few additions to the original version (some references to “Tactical Mode” and other tint ramping/aux options). I’m guessing they are just updated version revisions, but curious if this will progress as An-2 platform or become somewhat of an ‘Anduril 3’ compilation (?).
Some manufacturers are kind of bad about updating and use older firmware versions (sometimes as old as 2021), new features like tactical mode will be in the current releases as well as likely/ideally in new lights going forward, but you can always update your lights to run the latest version.
