Error (NRF_ERROR_TIMEOUT) when using nRF Connect

[RSA]

Hi, when following the tutorial, https://devzone.nordicsemi.com/nordic/short-range-guides/b/bluetooth-low-energy/posts/ble-advertising-a-beginners-tutorial i ran into problems.

I running and building/flashing to the nRF52840 DK (using segger and SDK 15.0.0 without any noticeable issues.

The problem appears when using "Connect v 3.1.0 Bluetooth low energy"

i've made sure to test my UART in other projects (as mentioned in https://devzone.nordicsemi.com/f/nordic-q-a/28729/nrf-connect-error-nrf_error_timeout).

I haven't followed the " nRF Connect getting started assistant" since im using  the fore mentioned SDK, hopefully this doesn't cause any issues?

Update: i have know tried to flash the 140 softdevice on it's own.. the connector works this way, meaning that the connection is solid.. But the Issue at hand remains.

[Simonr]

Hi

Please try erasing the program on your device, either using nrfjprog or the programmer app in nRFConnect and try connecting using the Bluetooth Low Energy app again. You should get a pop-up saying: Device must be programmed, do you want to proceed? Confirm this, and see if you're able to connect successfully. 

Also, please upload the log you see when you get this error message, so I can have a better look at the error messages. You can press the Open log file button (third from the right in the bottom right corner) to open a log file and upload that.

Best regards,

Simon

[RSA]

I am able to connect sucessfully using the procedure you wrote.

I attached the LOG file.

Fullscreen 2019-08-26T09_16_47.901Z-log.txt Download

2019-08-26T09:16:48.994Z INFO Application data folder: C:\Users\RAbbas\AppData\Roaming\nrfconnect\pc-nrfconnect-ble
2019-08-26T09:16:49.171Z DEBUG App pc-nrfconnect-ble v2.3.1 official
2019-08-26T09:16:49.171Z DEBUG App path: C:\Users\RAbbas\.nrfconnect-apps\node_modules\pc-nrfconnect-ble
2019-08-26T09:16:49.171Z DEBUG nRFConnect 3.1.0 is supported by the app (^3.0.0)
2019-08-26T09:16:49.171Z DEBUG nRFConnect path: C:\Users\RAbbas\AppData\Local\Programs\nrfconnect\resources\app.asar
2019-08-26T09:16:49.171Z DEBUG HomeDir: C:\Users\RAbbas
2019-08-26T09:16:49.171Z DEBUG TmpDir: C:\Users\RAbbas\AppData\Local\Temp
2019-08-26T09:16:50.384Z VERBOSE Could not fetch serial number for serial port at COM1
2019-08-26T09:16:50.384Z VERBOSE Could not fetch serial number for serial port at COM4
2019-08-26T09:16:51.099Z INFO Validating connectivity firmware for device with serial number 000683452187...
2019-08-26T09:17:01.912Z INFO Connectivity firmware is valid.
2019-08-26T09:17:01.912Z INFO Getting information from J-Link debugger...
2019-08-26T09:17:06.537Z INFO Found device type: unknown. J-Link firmware: J-Link OB-SAM3U128-V2-NordicSemi compiled Jan  7 2019 14:07:15.
2019-08-26T09:17:06.537Z INFO Connectivity firmware version: 4.1.1. SoftDevice API version: 3. Baud rate: 1000000.
2019-08-26T09:17:06.538Z INFO Opening adapter connected to COM5
2019-08-26T09:17:07.463Z INFO Successfully opened COM5. Baud rate: 1000000. Flow control: none. Parity: none.
2019-08-26T09:17:07.463Z DEBUG State change: STATE_START -> STATE_RESET
2019-08-26T09:17:07.463Z DEBUG        1 ->  [N/A] type:          RESERVED_5 reliable: no seq#:0 ack#:0 payload_length:0 data_integrity:0 err_code:0x0
2019-08-26T09:17:07.464Z INFO Reset performed on adapter COM5
2019-08-26T09:17:07.494Z DEBUG     1/ 0 <-  [01 7e ] type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:2 data_integrity:0 err_code:0x0 [SYNC]
2019-08-26T09:17:07.764Z DEBUG State change: STATE_RESET -> STATE_UNINITIALIZED
2019-08-26T09:17:07.764Z DEBUG        2 ->  [01 7e ] type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:2 data_integrity:0 err_code:0x0 [SYNC]
2019-08-26T09:17:07.796Z DEBUG     2/ 0 <-  [02 7d ] type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:2 data_integrity:0 err_code:0x0 [SYNC_RESP]
2019-08-26T09:17:07.796Z DEBUG State change: STATE_UNINITIALIZED -> STATE_INITIALIZED
2019-08-26T09:17:07.796Z DEBUG        3 ->  [03 fc 11 ] type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:3 data_integrity:0 err_code:0x0 [CONFIG [ sliding-window-size:1 out-of-frame:0 data-integrity-check-type:1 version-number:0 ]]
2019-08-26T09:17:08.047Z DEBUG        4 ->  [03 fc 11 ] type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:3 data_integrity:0 err_code:0x0 [CONFIG [ sliding-window-size:1 out-of-frame:0 data-integrity-check-type:1 version-number:0 ]]
2019-08-26T09:17:08.197Z DEBUG     3/ 0 <-  [01 7e ] type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:2 data_integrity:0 err_code:0x0 [SYNC]
2019-08-26T09:17:08.197Z DEBUG        5 ->  [02 7d ] type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:2 data_integrity:0 err_code:0x0 [SYNC_RESP]
2019-08-26T09:17:08.298Z DEBUG        6 ->  [03 fc 11 ] type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:3 data_integrity:0 err_code:0x0 [CONFIG [ sliding-window-size:1 out-of-frame:0 data-integrity-check-type:1 version-number:0 ]]
2019-08-26T09:17:08.331Z DEBUG     4/ 0 <-  [03 fc 11 ] type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:3 data_integrity:0 err_code:0x0 [CONFIG [ sliding-window-size:1 out-of-frame:0 data-integrity-check-type:1 version-number:0 ]]
2019-08-26T09:17:08.331Z DEBUG        7 ->  [04 7b 11 ] type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:3 data_integrity:0 err_code:0x0 [CONFIG_RESP [ sliding-window-size:1 out-of-frame:0 data-integrity-check-type:1 version-number:0 ]]
2019-08-26T09:17:08.549Z DEBUG        8 ->  [03 fc 11 ] type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:3 data_integrity:0 err_code:0x0 [CONFIG [ sliding-window-size:1 out-of-frame:0 data-integrity-check-type:1 version-number:0 ]]
2019-08-26T09:17:08.582Z DEBUG     5/ 0 <-  [04 7b 11 ] type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:3 data_integrity:0 err_code:0x0 [CONFIG_RESP [ sliding-window-size:1 out-of-frame:0 data-integrity-check-type:1 version-number:0 ]]
2019-08-26T09:17:08.582Z DEBUG State change: STATE_INITIALIZED -> STATE_ACTIVE
2019-08-26T09:17:08.600Z INFO Adapter connected to COM5 opened
2019-08-26T09:17:08.603Z DEBUG        9 ->  [00 60 01 0a 00 00 01 07 01 00 f7 00 00 00 00 00 00 ] type:     VENDOR_SPECIFIC reliable:yes seq#:0 ack#:0 payload_length:11 data_integrity:1 header_checksum:21 err_code:0x0
2019-08-26T09:17:08.623Z DEBUG     6/ 0 <-  [N/A] type:                 ACK reliable: no seq#:0 ack#:1 payload_length:0 data_integrity:0 err_code:0x0
2019-08-26T09:17:08.623Z DEBUG     7/ 0 <-  [01 60 00 00 00 00 ] type:     VENDOR_SPECIFIC reliable:yes seq#:0 ack#:1 payload_length:6 data_integrity:1 header_checksum:ca err_code:0x0
2019-08-26T09:17:08.623Z DEBUG       10 ->  [N/A] type:                 ACK reliable: no seq#:0 ack#:1 payload_length:0 data_integrity:0 err_code:0x0
2019-08-26T09:17:08.630Z DEBUG       11 ->  [00 66 01 ] type:     VENDOR_SPECIFIC reliable:yes seq#:1 ack#:1 payload_length:3 data_integrity:1 header_checksum:f9 err_code:0x0
2019-08-26T09:17:08.660Z DEBUG     8/ 0 <-  [N/A] type:                 ACK reliable: no seq#:0 ack#:2 payload_length:0 data_integrity:0 err_code:0x0
2019-08-26T09:17:08.660Z DEBUG     9/ 0 <-  [01 66 00 00 00 00 08 59 00 91 00 ] type:     VENDOR_SPECIFIC reliable:yes seq#:1 ack#:2 payload_length:b data_integrity:1 header_checksum:71 err_code:0x0
2019-08-26T09:17:08.660Z DEBUG       12 ->  [N/A] type:                 ACK reliable: no seq#:0 ack#:2 payload_length:0 data_integrity:0 err_code:0x0
2019-08-26T09:17:08.661Z DEBUG       13 ->  [00 7d 01 f8 00 01 ] type:     VENDOR_SPECIFIC reliable:yes seq#:2 ack#:2 payload_length:6 data_integrity:1 header_checksum:c0 err_code:0x0
2019-08-26T09:17:08.694Z DEBUG    10/ 0 <-  [N/A] type:                 ACK reliable: no seq#:0 ack#:3 payload_length:0 data_integrity:0 err_code:0x0
2019-08-26T09:17:08.695Z DEBUG    11/ 0 <-  [01 7d 00 00 00 00 01 05 00 6e 52 46 35 78 ] type:     VENDOR_SPECIFIC reliable:yes seq#:2 ack#:3 payload_length:e data_integrity:1 header_checksum:38 err_code:0x0
2019-08-26T09:17:08.695Z DEBUG       14 ->  [N/A] type:                 ACK reliable: no seq#:0 ack#:3 payload_length:0 data_integrity:0 err_code:0x0
2019-08-26T09:17:08.695Z DEBUG       15 ->  [00 6d 01 ] type:     VENDOR_SPECIFIC reliable:yes seq#:3 ack#:3 payload_length:3 data_integrity:1 header_checksum:e7 err_code:0x0
2019-08-26T09:17:08.732Z DEBUG SoftDevice BLE stack enabled.
2019-08-26T09:17:08.733Z DEBUG    12/ 0 <-  [N/A] type:                 ACK reliable: no seq#:0 ack#:4 payload_length:0 data_integrity:0 err_code:0x0
2019-08-26T09:17:08.733Z DEBUG    13/ 0 <-  [01 6d 00 00 00 00 02 92 9e a9 4d 6f e6 ] type:     VENDOR_SPECIFIC reliable:yes seq#:3 ack#:4 payload_length:d data_integrity:1 header_checksum:3f err_code:0x0
2019-08-26T09:17:08.733Z DEBUG       16 ->  [N/A] type:                 ACK reliable: no seq#:0 ack#:4 payload_length:0 data_integrity:0 err_code:0x0
2019-08-26T09:20:41.439Z DEBUG       17 ->  [05 01 ] type:     VENDOR_SPECIFIC reliable:yes seq#:4 ack#:4 payload_length:2 data_integrity:1 header_checksum:ee err_code:0x0
2019-08-26T09:20:41.684Z DEBUG       18 ->  [05 01 ] type:     VENDOR_SPECIFIC reliable:yes seq#:4 ack#:4 payload_length:2 data_integrity:1 header_checksum:ee err_code:0x0
2019-08-26T09:20:41.935Z DEBUG       19 ->  [05 01 ] type:     VENDOR_SPECIFIC reliable:yes seq#:4 ack#:4 payload_length:2 data_integrity:1 header_checksum:ee err_code:0x0
2019-08-26T09:20:42.188Z DEBUG       20 ->  [05 01 ] type:     VENDOR_SPECIFIC reliable:yes seq#:4 ack#:4 payload_length:2 data_integrity:1 header_checksum:ee err_code:0x0
2019-08-26T09:20:42.439Z DEBUG       21 ->  [05 01 ] type:     VENDOR_SPECIFIC reliable:yes seq#:4 ack#:4 payload_length:2 data_integrity:1 header_checksum:ee err_code:0x0
2019-08-26T09:20:42.690Z DEBUG       22 ->  [05 01 ] type:     VENDOR_SPECIFIC reliable:yes seq#:4 ack#:4 payload_length:2 data_integrity:1 header_checksum:ee err_code:0x0
2019-08-26T09:20:42.941Z DEBUG Failed to issue connectivity reset: Error occured when resetting connectivity device. Errorcode: Unknown value (0x802a)
. Proceeding with close.
2019-08-26T09:20:42.946Z DEBUG State change: STATE_ACTIVE -> STATE_CLOSED
2019-08-26T09:20:42.946Z DEBUG serial port read on port COM5 aborted.
2019-08-26T09:20:42.951Z INFO Device closed.
2019-08-26T09:21:53.264Z INFO Validating connectivity firmware for device with serial number 000683452187...
2019-08-26T09:21:56.285Z INFO Connectivity firmware is valid.
2019-08-26T09:21:56.285Z INFO Getting information from J-Link debugger...
2019-08-26T09:22:00.701Z INFO Found device type: unknown. J-Link firmware: J-Link OB-SAM3U128-V2-NordicSemi compiled Jan  7 2019 14:07:15.
2019-08-26T09:22:00.701Z INFO Connectivity firmware version: 4.1.1. SoftDevice API version: 3. Baud rate: 1000000.
2019-08-26T09:22:00.702Z INFO Opening adapter connected to COM5
2019-08-26T09:22:01.629Z INFO Successfully opened COM5. Baud rate: 1000000. Flow control: none. Parity: none.
2019-08-26T09:22:01.629Z DEBUG State change: STATE_START -> STATE_RESET
2019-08-26T09:22:01.629Z DEBUG        1 ->  [N/A] type:          RESERVED_5 reliable: no seq#:0 ack#:0 payload_length:0 data_integrity:0 err_code:0x0
2019-08-26T09:22:01.630Z INFO Reset performed on adapter COM5
2019-08-26T09:22:01.931Z DEBUG State change: STATE_RESET -> STATE_UNINITIALIZED
2019-08-26T09:22:01.932Z DEBUG        2 ->  [01 7e ] type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:2 data_integrity:0 err_code:0x0 [SYNC]
2019-08-26T09:22:02.183Z DEBUG        3 ->  [01 7e ] type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:2 data_integrity:0 err_code:0x0 [SYNC]
2019-08-26T09:22:02.440Z DEBUG        4 ->  [01 7e ] type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:2 data_integrity:0 err_code:0x0 [SYNC]
2019-08-26T09:22:02.687Z DEBUG        5 ->  [01 7e ] type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:2 data_integrity:0 err_code:0x0 [SYNC]
2019-08-26T09:22:02.938Z DEBUG        6 ->  [01 7e ] type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:2 data_integrity:0 err_code:0x0 [SYNC]
2019-08-26T09:22:03.190Z DEBUG        7 ->  [01 7e ] type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:2 data_integrity:0 err_code:0x0 [SYNC]
2019-08-26T09:22:03.441Z DEBUG State change: STATE_UNINITIALIZED -> STATE_NO_RESPONSE
2019-08-26T09:22:03.442Z ERROR Received status with code 0 PKT_SEND_MAX_RETRIES_REACHED, message: 'No response from device. Tried to send packet 6 times.'
2019-08-26T09:22:04.629Z DEBUG serial port read on port COM5 aborted.
2019-08-26T09:22:04.630Z INFO serial port COM5 closed.
2019-08-26T09:22:04.641Z ERROR Error occured when opening port. Errorcode: NRF_ERROR_TIMEOUT (0xd)

[__Tom]

Encountered same error, solved after erasing program.

It would be better if Bluetooth Low Energy app can detect firmware compatibility issue and give a pop-up.