nRF52/S132: pm_conn_secure fails with error 0x200038B0

[Kraust]

I've ported an nRF51 DK project over to the nRF52 DK and the only issue I seem to have with the nRF52 is that the device refuses to pair with my peripheral, hard faulting when I make a call to pm_conn_secure with the force re-pairing argument set to true.

Previously, on the nRF51 this worked without issue.

Deep inside the peer manager code the error code is generated by pds_peer_data_read_ptr_get() which returns NRF_ERROR_NOT_FOUND.

Did the initialization of the peer manager change between the S130 and S132? Any insight on what is going on would be helpful.

[Petter Myhre]

Do you get a hard fault or do you get a reset because APP_ERROR_CHECK() is called with an error code? When do you see this behavior? Are you re-pairing to a peripheral that you have a bond with? Or is this the initial pairing? Let me know, and I'll try to reproduce.