Unfortunately the problem still exists in the simplelink_cc13x2_26x2_sdk_4_40_00_44:
New discussion in TI E2E forum: https://e2e.ti.com/support/wireless-connectivity/bluetooth/f/538/t/946492
Hi,
sorry for the delayed response. I still see the issue when using the multirole example on the LaunchXL-CC26x2R1.
I'm not really able to give you a step-by-step guide how to reproduce this issue. This time I did these steps:
- activate "Sync Whitelist With Bonded Devices" in sysconfig -> BLE -> Bond Manager
- build and run the code
- bond with a smartphone (called "first smartphone" in the following)
- stop debug session
- In sysconfig under BLE -> Broadcaster Configuration -> Advertisement Set 1 -> Advertisement Parameters 1, set "Filter Policy" to "Process scan req from all devices and only conn req from devices in WL"
- build and run the code
- Connect with the first smartphone and change the CCCDs of some characteristics some times
- Use a second smartphone, which has not been bonded before, start a scan request and try to connect
Steps 7 and 8 can be different. I could also observe the issue when I've tried to connect with the first smartphone during a running scan of the second smartphone.
