fix(connectivity): harden BLE reprovisioning under memory pressure
This commit is contained in:
@@ -180,6 +180,27 @@ menu "TQ Cat Configuration"
|
||||
default 2
|
||||
range 1 10
|
||||
|
||||
config TQ_MINI_PROGRAM_PROVISIONING_MIN_FREE_INTERNAL_BYTES
|
||||
int "Minimum free internal memory before BLE provisioning"
|
||||
depends on TQ_MINI_PROGRAM_PROVISIONING_ENABLE
|
||||
default 49152
|
||||
range 16384 131072
|
||||
help
|
||||
BLE controller initialization requires internal DMA-capable
|
||||
memory even when the NimBLE host uses external RAM. Runtime
|
||||
reprovisioning performs a controlled recovery boot when free
|
||||
internal memory remains below this threshold after teardown.
|
||||
|
||||
config TQ_MINI_PROGRAM_PROVISIONING_MIN_LARGEST_DMA_BYTES
|
||||
int "Minimum largest DMA block before BLE provisioning"
|
||||
depends on TQ_MINI_PROGRAM_PROVISIONING_ENABLE
|
||||
default 12288
|
||||
range 4096 65536
|
||||
help
|
||||
Minimum contiguous DMA-capable block required before entering
|
||||
the BLE controller. This headroom prevents the controller ROM
|
||||
from asserting after a late allocation failure.
|
||||
|
||||
endmenu
|
||||
|
||||
menu "Runtime Diagnostics"
|
||||
|
||||
Reference in New Issue
Block a user