About nRf52832 not received the event of PM_EVT_PEER_DATA_UPDATE_SUCCEEDED when pairing to windows 10

[Aileen Wang]

Hi all,

The chip we used is nRf52832,  the version of SDK I used is nRF5_SDK_15.2.0_9412b96.

The problem is when I pair to windows 10, sometimes PM_EVT_PEER_DATA_UPDATE_SUCCEEDED event not received.

BLE_GAP_EVT_CONN_SEC_UPDATE event and BLE_HIDS_EVT_NOTIF_ENABLED event I have received.

And device can receive data from host, but without  PM_EVT_PEER_DATA_UPDATE_SUCCEEDED event peer id and white list 

can not be updated and reconnecting process will fail.

So we think this case as incomplete pairing process.

My question is why sometime we can't get the PM_EVT_PEER_DATA_UPDATE_SUCCEEDED event.

Thanks.

Aileen Wang

[haakonsh]

You need to catch this event with a sniffer trace

[Aileen Wang]

Hi I have captured the air trace for this issue, the problem occurred at the time 17:15:29 china time, packet number is  375512, the bt address of the device is CE:38:DB:D9:4F:4A , that pair process the device didn't receive the event of  PM_EVT_PEER_DATA_UPDATE_SUCCEEDED and BLE_HIDS_EVT_NOTIF_ENABLED, so the pair process failed, but it showed success in the host side. Pair and become brick problem 171529_07312020.zip

[Kenneth]

Update: I think I found the issue, see next reply.

[Kenneth]

Looking at the case it seems that during the problematic connection, that Windows 10 do not distribute the SMP identity address information (BDADDR). According to the BLE specification:

"BLUETOOTH CORE SPECIFICATION Version 5.2 | Vol 3, Part H page 1680
IdKey is a 1-bit field that is set to one to indicate that the device shall
distribute IRK using the Identity Information command followed by its public
device or static random address using Identity Address Information."

In the problematic connection the central only disitribute the IRK, not the public address.

Best regards,
Kenneth