NRF52 BLE connection terminiated by Apple device after reconnect

RE: NRF52 BLE connection terminiated by Apple device after reconnect

Einar Thorsrud — Wed, 09 Jan 2019 14:23:58 GMT

Hi,

I see. From the behavior you described in the initial question and what you wrote now, it seems to me that you have not enabled repairing, and that is why you get the disconnect with reason 0x13.

The only thing you need to do to allow repairing is to adjust the handling of the PM_EVT_CONN_SEC_CONFIG_REQ (refer to most SDK BLE peripheral examples) so that you set .allow_repairing = true.

There is nothing specific you need to do to allow multiple phones to bond with the nRF other then reserving enough FDS pages to hold the bonding data (the default configuration of 2 pages plus 1 swap page is probably enough unless you need a very high number?).

RE: NRF52 BLE connection terminiated by Apple device after reconnect

Bing — Fri, 04 Jan 2019 11:29:08 GMT

Hi Einar,

In fact, I want to find an example to that allow multiple phones to connect with nRF with pairing and bonding in SDK15.0 by using BLE_GAP_IO_CAPS_NONE. And also permit repairing with the the phone device that already pairing with it. But I don't know which example can meet my requirment. Maybe the problem is caused by my wrong modifications to the ble_app_ancs_c example.

RE: NRF52 BLE connection terminiated by Apple device after reconnect

Einar Thorsrud — Fri, 04 Jan 2019 09:55:58 GMT

Hi,

I have a few questions:

Can you confirm that you only do pairing, not bonding (from the defines you have listed it seems like you do bonding as well)?
If you do bonding, do you delete bonds on either the phone(s) or nRF at any point during the procedure you have described?
Can you upload a sniffer trace that shows the sequence you have described?