device context storing issue

[sunil kumar]

what is the procedure to find connected device is bonded or not, should i store the device, application or service context in persistent memory to help recognizing bonded devices? Iam using SDK10.0 and SoftDevice Version 110. iam using device manager for handling bonding process.

EDIT1: Actually the device was getting paired but not getting bonded. So the bonded device were not getting recognized.

I have attached the debug log trace here

[Sigurd]

Take a look at the function dm_ble_evt_handler() in device_manager_peripheral.c. Here bonded devices are stored in the bonded device list(m_connection_table).

In order to check if a device already exists in the bonded device list, the function device_instance_find() is used. If the device exits in the list, the function returns NRF_SUCCESS.

[sunil kumar]

I have inserted a breakpoint at Event DM_EVT_DEVICE_CONTEXT_STORED in call back function device_manager_evt_handler, which was not hit, does the processor still stores the bonding information?

[sunil kumar]

can we clear the data in the bonded device list (m_connection_table)? i want to do this because iam using passkey pairing, there are situations where passkey is changed, when passkey is changed all bonded devices should pair again.

[Sigurd]

You can't clear it directly, if you want to delete all the bond information, you need to use the function dm_device_delete_all

[sunil kumar]

the function device_instance_find() is returning NRF_ERROR_NOT_FOUND for already paired devices, i think it is not storing device information, and dm_device_add() is not implemented, is there any way to make this work.

dm_device_delete_all() is deleting my eeprom memory which i use to store data. is there any way to delete devices and retain our eeprom data?

[sunil kumar]

I inserted a breakpoint at event DM_EVT_DEVICE_CONTEXT_STORED in call back function device_manager_evt_handler(), which was not hit.