Show live ESP32 partition check in migration guidance

This commit is contained in:
mikecarper committed 2026-09-27 12:57:12 -07:00
1 parent 6c3e52c923
commit 3d984bfe8b
9 files changed
+261 -244

No files matched your search

+5
View File
@@ -1065,6 +1065,11 @@
"Verify that the hardware name and every displayed variant match the physical board.",
"Back up configuration, keys, and radio settings before changing roles or profiles.",
];
if (isExpandedEsp32Infrastructure(profile)) {
common.push(
"If supported by the installed firmware, run get storage.layout to record the live flash size and OTA slots. Firmware version alone does not prove which partition table is installed."
);
}
if (profile.role === "partition-expander") {
return common.concat(
kind === "zip"
+9 -1
View File
@@ -33,6 +33,9 @@ from the published firmware assets.
exact board and role migration ZIP is listed, follow its included README
for a supported Wi-Fi or LoRa route. USB installation uses the matching
merged image instead. An app-only .bin cannot change the partition table.
If the installed firmware supports it, run <code>get storage.layout</code>
to see the live flash size and OTA slots. Firmware version alone does not
prove the installed layout.
</p>
</div>
@@ -241,7 +244,12 @@ Use the exact-board merged image over USB, or a supported exact board and role
staged migration ZIP from the [utility release](https://github.com/mikecarper/MeshCore/releases/tag/utility-v1.17.1.7-halo-keymind-cascade-dev-2d03e098).
Read that ZIP's README before choosing the Wi-Fi or LoRa route. Do not send a
loose app-only Full `.bin` directly to an older layout: the running application
cannot move its own active and inactive partitions.
cannot move its own active and inactive partitions. Run
[`get storage.layout`](cli_commands.md#show-the-storage-layout) on the installed
firmware if available. It reports the live partition table; a version-based
guess cannot confirm the installed layout. See the
[partition lookup guide](esp32_partition_catalog.md) when the old firmware lacks
that command.
Current `full-usb-wifi` profiles use one binary for no external output, USB
packet logging/USB-connected MQTT, direct WiFi MQTT, or both. The picker shows
+1 -1
View File
@@ -7,7 +7,7 @@ The release family contains 536 qualified firmware profiles on five GitHub relea
## Installation
- Match the exact board and radio variant. Use the application image only with a compatible bootloader and partition layout.
- For an ESP32 that needs the expanded Full layout, flash the exact merged image over USB, or use a supported exact board and role migration ZIP from the utility release for a staged Wi-Fi or LoRa route. The 94 migration packages and complete bundle are included there. Read the package README before installation; the bridge writes the partition table and a power loss can require cable recovery. Do not send a loose app-only Full image directly to an older layout.
- For an ESP32 that needs the expanded Full layout, flash the exact merged image over USB, or use a supported exact board and role migration ZIP from the utility release for a staged Wi-Fi or LoRa route. The 94 migration packages and complete bundle are included there. Read the package README before installation; the bridge writes the partition table and a power loss can require cable recovery. Run `get storage.layout` on the installed firmware if supported to see its live partitions; version alone cannot prove the installed layout. Do not send a loose app-only Full image directly to an older layout.
- nRF52 application UF2 and DFU packages do not install a bootloader. Use the matching OTAFIX 2.4.8 bootloader where required.
- The RAK 3x72, Tiny Relay, Wio-E5 Mini, and Wio-E5 USB Companion images retain their framed USB transport and 32 KiB LittleFS area. Packet diagnostics are omitted on these four 256 KiB STM32WL targets to keep the application within flash.