• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 52 subscribers
  • Views 278 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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: Multiple identical peripherals appears in MacOS when using RPA with public ID

CC2642R: BLE Midi peripheral using RPA appears multiple times in MacOS Central

jerome d.
Expert 1275 points
Part Number: CC2642R
Other Parts Discussed in Thread: SYSCONFIG

Hi All
I still not solve the issue mentioned in the post below :

https://e2e.ti.com/support/wireless-connectivity/bluetooth/f/bluetooth-forum/947873/cc2642r-multiple-identical-peripherals-appears-in-macos-when-using-rpa-with-public-id

I'm using MIDI over BLE.
Latest SDK, CCS, etc
My app is based on Multi role example.

When my device acts as a peripheral, using PUBLIC address :

- Works fine on MacOS
- Second unit does not pair with Win 10 (First unit works well, second unit result in PAIR_STATE_COMPLETE with error code 0x08).

When my device acts as a peripheral, using RPA with Public ID :

- Same device appears multiple time on MacOS after each power cycle
- Second unit does pair well with Win 10.

Is there anybody to help ?
Thanks

  • 0
    TI__Guru**** 169004 points

    Hi,

    Interesting; this indeed is a bit strange.

    Given you are working with the various address modes, there is a very similar (but not identical) behaviour reported that needs to be adjusted in the Sysconfig IRK distribution settings. I reproduce the explanation below:

    By inspecting the Windows system logs, we found out that IRKs were being distributed by each peripheral when the Bond configurations were set to either Random Static Address or Public Address modes. In these modes, we set the IRK to zeros and therefore Windows 10 was refusing the second pairing given the IRK was the same as the previous pairing.

    In this case, given the IRK is not used on the non-RPA modes you have to prevent them from being distributed. This is manually set at the Bond Manager configurations of the Sysconfig file of the project. In the picture below, uncheck the box near the option Slave IRK and ID information of the Key Distribution List drop-down menu options.

    Please check if these settings influence the outcome of this scenario, at least for Windows 10. Also, check the Windows System Logs to see if there are any additional information being reported by this OS. 

    Hope this helps,

    Rafael

  • 0 in reply to desouza
    Expert 1275 points

    Hi
    Thanks for your reply.
    Removing that key from sysconfig indeed solves the issue on Windows (my device being peripheral)
    BUT
    When connecting to MacOS or iOS peripheral (my device being central), it fails.
    Once the pop up to pair/bound is shown, it re-displays the same pop up again and again.
    Any other idea ?
    Thanks
    Jerome

  • 0 in reply to jerome d.
    TI__Guru**** 169004 points

    Jerome,

    Are you able to connect to your multi-role device from anything else other than macOS or iOS? Also, is there any encryption or bond error reported by your multi-role device or the macOS/iOS?  I say multi-role as I imagine it is the same device, right? Or are two separate devices?

    At any rate, without a sniffer capture it is difficult to locate the source of the problem for the rejected bond. Is it possible to get one?

    Just to confirm, you are keeping the same configuration of Public address and disable the distribution of the Slave IRK and ID information, right? That is the scenario that works on Windows 10.

    Regards,

    Rafael