PM_EVT_CONN_SEC_FAILED

[mzarling]

I am developing a Central/Peripheral application with SDK 15.2.0 for s132 device on nRF52 development kits. I switch back and forth between my application and the example "ble_app_hrs_rscs_relay" on my nRF52 development boards. In doing so, eventually my nRF52 development boards will throw the error PM_EVT_CONN_SEC_FAILED when running on my application firmware and connecting to a peripheral device. I can never get PM_EVT_CONN_SEC_SUCCEEDED again on this nRF52 development board operating as a Central and Peripheral. When I put my application firmware on a new nRF52 DK, it runs fine and gets PM_EVT_CONN_SEC_SUCCEEDED every time it connects to a peripheral BLE device. This has happened to me with two nRF DKs and now I'm working with a 3rd, but I have not cycled between the "ble_app_hrs_rscs_relay" and my application firmware. I have only been programming it with my application firmware and it has been running fine. I have tried "erase all" on the problem DKs and this didn't help.

[Simon]

Are you able to reproduce the error?  If so,  take a look at the log in pm_handler_pm_evt_log(..)  (In the peer_manager_handler.c) and check which procedure failed (pm_conn_sec_procedure_t) and the error code (pm_sec_error_code_t).

Best regards,

Simon

[mzarling]

<info> peer_manager_handler: Connection security failed: role: Central, conn_handle: 0x0, procedure: Bonding, error: 133

Is this what you asked for?

[mzarling]

Hi Simon. I never said that I got a procedure failed of 133 (0x85), so I'm not sure your suggested changes in im_ble_evt_handler() are relevant.

[Simon]

mzarling said:

<info> peer_manager_handler: Connection security failed: role: Central, conn_handle: 0x0, procedure: Bonding, error: 133

Is this what you asked for?

[mzarling]

My mistake, sorry. I will set the breakpoint as suggested and proceed from there.

[Simon]

No problem. Let me know if you have any more issues.

[mzarling]

Hi Simon. I've been assuming that the problem resided on my nRF52 development boards because that is where I am developing new code, which is operating as a Central and Peripheral. Performing an erase all on these boards never changed the PM_EVT_CONN_SEC_FAILED symptom.

Today I performed an erase all on our custom BLE device which acts as a peripheral. It is the device that my Central/Peripheral must automatically connect to. The erase all and reprogramming of the custom peripheral device caused the failed Central/Peripheral nRF52 boards to start working again.

[Simon]

That's great, I'm happy you finally figured it out.