nRF Connect for VS Code Plugin - J-Link probe not showing up in "Connected Devices" in latest extension release

[zpm1066]

Hello,

On nRF Connect for VS Code extension v2024.9.87 and v2024.9.31, a USB connected J-Link probe (Segger Edu Mini) no longer appears under "Connected Devices".

J-link probe under nRF Connect for VS Code extension v2024.7.13 and earlier versions works fine in "Connected Devices".

Environment: Mac OS 11.7.10 (Big Sur), VS Code v1.19.2



What has changed in the Sep 2024 build to break the functionality?  Thank you.

Regards,
Ravi

[Priyanka]

Hi Ravi,

I have reported this internally. In the meantime, could you upload your "Support Information" from the VSCode?

Regards,

Priyanka

[Priyanka]

Hi,

Could you try to list the devices on command line? To make sure the same version is installed in the system: nrfutil install device=2.5.0 --force
The monitor process we start looks like this: nrfutil device --json list --hotplug --traits seggerUsb
When this is running, try to connect/disconnect the device and see what output is generated.

Please let us know your J-Link DLL version too.

Also, have you tried clicking the refresh icon in the connected devices panel.

-Priyanka

[zpm1066]

Hello Priyanka,

I'm using the latest Segger J-Link software v798i (and also earlier v796a). Both work with nRF Connect for VS Code extension v2024.7.13 and earlier.

With the latest NCS v2.7.0, I have no issues building and flashing NCS firmware from the command line and using "west flash --runner=jlink".

The only issue is in using the latest nRF Connect for VS Code extension and not seeing the J-Link probe appear under "Connected Devices" with latest extension.

I do not see any detailed nrfutil version history info on the Nordic site, so cannot determine which macOS version are now supported.

$ nrfutil search

Command           Installed Latest Status

91                        0.4.1     0.4.1  Installed

ble-sniffer            0.12.0    0.12.0 Installed

completion          1.4.0     1.4.0  Installed

device                2.3.6     2.3.6  Installed

npm                    0.3.0     0.3.0  Installed

nrf5sdk-tools      1.0.1     1.0.1  Installed

toolchain-manager 0.14.4    0.14.4 Installed

trace                   2.1.0     2.1.0  Installed

Attempting to force install  device version 2.5.0 throws the following error.

$nrfutil install device=2.5.0 --force

Error: Failed to install nrfutil-device

Caused by:

    Version for package was not found

It appears that post " nRF Connect for VS Code extension v2024.7.13", nrfutil on macOS 10.11.x (Big Sur) is not being supported as "nrfutil device 2.5.0" cannot be installed.

If so, Is there any way that engineering can provide a patch for "nrfutil device 2.5.0" for macOS 11.x?

Segger J-Link software is fully supported on macOS 10.11.x and works perfectly well with the latest NCS & Zephyr from the command line for firmware builds and flashing.

Regards,
Ravi

[Priyanka]

Thank you for the details. I will discuss this internally and get back to you.

-Priyanka

[zpm1066]

Hi Priyanka,

Thanks.

With the latest "nRF Connect for VS Code" extension v2024.9.87, it looks like I have a workaround if I use nrfprog instead of nrfutil as the device enumerator in the nRF Connect extension settings.

nrfjprog finds the J-Link Edu Mini under "CONNECTED DEVICES".

________________________________________________________________

I tried again to upgrade to the latest nrfutil b.y using the following

1. $nrfutil self-upgrade

2. $nrfutil upgrade

Successfully upgraded nrfutil device command to 2.5.4 on macOS 11.x.

Afterwards, switching the device enumerator back to nrfutil the J-Link probe still didn't appear under "CONNECTED DEVICES".

I get the following error:

Under macOS 12 (Monterey), the command nrfutil device --json list --hotplug --traits seggerUsb (although built for macOS 13) works.
 

For now, I'll use nrfjprog as the device enumerator until I hear back from you.

Regards,
Ravi

[Priyanka]

Hi Ravi,

If you can list devices on command line with version 2.3.6, you need to set this setting: https://docs.nordicsemi.com/bundle/nrf-connect-vscode/page/reference/settings.html#nrf-connectnrfutilhome 
The directory to be set is probably .nrfutil under the user's home directory.

Upgrading your OS is definitely a wise decision. 

Also, thank you for letting us know your updates.

-Priyanka

[zpm1066]

Hi Priyanka,

Unfortunately, with both nrfutil device 2.3.6 and 2.5.4, setting nrf-connect.nrfutil.home made no difference in getting nrfutil to work as the device enumerator in nRF52840-connect settings.

I'm unable to upgrade macOS 11..x to a later version on several of our Macs..

The error, from my earlier response, in running nrfutil device --json list --hotplug --traits seggerUsb seems to be because nrfutil Is now being built with macOS 13. However, this command runs fine under macOS 12 and J-Link device gets enumerated correctly.

Can you please check if it is possible for dev to build nrfutil for macOS 11? J-Link device enumeration works with nrfjprog but not with nrfutil as the device provider in nrf-connect settings. Thank you.


Regards,
Ravi