• State Verified Answer
  • Locked Locked
  • Replies 7 replies
  • Subscribers 89 subscribers
  • Views 1917 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 281621
Options
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Trouble connection multiple times : Bonding, error: 133

c.tessierpiart

Hi, 

I am trying to integrate the CTS (Clock Time Service) within my application. My current application is heavily based on the BLE UART from SDK 17.1 and I tried to integrate parts of the exemple cts from the same SDK.

I don't have any trouble connecting once or twice but systematically, the third connection resulting in the following error : 

<info> peer_manager_handler: Connection security failed: role: Peripheral, conn_handle: 0x0, procedure: Bonding, error: 133

As CTS needs bonding (or is it pairing) to work, the pairing method I use is very similar to the one in CTS.

Furthermore, I am trying to use an Apple smartphone with a custom application and the BLE service send the callback "Readin not permitted" and I think this issue is linked with the pairing problem.

Best Regards,

Charles

  • 0 in reply to Simonr

    But don't I want to be bonded for using CTS and Apple devices ?

  • +1

    Hi

    Yes, you might want to use bonding in your application, the easiest way to implement a working solution would be not to use bonding, which is why I suggested that.

    You can do bonding and I'd recommend doing so for security purposes, but if doing so, make sure that your application does not delete bonding information upon a disconnect, and make sure you don't forget the device when you disconnect on the central side either.

    I think the ble_app_gls example project is well suited as reference for a peripheral project like this.

    Best regards,

    Simon

Related