nRF Connect Error "NRF_ERROR_TIMEOUT"

RE: nRF Connect Error "NRF_ERROR_TIMEOUT"

gnf — Wed, 31 Jan 2018 14:55:43 GMT

I just tried to install v2.3.0-alpha but the installation fails with

"---------------------------
nRF Connect Setup
---------------------------
Error opening file for writing: 



C:\Users\[user name]\AppData\Local\Programs\nrfconnect\Uninstall nRF Connect.exe



Click Abort to stop the installation,

Retry to try again, or

Ignore to skip this file.
---------------------------
Abort   Retry   Ignore   
---------------------------

Edit: Ok, after some trying I managed to install v2.3.0-alpha6. The above error could maybe be blamed on my antivirus software.

I have now done some tests and to me it seems to work both with msdenable and msddisable in this version. The NRF_ERROR_TIMEOUT is also not showing up in this version!

RE: nRF Connect Error "NRF_ERROR_TIMEOUT"

Bjørn Inge — Tue, 30 Jan 2018 07:29:22 GMT

Do you see the issue with MSDDisable'ed device not showing also in v2.3.0-alpha (linked in my previous comment)?

RE: nRF Connect Error "NRF_ERROR_TIMEOUT"

gnf — Mon, 29 Jan 2018 14:22:51 GMT

I have written about this in another thread where I was given the suggestion to run MSDDisable to help solve the NRF_ERROR_TIMEOUT problem. The device is not showing up in the drop down in this mode when running v2.2.1.

RE: nRF Connect Error "NRF_ERROR_TIMEOUT"

Bjørn Inge — Mon, 29 Jan 2018 13:28:53 GMT

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?

RE: nRF Connect Error "NRF_ERROR_TIMEOUT"

gnf — Mon, 29 Jan 2018 11:57:38 GMT

Yes! Version 2.2.0 is actually working! In this version my device also shows up when I have set the "MSDDisable" (disable mass storage functionality) that also does not work in 2.2.1

RE: nRF Connect Error "NRF_ERROR_TIMEOUT"

Bjørn Inge — Mon, 29 Jan 2018 09:07:18 GMT

Hi,
could you try to downgrade nRF Connect Core to version 2.2.0 (I assume you are using the latest v2.2.1 now). There was a change in v2.2.1 that might have contributed to what you are seeing. A new version that includes a fix is soon to be released.

RE: nRF Connect Error "NRF_ERROR_TIMEOUT"

gnf — Fri, 26 Jan 2018 12:12:21 GMT

I wanted to comment that I am also experiencing this, but my logfile was too big for the comment field. See my answer above.

RE: nRF Connect Error "NRF_ERROR_TIMEOUT"

gnf — Fri, 26 Jan 2018 12:09:16 GMT

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)

RE: nRF Connect Error "NRF_ERROR_TIMEOUT"

jowegele — Tue, 16 Jan 2018 09:14:54 GMT

Ok, finally I looked it over with colleges and we found "smoke signes" on the board. A college had modified it for current measurements. So maybe not worth staying to long on this device. I will order a new one.

RE: nRF Connect Error "NRF_ERROR_TIMEOUT"

jowegele — Tue, 16 Jan 2018 09:08:47 GMT

Hi again Bjørn, indeed I only have one nrf52 DK. I did nrfjprog --eraseall with the output:

Erasing user available code and UICR flash areas. Applying system reset.

Now nrf-Connect asks me to install the "required firmware" - Ok - Some flickering icons on the taskbar - Same error again.

I send the log in a new post.

RE: nRF Connect Error "NRF_ERROR_TIMEOUT"

jowegele — Tue, 16 Jan 2018 07:46:31 GMT

Thank you Bjørn Inge I will try in some minutes.

RE: nRF Connect Error "NRF_ERROR_TIMEOUT"

Bjørn Inge — Tue, 16 Jan 2018 07:38:57 GMT

Hi, you should stick to the latest version of nRF Connect. Is the issue for one devkit in particular, or several?
Try to erase the memory with nrfjprog --eraseall.
Could you also upload the logfile.

RE: nRF Connect Error "NRF_ERROR_TIMEOUT"

