This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Error (NRF_ERROR_TIMEOUT) when using nRF Connect

Hi, I am attempting to use the Bluetooth Low Energy Application v2.4.2 in nRF Connect v3.6.0 to connect the nRF5340 board. However, when I do so, two errors pop up:

Received status with code 0 PKT_SEND_MAX_RETRIES_REACHED, message: 'No response from device. Tried to send packet 6 times.'

and
Error occured when opening port. Errorcode: NRF_ERROR_TIMEOUT (0xd)
After searching through these forums, I found someone with a similar problem.
However, this person wiped their board and got it working.
When I wipe my board, either through the command line or through the nRF Connect programmer, the problem persists.
I have attached the logs below. Thank you for your help.

2020-11-11T20:32:36.323Z INFO Application data folder: C:\Users\Ben\AppData\Roaming\nrfconnect\pc-nrfconnect-ble
2020-11-11T20:32:36.391Z DEBUG App pc-nrfconnect-ble v2.4.2 official
2020-11-11T20:32:36.391Z DEBUG App path: C:\Users\Ben\.nrfconnect-apps\node_modules\pc-nrfconnect-ble
2020-11-11T20:32:36.391Z DEBUG nRFConnect 3.6.0 is supported by the app (^3.6.0)
2020-11-11T20:32:36.391Z DEBUG nRFConnect path: C:\Users\Ben\AppData\Local\Programs\nrfconnect\resources\app.asar
2020-11-11T20:32:36.392Z DEBUG HomeDir: C:\Users\Ben
2020-11-11T20:32:36.392Z DEBUG TmpDir: C:\Users\Ben\AppData\Local\Temp
2020-11-11T20:33:28.974Z INFO Connected to device with serial number: 000960171454 and family: nrf53 
2020-11-11T20:33:28.974Z DEBUG Note: no pre-compiled firmware is available for the selected device. You may still use the app if you have programmed the device with a compatible connectivity firmware.
2020-11-11T20:33:28.974Z INFO The device is not in the list of supported devices. Attempting to open as a custom device.
2020-11-11T20:33:28.974Z INFO Opening custom device
2020-11-11T20:33:28.974Z INFO Note: firmware must be compatible with connectivity firmware version: 4.1.2, SoftDevice API version: 5 and baud rate: 1000000.
2020-11-11T20:33:28.975Z INFO Opening adapter connected to COM4
2020-11-11T20:33:29.895Z INFO Successfully opened COM4. Baud rate: 1000000. Flow control: none. Parity: none.
2020-11-11T20:33:29.895Z DEBUG State change: STATE_START -> STATE_RESET
2020-11-11T20:33:29.896Z DEBUG        1 ->  [N/A] type:          RESERVED_5 reliable: no seq#:0 ack#:0 payload_length:0 data_integrity:0 err_code:0x0
2020-11-11T20:33:29.896Z INFO Reset performed on adapter COM4
2020-11-11T20:33:30.197Z DEBUG State change: STATE_RESET -> STATE_UNINITIALIZED
2020-11-11T20:33:30.197Z DEBUG        2 ->  [01 7e ] type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:2 data_integrity:0 err_code:0x0 [SYNC]
2020-11-11T20:33:30.447Z DEBUG        3 ->  [01 7e ] type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:2 data_integrity:0 err_code:0x0 [SYNC]
2020-11-11T20:33:30.698Z DEBUG        4 ->  [01 7e ] type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:2 data_integrity:0 err_code:0x0 [SYNC]
2020-11-11T20:33:30.949Z DEBUG        5 ->  [01 7e ] type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:2 data_integrity:0 err_code:0x0 [SYNC]
2020-11-11T20:33:31.199Z DEBUG        6 ->  [01 7e ] type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:2 data_integrity:0 err_code:0x0 [SYNC]
2020-11-11T20:33:31.450Z DEBUG        7 ->  [01 7e ] type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:2 data_integrity:0 err_code:0x0 [SYNC]
2020-11-11T20:33:31.700Z DEBUG State change: STATE_UNINITIALIZED -> STATE_NO_RESPONSE
2020-11-11T20:33:31.700Z ERROR Received status with code 0 PKT_SEND_MAX_RETRIES_REACHED, message: 'No response from device. Tried to send packet 6 times.'
2020-11-11T20:33:32.896Z DEBUG serial port read on port COM4 aborted.
2020-11-11T20:33:32.897Z INFO serial port COM4 closed.
2020-11-11T20:33:32.913Z ERROR Error occured when opening port. Errorcode: NRF_ERROR_TIMEOUT (0xd)

Related