nRF Connect Error "NRF_ERROR_TIMEOUT"

[Diogo]

I am trying to use the nRF Connect v1.0 RC with the pca10040 board. I followed the instructions of your [page] and when i open the serial port i got an error (Error occurred opening serial port. (NRF_ERROR_TIMEOUT)) as shown in the attached figure. I programmed the “connectivity_115k2_with_s132_2.0.1.hex” file by two ways: via drag and drop and by nrfjprog tool (version 8.4 and also 8.0) and i programmed ble example applications (with and without uart initialisation) with Keil uVision5. I noticed that the board receives the ASCII characters “*” “NUL” “ENQ” “NUL” “*” “*” and not respond any data. Any suggestion what i might be doing wrong or not doing?

[gnf]

I am facing the same problem with "NRF_ERROR_TIMEOUT". nRF Connect v2.2.1 was working earlier this week, but today suddenly it stopped working. I have uninstalled everything from Nordic and Segger and now I have reinstalled nRF Connect v2.2.1. It installs SEGGER JLink_V620b automatically I think. I also erased my device with

nrfjprog --eraseall

before running nRF Connect.

This is my logfile:

2018-01-26T12:04:06.337Z INFO Application data folder: C:\Users\xxxxxx\AppData\Roaming\nrfconnect
2018-01-26T12:04:31.617Z INFO Opening adapter connected to COM16
2018-01-26T12:04:32.133Z INFO Successfully opened COM16. Baud rate: 1000000. Flow control: none. Parity: none.

2018-01-26T12:04:32.133Z DEBUG State change: STATE_START -> STATE_RESET

2018-01-26T12:04:32.133Z DEBUG        1 ->  []
               type:          RESERVED_5 reliable: no seq#:0 ack#:0 payload_length:0 data_integrity:0 err_code:0
2018-01-26T12:04:32.134Z INFO Reset performed on adapter COM16
2018-01-26T12:04:32.432Z DEBUG State change: STATE_RESET -> STATE_UNINITIALIZED

2018-01-26T12:04:32.432Z DEBUG        2 ->  [01 7e ]
               type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:2 data_integrity:0 err_code:0
               [SYNC]
2018-01-26T12:04:32.434Z DEBUG     1/ 0 <-  [02 7d ]
               type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:2 data_integrity:0 err_code:0
               [SYNC_RESP]
2018-01-26T12:04:32.434Z DEBUG State change: STATE_UNINITIALIZED -> STATE_INITIALIZED

2018-01-26T12:04:32.434Z DEBUG        3 ->  [03 fc 11 ]
               type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:3 data_integrity:0 err_code:0
               [CONFIG [ sliding-window-size:1 out-of-frame:0 data-integrity-check-type:1 version-number:0 ]]
2018-01-26T12:04:32.684Z DEBUG        4 ->  [03 fc 11 ]
               type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:3 data_integrity:0 err_code:0
               [CONFIG [ sliding-window-size:1 out-of-frame:0 data-integrity-check-type:1 version-number:0 ]]
2018-01-26T12:04:32.934Z DEBUG        5 ->  [03 fc 11 ]
               type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:3 data_integrity:0 err_code:0
               [CONFIG [ sliding-window-size:1 out-of-frame:0 data-integrity-check-type:1 version-number:0 ]]
2018-01-26T12:04:32.936Z DEBUG     2/ 0 <-  [01 7e ]
               type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:2 data_integrity:0 err_code:0
               [SYNC]
2018-01-26T12:04:32.936Z DEBUG        6 ->  [02 7d ]
               type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:2 data_integrity:0 err_code:0
               [SYNC_RESP]
2018-01-26T12:04:33.184Z DEBUG        7 ->  [03 fc 11 ]
               type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:3 data_integrity:0 err_code:0
               [CONFIG [ sliding-window-size:1 out-of-frame:0 data-integrity-check-type:1 version-number:0 ]]
2018-01-26T12:04:33.185Z DEBUG     3/ 0 <-  [04 7b 11 ]
               type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:3 data_integrity:0 err_code:0
               [CONFIG_RESP [ sliding-window-size:1 out-of-frame:0 data-integrity-check-type:1 version-number:0 ]]
2018-01-26T12:04:33.435Z DEBUG        8 ->  [03 fc 11 ]
               type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:3 data_integrity:0 err_code:0
               [CONFIG [ sliding-window-size:1 out-of-frame:0 data-integrity-check-type:1 version-number:0 ]]
2018-01-26T12:04:33.435Z DEBUG State change: STATE_INITIALIZED -> STATE_FAILED

2018-01-26T12:04:33.436Z DEBUG     4/ 0 <-  [04 7b 11 ]
               type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:3 data_integrity:0 err_code:0
               [CONFIG_RESP [ sliding-window-size:1 out-of-frame:0 data-integrity-check-type:1 version-number:0 ]]
2018-01-26T12:04:33.438Z DEBUG     5/ 0 <-  [03 fc 11 ]
               type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:3 data_integrity:0 err_code:0
               [CONFIG [ sliding-window-size:1 out-of-frame:0 data-integrity-check-type:1 version-number:0 ]]
2018-01-26T12:04:33.940Z DEBUG     6/ 0 <-  [03 fc 11 ]
               type: LINK_CONTROL_PACKET reliable: no seq#:0 ack#:0 payload_length:3 data_integrity:0 err_code:0
               [CONFIG [ sliding-window-size:1 out-of-frame:0 data-integrity-check-type:1 version-number:0 ]]
2018-01-26T12:04:34.139Z ERROR Error occured when opening port. Errorcode: NRF_ERROR_TIMEOUT (0xd)

[Bjørn Inge]

Hi, thanks for reporting back. We have a pre-release of the next update: v.2.3.0-alpha. You mention that the device didn't show up when you had done MSDDisable? Could you elaborate on that, I'm not aware of that issue. Does the device simply not show up in the drop down one you have disabled MSD?