Bonding Information not stored in Flash memory

[naman.trivedi]

I am using nrf52 with SDK 14.2.0 and SD is S132.

The issue I am facing is that after Central is paired with one peripheral and bonding is done, the bonding information is not stored by central and so the next time when the already bonded peripheral tries to connect with the Central, it follows pairing and bonding procedure. Below are the peer manager events that I am getting:

1. PM_EVT_CONN_SEC_PARAMS_REQ

2. PM_EVT_CONN_SEC_SUCCEEDED

3. PM_EVT_CONN_SEC_PARAMS_REQ

4. PM_EVT_CONN_SEC_SUCCEEDED

The above events are coming for new device as well as already paired device.

Also, one issue I think is I am never getting PM_EVT_PEER_DATA_UPDATE_SUCCEEDED event even after bonding is done. Also one more strange behavior is that my system event handler, which I registered using NRF_SDH_SOC_OBSERVER, is never called.

Can you please help me to resolve this issue?

[Vidar Berg]

Hi,

It sounds like the devices are being paired and not bonded. Please verify that the bond flag is set to 'true' when you initialize the PM module:

static void peer_manager_init(void)
{ 

   ...

   sec_param.bond           = SEC_PARAM_BOND;

   ...

Then check if the peer device supports bonding as well . This will be reported through the PM_EVT_CONN_SEC_PARAMS_REQ event:

[Matt]

So your nRF52 is running as a GAP central role? Can you share your bare minimal GAP central code here?

[naman.trivedi]

1. Yes, SEC_PARAM_BOND is true.

2. yes, peer device also supports bonding. I am using same, nrf52 as peer device which will be in peripheral role. The peer device uses SoftDevice 2.0 and the central is using SoftDevice 5.0. Can that be an issue?

[naman.trivedi]

I can share specific part of the code. Can you tell me what exactly I should share?

[Matt]

Ideally it should be a whole project that the Nordic support folks can take and compile and execute right away. So make sure it's bare bone and does not contain any proprietary and sensitive info from your company :)