Other Parts Discussed in Thread: SYSCONFIG
Tool/software:
Hi,
I am referring to the unresolved ticket here: https://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1373648/cc2651r3-previously-bonded-devices-can-not-connect-in-whitelist-mode
My colleague Vikas R J was able to patch it using the following workaround in SDK v8.30.01.01 for target MCU CC2651R3:
:
-
Issue observed: Bonded devices unable to reconnect when whitelist filtering enabled.
-
SysConfig set to:
-
Advertisement policy: "Allow scan from all, connect only from whitelist"
-
Pairing policy: "Allow pairing from all devices"
-
-
Despite correct SysConfig, reconnects failed.
-
In
setBondManagerParameters()
, SDK sets:-
GAPBondMgr_SetParameter(GAP_ADV_AL_POLICY_ANY_REQ, sizeof(uint8_t), &autoSyncAL);
-
which is incorrect — it controls advertising, not bonding.
-
-
Correct parameter is:
-
GAPBondMgr_SetParameter(GAPBOND_AUTO_SYNC_AL, sizeof(uint8_t), &autoSyncAL);
-
Overriding
ti_ble_config.c
didn't work; value was overwritten.
-
-
Final fix applied in application init (after
setBondManagerParameters()
):-
GAPBondMgr_SetParameter(GAPBOND_AUTO_SYNC_AL, sizeof(uint8_t), &autoSyncAL);
-
Result: Bonded devices can now reconnect successfully when whitelist is active.
-
It seems like the interface between the SysConfig tool and the generated ti_ble_config.c file may be the issue. Could you please report this to the R&D team?
Also, the ticket was addressed to the R&D team quite some months before, however the bug still persists in the newest SDK.
Thanks, Kaiwalya