This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

DM_EVT_DEVICE_CONTEXT_DELETED notified dm_device_delete

I'd like to do the same thing : how to use dm_device_delete

  • nRF51822 S110 v8.0.0
  • nRF51 SDK v10.0.0
  • DEVICE_MANAGER_MAX_BONDS=2

I test Nexus5, Nexus7, iPad mini for peer device. Nexus5 and iPad mini work well, but Nexus7 always fails.

"dm_device_delete_all_except_this()" is called in DM_EVT_SECURITY_SETUP_COMPLETE and returns NRF_SUCCESS.
System event dispatch function called with NRF_EVT_FLASH_OPERATION_SUCCESS 3times and NRF_EVT_FLASH_OPERATION_ERROR 3times.
And DM_EVT_DEVICE_CONTEXT_DELETED is notified(event_result=0x000D).

"dm_device_delete_all_except_this()" is called in DM_EVT_DEVICE_CONTEXT_STORED or DM_EVT_SERVICE_CONTEXT_STORED, and it sames.

What can I do ?

Thanks.

Parents
  • I do not quite get what your question is. There are some issues with Device Manager when the other device uses random private resolvable addresses. The entry in the bonding table is not resolved correctly, which leads to multiple entries on bonding. This may be related, i.e. the bonded device is not found in the table and gets deleted. The issue is fixed with the new Peer Manager, available from SDK 11.

Reply
  • I do not quite get what your question is. There are some issues with Device Manager when the other device uses random private resolvable addresses. The entry in the bonding table is not resolved correctly, which leads to multiple entries on bonding. This may be related, i.e. the bonded device is not found in the table and gets deleted. The issue is fixed with the new Peer Manager, available from SDK 11.

Children
No Data
Related