-
WarpAxe v0.1.38
Stablereleased this
2026-10-24 07:59:27 +00:00 | 194 commits to main since this releaseDownload mode without a crash, and no passwords in a downloaded core dump. This release changes nothing in how your miner mines. It fixes a crash on the way into download mode, keeps passwords out of a downloaded core dump, and smooths a few rough edges around updates and the pool connection.
What is new.
- Download mode no longer crashes. Up to v0.1.37, System → Download mode crashed on the way into download mode, every time: the USB driver was taken down while log lines still went to its console port, and the next line, often from the Wi-Fi shutting down, hit a USB lock that no longer existed. The miner still ended up in download mode, so flashing worked, but the next start showed a crash. The console now moves back to the chip's own USB port before the driver goes down. Found while switching our miners to the larger core dump partition; with that partition, the crash left a 70 KB dump that showed exactly this chain.
- The crash banner after a USB session tells the truth. The reset with which a flashing tool leaves download mode no longer counts as a crash, even when the chip reports it as a watchdog reset. A real crash on the way into download mode still does. The raw reset cause from the chip now appears next to the reset reason in the log, in
/api/system/info(resetCause) and in the diagnostics file. - Passwords stay out of a downloaded core dump. A core dump holds what the firmware's tasks had in hand at the crash, and that can include a password. Its download (
GET /api/v1/coredump) now replaces the Wi-Fi password, the pool passwords, the hotspot password, the Wi-Fi name and the worker names and addresses withxand corrects the dump's checksum, so the usual tools still read it. Other details, such as the pool addresses or the miner's IP address, stay in the dump. The copy in the miner's flash stays as it was written. - One online install at a time. A second click on Install, or a click from another browser tab, used to queue a second install that started as soon as a failed first attempt ended. The button now turns off as soon as you confirm the install, and the miner refuses a second install request while one is queued or running. Thanks to John11 for the report.
- The pool's certificate waits for the clock. After a USB session or a restart, the miner's clock is carried over from before the reset and can be wrong until the network time arrives. An Sv2 pool's certificate checked against that clock looked invalid, and three such failures sent the miner to the fallback pool for up to five minutes. In the first five minutes after a start, the miner now waits up to 20 seconds for the network time before it connects, and a certificate that fails against an unconfirmed clock no longer counts towards the fallback.
- 'B' on the USB console goes the clean way. Typing
Bon the miner's USB console port puts it into download mode the same way as the web UI does: the chips are switched off first, and a restart marker lets the next start tell the flashing tool's reset from a crash. If the firmware does not respond, the miner still enters download mode on its own after 10 seconds.
Details:
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; for the first installwarpaxe-factory.binandweb-flasher.tar.gz(checksums ininstall.sha256).Downloads