nRF Connect for Desktop v5.0.2, programmer v4.4.1, rust-panic on startup

RE: nRF Connect for Desktop v5.0.2, programmer v4.4.1, rust-panic on startup

mhilden — Wed, 30 Oct 2024 17:46:28 GMT

Another update, after playing around some more... The environment variable hacks may help with nRF Connect for Windows but don't always work for VS Code and the nRF Connect Extension. This is why I was looking for a fix in the first place. If your boards are showing up in nRF Connect for Windows but aren't reliably showing up in the VS Code Extension, you can try another route.

Install the latest version of the nRF Connect Command Line Tools, and then change a setting in the nRF Connect VS Code Extension to use the command line tools connection manager.

File -> Preferences -> Settings -> Search for `nrf-connect device provider` and change the setting to `nrfjprog`

RE: nRF Connect for Desktop v5.0.2, programmer v4.4.1, rust-panic on startup

Loubear — Wed, 30 Oct 2024 17:42:50 GMT

I was not having this issue, but without changing anything on my end (except perhaps automatic updates to nRF Connect for VS Code) this issue began to happen.

I followed your steps and adding the environment variables fixed the issue in nRF Connect for Desktop but did not fix the issue in nRF Connect for VS Code.

The only solution that worked for me was downloading nRF Command Line tools and changing my Nrf-connect: Device Provider setting in the VSCode extension from nrfutil to nrfjprogSomething in nrfutil seems broken. I concur that this issue needs to be fast tracked as other users will probably have the same issues that are very difficult to track down when occurring in a fundamental piece of the toolchain.

RE: nRF Connect for Desktop v5.0.2, programmer v4.4.1, rust-panic on startup

Simonr — Wed, 23 Oct 2024 07:54:02 GMT

I have forwarded your request and we are currently working on a fix, but I do not have a timeline unfortunately. Thank you for your thorough report. I've also updated my last reply with the workaround to reflect that the J-Link must also be upgraded.

Best regards,

Simon

RE: nRF Connect for Desktop v5.0.2, programmer v4.4.1, rust-panic on startup

mhilden — Tue, 22 Oct 2024 20:26:32 GMT

This worked for me (generally) but I needed to expand on it. Just getting nRF Connect for Desktop isn't enough - I need to be able to program and debug my application from the nRF Connect Extension for VS Code. Setting the two environment variables mentioned globally for my user in Windows (reboot after adding them!) is ultimately what I needed to do.

Of course, changing from version 2.5.0 -> 2.6.1 means that my J-Link driver needed to be upgraded from V7.94e to V7.94i also!

This took me a very painful two days to figure out, and I needed to reset everything related to nRF Connect and VS Code in the process. I do believe that I am back on track again.

@Nordic, please fast track a fix for this, as I expect that other users will also have problems, even with first-time installs. Fundamentally, it seems that the 2.5.0 version can't find its own DLLs in the lib folder. Running the tool manually would crash every time with this error:

RE: nRF Connect for Desktop v5.0.2, programmer v4.4.1, rust-panic on startup

Simonr — Mon, 07 Oct 2024 13:32:54 GMT

So, the procedure to recover a Dongle that's "lost" it's bootloader (although it seems to be fine based on your description) is described in the Dongle programming tutorial here (see the final section on recovery). I guess what might have happened is that the REG0 voltage is 1.8V, as that will result in a device not being recognized by the computer.

For the J-Link version, I think you need to downgrade this, as nRF Connect for Desktop isn't tested with J-Link v8 yet I think. To downgrade you need to manually uninstall your J-Link version and install v7.94i from here: https://www.segger.com/downloads/jlink/. Try that first, and see if the Dongle is recognized by the computers if you do that.

Best regards,

Simon

RE: nRF Connect for Desktop v5.0.2, programmer v4.4.1, rust-panic on startup

gmn — Mon, 07 Oct 2024 01:20:44 GMT

Simonr - an important update! I didn't check the Saturday mail until this afternoon (Sunday) and a my second nrf52840 dongle arrived. It -is- (woohoo!) seen by Nordic programmers on both w11 and Debian.

