VS code does not show connected devices on Windows

[Georgi Valkov]

VS code does not show connected devices on Windows. This used to work before I upgraded to nRF Connect SDK v2.4.0. macOS works fine. The connected device is visible in my debugger and also in the nRF Programmer. I tried nRF9160dk, nRF52840dk, Thingy:91.

Could be related to the other issue from the screenshot, where build/mcuboot/child_image_preload.cmake is created with backslash '\' instead of forward slash '/' on line 7.

Fullscreen child_image_preload.cmake.txt Download

# Generated file used for preloading a child image
set(CMAKE_BUILD_TYPE "" CACHE INTERNAL "NCS child image controlled")
set(CMAKE_VERBOSE_MAKEFILE "FALSE" CACHE INTERNAL "NCS child image controlled")
set(BOARD_DIR "V:/nordic/v2.4.0/nrf/boards/arm/thingy91_nrf9160" CACHE INTERNAL "NCS child image controlled")
set(ZEPHYR_TOOLCHAIN_VARIANT "zephyr" CACHE INTERNAL "NCS child image controlled")
set(NCS_TOOLCHAIN_VERSION "NONE" CACHE INTERNAL "NCS child image controlled")
set(WEST_PYTHON "v:\nordic\toolchains\31f4403e35\opt\bin\python.exe" CACHE INTERNAL "NCS child image controlled")
set(BOARD "thingy91_nrf9160" CACHE INTERNAL "NCS child image controlled")
set(OVERLAY_CONFIG "V:/nordic/v2.4.0/nrf/modules/mcuboot/tfm.conf;V:/nordic/v2.4.0/nrf/modules/mcuboot/fih_low_enable.conf;V:/nordic/v2.4.0/nrf/subsys/partition_manager/partition_manager_enabled.conf" CACHE INTERNAL "NCS child image controlled")

[Priyanka]

Hi Georgi,

Could you try setting the Device Provider to nrfjprog in the nRF Connect for VSCode settings?

Best Regards,

Priyanka

[Georgi Valkov]

Thank you, Priyanka!

As soon as I changed Device provided to nrfjprog on Windows, my Nordic board appeared under connected devices.
I see that on macOS the setting is still set to nrfutil and it works fine. So there might be an issue with nrfutil on Windows.
I have the latest version of Segger j-link drivers.

[Priyanka]

Glad to hear that it worked

Yes a lot of customers are facing this issue and we are looking into it.

-Priyanka

[Georgi Valkov]

The two most serious issues with Nordic:

1. Frequent design changes that render existing work useless. It would help if useful comments are added to the headers, in order to help through these changes.
2. Untested releases with obvious bugs that occur as soon as a project is compiled, and require porting of existing projects to new a API, when the SDK is updated to resolve the issues.

Due to these, a project I worked on in the past failed. I am presently developing support for Nordic boards in nano RTOS, so that I don't have to relay on broken SDK and changing APIs.

Other than that, the people from management and support are very kind.