Report nRF52 LoRa mOTA capabilities and storage requirements
This commit is contained in:
1 parent
85562f2efb
commit
27616e2e5b
9 files changed
+1415
-184
No files matched your search
+1172
-60
File diff suppressed because it is too large.
Load diff
@@ -103,6 +103,18 @@ push commits, create remote tags, or publish a GitHub release.
|
||||
|
||||
## Published release set and small-slot Heltec V4 updates
|
||||
|
||||
The capability JSON and target inventories now report both Bluetooth DFU and
|
||||
LoRa mOTA for all 60 nRF52 receiver profiles. The original report omitted the
|
||||
nRF52 LoRa method. Each affected manifest includes `ota_update_requirements.lora`
|
||||
with its storage type, accepted package types, exact-base requirement for deltas,
|
||||
and the matching OTAFIX bootloader link. Internal-flash receivers accept in-place
|
||||
deltas; supported QSPI/SD receivers also accept full application packages. The
|
||||
20 retained-RAM receivers require OTAFIX 2.4.6's matching handoff support.
|
||||
These reports verify the released application bytes and storage layout; they
|
||||
do not certify the bootloader installed on a physical device. Firmware binaries
|
||||
and tags are unchanged. Full Companion mOTA sending remains separate from
|
||||
self-update capability.
|
||||
|
||||
Published firmware tags remain at source commit `26303793`. Documentation can
|
||||
advance independently. The original matrix qualified 540 profiles (1,080
|
||||
firmware files) from 551 attempts; 11 oversized portable attempts have expanded
|
||||
|
||||
Reference in new issue
Block a user