From 8882d5876ffbf4507b1b5ded8ff495363d0c52df Mon Sep 17 00:00:00 2001
From: liquidraver <504870+liquidraver@users.noreply.github.com>
Date: Wed, 22 Jul 2026 11:20:43 +0200
Subject: [PATCH] e5 ram

---
 zephcore/boards/stm32wl/lora_e5_mini/board.conf | 12 ++++++++++--
 1 file changed, 10 insertions(+), 2 deletions(-)

diff --git a/zephcore/boards/stm32wl/lora_e5_mini/board.conf b/zephcore/boards/stm32wl/lora_e5_mini/board.conf
index 64736da..bab3a00 100644
--- a/zephcore/boards/stm32wl/lora_e5_mini/board.conf
+++ b/zephcore/boards/stm32wl/lora_e5_mini/board.conf
@@ -28,6 +28,14 @@ CONFIG_ZEPHCORE_DEFAULT_TX_POWER_DBM=22
 # so cap them hard. These only allocate in the companion role; the repeater
 # build ignores them. A serial companion on this constrained board is for
 # modest contact lists.
-CONFIG_ZEPHCORE_MAX_CONTACTS=24
-CONFIG_ZEPHCORE_OFFLINE_QUEUE_SIZE=8
+#
+# 2026-07-22: retightened after companion-only RAM growth (ACL/offline-queue/
+# mesh-tables additions since the 2026-06-21 port) overflowed the region by
+# 5716 bytes. BLE_QUEUE_SIZE default is 24 (Kconfig warns 12 overran the recv
+# queue during channel-sync bursts, but that was measured against the
+# *default* MAX_CHANNELS=40); with MAX_CHANNELS capped to 8 here, 12 still
+# gives 1.5x headroom over the worst-case back-to-back CMD_GET_CHANNEL burst.
+CONFIG_ZEPHCORE_MAX_CONTACTS=12
+CONFIG_ZEPHCORE_OFFLINE_QUEUE_SIZE=2
 CONFIG_ZEPHCORE_MAX_CHANNELS=8
+CONFIG_ZEPHCORE_BLE_QUEUE_SIZE=12