• State Verified Answer
  • Replies 4 replies
  • Subscribers 68 subscribers
  • Views 149 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 335923
Options

After v2024.11.22 update, nRF-Connect VS Code plugin lost "Device Provider" setting, causing issues with my "Connected Devices" panel

htownclyde

Hi,

After the latest update, the below setting allowing me to select nrfjprog as my device provider is now gone:

I am using the nRF Playground Docker container example as my build environment, and have attached a VS Code window to the running container, which is where I have now encountered this problem. I have previously been unable to see connected devices when selecting "nrfutil" as my device provider, so now that the option to use nrfjprog is removed, I am wondering how I can move forward with enumerating devices again.

Is the setting for using nrfjprog moved somewhere else, or do I just need to figure out how to get nrfutil to enumerate my devices?

I have it installed in /usr/local/bin/nrfutil, just as nrfjprog is in /usr/local/bin/nrjprog, but it seems to not work with the extension's Connected Devices panel.

Thank you for the help.

Parents
  • 0

    Ok, I can see my devices after restarting my hub (still waiting for a new one to arrive). 

    I have it installed in /usr/local/bin/nrfutil, just as nrfjprog is in /usr/local/bin/nrjprog, but it seems to not work with the extension's Connected Devices panel.

    Are you pointing to nrfutil in the nrf-connect.nrfutil.home setting? If you are, try removing it to see if the bundled binaries can detect your devices. If that doesn't work, try pointing to it, and make sure that nrfutil device is installed. If not, you can install it using the command:

    nrfutil install device

    After this, you should be able to use the command "nrfutil device list" to show your connected devices. Are you? And do they show up in your "Connected Devices"?

    Best regards,

    Edvin

  • 0 in reply to Edvin

    Hi, apologies for the late reply -

    Me and another person both tried this, but could not get the devices to appear.

    However, they did appear after running apt-get install libusb-1.0-0-dev. We didn't get an error message but expect that under the hood, the extension was having trouble utilizing nrfutil device because of the absence of libusb. 

    Maybe in the older version, when nrfjprog could be selected as the device provider, libusb wasn't required - not sure!

    But it works now. Thank you for your help!

Reply
  • 0 in reply to Edvin

    Hi, apologies for the late reply -

    Me and another person both tried this, but could not get the devices to appear.

    However, they did appear after running apt-get install libusb-1.0-0-dev. We didn't get an error message but expect that under the hood, the extension was having trouble utilizing nrfutil device because of the absence of libusb. 

    Maybe in the older version, when nrfjprog could be selected as the device provider, libusb wasn't required - not sure!

    But it works now. Thank you for your help!

Children
  • +1 in reply to htownclyde

    I see. I guess nrfjprog was not dependent on libusb, but nrfutil is. I am glad you got it working. nrfutil will replace nrfjprog completely within the next couple of NCS major releases, so the best is to get nrfutil working.

    Thank you for letting me know about the libusb dependency. It is good to be aware of, in case others are seeing similar issues. 

    Best regards,

    Edvin

Related