From a80e68186ddffaba634ceec7ea7ba9a86faa5e39 Mon Sep 17 00:00:00 2001 From: TeTeHacko Date: Mon, 16 Nov 2026 22:02:39 +0100 Subject: [PATCH] docs/ota.md: watchdog recovery, and flag it as a rolling dev release Co-Authored-By: Claude Opus 4.8 --- docs/ota.md | 26 +++++++++++++++++++++++--- 1 file changed, 23 insertions(+), 3 deletions(-) diff --git a/docs/ota.md b/docs/ota.md index 053b6b21..ddd9a98f 100644 --- a/docs/ota.md +++ b/docs/ota.md @@ -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 reboot if the radio hears nothing for (persisted); + catches an OTA that boots with a dead radio + set radio.txstall 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