So, I think the questions become:

1) how to recover from a clobbered bootloader that is in bootloader-mode (1hz red led), but that the programmer does not recognize?

2) how to tell nrf desktop to expect jlink v8 instead of v7? Same message on both Linux and w11.

Thank you!

RE: nRF Connect for Desktop v5.0.2, programmer v4.4.1, rust-panic on startup

gmn — Sun, 06 Oct 2024 22:46:51 GMT

Simonr - hey, baby steps, things are moving in the right direction!

1) no rust-panic and desktop is detecting nrfutil-device version 2.6.1. woohoo!

2) The dongle is attached and in bootloader mode (1hz red led), but is not detected. I tried programmer, quick-start, board-configurator, and bluetooth-low-energy all with no luck.

3) desktop seems to have an issue with jlink_v8.10a installed and it is expecting jlink_v7.94i

Question: how to set the jlink version that desktop is expecting?

Here is summary from the terminal session:

// forced install:
C:\Users\me\Downloads\nrf-dongle>nrfutil.exe install device=2.6.0 --force
nrfutil-device already installed
Uninstalled nrfutil-device
[00:00:06] ###### 100% [Install packages] Install packages
C:\Users\me\Downloads\nrf-dongle>

// set the required environment variables:
C:\Users\me\Downloads\nrf-dongle>set NRF_OVERRIDE_NRFUTIL_SETTINGS=true
C:\Users\me\Downloads\nrf-dongle>set NRF_OVERRIDE_VERSION_DEVICE=2.6.1

// move to the .exe location
C:\Users\me\Downloads\nrf-dongle>cd "C:\Users\Gary\AppData\Local\Programs\nrfconnect\"
C:\Users\me\AppData\Local\Programs\nrfconnect>"nRF Connect for Desktop.exe"

//Programmer:
16:29:12.112	Initialising nrfutil module: device
16:29:13.993	Using nrfutil-device core version: 7.13.0
16:29:14.806	Using nrfutil-device version: 2.6.1
16:29:14.806	Using nrf-device-lib version: 0.17.33
16:29:14.806	Using nrfjprog DLL version: 10.24.2
16:29:14.806	Using JLink version: JLink_V8.10a
16:29:14.807	Installed JLink version does not match the expected version (JLink_V7.94i)

Here is the programmer output:

16:35:32.558	Initialising nrfutil module: device
16:35:34.526	Using nrfutil-device core version: 7.13.0
16:35:35.344	Using nrfutil-device version: 2.6.1    <<<<==== woohoo!
16:35:35.345	Using nrf-device-lib version: 0.17.33
16:35:35.345	Using nrfjprog DLL version: 10.24.2
16:35:35.345	Using JLink version: JLink_V8.10a
16:35:35.345	Installed JLink version does not match the expected version (JLink_V7.94i)

I setup for dual boot with linux on this box and installed Debian 12. Debian 12 also does not see the device, it does not have a rust-panic, and it also complains about the jlink version mismatch. I -think- this will be a good testing setup because same hardware approaching from different OS. Note this is not a linux VM, it is a whole dual boot setup.

Thank you for the help! Now let's figure out why the device is not being detected. I picked up parts and I think I can add a jtag header to this dongle if that would be helpful.

Gary

RE: nRF Connect for Desktop v5.0.2, programmer v4.4.1, rust-panic on startup

Simonr — Fri, 04 Oct 2024 08:52:12 GMT

Yes, it is actively being looked into. We know about it and is looking into fixing it by releasing new app versions running on this new CLI version. They've provided a workaround that will work as well here (in case force updating nrfutil didn't work):

Close nRF Connect for Desktop
Set these environment variables:
export NRF_OVERRIDE_NRFUTIL_SETTINGS=true
export NRF_OVERRIDE_VERSION_DEVICE=2.6.1
When updating to v2.6.1 of nRFUTIL device, you also need at least v7.94i of the J-Link drivers.
Start nRF Connect for Desktop from the terminal having these environment variable

