nRF Connect for VS Code settings failure and consequences

Hello, this ticket addresses three issues:

1. After installing nrfutil with subcommands device and toolchain-manager and sdk-manager, into %USERPROFILE%\.nrfutil, everything works fine when I set Nrf-connect › Nrfutil: Home in VS Code to that value. However, when I only install subcommands device and toolchain-manager, like the help information paragraph for that variable states, things do not work. So, this ticket I am opening to ask you to update the help information. I realize that sdk-manager is a newer command than toolchain-manager.

2. After setting the Nrf-connect › Nrfutil: Home variable, it is ignored when I attempt to flash a device. Instead, nRF Connect for VS Code insists on using the nrtutil in the toolchain.

3. As you are hopefully aware by now from various tickets that I and others have opened, C:\ncs\toolchains\66cdf9b75e\nrfutil\home\bin\nrfutil-device.exe has a bug and does not work if there are any CH340 or CP2102 devices on the USB bus. I was forced to replace that file in the toolchain with C:\Users\test\.nrfutil\bin\nrfutil-device.exe in order to flash my nRF9160DK when I have a CP2102 device on the USB bus.

The three issues are of course closely interrelated. Please let me know the schedule and plans for fixing these issues.

Regards,

Burt Silverman

Parents Reply Children
No Data
Related