Hi,
I have an application that we are migrating from NCS v1.7.0 to v2.2.0. With v1.7.0, I was able to build, flash and monitor using VS Code (on Windows 10). The SDK has been installed using the nRF Connect Toolchain Manager.
Our normal build process is from the command line (opened through the toolchain manager), and we can build and flash using west just fine.
However, during the migration process, we encountered an issue that we need to debug. When attempting to set up the build configuration in VScode (launched using the button in the toolchain manager), we get the following error:
Executing task: nRF Connect: Generate config [email protected] for c:\dev\ml-firmware-nRF\nRF_NCS\ml-assetTracker\nrf9160 Building nrf9160west build --build-dir c:\dev\ml-firmware-nRF\nRF_NCS\ml-assetTracker\nrf9160\build c:\dev\ml-firmware-nRF\nRF_NCS\ml-assetTracker\nrf9160 --pristine --board [email protected] -- -DNCS_TOOLCHAIN_VERSION:STRING="NONE" -DCONFIG_DEBUG_OPTIMIZATIONS=y -DCONFIG_DEBUG_THREAD_INFO=y -DBOARD_ROOT:STRING="c:/dev/ml-firmware-nRF/nRF_NCS;c:/dev/ml-firmware-nRF/nRF_NCS/ml-assetTracker/nrf9160"'west' is not recognized as an internal or external command,operable program or batch file.
We CAN still build using the command line.
We have tried:
- adding the path to west.exe in the 2.2.0 SDK to the local environment variable (this produces a python error that says module 'west' not installed'
- uninstalling the entire SDK / VScode / NCS extensions, with no effect.
- reverting to our v1.7.0 project, and that no longer can build either due to the same error
Any ideas?
