Enable LoRa OTA room and nRF52 sensor variants

This commit is contained in:
mikecarper committed 2026-09-26 09:58:43 -07:00
1 parent df19760c85
commit f215792162
8 files changed
+142 -48

No files matched your search

+3 -3
View File
@@ -54,7 +54,7 @@
const OTA_LABELS = Object.freeze({
none: "No LoRa OTA",
"lora-receiver": "LoRa OTA repeater",
"lora-receiver": "Receives LoRa OTA",
"lora-source": "LoRa OTA source only (Full Companion)",
});
@@ -1075,7 +1075,7 @@
],
zip: [
"Use the ZIP as the native nRF52 Serial DFU package; it is not an extra archive.",
"For a LoRa OTA repeater, install the exact-board OTAFIX bootloader first.",
"For LoRa OTA reception, install the exact-board OTAFIX bootloader first.",
],
uf2: [
"Place the device in its UF2 bootloader mode and copy the UF2 to the mounted drive.",
@@ -1102,7 +1102,7 @@
}
if (profile.ota === "lora-receiver") {
extra.push(
"This installs the LoRa OTA repeater profile. The later update package must still match the exact target and partition signature."
"This image can receive LoRa OTA updates. The later update package must still match the exact target and partition signature."
);
} else if (profile.ota === "lora-source") {
extra.push(
+6 -7
View File
@@ -162,7 +162,7 @@ from the published firmware assets.
| Wi-Fi MQTT observer | Firmware connects directly to MQTT over Wi-Fi; this is not USB logging |
| USB logging + Wi-Fi MQTT | Unified FULL image sends to both paths; avoid two publishers aimed at the same broker unless messages are deduplicated |
| No logging | Normal standalone operation without the dedicated logging/MQTT profile |
| LoRa OTA repeater | Repeater profile that can stage an exact matching update received over LoRa |
| Receives LoRa OTA | Repeater, room server, or sensor image that can stage an exact matching update received over LoRa |
| LoRa OTA source only | Full Companion serving a host-supplied update to another node without self-installing it |
Connection and bridge choices depend on the selected role. Companion firmware
@@ -362,15 +362,14 @@ node configuration and verify every filename suffix before flashing.
## LoRa OTA and OTAFIX
A LoRa OTA repeater build installs repeater firmware that can receive and
stage updates. A later LoRa update still needs an exact target identity,
A LoRa OTA capable build can receive and stage updates for its role. A later
LoRa update still needs an exact target identity,
compatible partition signature, matching radio settings, and the correct
update package.
nRF52 LoRa OTA requires an OTAFIX bootloader built for the exact board. There
is no universal bootloader file. Use the
[OTAFIX 2.4.6 for this release](https://github.com/mikecarper/Adafruit_nRF52_Bootloader_OTAFIX/releases/tag/0.11.0-OTAFIX2.4.6)
and select the hardware-matched HEX, Serial DFU ZIP, or bootloader-update UF2.
nRF52 LoRa OTA requires an OTAFIX bootloader built for the exact board and
storage layout. Select the hardware-matched HEX, Serial DFU ZIP, or
bootloader-update UF2 for the application image being installed.
## Hardware and variant names
+6 -3
View File
@@ -95,8 +95,10 @@ payload. If any required window closes, the transfer stops making progress and c
overlapping window.
`build.sh` provides a `*_repeater_lora_ota_no_external_sensors` or
`*_room_server_lora_ota_no_external_sensors` build for standalone ESP32 and nRF52
infrastructure targets that need a smaller internal update workspace. Those siblings omit selected optional environmental
`*_room_server_lora_ota_no_external_sensors` build for standalone infrastructure
targets that need a smaller internal update workspace. nRF52 sensors also have
`*_sensor_lora_ota_no_external_sensors` builds. ESP32 room servers and sensors
use their expanded Full image for LoRa OTA. These compact siblings omit selected optional environmental
and ranging drivers while retaining board-native features such as displays, buttons, battery monitoring,
and GPS where the target uses the GPS-preserving lean profile. RAK3401 and RAK4631 reduced builds also
retain INA219, INA226, INA260, and INA3221 I2C voltage/current monitors; together these drivers cost less
@@ -119,7 +121,8 @@ Selected nRF52 boards with matched external
QSPI application and bootloader support can instead make the normal full-sensor
repeater or room-server install-capable; those targets do not need to reserve internal flash
for the downloaded container. SolarXiao 30S and 33S use this matched external-QSPI
path and therefore do not emit redundant no-external-sensors siblings. A
path: repeaters retain their existing OTA target, and room servers use the explicit
`*_room_server_lora_ota` target with the matching OTAFIX QSPI bootloader. A
RAK19007 can use the same separately wired W25Q16 with either RAK4631 or
RAK3401 + RAK13302: the flash consumes no WisBlock slot and GPS remains
supported in slot A. This is not the RAK15001 arrangement; RAK15001 and
+8 -7
View File
@@ -133,13 +133,14 @@ artifacts, including room, sensor, and repeater roles, must fit the legacy slot
limit and the target's actual app partition. The ESP32-C6 `no_external_sensors` OTA siblings are the narrow
exception: the Arduino 3.x WiFi runtime cannot fit that cross-family ceiling, so those images retain their
established target-specific 1920 KiB or larger A/B app layout and are checked against the actual app
partition. For standalone ESP32 and nRF52 repeater and room-server roles that
need a lean staging profile, `build.sh` also exposes an explicit
`*_lora_ota_no_external_sensors` artifact: the ordinary role remains
sensor-enabled, while that sibling trims selected optional environmental/ranging
drivers for LoRa distribution. SolarXiao 30S and 33S use matched external QSPI
staging, so their ordinary full-sensor repeater and room-server images are
already install-capable and no redundant lean sibling is generated. Integrated GPS and other
partition. ESP32 room servers and sensors use their expanded Full image for LoRa OTA.
For standalone repeater and room-server roles, and for nRF52 sensors that need a lean
staging profile, `build.sh` exposes an explicit `*_lora_ota_no_external_sensors`
artifact: the ordinary role remains sensor-enabled, while that sibling trims
selected optional environmental/ranging drivers for LoRa distribution. SolarXiao
30S and 33S use matched external QSPI staging. Their repeaters keep the existing
OTA target; their room servers use an explicit `*_room_server_lora_ota` image
with the matching OTAFIX QSPI bootloader. Integrated GPS and other
board-native telemetry remain enabled where the target selects the GPS-preserving lean profile. The legacy
suffix describes a driver trim, not removal of the generic I2C bus. Reduced RAK3401 and RAK4631 profiles
retain INA219, INA226, INA260, and INA3221 voltage/current monitors. These are retained optional-sensor-table