Publish 1.18.0.1 release catalogs and bootloader picker choices

This commit is contained in:
mikecarper committed 2026-10-24 13:58:25 -07:00
1 parent 03214a16df
commit ec478c30ed
17 files changed
+37893 -8184

No files matched your search

File diff suppressed because it is too large. Load diff
+26 -2
View File
@@ -1048,6 +1048,17 @@
profile.variant = variantWithoutSensorMarker(profile.variant);
}
}
const embedded = controls.embeddedBootloader;
if (profile.sensorProfile && ["repeater", "room"].includes(profile.role) &&
sensorSourceMatches && controls.embeddedBootloaderSource === sensorSource &&
embedded && /^\d+(?:\.\d+){2}$/.test(embedded.release || "") &&
embedded.automatic_delay_seconds === 70 && embedded.image_bytes === 40960 &&
embedded.activation === "ota bootloader update" &&
/^[0-9a-f]{64}$/.test(embedded.candidate_sha256 || "") &&
/^[0-9a-f]{64}$/.test(embedded.asset_sha256 || "") &&
profile.target.endsWith("-with-bootloader-" + embedded.release + "-" + profile.sensorProfile)) {
profile.embeddedBootloader = embedded;
}
}
function variantWithoutSensorMarker(value) {
@@ -1385,8 +1396,15 @@
function firmwareProfileLabel(profile) {
if (profile.sensorProfile) {
const label = (profile.sensorProfile === "full" ? "Full supported sensors" : "Reduced sensors") + " + LoRa OTA";
const variant = variantWithoutSensorMarker(profile.variant);
return label + (variant !== "default" ? " - " + humanizeVariant(variant, profile.hardware) : "");
let variant = variantWithoutSensorMarker(profile.variant);
const embedded = profile.embeddedBootloader;
if (embedded) {
variant = variant.replace(new RegExp("(?:^|-)with-bootloader-" +
escapeRegExp(embedded.release.replace(/\./g, "-")) + "(?=-|$)"), "")
.replace(/^-+|-+$/g, "") || "default";
}
return label + (variant !== "default" ? " - " + humanizeVariant(variant, profile.hardware) : "") +
(embedded ? " + OTAFIX " + embedded.release + " bootloader included" : "");
}
const parts = [];
if (profile.feature === "full") parts.push("Full");
@@ -2007,6 +2025,12 @@
],
};
const extra = [];
if (profile.embeddedBootloader) {
const embedded = profile.embeddedBootloader;
extra.push("This application includes the exact-board OTAFIX " + embedded.release +
" bootloader. Leave it running for at least " + embedded.automatic_delay_seconds +
" seconds after startup. It checks once when radio and OTA activity are idle, updates a recognized compatible older bootloader, and skips a matching current or newer version. Recovery and unrecognized bootloaders require the documented local migration route. After any reboot, check get bootloader.ver.");
}
if (isExpandedEsp32Infrastructure(profile) && kind === "bin") {
extra.push(
"If the node still has a smaller layout, first flash the matching merged image over USB or use the linked exact board/role migration ZIP, when available. Follow its README to check the installed OTA target and source layout before starting. Never send this app-only image across a partition change."
+13 -6
View File
@@ -4,7 +4,7 @@
# Firmware picker
<div class="firmware-picker" data-firmware-picker data-release-repo="mikecarper/MeshCore" data-controls-url="../_data/firmware_controls.json?v=t114-autodisplay-794f5f7b" data-bootloaders-url="../_data/bootloader_manifest.json?v=20261002-1" data-share-url="https://mikecarper.github.io/MeshCore/p/">
<div class="firmware-picker" data-firmware-picker data-release-repo="mikecarper/MeshCore" data-controls-url="../_data/firmware_controls.json?v=1.18.0.1-03214a16" data-bootloaders-url="../_data/bootloader_manifest.json?v=otafix-2.4.12" data-share-url="https://mikecarper.github.io/MeshCore/p/">
<form class="firmware-picker-form" data-role="form">
<div class="firmware-picker-feedback firmware-picker-wide" data-role="filter-feedback" hidden>
<div aria-live="polite" aria-atomic="true">
@@ -286,7 +286,7 @@ capacity and sensor-profile choices.
Moving an older ESP32 installation to an expanded Full layout requires a
partition migration.
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.9-halo-keymind-cascade-dev-88c85108).
staged migration ZIP from the [utility release](https://github.com/mikecarper/MeshCore/releases/tag/utility-v1.18.0.1-halo-keymind-cascade-dev-03214a16).
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. Run
@@ -478,7 +478,7 @@ is available. ESP32 and other chip families do not show this section. The web
picker checks the latest stable OTAFIX release; the downloadable picker
includes the bootloader release named in its saved catalog. If a board has no
verified mapping or a file is missing, the picker explains that instead of
offering another board's bootloader. OTAFIX 2.4.11 publishes a combined
offering another board's bootloader. OTAFIX 2.4.12 includes a combined
MeshTower V2 SD/internal image, mapped only to `Heltec_tower_v2_sdcard`.
The historical `Heltec_tower_v2` internal-only profile is explicitly retired:
move to the normal combined image with a one-time local USB/BLE DFU or SWD
@@ -493,8 +493,15 @@ for the source checks and boards still awaiting a dedicated, tested release.
Board mappings and file names, URLs, sizes and SHA-256 hashes come from
`bootloader-manifest.json` in the
[OTAFIX release](https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/latest).
Application UF2 and DFU files do not install a bootloader. Follow the bootloader
release's migration instructions if the installed version needs a recovery bridge.
Ordinary application UF2 and DFU files preserve the installed bootloader.
Separate **OTAFIX 2.4.12 bootloader included** Repeater and Room Server choices
carry their exact-board bootloader inside the application. Leave that application
running for at least 70 seconds after startup; it checks once when radio and OTA
activity are idle, updates a recognized compatible older bootloader, and skips
a matching current or newer version. Check `get bootloader.ver` after reboot.
Recovery and unrecognized bootloaders require the documented migration route;
the embedded updater does not guess a different board identity. See
[embedded bootloader installation](nrf52_embedded_bootloader.md).
nRF52 LoRa OTA requires an OTAFIX bootloader built for the exact board and
storage layout. Select the hardware-matched HEX, Serial DFU ZIP, or
@@ -509,7 +516,7 @@ pin map, and other physical differences without crowding the Hardware dropdown.
that need a different image or wiring, such as serial port or external storage.
The picker skips this step when all available profile choices lead to the
same firmware file.
The 1.17.1.9 nRF52 repeater, room-server and sensor releases publish two separately
The 1.18.0.1 nRF52 repeater, room-server and sensor releases publish two separately
qualified choices: **Reduced sensors + LoRa OTA** and
**Full supported sensors + LoRa OTA**, with `-reduced-ota` and `-full-ota` artifact suffixes. Each keeps
its exact board/role OTA identity and storage layout; the suffix is not a new
+4 -4
View File
@@ -8,8 +8,8 @@ Choose firmware with the [firmware picker](firmware_picker.md). For help with a
## Current release
- [1.17.1.8 USA Cascade release notes](releases/1.17.1.8.md)
- [Test Results](test-results/index.md) — validation archive and 1.17.1.8 Preview 1 qualification evidence
- [1.18.0.1 USA Cascade release notes](releases/1.18.0.1.md)
- [Test Results](test-results/index.md) - source-specific validation archive
## Documentation
@@ -32,7 +32,7 @@ The navigation groups the remaining guides under Documentation, including board-
## Engineering records
- [Research](research/index.md) — design notes, diagnostics, and historical update-chain studies
- [Old Releases](old-releases/index.md) — historical release notes and supporting files
- [Research](research/index.md) - design notes, diagnostics, and historical update-chain studies
- [Old Releases](old-releases/index.md) - historical release notes and supporting files
Found a mistake or missing information? [Edit the documentation](https://github.com/mikecarper/MeshCore/tree/keymindCascade/docs).
+1 -1
View File
@@ -4,7 +4,7 @@
# Old Releases
Historical release notes and their supporting files are kept here for reference. Use the [current 1.17.1.8 release notes](../releases/1.17.1.8.md) for current firmware.
Historical release notes and their supporting files are kept here for reference. Use the [current 1.18.0.1 release notes](../releases/1.18.0.1.md) for current firmware.
- [1.17.1.7 release](1.17.1.7.md)
- [1.17.1.6 release](1.17.1.6.md)
+4 -2
View File
@@ -5,8 +5,10 @@
# nRF52 bootloader updates over LoRa
For an application image that carries its own board-matched 2.4.12 replacement,
see [embedded nRF52 bootloader updates](nrf52_embedded_bootloader.md). That opt-in
bridge uses a separate admin activation command after the application is running.
see [embedded nRF52 bootloader updates](nrf52_embedded_bootloader.md). A separate
`with-bootloader-2.4.12` image checks once after 70 seconds of startup and updates
a recognized compatible older bootloader when radio and OTA activity are idle.
The authenticated admin activation command remains available for manual retry.
For **1.17.1.5**, use the exact board/storage profile from
[OTAFIX 2.4.6](https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6)
+106
View File
@@ -0,0 +1,106 @@
<!-- meshcore-hosted-doc-link:start -->
<p class="meshcore-hosted-doc-link"><a href="https://mikecarper.github.io/MeshCore/releases/1.18.0.1/">View this page on MeshCore Docs</a>.</p>
<!-- meshcore-hosted-doc-link:end -->
# MeshCore 1.18.0.1 USA Cascade
Firmware source: `03214a16df2bd09d3272dfb001d2d322c6740f60`.
USA Cascade defaults are **910.525 MHz, 62.5 kHz bandwidth, SF7 and CR5**.
Saved radio settings take precedence. Choose the exact board, radio, storage
layout and role in the [firmware picker](../firmware_picker.md).
Download the [1.18.0.1 release family](https://github.com/mikecarper/MeshCore/releases/tag/v1.18.0.1-halo-keymind-cascade-dev-03214a16)
and its [migration and bootloader utilities](https://github.com/mikecarper/MeshCore/releases/tag/utility-v1.18.0.1-halo-keymind-cascade-dev-03214a16).
The picker, Mesh America and the Keymind choices in meshfirmware select these
same exact release assets.
## Changes since 1.17.1.9
- Supported nRF52 Repeater and Room Server targets have separate application
images carrying their exact-board **OTAFIX 2.4.12** bootloader. Ordinary
applications remain available, together with standalone bootloader files.
- Full Companion includes Meshtext on all supported board families. Message
retries are bounded; repeated traffic does not become a new local message.
- [ESP-NOW](../espnow_bridge_setup.md) and
[RS232](../rs232_bridge_setup.md) bridges provide runtime status, counters
and link probes. The [WiFi UDP bridge](../udp_bridge_setup.md) supports eight
authenticated IP peers per repeater on an existing station network.
- [Telemetry packet selections](../cli_commands.md#read-repeater-telemetry-history)
independently control temperature, battery, external I2C voltage, main-radio
noise and radio2 noise snapshots. All five selections default on; the
telemetry transmitter itself remains off until enabled.
- Optional [battery forwarding thresholds](../cli_commands.md) can stop repeat
and flood forwarding independently. Both controls default off; their
percentages and supported voltage calibration are saved settings.
- Supported radios expose saved `radio.fast` acceleration controls and
`radio.fast.spi` choices. A `9` MHz selection uses approximately 8.889 MHz
where the controller supports that rate. Read `get radio.fast.caps` for the
actual board's options.
- Board profiles consolidate supported display and transport choices, including
T114 automatic display detection. Exact V4 hardware and storage variants
remain distinct where their wiring requires a different image.
- T1000-E Companion gives an enumerated USB data connection priority over
Bluetooth. Bluetooth resumes after USB disconnects if it is enabled;
battery and a charge-only wall supply allow Bluetooth. Pairing and the saved
Bluetooth setting are retained.
- Release capacity fixes retain the qualified feature sets with compact help,
shared buffers and board-specific memory placement. Every image includes its
own capability and memory reports; capacities still differ between boards.
See [feature controls](../role_feature_switches.md), the
[Full Companion guide](../full_companion_features.md) and
[CLI reference](../cli_commands.md) for supported commands and defaults.
## Choose an installation
For ESP32, the merged `.bin` installs bootloader, partitions and application
over USB. An app-only `.bin` requires a compatible existing partition layout.
When expansion is needed over WiFi or LoRa, use the exact board/role migration
ZIP in this release family's utility page and install its supplied Full
application. Follow the included README; an app-only image cannot expand
partitions. `get storage.layout` reports the live layout where supported.
Ordinary nRF52 UF2 and Serial DFU ZIP files install the application and preserve
the installed bootloader. Repeater, Room Server and Sensor retain separately
qualified **Full supported sensors + LoRa OTA** and
**Reduced sensors + LoRa OTA** choices. These keep the exact OTA target and
storage layout; sensor policy is not a different radio identity.
Separate `with-bootloader-2.4.12` Repeater and Room Server applications carry a
board-matched bootloader. Leave the application powered for at least 70 seconds
after installation. It checks once when radio and OTA activity are idle and
updates a recognized compatible older bootloader; matching current or newer
versions are skipped. Recovery or unrecognized bootloaders require their
documented local migration route. Check `get bootloader.ver` afterward. See
[embedded bootloader installation](../nrf52_embedded_bootloader.md).
The utility release also supplies exact-board bootloader-update UF2,
SoftDevice/bootloader DFU ZIP and SWD HEX files for 23 published OTAFIX profiles
covering 40 hardware aliases. The SoftDevice/bootloader DFU package requires
reinstalling the application. Pending, blocked and retired board mappings are
identified rather than replaced by another board's image.
LoRa OTA reception requires the matching bootloader, target identity, storage
layout and radio settings. Full Companion can send a host-supplied update to
another node; it does not install that LoRa transfer onto itself.
## Verification scope
The complete release has **589 qualified firmware packages**: 435 ordinary
packages and 154 embedded-bootloader variants. The latter cover 77 logical
Repeater/Room targets with both sensor policies. It also includes **69
standalone bootloader files**, **96 exact ESP32 board/role migration packages**
and **26 migration utility builds**.
The completed matrix passed exact target inventory, source provenance,
checksums, packaged OTA identity, native DFU, firmware size, runtime RAM,
sensor-pair, bootloader mapping and migration-layout validation. All 14 jobs in
the [source revision's CI run](https://github.com/mikecarper/MeshCore/actions/runs/40101490838)
passed.
Physical results remain tied to the hardware, revision and installation route
recorded in the [test reports](../test-results/index.md). Building every target
does not establish every board's physical USB, Bluetooth, WiFi, RF, sleep or
update behavior. The release does not qualify every starting firmware or
bootloader migration path.