Bonding issue when using synthesized clock (BLE on NRF5340)

RE: Bonding issue when using synthesized clock (BLE on NRF5340)

weamx — Sun, 05 Jan 2025 07:51:20 GMT

Hello,

I encountered a similar issue, which took me a couple of days to resolve. While your situation might not be identical, the solution that worked for me was to ensure that the network core configuration matched the application core configuration. Specifically (in your case), just add the following lines to the network core configuration:

CONFIG_SOC_ENABLE_LFXO=n
CONFIG_CLOCK_CONTROL_NRF_K32SRC_SYNTH=y

Also you can check this bluetooth-won-t-connect thread for more information

Hope this helps!

RE: Bonding issue when using synthesized clock (BLE on NRF5340)

Susheel Nuguru — Mon, 12 Aug 2024 05:53:13 GMT

Thomas,

Unfortunately no, I might have to include some hardware experts into this. This might take some time. Will be back to you when I have some insights.

RE: Bonding issue when using synthesized clock (BLE on NRF5340)

thomas_hexploy — Wed, 07 Aug 2024 11:03:35 GMT

Hello,

Do you have any news ?

Thank you.

RE: Bonding issue when using synthesized clock (BLE on NRF5340)

Susheel Nuguru — Wed, 31 Jul 2024 08:52:22 GMT

I can reproduce this.

Actually you need to set this config in both cores also in child_image\hci_ipc.conf file.

But still it does not work. We have had issues using synth clock in older SDKs but we thought we fixed it. It seems like the issues are still there. i will have to spend more time on this to investigate. Will be back to you when I have more info or have heard some insights from the experts in the softdevice team,

RE: Bonding issue when using synthesized clock (BLE on NRF5340)

Susheel Nuguru — Mon, 29 Jul 2024 16:36:38 GMT

I will try to test this tomorrow. You seems to have provided enough info to attempt to replicate the issue.

RE: Bonding issue when using synthesized clock (BLE on NRF5340)

thomas_hexploy — Mon, 29 Jul 2024 11:00:17 GMT

Hello,

I used this example because he has L2 security. Security layer is not related to the upper layers (so even if example targets iOS, bonding should work everywhere).

Anyway, I tried `peripheral_cts_client` example, and in the connected callback I added:

bt_conn_set_security(conn, BT_SECURITY_L2);

=> I can reproduce the issue using this example.

RE: Bonding issue when using synthesized clock (BLE on NRF5340)

Susheel Nuguru — Mon, 29 Jul 2024 06:57:34 GMT

Yes, please try with an iphone and see if you have the same issue.

RE: Bonding issue when using synthesized clock (BLE on NRF5340)

billtsai — Mon, 29 Jul 2024 03:30:34 GMT

Hi,

ANCS is for iOS only. Maybe you should try it with iPhone.