Can't connect a device after updating nrf connect for vs code extentions version 2024.12.55.

RE: Can't connect a device after updating nrf connect for vs code extentions version 2024.12.55.

Edvin — Mon, 03 Feb 2025 13:37:11 GMT

Hello,

I don't think the nRF52840 dongle has ever been showing in nRF Connect for VS Code. Only the DKs show up. To program the dongle, I have always used nRF Connect for Desktop -> Programmer.

As "proof", the nRF Connect for VS Code used to use nrfjprog, before recently switching over to the new version of nrfutil. While this new nrfutil can see the dongle, it doesn't list it, as it can't directly program it.

nrfjprog only interacts with debuggers, and since the dongle doesn't have a debugger, it has never been able to interact with nrfjprog. Hence, since nRF Connect for VS Code used to use nrfjprog, it couldn't even detect whether a dongle was present.

Best regards,

Edvin

RE: Can't connect a device after updating nrf connect for vs code extentions version 2024.12.55.

Jim Merritt — Thu, 30 Jan 2025 14:45:29 GMT

Follow up:

I have the dongle plugged into a usb hub. When I unplugged the other devices from the hub I got this from nrfutil device list:

$ nrfutil device list
285A4D1B8834E6F5
product USB-DEV
ports COM11, vcom: 0
COM14, vcom: 1
traits serialPorts, usb

Found 1 supported device(s)

VS Code still reports No devices found.

I also tried it directly plugged into the computer.

RE: Can't connect a device after updating nrf connect for vs code extentions version 2024.12.55.

Jim Merritt — Thu, 30 Jan 2025 14:12:03 GMT

The device I'm using is an nRF52840 Dongle. This all work previously but stopped working.

$ nrfutil --version
nrfutil 7.13.0 (8289424 2024-07-01)
commit-hash: 82894242d19ff24a1541712312b3ea3af0ca8f85
commit-date: 2024-07-01
host: x86_64-pc-windows-msvc
build-timestamp: 2024-07-01T07:37:50.864803700Z
classification: nrf-external

$ nrfutil device list
thread 'main' panicked at src\list.rs:63:30:
comName did not have a string value
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Error: Subprocess C:\Users\jmerritt\.nrfutil\bin\nrfutil-device.exe failed with unexpected exit code Some(101)

$ nrfutil device --version
nrfutil-device 2.7.12 (04ede56 2025-01-20)
commit-hash: 04ede561c1b347f518d959f08a6d1d2721504cd3
commit-date: 2025-01-20
host: x86_64-pc-windows-msvc
build-timestamp: 2025-01-20T09:44:50.298273400Z
classification: nrf-external

Detected SEGGER J-Link version: JLink_V8.12c

The device command version you are currently using was tested with a different J-Link version (JLink_V8.10f) than the one you have installed (JLink_V8.12c). The tested version is not required, and your J-Link version will most likely work fine. If you get issues related to J-Link with your devices, use the tested version.

I downgraded J-Link to 8.10f and the warning went away but "nrfutil device list" still crashed.

RE: Can't connect a device after updating nrf connect for vs code extentions version 2024.12.55.

Edvin — Thu, 30 Jan 2025 08:27:57 GMT

Hello Jim,

Please make sure that (the new) nrfutil is installed, and is available via command line interface. So after installing it, open a command line, and type:

nrfutil --version

And check that it prints the version that you have. If it doesn't print the version, make sure nrfutil is in your computer's environment path. (let me know if this isn't working)

Also make sure that you have installed the submodule "device" by running the command:

nrfutil install device

After this, you can run the command:

nrfutil device list

And see if it prints some info about the connected device(s). If it does, this is the info that nRF Connect for VS Code uses to show you the connnected devices. If this command prints your device info, try restarting Visual Studio Code, and see if it now shows. If not, let me know which of the steps above that doesn't behave as described.

Best regards,

Edvin

RE: Can't connect a device after updating nrf connect for vs code extentions version 2024.12.55.

Jim Merritt — Wed, 29 Jan 2025 19:10:11 GMT

I'm having the same issue.

I've followed your instructions and set the Nrf-connect>Nrfutil: Home property and restarted VSCode. Still No Devices Found. This abruptly quit working so I uninstalled everything and upgraded.

SDK 2.8.0

Toolchain 2.8.0

VSCode 1.96.4

Any ideas?

Jim M.

RE: Can't connect a device after updating nrf connect for vs code extentions version 2024.12.55.

Edvin — Fri, 03 Jan 2025 13:24:54 GMT

Hello,

We are transitioning away from nrfjprog (nRF Command Line Tools) over to nrfutil. If you are using a new NCS version, this will be automatically added to the toolchain, but if you are using an old version of NCS (a version before nrfutil was used as a standard), you may see issues like this.

Therefore, try installing nrfutil on your computer (outside any SDK environment). You can find it here:

https://www.nordicsemi.com/Products/Development-tools/nRF-Util

After installing it, please run a couple of commands:

1: "nrfutil self-upgrade"

2: "nrfutil install device"

3: "nrfutil upgrade device"

This will make sure that:

1: You are using the latest version of nrfutil.

2: You have installed the "device" submodule

3: You have the latest version of the "device" submodule installed.

The "device" submodule is what replaces the functionality of nrfjprog.

Try this, and let me know if it doesn't work. You may need to properly close and re-start VS Code after completing steps 1-3.

Best regards,

Edvin