All apps will now use nrfutil device v2.6.1 and should work as expected.

Best regards,

Simon

RE: nRF Connect for Desktop v5.0.2, programmer v4.4.1, rust-panic on startup

gmn — Fri, 04 Oct 2024 01:58:13 GMT

Simonr can the developers reproduce the error? Any idea if it's actively being looked into yet? Thanks!

RE: nRF Connect for Desktop v5.0.2, programmer v4.4.1, rust-panic on startup

Simonr — Thu, 03 Oct 2024 10:51:52 GMT

Try running nrfutil install device=2.6.0 --force to force upgrade the nrfutil device version to 2.6.0 and see if that helps at all.

Best regards,

Simon

RE: nRF Connect for Desktop v5.0.2, programmer v4.4.1, rust-panic on startup

gmn — Wed, 02 Oct 2024 16:21:30 GMT

yes, done yesterday.

RE: nRF Connect for Desktop v5.0.2, programmer v4.4.1, rust-panic on startup

ogulcan — Wed, 02 Oct 2024 09:59:01 GMT

I have tried doing it under the same folder but nothing changed.

[00:00:00] ###### 100% [Upgrade packages] Upgrade packages
....\AppData\Roaming\nrfconnect\nrfutil-sandboxes\device\2.5.0\bin>

Is this the location that you mean to run the command or is it somewhere else?

RE: nRF Connect for Desktop v5.0.2, programmer v4.4.1, rust-panic on startup

Simonr — Wed, 02 Oct 2024 08:50:37 GMT

Did you also try running nrfutil upgrade in the command line in the folder where nrfutil is located?

Best regards,

Simon

RE: nRF Connect for Desktop v5.0.2, programmer v4.4.1, rust-panic on startup

ogulcan — Wed, 02 Oct 2024 07:29:02 GMT

Hi,

I am having the same problem on a W10 laptop and J-Link V7.94e. Here is the error code:

AppData\Roaming\nrfconnect\nrfutil-sandboxes\device\2.5.0\bin\nrfutil-device.exe failed with unexpected exit code Some(-1073740791)

I can use the nRF5340-DK with Visual Studio Code for debugging and flashing the connected device.

I fixed the issue by uninstalling nRF Connect 5.0.2 and installing an older version for nRF Connect 4.4.0 with nRF Programmer 4.1.0.

However this is just a temporary fix as I can not keep using the old version of these programs.

Best,

Ogulcan

RE: nRF Connect for Desktop v5.0.2, programmer v4.4.1, rust-panic on startup

gmn — Wed, 02 Oct 2024 04:06:11 GMT

Fresh install on different W11 box, same error:

