TI SDK 1.40.00.45 : Crash when re-pairing with a peer device that lost or removed its bonding keys still exists

Hi Krithiga,

Do you have a sniffer capture of the failure to start encryption? If you use Simple Central and Simple Peripheral instead of the iPhone does the same crash occur?

Hi Rachel,

As discussed in the previous thread
e2e.ti.com/.../2257931
we have given all the proof for the issue.looks one side the issue got resolved
could you please check and confirm the same at your end ?

Hello Krithiga,

What you describe is not a "crash" but a potential issue on your central device. As Rachel requested, please kindly capture and attach a BLE air sniffer trace showing 1) the peripheral sending a "PIN or Key Missing" error code in response to an Encryption Request and 2) the central initiating a Pairing Request.

In reference to the above, please see "10.3 AUTHENTICATION PROCEDURE" in the BT 4.2 core specification, Vol 3, Part C.

Best wishes

Hello JXS and Rachel,

I have collected the sniffer data.

.zip files contains following two data :

1. Sniffer Data when Bonding is deleted from Central (Android phone) but not on the peripheral (CC2640R2F hardware)

2. Sniffer Data when Bonding is deleted from Peripheral(CC2640R2F hardware) but not on the central(Android phone)

RE-pairing analysis.zip

 

 

 

Kindly provide your inputs.

Thanks,

Krithiga

Hello,

Kindly analyze the sniffer log attached when pairing is deleted from either central or peripheral end and provide your inputs.

Thanks,

Krithiga.

Hello JXS,

By using GAPBOND_PAIRING_MODE_WAIT_FOR_REQ , I am able to bond and discover services successfully when bond information has been deleted either from Central or peripheral side. This successful execution has been tested with Android mobile.

But the same is not possible using iPhone. Is there any other way rather than deleting bond information from iPhone end ?

Please reply.

Thanks,

Krithiga.

Hello JXS,

Thank you for your reply. This clears up the problem on iPhone end.

As in iPhone, BLED112 dongle also does not ask for re-pair when bond information is deleted from Peripheral.

Any input on is it possible from Dongle end and if so, how ?

Many thanks,

Krithiga.

Hello Krithiga,

Although I can't comment on the BLED112 dongle as this is not a TI firmware product, I do have some good news of sorts to share. After further consolation with L2 support, I can confirm that the iOS device, even said iPhone 8, will re-pair/bond successfully if you send Insufficient Authorization (ATT_ERR_INSUFFICIENT_AUTHOR) to a GATT Read/Write provided you do not change your IRK. Previously, I was erasing the SNV page which not only erased the bond but also erased the IRK. Instead, if you call GAPBondMgr_SetParameter(GAPBOND_ERASE_ALLBONDS, 0, NULL) to clear the previous bonding(s) and send Insufficient Authorization as mentioned above, you will be able to re-pair/bond with iOS without having to visit the BT settings menu.

How to know if you are bonded (encrypted)? You can use a global variable that gets updated when GAPBOND_PAIRING_STATE_COMPLETE or BOND_PAIRING_STATE_BONDED events are received with status=success. Then check your global variable in your Read/Write Attribute callback functions for the characteristics you want to protect.

Best wishes

Hello JXS.

Do you mean to say that SNV should not be erased ? Because, When Mass Erase is done on CC2640R2F, all pages including SNV will be erased.

Also, call to GAPBondMgr_SetParameter(GAPBOND_ERASE_ALLBONDS, 0, NULL) cannot be placed on software end as it is not possible to know when peripheral end will lose the bond information and central would not.

Kindly clarify if what you mentioned the call to GAPBondMgr_SetParameter(GAPBOND_ERASE_ALLBONDS, 0, NULL) and sending Insufficient Authorization is to *replace* deleting SNV page.

Is my understanding correct ?

Thanks,
Krithiga.