Disconnected, reason 62 in nrf5340 DK kit

RE: Disconnected, reason 62 in nrf5340 DK kit

Vidar Berg — Mon, 03 Mar 2025 16:14:08 GMT

All three pictures show a central in a connection with a peripheral device but I don't know which devices these are. The capture should include the failing case where your central is sending the connect ind packet but failing to establish the connection. What happens when you try to upload the capture files?

RE: Disconnected, reason 62 in nrf5340 DK kit

Aravibala — Fri, 28 Feb 2025 08:40:02 GMT

Hi,

thank you for the mail, i tried to use sniffer to capture the events during the error reason 62 using nrf dongle. since I'm a new to the controller, I'm not sure how to identity the issue looking into the log. i'm not sure how to add the log file in the chat since there is no option to add a file i'm providing the snap of the log.

Moreover i tried to add the config bit to enable internal RC as per the example you have mentioned in added the config file under the directory child and also have added a folder called boards and added nrf5340dk_nrf5340_cpuapp.conf as well but still i get the error 62 and i gets a warning as CONFIG_SOC_ENABLE_LFXO was already disabled. Missing dependencies:
SOC_NRF5340_CPUAPP can u plz tel what is difference between using conifg file in board folder , child folder and directly in the project as .confg file

RE: Disconnected, reason 62 in nrf5340 DK kit

Vidar Berg — Thu, 27 Feb 2025 09:07:11 GMT

Hi,

In v2.6.0 you can create a folder named 'child_image' in your project root to apply configuration changes to the child images. Like in the throughput sample here: https://github.com/nrfconnect/sdk-nrf/tree/v2.6.3/samples/bluetooth/throughput/child_image (Permanent configuration changes to child images). Alternatively, you can change the default clock source in your board file if you have defined your own board instead of building for the nRF5340 DK.

The BT_HCI_ERR_CONN_FAIL_TO_ESTABL error is raised by the controller when the peer device does not respond to the CONNECT_IND packet after six connection events. In your previous ticket, I suggested capturing a BLE sniffer trace to help troubleshoot this.

RE: Disconnected, reason 62 in nrf5340 DK kit

Aravibala — Wed, 26 Feb 2025 22:58:37 GMT

hi vidar, thank you for the mail the nrf sdk I'm currently using is 2.6.0 . kindly let me know the steps

moreover if the clock drift is not the issue since I'm using the nordic DK kit then what else would be the issue because i even tried increasing the maximum time out time to 10 sec form default 3 sec using the configuration bit but still i get this error hoe can i determine what exactly causes this error.

RE: Disconnected, reason 62 in nrf5340 DK kit

Vidar Berg — Wed, 26 Feb 2025 18:06:15 GMT

Hi,

It it is not very likely to be related to clock drift if you are testing with a nRF5340 DK on both ends of the link, but you can rule out this possibility by changing to the internal RC oscillator. Please let me know the SDK version you are on so I explain the steps for changing the clock source on the netcore.

Best regards,

Vidar