• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 51 subscribers
  • Views 573 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.

CC1352R: How to distinguish "Just works" bond from bond with correct passkey

Miriam Krieg
Prodigy 100 points

Part Number: CC1352R
Other Parts Discussed in Thread: SIMPLELINK-CC13X2-26X2-SDK

Hello,

I have encountered the following problem with bonding: some versions of bluez try to establish a "Just works" bond with our device as soon as it only allows encrypted communication with passkey.

The characteristics are still not readable/writeable for the bluez, but in the device the bond count is increased by one.

How can I forbid a "Just Works" bond or distinguish the saved bonds so I can delete or ignore it? 

We use the SIMPLELINK-CC13X2-26X2-SDK v4.10.00.78 14-APR-2020

  • +1
    TI__Mastermind 27937 points

    Hi Miriam,

    You can distinguish a Just Works pairing from a normal pairing as follows:

    • If you look at source\ti\ble5stack\inc\sm_internal.h, you will see the following
    • a variable called pPairingParams, and a define called SM_PAIRING_JUST_WORKS
    • If you manage to read pPairingParams.type from your application, you could check the type member against that define value.

    Note that this structure is NULL when not pairing, so you somehow must intercept that process in your application.

    Regards,

    Arthur