• v0.1.37 3e0188ba64

    WarpAxe v0.1.37
    All checks were successful
    CI / Rust checks (push) Successful in 56s
    CI / Regulator scenarios (push) Successful in 55s
    Stable

    dvb-projekt released this 2026-10-23 19:32:56 +00:00 | 202 commits to main since this release

    A crash now leaves a trace. This release changes nothing in how your miner mines. It leaves more to look at if WarpAxe ever crashes, and it removes a likely cause of the crash that started this.

    Why. A user's miner came back from the restart at the end of an online update with a crash (reset reason panic) instead of a normal restart, and left no core dump. Looking into it showed that this firmware's crash dumps are 60–64 KB, while the partition that holds them is 64 KB; a dump that does not fit is not written at all. So whether a crash left a dump was largely luck.

    What is new.

    • Last words. A Rust panic now writes the task, the file and line and the message into memory that survives the reset; a stack overflow writes the name of its task. The next boot logs them, and the diagnostics file carries them as lastWords, whether or not a core dump was written. Other crashes, such as a hardware exception or a watchdog reset, leave no last words; for those there is the core dump.
    • A crash during a restart is named. If the miner crashes while restarting (after an update or an upload, or a restart from the web UI), the next boot records an event that says so and names the step: while switching the chips off, or in the system reset itself.
    • A likely cause, fixed. The interrupt watchdog now allows 1000 ms instead of 300 ms. Erasing a flash sector can take up to 600 ms, and while it runs, the watchdog is not fed, so the old limit could run out in the middle of an erase. On our Bitaxe Gamma, an image uploaded after 39 minutes of uptime came back with an interrupt-watchdog reset. The restart event named the step "in the system reset", the moment the restart writes its record to flash, and there was no core dump even though the partition was 256 KB: a crash during a flash operation never leaves one, because the dump cannot be written while the flash is busy. The user's miner, on v0.1.34, reported a panic rather than a watchdog reset, and it too wrote to flash (its install record) shortly before the reset; so this is a probable cause, not a proven one. If a flash write during a restart takes 100 ms or longer, the log now says so.
    • Updates report themselves on every bootloader. A finished update or upload now shows up as "installed" in the event log even on miners whose bootloader predates v0.1.22, but not when the miner rolled back to the previous version. Like the restart event, this works for restarts begun by v0.1.37 or later: the update from an older version to v0.1.37 is not yet covered.
    • No crash banner after an install over USB. The browser installer, espflash and esptool -a watchdog-reset leave download mode with an RTC-watchdog reset, and since v0.1.34 WarpAxe took that reset for a crash: the browser installer brought up the crash banner after every install. Now that reset no longer counts as a crash on the first boot of a newly flashed image, or after a restart into download mode; it still does after a rollback to the previous version. A panic, an interrupt-watchdog reset or a task-watchdog reset always counts as a crash. The banner still shows when you reflash the image that ran last over USB without starting at System → Download mode. The price: a real watchdog hang in the very first moments of a new image goes unreported.
    • A 256 KB core dump partition. The partition grows from 64 to 256 KB, so a full dump fits. It comes only with an install over USB, because an online update never rewrites the partition table. The browser installer keeps your settings; warpaxe-factory.bin flashed with esptool starts with empty settings. A miner first installed before v0.1.37 and since updated only online keeps the 64 KB partition: last words and the restart event work there too.

    Details and the investigation: docs/12-Panic-without-a-core-dump-in-the-restart-after-an-update.md.

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

    Downloads