Publish one ordinary ESP32 Full image per board role

This commit is contained in:
mikecarper committed 2026-09-26 09:29:18 -07:00
1 parent b0b9e53dd7
commit df19760c85
6 files changed
+311 -44

No files matched your search

+11 -4
View File
@@ -46,15 +46,22 @@ an old or failed artifact without a verified sidecar.
For a single ESP32 repeater or room-server target, `auto` selects its matching
combined Full MQTT/USB/WiFi image when that image covers the plain Full recipe.
The direct observer and Full-matrix paths use the same `full-usb-wifi-ota`
artifact and runtime output controls. Plain Full T-Beam SX1262/SX1276 profiles
and the TLora V2 repeater remain alternatives because their MQTT siblings have
lower routing-table capacities.
artifact and runtime output controls. The ordinary bulk release publishes one
Full OTA identity per exact ESP32 board and role. Audited plain targets keep
their identity while compiling the combined observer/ESP-NOW sources; G2 keeps
its deployed observer identity. T-Beam SX1262/SX1276 and TLora V2 choose the
observer in the ordinary release. Their plain Full recipes remain available
as explicit alternatives with different routing capacities. Build one with
`bash build.sh build-firmware <target> --full-exact`, then deliberately install
it over LoRa with `ota pull <MID8> flash` and `ota install` on compatible
hardware and partition layouts.
Standard and reduced OTA images, including images that fit the 1.25 MiB
portable application slot, remain available and remain in the standard matrix
pass. Select `--build-profile standard` to retain the original target and
partition contract. Moving from a plain target to its MQTT sibling changes the
LoRa OTA target identity; existing nodes need an appropriate wired migration.
LoRa OTA target identity; a partition layout change needs its matching
migration step.
For the normal-role partition migrations, the matrix also publishes a
canonical Full image under the normal target identity. Install its matching
merged image over USB once; mOTA rejects the incompatible partition signature
+13 -1
View File
@@ -205,7 +205,9 @@ long ago it was seen. The fit marker:
in-place delta. A matched external-QSPI nRF52 can accept that full codec.
- **[rescue]** - an installable in-place nRF52 delta for the same target, but this running firmware has no
valid app-side EndF. It requires the explicit rescue download and install flow below.
- **[name]** - a different known board or role (for example `[ProMicro_companion_radio_usb]`). Don't install it.
- **[name]** - a different known board or role (for example `[ProMicro_companion_radio_usb]`).
Install it only if you deliberately chose a different role for the same hardware; the installer
still checks the hardware identity and partition layout.
- **[?]** - can't tell (a build with no target id set, e.g. a bare IDE build rather than a release build).
Run it again after a few seconds - discovery happens in the background, so the list fills in. Nothing is
@@ -233,6 +235,16 @@ host folder - nothing is staged on this node. That's how you grab an **exact cop
firmware** off the mesh (to a `.mota` file) so you can later build a *delta* against firmware you don't
otherwise have. (`ota get` is an alias.)
**Deliberate alternate image.** An operator can choose a different target ID
for the same physical board by selecting its exact manifest ID from `ota ls`,
then running `ota pull <MID8> flash` and `ota install`. The target ID controls
which image is discovered and fetched; it does not lock manual installs to
the current role. The hardware identity, codec, image hash, and partition
checks still run. Automatic updates follow the firmware's selected target
(or its declared one-way successor), so use `ota config autofetch off` and
`ota config autoinstall off` if you want to keep an alternate image without
automatic convergence.
**`validate` (warm-start, advanced).** Capturing a full image over the radio is slow. If you have a
*similar* build on the computer (e.g. a fresh recompile of the same firmware), run motatool with
`--seed <that.mota>` and add **`validate`**: the node fetches just the target's block fingerprints, keeps