• State Verified Answer
  • Replies 2 replies
  • Subscribers 68 subscribers
  • Views 488 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 234490
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

SDK 15.0 SDK 15.3 migration error in pairing pin

hossein_m

I built my project with SDK 15.0 but for some modifications I migrated to SDK15.3

In my application I use pairing key to secure connections but since migrating to SDK 15.3 the following problem happens

On first connection to each client, my device truly asks for the pairing code and then starts working but when one the clients removes the device pairing information and tries for a re pair to the device the pairing code is not asked and the clients pairs with the device without pairing code. 

It is worth mentioning that this problem shows itself on windows or mac operating systems and the device works fine with nrf connect app.

Does anybody experiance this problem before? What can I do about it? I really need migrating to SDK 15.3.

Parents
  • +1

    Hi Hossein

    This issue did not occur when using SDK v.15.0, correct? What SoftDevice version are you using now, and what version did you use before the migration (If you're using a SoftDevice, that is)?

    Are you using the Peer Manager? In that case, please note that the peer manager went through some rather big changes from v.15.0.0 to v.15.3.0 of the SDK. It might be that you were "using" this bug in SDK v.15.0: Fixed a bug where pairing (no bonding) could happen with an already bonded peer without triggering a PM_EVT_CONN_SEC_CONFIG_REQ event. This was fixed in SDK v.15.3 so you'll have to use the PM_EVT_CONN_SEC_CONFIG_REQ event in order to re-pair with a device.

    Best regards,

    Simon

Reply
  • +1

    Hi Hossein

    This issue did not occur when using SDK v.15.0, correct? What SoftDevice version are you using now, and what version did you use before the migration (If you're using a SoftDevice, that is)?

    Are you using the Peer Manager? In that case, please note that the peer manager went through some rather big changes from v.15.0.0 to v.15.3.0 of the SDK. It might be that you were "using" this bug in SDK v.15.0: Fixed a bug where pairing (no bonding) could happen with an already bonded peer without triggering a PM_EVT_CONN_SEC_CONFIG_REQ event. This was fixed in SDK v.15.3 so you'll have to use the PM_EVT_CONN_SEC_CONFIG_REQ event in order to re-pair with a device.

    Best regards,

    Simon

Children
Related