KW36 IPhone BLE pairing failure

[Melton]

Dear Sir，

       I have a problem with the KW36 and need help，When I call Gap_SendSlaveSecurityRequest this API inside BleApp_ConnectionCallback function，When I use my iPhone to connect repeatedly，There is a small probability that there will be an error on the iPhone and the connection will be lost NoLtk，However, after viewing the bin file, the bonding information in the NVM is not lost 。I want to know，Whether this API（Gap_SendSlaveSecurityRequest） is reasonable to call here？And why is there such a small probability of NoLtk on iphones and Android doesn't have this problem。

Melton_0-1710300994724.png

[Ricardo_Zamora]

Hello,

Hope you are doing well. Could you please clarify what SDK version are you using?

What SDK example are you using as a base? What modifications did you made?

What are you trying to achieve?

Regards,

Ricardo

[Melton]

SDK Version : 2.2.12

SDK Example: frdmkw36_wireless_examples_bluetooth_w_uart_freertos

SDK Modify: wireless_uart.c->BleApp_ConnectionCallback->gConnEvtConnected_c

add  (void)Gap_SendSlaveSecurityRequest(peerDeviceId, &gPairingParameters);

Problem spot: If you do not add this api, When the KW36 deletes the pairing information, the phone retains the pairing information,The phone will not initiate a pairing popup request,Android phones don't seem to go wrong with additions like this,

however, the iPhone will have a small probability of not pop-up window.I want to know how this problem is solved,and I want to know the correct way to use this API.

Think you,best regard! @Ricardo_Zamora 

[Ricardo_Zamora]

Hello,

Have you tried just enabling the gAppUsePairing_d and gAppUseBonding_d?

The Gap_SendSlaveSecurityRequest is already used in the BleConnManager_GapPeripheralEvent.

Regards,

Ricardo

[Melton]

Thank you sir,

  I've already enabled the gAppUsePairing_d and gAppUseBonding_d.

  I known the Gap_SendSlaveSecurityRequest is already used in the BleConnManager_GapPeripheralEvent.

  However, after KW36 is successfully paired with the mobile phone once, the pairing information of either party is deleted, and the pairing is performed again. At this time, the pairing fails, because the other party does not know that the other party has lost the pairing information, so it needs to call this api again in the connection event, which seems to be feasible for Android phones.  But it doesn't seem to work on iphone, I would like to ask your advice. @Ricardo_Zamora 

[Ricardo_Zamora · Accepted solution]

Hello,

This particular situation is completely on the iPhone side, and not related to KW36.

The best way to solve this would be to find a way to delete the bonding information on the iPhone.

Regards,

Ricardo