Bonding Information/ Whitelist

[annapalu]

Hi all,

Is there a tutorial that explain better the bonding information and whitelist? I have more doubt about that.

My first code i have pairing and bonding:

1. If i delete bonding information from app side, connection fail i delete information on nrf52 side, too and connection is ok
2. I delete information on nrf52, conenction fail, i delete information bonding also on phone side and connection is ok.

After i need to add a whitelist to have a connection one to one, so i have a second release of code.

The option 1 doesn't works, the connection fails always, though i delete the information on nrf52 side.(Pairing reject)

i resolve the problem setting this flag to false:

  case PM_EVT_CONN_SEC_CONFIG_REQ:
     {
     // Reject pairing request from an already bonded peer.
     pm_conn_sec_config_t conn_sec_config = {.allow_repairing = false};
     pm_conn_sec_config_reply
   }

but i would to understand why when i have added the whitelist, i haven't problem with option 1. When i use

   uint32_t err_code ;
   err_code = pm_peers_delete();
   APP_ERROR_CHECK(err_code);

i don't delete the bonding information? How the softdevice understand that the pairing is with an already bonding device, after i delete the bonding information?

thanks, Anna

[annapalu]

HI Petter, what don't you understand? I have two code version. One without white list and one with white list. In both version i reproduce the scenario where i delete the bonding information of only one side in first time and after the connection failed i delete the bonding information on in the other side too.

In the case i add whitelist and delete in bonding information on APP side first, and after in nrf52 after the pairing is always reject. I would understand better the relationship between whitelis and bonding information.