-
WarpAxe v0.1.44
Stablereleased this
2026-11-12 21:04:45 +00:00 | 95 commits to main since this releaseA clock of its own per chip, the Bitaxe Naja Duo on our bench, and more internal memory. On boards with more than one chip, each chip can now run at its own clock, so the weakest chip no longer sets the voltage for all of them. The Naja Duo now runs on our bench, and its second chip now gets a setting that its init never delivered. A single-chip miner with no trouble mines as before.
New.
- A clock of its own per chip (
chipFreqOffsets, MHz added to the frequency per chip). The firmware writes each chip's clock to that chip alone, without restarting the chain, and no chip passes its own target clock on the way. The expected hashrate, the self-test and the watchdogs follow each chip's clock. Limits: no chip above the board's maximum or below half the base clock. On boards whose chips sit in series (Naja Duo, Gamma Hex, NerdQAxe++ Rev 7) the clocks may lie at most 25 MHz apart (or 8 % of the base clock, where that is less), because a slowed chip takes voltage from the other. The web interface has a field per chip under frequency and voltage. For now the offsets are set by hand; an automatic search in WarpTune is planned for a later WarpPool release. Tested on a NerdOctaxe at 625 MHz: one chip set 25 MHz lower hashed about 4 % less, the other seven were unchanged. - New API fields for tuners:
asicFrequencies(each chip's clock),chipFreqOffsetsSupported,voltageDomains,chipFreqOffsetSpread, and per chiphashCount(a cumulative hash counter, so a tuner gets each chip's hashrate from two readings) andcounterRestarts(a chip that reset itself).minerStackFreereports the mining loop's spare stack. - Bitaxe Naja Duo on our bench. It has run on our bench since 12 November; the web interface still marks it untested until it has run for some days. It uses ESP-Miner's BM1373 init by default, with a slower variant and NerdOS's init as fallbacks (
chipInit). Its 320×170 colour screen shows the Bitaxe logo as printed on the board, with "1201" at boot, and the self-test reads both phases of its stacked regulator. Found on the way: the init sent the second chip's domain-end IO strength (register 0x58) to an address no chip has (0x10 shifted right by two, as in ESP-Miner), so the second chip never got it. Single-chip writes on the BM1373 now go to the chip's full address; reported to ESP-Miner as issue #2094.
What is fixed.
- Two-chip boards: no false overheat stop before the chips run. On a user's Gamma Turbo, chip 1's sensor read 72.75 °C eleven seconds after power-on, before the chips were running. That is over the 70 °C stop line, so the start stopped and the chips stayed off for a minute. Until the chips have power and the chain has answered after a reset or power-on, the chip sensors of the Gamma Turbo and the Naja Duo now count as no reading. The regulator's own sensor keeps watching throughout, and once the chips run the stop line applies as before.
- Back on after a regulator fault. On boards whose chip sensor gives nothing while the chips are off (Bitaxe Gamma, the two-chip boards), the chips stayed off after a regulator fault until someone switched them on. They now come back after the minute off with the regulator cool, as after an overheat stop; a third stop within the hour still latches.
- Self-test phase check. A phase reading taken while the chips draw no load (all phases together under 5 A) is skipped instead of switching the chips off.
- Display orientation on import. A Naja Duo or Gamma Hex coming from AxeOS 2.15 showed its screen upside down; the AxeOS rotation is now taken per display type.
- More internal memory. The mining loop's large state moved to PSRAM and its stack shrank, so more internal RAM stays free than under v0.1.43 (measured on a NerdAxe Gaia on a TLS pool: about 30 KB instead of 25 KB).
One image for every supported board:
warpaxe.bin,warpaxe.bin.sha256,warpaxe.bin.sig; for the first installwarpaxe-factory.binandweb-flasher.tar.gz(checksums ininstall.sha256).Downloads
- A clock of its own per chip (