22:00:32.242	Initialising nrfutil module: device
22:00:34.104	Using nrfutil-device core version: 7.13.0
22:00:34.786	thread '<unnamed>' panicked at src\usb-lister-rs\src\windows.rs:1160:5: assertion `left == right` failed left: 14 right: 68
22:00:34.786	note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace thread '<unnamed>' panicked at library\panic_unwind\src\seh.rs:290:8: Rust panics cannot be copied stack backtrace:
22:00:34.797	0: 0x7ffa9001dbfd - <unknown>
22:00:34.798	1: 0x7ffa90013e29 - <unknown> 2: 0x7ffa9001c361 - <unknown> 3: 0x7ffa9001d9d6 - <unknown> 4: 0x7ffa9001f3c8 - <unknown> 5: 0x7ffa9001f076 - <unknown>
22:00:34.798	6: 0x7ffa9001f8f8 - <unknown> 7: 0x7ffa9001f779 - <unknown> 8: 0x7ffa9001e2ef - <unknown>
22:00:34.798	9: 0x7ffa9001f468 - <unknown> 10: 0x7ffa9018a874 - nrfdl_wait_timed_async_task_complete 11:
22:00:34.798	0x7ffa9003ae6c - <unknown>
22:00:34.843	12: 0x7ffab35822b1 - <unknown>
22:00:34.843	13: 0x7ffab3582008 - <unknown> 14: 0x7ffab3582529 - __ExceptionPtrCurrentException 15: 0x7ffa90192e6f - nrfdl_wait_timed_async_task_complete
22:00:34.856	16: 0x7ffabdfc1080 - <unknown>
22:00:34.857	17: 0x7ffabdfc2715 - _NLG_Return2
22:00:34.880	18:
22:00:34.881	0x7ffb0ad34a26 - RtlCaptureContext2 19: 0x7ffa9014c6cf - <unknown> 20: 0x7ffa9012a1c3 - <unknown> 21: 0x7ffa9014d382 - <unknown>
22:00:34.881	22: 0x7ffa90150953 - <unknown> 23: 0x7ffa9012aad4 - <unknown> 24
22:00:34.881	: 0x7ffa90129588 - <unknown> 25: 0x7ffab35929a9 - Concurrency::details::_Schedule_chore 26:
22:00:34.882	0x7ffb0acf289a - RtlHashUnicodeString 27: 0x7ffb0acc5e66 - RtlClearThreadWorkOnBehalfTicket
22:00:34.890	28: 0x7ffb0920257d - BaseThreadInitThunk 29:
22:00:34.890	0x7ffb0aceaf28 - RtlUserThreadStart thread '<unnamed>' panicked at library\panic_unwind\src\seh.rs:290:8: Rust panics cannot be copied stack backtrace: 0: 0x7ffa9001dbfd - <unknown> 1: 0x7ffa90013e29 - <unknown> 2: 0x7ffa9001c361 - <unknown>
22:00:34.891	3: 0x7ffa9001d9d6 - <unknown> 4: 0x7ffa9001f3c8 - <unknown> 5: 0x7ffa9001f076 - <unknown>
22:00:34.891	6: 0x7ffa9001f8f8 - <unknown> 7: 0x7ffa9001f779 - <unknown> 8: 0x7ffa9001e2ef - <unknown> 9:
22:00:34.891	0x7ffa9001f468 - <unknown> 10: 0x7ffa9018a874 - nrfdl_wait_timed_async_task_complete 11: 0x7ffa9003ae6c - <unknown>
22:00:34.892	12: 0x7ffab35822b1 - <unknown> 13: 0x7ffab35d2880 - std::basic_ostream<unsigned short,std::char_traits<unsigned short> >::write 14: 0x7ffabdfc1080 - <unknown>
22:00:34.892	15: 0x7ffabdfc2715 - _NLG_Return2 16: 0x7ffb0ad34a26 - RtlCaptureContext2 17: 0x7ffab3582008 - <unknown> 18:
22:00:34.892	0x7ffab3582529 - __ExceptionPtrCurrentException 19: 0x7ffa90192e6f - nrfdl_wait_timed_async_task_complete 20: 0x7ffabdfc1080 - <unknown> 21: 0x7ffabdfc2715
22:00:34.892	- _NLG_Return2 22: 0x7ffb0ad34a26 - RtlCaptureContext2 23: 0x7ffa9014c6cf - <unknown> 24: 0x7ffa9012a1c3 - <unknown> 25:
22:00:34.893	0x7ffa9014d382 - <unknown> 26: 0x7ffa90150953 - <unknown> 27: 0x7ffa9012aad4 - <unknown> 28:
22:00:34.893	0x7ffa90129588 - <unknown> 29: 0x7ffab35929a9 - Concurrency::details::_Schedule_chore 30: 0x7ffb0acf289a - RtlHashUnicodeString
22:00:34.893	31: 0x7ffb0acc5e66 - RtlClearThreadWorkOnBehalfTicket 32: 0x
22:00:34.894	7ffb0920257d - BaseThreadInitThunk 33: 0x7ffb0aceaf28 - RtlUserThreadStart fatal runtime error: Rust panics must be rethrown
22:00:34.908	Using nrfutil-device version: 2.5.0
22:00:34.909	Using nrf-device-lib version: 0.17.26
22:00:34.909	Using nrfjprog DLL version: 10.24.2
22:00:34.909	Using JLink version: JLink_V7.94e
22:00:35.092	Error: Subprocess C:\Users\delete-this\AppData\Roaming\nrfconnect\nrfutil-sandboxes\device\2.5.0\bin\nrfutil-device.exe failed with unexpected exit code Some(-1073740791)
22:00:35.106	Error: Failed with exit code 1.

