rich/MeshCore
1
0 Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Include and qualify Meshtext in RAK4631 Full Companion

Browse Source 
Port Meshtext settings to verified atomic nRF52 storage and use the existing radio RNG and hardware entropy. Keep the ExtraFS boundary, GPS, contacts, channel count and 8 KiB stack unchanged; omit unused library data to fit the image. Require linked codec and Companion transport evidence and build the real RAK Full profile in CI. Add configuration and storage-failure regression coverage.
This commit is contained in:
mikecarper committed 2026-10-12 22:39:00 -07:00
1 parent 7e5eabe81c
commit 65820d0dd2
13 files changed
+515 -9
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

docs/radio_profiles.md
+4 -2
View File
@@ -281,8 +281,10 @@ recognize these aliases.
### Meshtext channel chat
`MESH_ENABLE_MESHTEXT_CHAT` enables the text-only Meshtext backend in the
Companion. It defaults on only for ESP32-S3 **Full Companion** builds using
SX1262 LoRa, not an ESP-NOW primary. Other builds default off. This is not
Companion. It defaults on for ESP32-S3 **Full Companion** builds using
SX1262 LoRa and for the RAK4631 **Full Companion** starting with 1.17.1.10
preview3. An ESP-NOW primary and other builds default off. RAK4631 1.17.1.10
preview2 and earlier builds did not include this backend. This is not
a replacement for stock peer firmware or a cross-protocol bridge.
In an enabled build, an `mt-` name always requests Meshtext, even if radio2 is