jowegele — Mon, 15 Jan 2018 16:37:01 GMT

Hi there, I have experienced the same problem. After pressing the RESET button I followed Remi's description on another page of this site - link

Now I'm back again, the nrf52 DK is recognized as a J-link device for example in Seggers J-Flash tool V6.12a. But in nrf-Connect it will not work. Trying to use the nrf52 DK results in

Error occurred opening serial port.(NRF_ERROR_TIMEOUT)

I tried with nrf-Connect 1.1.0 and 2.2.1 having installed the latest command line tools.

What do I do wrong? I used it to make firmware over the air and to read characteristics. It worked for so long. I flashed some 50 PCBs last week and now this.

See also log: 2018-01-16T09_03_44.504Z-log.txt

RE: nRF Connect Error "NRF_ERROR_TIMEOUT"

Tony Garland — Tue, 20 Sep 2016 18:55:12 GMT

Wow - should have thought of that! Thanks for setting me straight!

RE: nRF Connect Error "NRF_ERROR_TIMEOUT"

Bjørn Inge — Tue, 20 Sep 2016 06:18:04 GMT

Hi, Tony,
nRF Connect does not support the PCA10000 dongle. For a list of compatible devices please have look at the Getting Started Guide under Supported Devices.

RE: nRF Connect Error "NRF_ERROR_TIMEOUT"

Tony Garland — Mon, 19 Sep 2016 21:20:23 GMT

I'm seeing a similar problem. I'm able to run Master Control Panel 3.10.0 just fine using USB dongle PCA10000 V 2.2.0 (2013.48). But I've been unable to get nRF Connect (1.0.0) to work in the same environment using the same dongle.

The environment is W7 running within a parallels 12 VM on OS X. I've also tried running nRF Connect directly under OS X (El Capitan 10.11.6), accounting for the known OS X issue work-arounds, and the results are always the same: "Error occurred opening serial port. (NRF_ERROR_TIMEOUT)."

I've manually programmed the dongle using nRFgo Studio under W7 with the related connectivity hex file (nRF51/S130 version in my case) and still no joy. The dongle seems to be found and programmed just fine, but whenever nRF Connect tries to talk to it, after successfully opening the COM Port, it reports the timeout.

Not sure what to try to solve this issue. Because of this, I've reverted to old faithful (Master Control Panel) and am unable to use nRF Connect under either OS X or W7.

RE: nRF Connect Error "NRF_ERROR_TIMEOUT"

Bjørn Inge — Mon, 23 May 2016 20:32:48 GMT

I fail to see what your other application has to do with nRF Connect, sorry if I'm missing anything obvious here. The merged connectivity and softdevice firmware (connectivity_115k2_with_s132_2.0.1.hex) needs to be programmed and run alone on the nRF52. No initialization is required, the connectivity application and nRF Connect synchronize automatically over uart (P0.08 and P0.06 + RTS/CTS on P0.05 and P0.07).

RE: nRF Connect Error "NRF_ERROR_TIMEOUT"

Diogo — Mon, 23 May 2016 09:38:13 GMT

I programmed in the same board (pca10040). My windows version is windows 7 64 bits. I am not running windows in a virtual machine. Regarding the application that I program, it is working properly. i already programmed an application that initialises and uses the uart but this one only calls my interrupt events of uart. I also have tried to put an application that don’t uses at all any uart function, but I don’t know how the softdevice (“connectivity_115k2_with_s132_2.0.1.hex”) can interact with uart communication of nRF52 to respond to NRF Connect software on windows. Do i have to do some initialisation? What are the pins that uart communication of the softdevice use? (Are P0.08 and P0.06?). Note: I can see the serial message from the nRF Connect in windows (by Jlink CDC UART Port) but i don’t see any response from board.

RE: nRF Connect Error "NRF_ERROR_TIMEOUT"

Bjørn Inge — Sat, 21 May 2016 07:20:55 GMT

Hi Diogo,
from what you describe it sounds like you are doing things correctly.
Just to clarify, when you say you programmed ble example applications from Keil, you are doing it to a second board and not on top of the connectivity application?
What Windows version are you running? Are you running windows in a virtual machine?