docs/ota.md: watchdog recovery, and flag it as a rolling dev release

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
tthandClaude Opus 4.8 committed 2026-11-16 22:02:39 +01:00
1 parent 7216a50ec3
commit a80e68186d
1 file changed
+23 -3
+23 -3
View File
@@ -10,9 +10,12 @@ The point is the **delta**: a package against the image the node runs is
usually a few kB, so it goes through LoRa in minutes. A full image (~300 kB)
goes only over USB or BLE.
**Experimental.** Tried on XIAO nRF52840 boards over USB and over the mesh
(one hop). A broken new firmware has nothing to fall back to: try every
release on one node within reach before the ones you cannot reach.
**Rolling release on `dev`, for experienced users.** These `-ota` images track
MeshCore `dev`, merged continuously, so a new release lands roughly twice a day
and each delta stays small. There is no stable channel, no second bank, and no
automatic rollback: a bad image that still boots keeps running until you push the
next one, and one that will not boot needs USB/BLE DFU in hand. Run it only on
nodes you can reach, and try every release on one within reach first.
## What a release carries
@@ -68,6 +71,23 @@ What the node checks before it touches its own image:
the rewrite leaves the node in the bootloader (back with USB/BLE DFU), not
in half an image.
## When an update goes wrong
No second bank, no automatic rollback. The checks above stop a *corrupt* package,
but firmware that passes them and still boots into a broken state keeps running.
Two watchdogs catch that, both **off by default** -- turn them on for nodes you
push to:
set radio.silence <min> reboot if the radio hears nothing for <min> (persisted);
catches an OTA that boots with a dead radio
set radio.txstall <min> reboot if the TX queue stalls (RAM only)
get radio.reboots watchdog reboots so far (survives power loss)
get boot why the board last reset, plus the hardfault record
A node that will not boot at all has to be reflashed over USB/BLE DFU. After an
`fw apply` over **BLE** the bond can drop (a supervision timeout while the node
reboots) -- re-pair from the same host; it is not a brick.
## Tools
```bash