[nRF52833] Bonding again with already bonded Central fails

RE: [nRF52833] Bonding again with already bonded Central fails

Vidar Berg — Fri, 16 Dec 2022 07:42:19 GMT

Hi Marco, Good catch! I am happy to hear you found the problem.

Calling ble_conn_state_init() after Peer manager init can lead to various hard to debug issues as it will clear the flags set by the peer manager during initialization. I have suggested to the SDK team that we have to find a way to make this clearer to users. For instance, by adding a note in the API documentation.

RE: [nRF52833] Bonding again with already bonded Central fails

Marco R — Thu, 15 Dec 2022 22:58:22 GMT

Hi Vidar, thank you very much for providing the example and especially for pointing me to the security_dispatcher.c relevant code.

I found the bug in my code. My call to pm_conn_sec_config_reply() was getting ignored by the security_dispatcher due to user_flag_is_acquired(m_flag_allow_repairing) failing.

The reason it was failing is because when I copy-pasted code between two example apps, I inherited the call to ble_conn_state_init() (which some examples call in services_init() ) which internally memsets to zero the global user flags m_bcs.acquired_flags -- which are checked by user_flag_is_acquired(m_flag_allow_repairing).

Removing that call fixed my issue.

Thanks for the help!

RE: [nRF52833] Bonding again with already bonded Central fails

Vidar Berg — Thu, 15 Dec 2022 21:16:19 GMT

Hi Marco, we have not been able to reproduce this here, unfortunately. I used the ble_app_hrs example from SDK 17.1.0 and created a new configuration for the nRF52833 DK (pca10100) with s113 and then tested it with an iPhone 12.

Here is the debug log I got when I had the phone bond again with the nRF:

And the project I used:

devzone.nordicsemi.com/.../6305.ble_5F00_app_5F00_hrs.zip

Maybe you can try to place a breakpoint at the two lines I have highlighted below to confirm where the security status ends up being set to BLE_GAP_SEC_STATUS_PAIRING_NOT_SUPP (133).

Best regards,

Vidar

RE: [nRF52833] Bonding again with already bonded Central fails

Marco R — Wed, 14 Dec 2022 18:59:56 GMT

Hi Sigurd, thanks for the reply. I'm using nRF5_SDK_17.1.0_ddde560. It reproduces with both iOS (iPhone13) and Android (Pixel 7)

RE: [nRF52833] Bonding again with already bonded Central fails

Sigurd — Wed, 14 Dec 2022 16:50:11 GMT

Hi,

I would also have assumed that passing allow_repairing=true was enough. I can try to reproduce the behavior here. What SDK version are you using? What kind of device did you use as central?