Multiperipheral and bonding

RE: Multiperipheral and bonding

Fabien Duay — Fri, 06 Jul 2018 14:05:24 GMT

ok, I've found the blocking point.

The first time I bonded my device and then unbonded on Android.

In the nrf chipset, the bonding informations were'nt deleted... and the repairing wasn't allowed, it is why I get disconnected every time...

RE: Multiperipheral and bonding

Fabien Duay — Thu, 05 Jul 2018 12:06:38 GMT

I have top stop for today my tests, a summary :

1. I haven't anymore the Fatal Error

2. I can bond only when, in the "peer_manager_init" func, I set the parameters as :

sec_param.bond = 0;
sec_param.kdist_own.enc = 0;
sec_param.kdist_own.id = 0;
sec_param.kdist_peer.enc = 0;
sec_param.kdist_peer.id = 0;

3. I cannot bond when, in the "peer_manager_init" func, I set the parameters as :

sec_param.bond = 1;
sec_param.kdist_own.enc = 1;
sec_param.kdist_own.id = 1;
sec_param.kdist_peer.enc = 1;
sec_param.kdist_peer.id = 1;

I uploaded a simplified version of the project I'm using.

This version allow the bonding, change the sec_param as said before and you won't be able to bond anymore.devzone.nordicsemi.com/.../bond_5F00_tests.zip

RE: Multiperipheral and bonding

Fabien Duay — Thu, 05 Jul 2018 11:42:14 GMT

Hi,

After some tests without results, I tried to recompile your exemple project, upload it to my DK board (with a previsous erase all) and I cannont bond anymore..

I have the same problem as with my own project..

I wrote some NRF_LOG in the "ble_evt_handler" function and here what I received : (The number is the event id (p_ble_evt->header.evt_id))

<info> app: ble_evt_handler : 19 -> BLE_GAP_EVT_SEC_PARAMS_REQUEST
<info> app: ble_evt_handler : 25 -> BLE_GAP_EVT_AUTH_STATUS
<info> app: ble_evt_handler : 18 -> BLE_GAP_EVT_CONN_PARAM_UPDATE
<info> app: ble_evt_handler : 18 -> BLE_GAP_EVT_CONN_PARAM_UPDATE
<info> app: ble_evt_handler : 17 -> BLE_GAP_EVT_DISCONNECTED
<info> app: BLE_GAP_EVT_DISCONNECTED
<info> app: Connection 0x0 has been disconnected. Reason: 0x13

For information, I tried to bond with nRF Connect Android app.

RE: Multiperipheral and bonding

Fabien Duay — Thu, 05 Jul 2018 08:25:58 GMT

Hi Vidar,

Your exemple seem to work fine with bonding.

After a short comparison, I've seen that I call the "peer_manager_init" function too early. I deplaced the function call as you did, just before the "advertising_start" func.

The fatal error is no more displayed. One good point.

But.. the bonding isn't functionnal, when I try to bond, I'm simply disconnected from the peripheral.

RE: Multiperipheral and bonding

Vidar Berg — Thu, 05 Jul 2018 06:57:46 GMT

Hi,

Handling of BLE_GATTS_EVT_SYS_ATTR_MISSING should be removed from ble_evt_handler() as it is being handled by the PM. However, not sure it is related to the error you got. You can add "DEBUG" to the list of pre-processor definitions to get a more detailed error message (file name, line number, and error code).

I did try to add bonding to the multi-peripheral in SDK 15 to see if I could reproduce the problem as well. Here is the project if you want to compare:

devzone.nordicsemi.com/.../ble_5F00_app_5F00_multiperipheral_5F00_w_5F00_bond.zip