38 releases 38 tags

RSS feed

• v0.1.16 e1e21b175e

  Compare

  WarpAxe v0.1.16 Stable

  dvb-projekt released this 2026-10-06 00:48:54 +00:00 | 270 commits to main since this release

  Never below the regulator's clean range. A core voltage is no longer commanded below the range the board's regulator holds cleanly. A TPS546 regulates accurately, with its undervoltage protection, from 0.25 V to 0.75 V at its reference, which is 1–3 V on the 0.25 divider most boards use and 0.5–1.5 V on 0.5. The driver refuses anything under that, PATCH /api/system answers such a voltage with 400, and /api/system/info publishes the floor as regulatorMinMv (1000 mV on the Bitaxe boards and the BitForge Nano, 800 mV on the NerdAxe Gaia and the TPS53647/53667 boards), so a tuner never searches below it.

  NerdAxe Gaia: regulator in the range the board is built for. The Gaia runs its BM1373 at 800–970 mV, but the stock firmware set its regulator to the 0.25 divider, which leaves those voltages below the clean range: no accuracy promised and no undervoltage warning. WarpAxe now uses 0.5 (clean 0.5–1.5 V). After a power cycle the regulator itself comes up on 0.5 with the same loop compensation, so this is the setting the board's straps were chosen for. On our Gaia at 340 MHz / 950 mV over seven hours the regulator read 945 mV in every minute, with 1,828 shares and none rejected; power and the chips' error rate stayed where they were on 0.25. The change puts the regulator inside its specified range; it does not make the Gaia more efficient.

  Honest about what did not happen. A core voltage the regulator turns down no longer counts as set: the old one stays, the request is retried every second, and the API shows coreVoltageRefused with the reason in boardError. Before, a refused value was taken as applied, so the rail could come back after an overheat stop at a voltage it never had. Chips that stop sending nonces are named in silentChips; chain restarts after a silent minute are counted in chainSilentRestarts, and in a row at the current core voltage in chainSilentRestartsSameMv (two or more: the chips do not run at this voltage). The firmware does not raise the voltage on its own; WarpTune reads the counter and steps up.

  Wi-Fi radio stays awake. WarpAxe left the radio in ESP-IDF's default modem sleep, which wakes only at the access point's beacons, so pool jobs and web answers waited up to ~100 ms for the next one. It now stays awake: on our NerdQAxe++ the ping went from 65 ms on average (up to 200 ms) to 8 ms over a night, web answers came about 20 ms sooner, and a network scan no longer misses a miner whose radio was asleep (seen on a dev board). The cost is a few tenths of a watt.

  Also in this release:

  • vrProbe in /api/system/info: the regulator's window (divider, set point, limits, compensation) as found at boot, before the firmware writes it.
  • Share difficulties in the log are rounded to three decimals instead of a long float (thanks John11).

  One image for every supported board: warpaxe.bin, warpaxe.bin.sha256, warpaxe.bin.sig; for the first install warpaxe-factory.bin and web-flasher.tar.gz (checksums in install.sha256).

  Downloads

  • Source code (ZIP)
    0 downloads
  • Source code (TAR.GZ)
    0 downloads