v0.1.16: never a core voltage below the regulator's clean range (Gaia VSL 0.5, refused voltage, regulatorMinMv, silent chain) #2
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "claude/warpaxe-v0116-regler-boden-8e99e8"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Four pieces around one rule (Oliver, 2026-10-05): a core voltage is never commanded below the range the regulator holds cleanly, and the firmware says what it did instead of pretending.
vrProbefor the check after a power cycle. Driver refuses any output below 0.25 V / VSL on every config. A NACKed VOUT limit register (percentages of VOUT_COMMAND; the fixed 0.9 UV warn value is refused below 0.95 V) no longer failsset_vout.coreVoltageRefused+boardErrorin the API.regulatorMinMvin/api/system/info(1000 on Bitaxe/Nano/Rev 7, 800 on the Gaia and the TPS5364x boards); PATCH below it → 400. Web UI minimum unchanged.chainSilentRestarts,chainSilentRestartsSameMv(reset after 10 min of nonces),silentChips,boardErrornames the voltage. No automatic step-up (Oliver / Warppool #2 to decide).Host gates green locally (fmt, clippy, tests, no_std, scenarios); ESP32-S3 image builds. No device run yet: the Gaia test waits for Oliver's OK and the word to Warppool #2.
🤖 Generated with Claude Code
Pull request closed