BLE pairing issue when BT_SECURITY_L4 with nRF5340

RE: BLE pairing issue when BT_SECURITY_L4 with nRF5340

Hung Bui — Thu, 30 Dec 2021 09:44:22 GMT

Thanks, I would suggest to test with the peripheral_sc_only, just in case if it works, then you can use it as the reference.

RE: BLE pairing issue when BT_SECURITY_L4 with nRF5340

SanketC — Thu, 30 Dec 2021 09:22:16 GMT

Hi Hung,

Actually, I have not used peripheral_sc_only example. I am using central_uart and peripheral_uart in which I have enabled the security. I shall try to provide the file with minimum changes on which you can reproduce this issue. Give me some time. I shall get back to you on this.

Regards,

RE: BLE pairing issue when BT_SECURITY_L4 with nRF5340

Hung Bui — Wed, 29 Dec 2021 15:22:10 GMT

Hi SC,

Could you provide the sample that can reproduce the issue so I can test here ?
I did a quick test with the peripheral_sc_only and the nRF Connect Desktop but couldn't reproduce the issue on the peripheral side. The central was able to re-connect after disconnect.

RE: BLE pairing issue when BT_SECURITY_L4 with nRF5340

SanketC — Wed, 29 Dec 2021 05:50:45 GMT

Hello Hung,

I have already gone through the case shared by you. Please see my reply below for your question:

You mentioned "if peripheral or central is unable to call bt_conn_auth_passkey_confirm() ", what exactly happened there ? Was bt_conn_auth_cancel() called or the connection simply dropped from one side at that time ?

SC: basically there is one use case because of that central and peripheral is not able to call bt_conn_auth_passkey_confirm() so after approx 10seconds I get " SMP time out " and "security failed" log I get from security_changed() call back. After this, if If I try to again pair then I get "Found valid connection in the disconnected state".

So, I want to clear out this reference and start fresh pair.

Best Regards,

RE: BLE pairing issue when BT_SECURITY_L4 with nRF5340

Hung Bui — Tue, 28 Dec 2021 13:20:59 GMT

Hi Sanket,

Can the issue be reproduced using the peripheral_sc_only example ? So we can test here.

You mentioned "if peripheral or central is unable to call bt_conn_auth_passkey_confirm() ", what exactly happened there ? Was bt_conn_auth_cancel() called or the connection simply dropped from one side at that time ?

We have a case with similar error, could you have a look and check if the solution there can help ?
https://devzone.nordicsemi.com/f/nordic-q-a/68150/bluetooth-codded-phy-couldn-t-connect-after-disconnecting-w-found-valid-connection-in-disconnected-state