• v0.1.45 a8cb5c1db9

    WarpAxe v0.1.45
    All checks were successful
    CI / Rust checks (push) Successful in 1m44s
    CI / Regulator scenarios (push) Successful in 53s
    Stable

    dvb-projekt released this 2026-11-16 05:47:52 +00:00 | 49 commits to main since this release

    A clock and a night mode on the display, the Naja Duo at its full power, and a power-supply sag watch. The display can show the time, and dims itself at night. The OLED moves its picture a pixel every ten minutes, so nothing burns in. On the Naja Duo the boot key now steps through the display pages, its current and power limits follow the maker's overclock, and WarpTune can take it up to 550 MHz. A miner that runs without trouble mines as before; the clock and the night mode are off until you switch them on.

    New.

    • A clock page and night mode. The colour displays get a page "clock": the time large, with weekday, date, week and hashrate beside it, and below it the block height with the price and fee when market data is on, else the pool and the uptime. The OLED gets a clock slide with time, short date and hashrate. Neither is among the factory pages; you add them on the Settings page under Pages (on the OLED: OLED slides), and night mode under Clock and night mode. In night mode (off by default, 22:00 to 07:00, brightness 50 %) the display shows a dimmed clock screen instead of the pages: on the colour displays the time, date, hashrate and temperature, on the OLED its clock slide. A key press brings the full display back for 30 seconds, and an alert (a found block, an overheat stop, an update) lights it at full brightness. Time format: 24 hours, or 12 hours with AM/PM in time zones that use it (clockFormat auto/24h/12h). API: nightMode, nightStart, nightEnd, nightBrightness, nightActive, clockFormat, clock12h.
    • Night brightness in even steps. On the OLED (Bitaxe Gamma and others with the 128×32 screen), contrast, pre-charge and VCOMH go down together, so 100 %, 75 % and 50 % look clearly different and a low night setting is really dark. On the NerdQAxe++, NerdOctaxe and the other Nerd boards, the backlight driver (AW9364) does not dim by PWM: it counts pulses. The firmware sends the pulses, and the brightness picks one of its 16 levels. The Naja Duo and Gamma Hex dim by PWM.
    • OLED: protection against burn-in. The picture moves by one pixel every ten minutes, through twelve positions (at most one pixel left or right, one up or two down). All OLED screens leave room for it, so nothing is cut off; the first ten minutes after a start stay unshifted.
    • Naja Duo and Gamma Hex: the boot key steps the display pages. These boards have no page key. A short press now goes to the next page, holding it for a second goes to the home page. The press that wakes the display does nothing else.
    • Power supply sag watch. The firmware compares the input voltage with the chips off against the voltage while hashing. If it drops by 8 % of the nominal input or more for a full minute, the System page shows a warning with the drop in volts (gone again below 6 %). It only reports; nothing is switched off. API: vinIdle, vinLoad, vinSag, psuSagWarning.
    • Hint for a block that is not Bitcoin's. If the pool reports a found block below height 900,000 while the coin setting says BTC (a pool for another coin, with the ticker left on BTC), the block banner shows the coin as "?", leaves out the mempool link and suggests checking the Coin setting.

    Naja Duo.

    • Current limits 61/68 A (warning/fault), as on ESP-Miner's master for the maker's 600 MHz overclock, and maxPower 105 W instead of 60 W. The firmware only reports maxPower; WarpTune takes 90 % of it (94.5 W) as its power limit, and at 60 W it skipped the Max step before measuring anything.
    • WarpTune up to 550 MHz at 1120 mV. The clock options now go up to 550 MHz and the core voltage up to 1120 mV, the voltage of the maker's own overclock; WarpTune's Max mode stops there. On our bench, 550 MHz needed about 1100 mV on the weaker chip, and at 600 MHz the regulator on the back reached 84 °C without a fan there. A core voltage above 1120 mV is no longer accepted; a higher value stored by an earlier version is set to 1120 mV at start. With the factory target temperature of 50 °C, the fan runs close to full speed at 550 MHz. In OC mode the clock can still be set up to 600 MHz by hand.
    • Expected hashrate. Both chips' counters read about 6,900 small cores, as on the Gaia; the expected hashrate is now based on the chip's 6,860 instead of ESP-Miner's 6,725, which put it 2.5 % low (reported as ESP-Miner issue #2102).
    • VOUT up to 2 V per voltage domain. On boards with two domains in series (Naja Duo, Gamma Hex, NerdQAxe++ Rev 7) a core voltage above 1000 mV read over 2 V and was dropped, so VOUT, the core voltage and the power were missing.

    What is fixed.

    • Settings form on a Bitaxe with an old chip stop. v0.1.32 lowered the Bitaxe chip stop ceiling to 75 °C. A Bitaxe that still had a higher chip stop stored from before could not save its settings: the browser refused the whole form. The stored value is now brought down to the ceiling at start-up, and the form saves again. The miner already stopped at 75 °C before.
    • A pool session that cannot send shares ends. The thread that sends shares now runs on a PSRAM stack. Before, with little internal memory left, it could fail to start, and the session took work and hashed without ever sending a share. If it still cannot start, the session ends, so the retry and the fallback pool take over.
    • Error rate colours on the BM1373. The Gaia and the Naja Duo showed their error rate without a colour. Green is now below 5 %, yellow from 5 %, red from 9 %; the BM1370 keeps 1 % and 5 %.
    • NerdNOS: the core voltage as it is. On the NerdNOS, whose core rail is fixed, the API and the self-test reported the stored but unused setting (1150 mV); they now report the board's 1400 mV.
    • One update progress bar. The System page showed two bars during an update; now it shows one.

    Smaller image. About 185 KB smaller than v0.1.44: the size work took out 232 KB (start-up pictures packed, API documents built in one call each, debug lines left out), and the clock and night mode added some of it back. This leaves room for future updates.

    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