docs: OTA side channel, the one engine in tth.meshcore, the phone app
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
a69e97583e
commit
27949062df
2 files changed
+23
-3
No files matched your search
@@ -203,7 +203,13 @@ zůstane v bootloaderu a vrátí se přes USB/BLE DFU.
|
||||
* První `*-ota` obraz se nahraje obyčejně (viz výše), další už jako delta.
|
||||
Nástroje: `tools/ota_push.py` (USB), `tools/ota_mesh_push.py` (přes mesh
|
||||
skrz companion; potřebuje pythonovou knihovnu `meshcore`, admin heslo bere
|
||||
z `[secrets] admin_pw` v `platformio.local.ini`), `tools/ota_pack.py info`.
|
||||
z `[secrets] admin_pw` v `platformio.local.ini`; s `--side` jde přenos po
|
||||
vedlejším kanálu mimo sdílený mesh), `tools/ota_pack.py info`. Přenos samotný
|
||||
je OTA engine kolekce
|
||||
[tth.meshcore](https://git.rfa.cz/tth-pub/meshcore-ansible) (modul
|
||||
`meshcore_fw_ota`), stejný kód pro nástroje i Ansible. Z telefonu: fork
|
||||
aplikace [meshcore-open](https://git.rfa.cz/tth-pub/meshcore-open), správa
|
||||
repeateru → Firmware update (OTA), deltu si najde v releasu sám.
|
||||
Postup a čísla: [docs/ota.md](docs/ota.md).
|
||||
* **Experimentální**: vyzkoušeno na XIAO na lavici přes USB i přes mesh
|
||||
(1 hop). Vadný nový firmware nemá kam se vrátit (není druhá banka) – nový
|
||||
@@ -422,8 +428,14 @@ cut during the rewrite leaves it in the bootloader, back via USB/BLE DFU.
|
||||
* The first `*-ota` image is flashed the usual way (above), later ones go as
|
||||
deltas. Tools: `tools/ota_push.py` (USB), `tools/ota_mesh_push.py` (over the
|
||||
mesh through a companion; needs the `meshcore` Python library, takes the
|
||||
admin password from `[secrets] admin_pw` in `platformio.local.ini`),
|
||||
`tools/ota_pack.py info`. How it works and bench numbers:
|
||||
admin password from `[secrets] admin_pw` in `platformio.local.ini`; `--side`
|
||||
carries the transfer on a side channel, off the shared mesh),
|
||||
`tools/ota_pack.py info`. The transfer itself is the OTA engine of the
|
||||
[tth.meshcore](https://git.rfa.cz/tth-pub/meshcore-ansible) Ansible
|
||||
collection (module `meshcore_fw_ota`), one code for the tools and Ansible.
|
||||
From a phone: the [meshcore-open](https://git.rfa.cz/tth-pub/meshcore-open)
|
||||
fork, repeater management → Firmware update (OTA), which finds the delta in
|
||||
the release by itself. How it works and bench numbers:
|
||||
[docs/ota.md](docs/ota.md).
|
||||
* **Experimental**: tried on XIAO boards on the bench over USB and over the
|
||||
mesh (1 hop). A bad new firmware has nothing to fall back to (no second
|
||||
|
||||
@@ -101,6 +101,14 @@ tools/ota_mesh_push.py /dev/serial/by-id/<companion> <node pubkey prefix> pkg.mc
|
||||
tools/ota_push.py /dev/serial/by-id/<node> pkg.mcfw --apply
|
||||
```
|
||||
|
||||
### From a phone
|
||||
|
||||
The [tth fork of meshcore-open](https://git.rfa.cz/tth-pub/meshcore-open)
|
||||
(Android, Obtainium) has it in the repeater management of an admin: Firmware
|
||||
update (OTA). With no file chosen it reads the node's target and image and
|
||||
takes the delta from the latest release (checked against `SHA256SUMS`); the
|
||||
side channel below is a switch there.
|
||||
|
||||
### Off the shared channel: `--side`
|
||||
|
||||
tools/ota_mesh_push.py <companion> <node> pkg.mcfw --apply \
|
||||
|
||||
Reference in new issue
Block a user