peer_manager stored Incorrect peer MAC address

[tsekioka]

Hello.
A re-connection failure problem happens on our products.

chip:nRF52832
SoftDevice:S132
SDK v11.0

1. pairing and bonding on LESC
2. reset connection and re-connect
3. Expect, Encrypt with stored Key
Result, re-send pairing request

I dumped Device flash and
found PM_PEER_DATA_ID_BONDING data.
The stored peer address is mismatch with bonded peer device.

Correct peer Address:DF:75:C4:1B:17:12(static random)
Stored peer Address:DF:75:C6:1B:17:12(static random)

I found that this probrem happens on specified peer device.
Even if delete bond information and re-pairing, same probrem occur.

The problem occurred in the sales products, so we stop selling.

thanks regard.

STORED DATA
10 D000 00 [FDS_PAGE_TAG_MAGIC]DEC0ADDE [FDS_PAGE_TAG_DATA]FE011EF1 [record_key bonding data]07C0 [length]1400 [field_id]00C0 [crc16]0000
10 D010 00 [record_id]01000000 [role]02 [irk]2F9F9A5017D6CAA4CA471B
10 D020 00 B67C261265 [addr_type]01 [addr]12171BC675DF [peer ltk]00000000
10 D030 00 000000000000000000000000 [lesc:1, auth:1, ltk_len:6]00 [ediv]0000 [rand]00
10 D040 00 00000000000000 [own ltk]00CE61CB491B64CA89
10 D050 00 8BA6A9CA1C0AAA [lesc:1, auth:1, ltk_len:6]5B [ediv]4100 [rand]000000000000
10 D060 00 00000000 [record_key peer_rank]06C0 [length]0100 [field_id]00C0 [crc16]0000 [record_id]02000000

bonding_problem.xlsx

[tsekioka]

I tried to change peer device address type to public static.

Set address is DF:75:C4:1B:17:12 but peer device SoftDevice use DF:75:C6:1B:17:12.

I think that SoftDevice has some limitation on MAC address.

[Simon]

I am back in office and am currently looking into your issue.

[Simon]

It is difficult to say what is causing the error, if you look at the release notes for SDK 12.3 you can find the following comment:

"Fixed a bug in Peer Manager which made it possible for Peer Manager to corrupt the flash memory under certain circumstances."

Where it is a bug in pds_peer_data_store() in peer_manager where the module attempts to cancel a reservation of flash space made with fds using fds_reserve_cancel() and  an incorrect parameter is passed to fds, ultimately leading fds page offsets to become corrupted and thus corrupt the flash as well.

However, this happened in SDK 12.2, and it seems like the Peer Manager is organized different in SDK 11. Thus, I am not sure if this is related to your bug.

Could you upload your project? Then I could try to recreate the error.

Best regards,

Simon

[tsekioka]

Sorry for the late reply.

This problem was caused by the failure to apply nRF52832 errata 108.

It's not a peer manager problem.

Best regards.