Add repeatable ESP32 partition migration build recipe

This commit is contained in:
mikecarper committed 2026-09-24 00:26:46 -07:00
1 parent 63b97cb1d4
commit 8d4716be5b
5 files changed
+266 -24

No files matched your search

+31 -17
View File
@@ -17,6 +17,30 @@ and its generated table-prefix test; the bridge core is otherwise shared.
| 8 MiB | `default_8MB.csv` | 0x330000 / 0x330000 | Seeed XIAO ESP32-S3 |
| 16 MiB | `default_16MB.csv` | 0x640000 / 0x640000 | Heltec V4 / V4.3 OLED |
## Repeatable ESP32 build recipe
From a clean commit, run the recipe in WSL/Linux. It builds the Full repeater
images first, then both small bridges for each selected board, then verifies
and publishes one ZIP per board. Only one PlatformIO process runs at a time;
`build.sh` can clean the shared `.pio/build` tree between Full targets.
```bash
python3 -B scripts/build_esp32_partition_migration.py \
--version v1.17.1.7-halo-keymind-cascade-dev \
--radio-preset usa-cascadia --profile cascade
```
The default builds both currently validated boards. Add `--board heltec-v4`
or `--board xiao-s3-wio` to build one; repeat `--board` for a selected set.
Use `--dry-run` to inspect the command order without building. The resulting
ZIPs appear under `.releases/esp32-expanded-<commit>/packages/`. The recipe
requires a clean checkout so each ZIP identifies the firmware commit it was
built from. It creates files only; it does not flash a device or erase flash.
Other ESP32 boards need a reviewed flash-size/partition plan, exact LoRa OTA
target ID, and board entry before they can be added to this recipe. Matching
flash capacity alone is not enough to claim a package is safe for a board.
## What the bridge preserves
Before it touches the partition table, the bridge reads the historical
@@ -56,25 +80,15 @@ Keep power stable while the bridge is replacing the 4 KiB table sector. A loss
of power before that point leaves the old table and source intact. After that
small critical write, the selected A copy of the bridge is the recovery path.
## Build and migrate a Seeed XIAO ESP32-S3
## Migrate a Seeed XIAO ESP32-S3
The production bridge is a legacy-slot application image:
```powershell
& "$env:USERPROFILE\.platformio\penv\Scripts\pio.exe" run -e xiao_s3_partition_migrator
```
Build the Full XIAO image with its 8 MiB table:
```powershell
$env:MESHCORE_ESP32_FULL_BUILD = '1'
& "$env:USERPROFILE\.platformio\penv\Scripts\pio.exe" run -e Xiao_S3_WIO_repeater_observer_mqtt
```
Upload the bridge through the legacy node's existing Wi-Fi browser updater.
Use `--board xiao-s3-wio` with the recipe above. Its Wi-Fi bridge is a
legacy-slot application image; its Full image keeps the old repeater's exact
LoRa OTA target ID. Upload `wifi-bridge.bin` from the ZIP through the legacy
node's existing Wi-Fi browser updater.
Then join `MeshCore-Migrate` (password `meshcore-migrate`) and wait for
**Expanded layout ready**. Upload the Full app-only `.bin` from the second
build at `/update`. Do not upload an `-merged.bin`: merged images include
**Expanded layout ready**. Upload `full-application.bin` at `/update`.
Do not upload an `-merged.bin`: merged images include
bootloader and table offsets for cable flashing, not browser OTA.
`xiao_s3_partition_legacy_seed` is a disposable-hardware test image only. It
+8 -5
View File
@@ -5,16 +5,19 @@ Heltec V4/V4.3 OLED repeaters with their normal 16 MiB flash use the shared
It changes Arduino's old `default.csv` layout, with two 1.25 MiB OTA slots,
to `default_16MB.csv`, with two 6.25 MiB OTA slots.
Build the bridge application image:
Build the complete V4 package with the repeatable ESP32 recipe in WSL/Linux:
```powershell
& "$env:USERPROFILE\.platformio\penv\Scripts\pio.exe" run -e heltec_v4_partition_migrator
```bash
python3 -B scripts/build_esp32_partition_migration.py \
--board heltec-v4 --version v1.17.1.7-halo-keymind-cascade-dev \
--radio-preset usa-cascadia --profile cascade
```
Upload `.pio/build/heltec_v4_partition_migrator/firmware.bin` through the
The ZIP contains the Wi-Fi bridge, LoRa bridge, and exact-target Full image.
Upload its `wifi-bridge.bin` through the
legacy browser Wi-Fi updater. Rejoin `MeshCore-Migrate` with password
`meshcore-migrate`; when it reports **Expanded layout ready**, upload the
app-only Full V4 repeater image at `/update`.
ZIP's `full-application.bin` at `/update`.
Do not use an `-merged.bin` in either browser uploader. Merged images contain
bootloader and table offsets for cable flashing. The bridge preserves the