RE: nRF Connect for Desktop v5.0.2, programmer v4.4.1, rust-panic on startup

gmn — Wed, 02 Oct 2024 02:32:57 GMT

Completely uninstalled nRF Desktop Connect and deleted the roaming directory and reinstalled. Same rust-crash.

The roaming directory looked like it contained mostly log files. I saved a copy of the who subdir in my temp folder in case the log files would be useful for debugging.

RE: nRF Connect for Desktop v5.0.2, programmer v4.4.1, rust-panic on startup

Simonr — Tue, 01 Oct 2024 11:11:19 GMT

One suggestion that came up. Can you try upgrading your nrfutil-device version to v2.5.4. Note that this is different from the nrfutil-device core version. You can do so by running nrfutil upgrade in the command line in the folder where nrfutil is located. It should upgrade to v2.5.4 by itself with no further inputs required.

Best regards,

Simon

RE: nRF Connect for Desktop v5.0.2, programmer v4.4.1, rust-panic on startup

Simonr — Tue, 01 Oct 2024 09:29:58 GMT

Okay, thank you for the explanation, I will need to take this onward with the nRF Connect for Desktop devs then. I'll let you know when I hear back from them. In the mean time you could try uninstalling the Programmer app and make sure the folder C:\Users\<YOUR USERNAME>\AppData\Roaming\nrfconnect\pc-nrfconnect-programmer is removed entirely before reinstalling the app.

Best regards,

Simon

RE: nRF Connect for Desktop v5.0.2, programmer v4.4.1, rust-panic on startup

gmn — Tue, 01 Oct 2024 06:03:50 GMT

Just to confirm, I -do- have nrf-command-line-tools-10.24.2-x64 installed and it is listed in both the system and my person path variables.

RE: nRF Connect for Desktop v5.0.2, programmer v4.4.1, rust-panic on startup

gmn — Mon, 30 Sep 2024 18:14:11 GMT

Hi Simon!

Yes, I can get the dongle into DFU bootloader mode (red light approximately 1hz). nRF Connect for Desktop has options for Bluetooth Low Energy, Direct Test Mode, RSSI Viewer, Serial Terminal, and Power Profiler all see the device. Quick Start sees the device and reports "not supported yet". Programmer crashes with the error message above and does not see the device. My first post left off a couple line of the initial crash text (in case that is useful).

12:03:41.734	Initialising nrfutil module: device
12:03:43.053	Using nrfutil-device core version: 7.13.0
12:03:43.408	thread '<unnamed>' panicked at src\usb-lister-rs\src\windows.rs:1160:5: assertion `left == right` failed left: 14 right: 68 note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
12:03:43.408	thread '<unnamed>' panicked at library\panic_unwind\src\seh.rs:290:8: Rust panics cannot be copied stack backtrace:
12:03:43.411	0: 0x7ffd9770dbfd - <unknown> 1: 0x

If it is useful, the device ID is DCF7B348AB3D

The programmer crashes either with no device, with a device not in DFU bootloader mode, and when in DFU bootloader mode (seems to make no difference, ... Programmer is just not happy software :-) )

Thank you for the help!

RE: nRF Connect for Desktop v5.0.2, programmer v4.4.1, rust-panic on startup

Simonr — Mon, 30 Sep 2024 13:00:38 GMT

Regarding this nRF52840 Dongle you have, how does it behave when plugging it into the computer on your end? Does it show up as DFU Bootloader in the nRF Programmer or with some other name? If you have programmed it already it might be running in its application mode, in which case you will need to hold the side-mounted reset button while plugging the Dongle into your computer to put it back into the DFU bootloader mode that lets it communicate through USB with the nRF Connect application. If that's not it I will have to ask the devs about this error, as I can't say it's something I've seen before.

Best regards,

Simon