Quickest simplest way to delete BLE bond infos for test purposes

RE: Quickest simplest way to delete BLE bond infos for test purposes

astella — Fri, 11 Sep 2020 07:25:22 GMT

Bonding infos are saved in normal flash. It is simple to find out where using all great tools Nordic provide. For example it is possible to like a diff using nRFConnect and the 'Program' utility to visually show memory areas and comparing memory areas length before and after doing a bonding. So it is definitely normal flash and can be erased with normal flash routines. the advantage in using pm_peers_delete() should be related to the fact that it uses a sophisticated flash memory handling, able to treat flash as a file system and to selectively delete/invalidate the smallest amount of flash possible. So that it is good also for flash life. This is what I understood

RE: Quickest simplest way to delete BLE bond infos for test purposes

astella — Fri, 04 Sep 2020 14:11:41 GMT

Thank you very much, so bonding infos are stored starting from BOOTLOADER_START_ADDR and going down there (the flash sector that comes before the bootloader)? Is it possible to delete as normal flash in case we want to delete all bond infos only for test purposes? Why is it convenient to use pm_peers_delete? Is there any info how bonding infos are structured in memory? Is it part of BLE specifications? Is there a way you suggest, like a tool to directly read and encode those infos? Any special command in nrfjprog so to interact with bonding infos?

Why should we use

pm_peers_delete instead of a simple flash sector erase?

I managed to use pm_peers_delete successfully. But after doing another bonding, I cannot delete bond infos anymore, when calling pm_peers_delete again ( every time a usb set feature command has been sent so to trigger pm_peers_delete )

Thank you

RE: Quickest simplest way to delete BLE bond infos for test purposes

Sigurd — Fri, 04 Sep 2020 13:55:16 GMT

Hi,

The pm_peers_delete() function is the correct function to use for this.If you are using a bootloader, peer manager bond data will be stored right below the bootloader: https://infocenter.nordicsemi.com/topic/sdk_nrf5_v17.0.0/lib_bootloader.html#lib_bootloader_memory