RE: ble bonding infos decoding

astella — Wed, 21 Oct 2020 10:26:40 GMT

Thank you sir, very nice reply

RE: ble bonding infos decoding

Dmitry — Wed, 21 Oct 2020 10:22:01 GMT

Hi,

Bonding info along with GATT cache data is written by peer manager to FDS storage space as a set of records - if you're curious, the format of FDS record itself can be found in components/libraries/fds/fds.h. The highlited block of data is not a single record but a sequence of different ones - see components/ble/peer_manager/peer_manager_types.h.

[quote userid="78952" url="~/f/nordic-q-a/67459/ble-bonding-infos-decoding"]How many are available[/quote]

As many as you have space in FDS.

[quote userid="78952" url="~/f/nordic-q-a/67459/ble-bonding-infos-decoding"]What happens when there is no any more room?[/quote]

Peer manager will initiate a garbage collection procedure - the whole flash space will be compacted by throwing away old records marked for deletion. If there's really no space (FDS is full), it's not surprizing that bonding info will not be saved.

[quote userid="78952" url="~/f/nordic-q-a/67459/ble-bonding-infos-decoding"]Can you please help me in finding out the right documentation, or provide one such structure example if possible?[/quote]

For example, you can find the format of bonding data (pm_peer_data_bonding_t structure) in components/ble/peer_manager/peer_manager_types.h. I don't think it's a good idea to work with these records directly, it's much better to use peer manager API.