v0.1.16: never a core voltage below the regulator's clean range (Gaia VSL 0.5, refused voltage, regulatorMinMv, silent chain) #2

Closed
dvb-projekt wants to merge 0 commits from claude/warpaxe-v0116-regler-boden-8e99e8 into main
Owner

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.

  1. NerdAxe Gaia on VOUT_SCALE_LOOP 0.5 (clean 0.5–1.5 V per TPS546D24A table 7-1; BitMaker's 0.25 put 800–970 mV below the clean range). VOUT_MAX 1.4 V, floor 0.8 V, compensation untouched (loop gain scales with VSL, the VSEL strap table points to 0.5 as the board's own divider). Pre-init window (VSL, VOUT_COMMAND/MIN/MAX, COMPENSATION_CONFIG) logged and in vrProbe for 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 fails set_vout.
  2. Refused core voltage is not applied: rail stays, retry once a second, coreVoltageRefused + boardError in the API.
  3. regulatorMinMv in /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.
  4. Silent chain: chainSilentRestarts, chainSilentRestartsSameMv (reset after 10 min of nonces), silentChips, boardError names 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

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. 1. **NerdAxe Gaia on VOUT_SCALE_LOOP 0.5** (clean 0.5–1.5 V per TPS546D24A table 7-1; BitMaker's 0.25 put 800–970 mV below the clean range). VOUT_MAX 1.4 V, floor 0.8 V, compensation untouched (loop gain scales with VSL, the VSEL strap table points to 0.5 as the board's own divider). Pre-init window (VSL, VOUT_COMMAND/MIN/MAX, COMPENSATION_CONFIG) logged and in `vrProbe` for 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 fails `set_vout`. 2. **Refused core voltage is not applied**: rail stays, retry once a second, `coreVoltageRefused` + `boardError` in the API. 3. **`regulatorMinMv`** in `/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. 4. **Silent chain**: `chainSilentRestarts`, `chainSilentRestartsSameMv` (reset after 10 min of nonces), `silentChips`, `boardError` names 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](https://claude.com/claude-code)
board: never a core voltage below the regulator's clean range (v0.1.16)
All checks were successful
CI / Rust checks (pull_request) Successful in 45s
CI / Regulator scenarios (pull_request) Successful in 47s
CI / Rust checks (push) Successful in 45s
CI / Regulator scenarios (push) Successful in 50s
13b0441459
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.

1. NerdAxe Gaia on VOUT_SCALE_LOOP 0.5. The TPS546D24A's reference DAC
   regulates cleanly from 0.25 to 0.75 V, so its recommended output
   range is 0.25 V / VSL to 0.75 V / VSL (SLUSDN0A table 7-1): 1–3 V on
   BitMaker's 0.25, 0.5–1.5 V on 0.5. The Gaia runs its BM1373 at
   800–970 mV, below the clean range on 0.25, where TI promises neither
   accuracy nor the UV warning/fault (7.3.6 note) — the shape of the
   unexplained voltage drop at 440 MHz / 970 mV. VOUT_MAX becomes 1.4 V,
   the top of the DAC's valid VOUT_COMMAND range at that divider (table
   7-34); the floor stays BitMaker's 0.8 V. The VSEL strap table (7-13)
   gives 0.5 for every boot voltage from 0.5 to 1.2 V, so a board around
   a ~1 V core most likely strapped 0.5 and had its MSEL1 compensation
   chosen for it; the voltage loop gain scales with VSL (equations 6/7),
   which is why the compensation block stays untouched and the
   pre-init window (VSL, VOUT_COMMAND/MIN/MAX, COMPENSATION_CONFIG —
   Tps546::window) is logged and shown in vrProbe at boot: after a power
   cycle it is what the straps programmed, the check for the bench.
   The driver itself now refuses an output below 0.25 V / VSL for every
   config (Config::min_vout / max_vout); ESP-Miner's Naja Duo floor of
   1.8 V on the 0.125 divider is lifted to the clean 2 V that way.

   Found on the way: the VOUT fault/warn/margin limits are percentages
   of VOUT_COMMAND in the part (7.6.33 / 7.6.37, OV 105–140 %, UV
   60–95 %); the fixed values written since ESP-Miner map at write time
   and the 0.9 UV warn value maps above 95 % below 0.95 V output, where
   the part NACKs it. Such a NACK no longer fails set_vout (the voltage
   is commanded and conversion turned on; every register is still
   tried): it is kept in Tps546::limit_fault and logged by the board.
   True ratios would change every board and belong on the bench, not
   in this release.

2. A core voltage the regulator refuses no longer counts as applied
   (board.rs: applied_mv stayed wrong, so the rail came back after an
   overheat at a voltage it never had). The rail stays where it is, the
   request is tried again once a second (a bus hiccup passes, a value
   outside the window keeps being refused until a new one comes), the
   log says so once per value, and the API shows coreVoltageRefused and
   boardError.

3. regulatorMinMv in /api/system/info: the regulator's clean floor per
   voltage domain (Profile::regulator_min_core_mv — a TPS546's floor
   never below 0.25 V / VSL, the TPS5364x driver's 800 mV VID floor;
   1000 on every Bitaxe, Nano and Rev 7, 800 on the Gaia and the
   TPS5364x boards). PATCH /api/system refuses a coreVoltage below it
   with 400, whatever the board's published choices say. The web UI's
   minimum is unchanged; WarpTune reads the field as the floor of every
   voltage search (agreed with the Taktsuche session, 2026-10-05).

4. A chain whose chips all went silent was restarted after a minute at
   the same voltage, forever, and nothing said so. Now the API counts
   the restarts (chainSilentRestarts) and the ones in a row at the
   current core voltage (chainSilentRestartsSameMv, back to 0 after ten
   minutes of nonces; two or more = the chips do not run at this
   voltage), shows silentChips, and boardError names the voltage. The
   voltage itself is not changed by the firmware: stepping up on its own
   would move the configured point under a tuner; left for Oliver and
   Warppool #2 to decide.

Host gates green (fmt, clippy -D warnings, tests, no_std build,
scenarios); the ESP32-S3 image builds. Not run on a device: the Gaia
test (voltage against READ_VOUT, error rate, hours of stability, the
window probe after a power cycle) waits for Oliver's OK and the word to
Warppool #2.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
dvb-projekt closed this pull request 2026-10-14 10:03:28 +00:00
All checks were successful
CI / Rust checks (pull_request) Successful in 45s
CI / Regulator scenarios (pull_request) Successful in 47s
CI / Rust checks (push) Successful in 45s
CI / Regulator scenarios (push) Successful in 50s

Pull request closed

Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
dvb-projekt/dvb-WarpAxe!2
No description provided.