• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 51 subscribers
  • Views 583 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Original question:

CC2642R: BugReport: ADV_CONN_CFG infinite loop if BondManager is updating while enabeling Advertisment

CC2642R: SDK Bugfix for 'sync Whitelist with Bonded devices'

Martin Reichelt
Prodigy 230 points

Part Number: CC2642R
Other Parts Discussed in Thread: LAUNCHXL-CC26X2R1, SYSCONFIG

Hello TI experts,

I've just seen that SDK 4.30.00.54 is available now for CC26x2. Is this bug https://e2e.ti.com/support/wireless-connectivity/bluetooth/f/538/t/922032 already fixed?

Regards,

Martin

  • 0
    TI__Genius 17265 points

    Hi Martin,

    Based off the ticket I found related to this issue, I believe it should be fixed in the 4_30 SDK which released today. Try it out and please let me know if you still have any issues with it. 

    Best Regards,
    Alec

  • 0 in reply to Alec May
    Prodigy 230 points

    Hi ,

    I still encounter the issue in SDK 4.30.00.54.

    Best Regards,

    Martin

  • 0 in reply to Martin Reichelt
    TI__Genius 17265 points

    Hi Martin,

    I'm sorry to hear this, I will reach out to the developer who was responsible for this issue and see if I can get some more information. Does this issue still persist the same way as it did before, or has anything changed? Are the steps to reproduce this issue that are listed in the previous post still a valid way to reproduce this issue? If not, would you mind stepping me through how to reproduce this issue?

    Best Regards,
    Alec

  • 0 in reply to Alec May
    Prodigy 230 points

    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:

    1. activate "Sync Whitelist With Bonded Devices" in sysconfig -> BLE -> Bond Manager
    2. build and run the code
    3. bond with a smartphone (called "first smartphone" in the following)
    4. stop debug session
    5. 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"
    6. build and run the code
    7. Connect with the first smartphone and change the CCCDs of some characteristics some times
    8. 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.

  • 0 in reply to Martin Reichelt
    TI__Genius 17265 points

    Hi Martin,

    My sincerest apologies for not replying earlier. I am actively working someone in R&D to determine if this part of the same issue that we patched, or if this is another issue entirely. 

    Best Regards,
    Alec