Qualify ESP-NOW RAM and Wio Mini release capacity
This commit is contained in:
1 parent
64885dab28
commit
efed592fdb
4 files changed
+19
-2
No files matched your search
@@ -33,7 +33,6 @@ layout before installing an image.
|
||||
complete sensor profile with the existing 8 KiB loop stack, 50 neighbors,
|
||||
color framebuffer and OTA arena. Their capability manifests record this
|
||||
capacity limit; heap qualification margins are unchanged.
|
||||
|
||||
- The RAK3401 unified repeater reserves 47 flood-rule entries so its full
|
||||
sensor profile, 8 KiB loop stack, 50 neighbors and internal/QSPI OTA stores
|
||||
fit the runtime RAM requirement. Full and reduced sensor images use the
|
||||
@@ -42,6 +41,15 @@ layout before installing an image.
|
||||
If active rules exceed an image's capacity, the stored file is preserved and
|
||||
policy saves are blocked. The CLI reports the capacity mismatch; install
|
||||
firmware with enough rule slots to recover the complete policy.
|
||||
- ESP32 filesystem buffer checks cover the pinned Arduino 3 frameworks used
|
||||
by RC32 and C6 targets and continue rejecting unhonored buffer allocations.
|
||||
- Generic ESP-NOW Full Companion retains all Full transports and 100 contacts
|
||||
with a 224-frame offline queue to meet the unchanged runtime RAM requirement.
|
||||
- Wio-E5 Mini Companion uses smaller generated code while preserving its
|
||||
filesystem allocation, contacts, channels and physical-button controls.
|
||||
CI compiles its actual Cascade release profile with the full version string.
|
||||
- Mesh America preserves download-only installation for hardware cards that
|
||||
require it, including their Full and reduced sensor profiles.
|
||||
|
||||
## Installation
|
||||
|
||||
|
||||
Reference in new issue
Block a user