Cannot compile after update nRF Connect for VS Code to v2023.4.148

I can no longer compile my projects after updating extension "nRF Connect for VS Code" to v2023.4.148 today.
Up to v2023.2.56 it worked fine!

From version v2023.4.148 comes:
CMake Error at D:/Nordic/v2.2.0/zephyr/cmake/modules/FindZephyr-sdk.cmake:56 (find_package):
Could not find a configuration file for package "Zephyr-sdk" that is
compatible with requested version "0.15".

The following configuration files were considered but not accepted:

D:/Nordic/toolchains/v2.1.3/opt/zephyr-sdk/cmake/Zephyr-sdkConfig.cmake, version: 0.14.1

Call Stack (most recent call first):
D:/Nordic/v2.2.0/zephyr/cmake/modules/FindHostTools.cmake:53 (find_package)
D:/Nordic/v2.2.0/zephyr/cmake/modules/dts.cmake:8 (find_package)
D:/Nordic/v2.2.0/zephyr/cmake/modules/zephyr_default.cmake:108 (include)
D:/Nordic/v2.2.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:66 (include)
D:/Nordic/v2.2.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:92 (include_boilerplate)
CMakeLists.txt:5 (find_package)

It might be interesting that I have several SDK versions installed (NCS 1.9.1, 2.0.2, 2.1.3, 2.2.0, 2.3.0).
I have my projects in a workspace with:
"nrf-connect.topdir": "${nrf-connect.sdk:2.1.3}",
"nrf-connect.toolchain.path": "${nrf-connect.toolchain:2.1.3}",

Apparently the new extension mixes v2.1.3 and v.2.2.0:
-- Found Python3: D:/Nordic/toolchains/v2.1.3/opt/bin/python.exe (found suitable exact version "3.8.2") found components: Interpreter
-- Cache files will be written to: D:/Nordic/v2.2.0/zephyr/.cache
-- Zephyr version: 3.2.99 (D:/Nordic/v2.2.0/zephyr)
-- Found west (found suitable version "0.14.0", minimum required is "0.7.1")

Parents
  • Hi Marko,

    Thank you for reporting this to us. Did you also upgrade you VSCode version?

    Also, does this re-solve when you try downgrading to the previous nRF Connect VS Code extension version?

    Best Regards,

    Priyanka

  • Hi Priyanka,

    there was an update of VSCode last week, but there was no problem. The problem only appeared today with the update of the extension.

    In the meantime I have downgrade the "nRF Connect for VS Code" extension to v2023.2.56 and can work with it again.

    Here are my version data (where it works):
    Version: 1.77.3 (system setup)
    Commit: 704ed70d4fd1c6bd6342c436f1ede30d1cff4710
    Date: 2023-04-12T09:16:02.548Z
    Electron: 19.1.11
    Chrome: 102.0.5005.196
    Node.js: 16.14.2
    V8: 10.2.154.26-electron.0
    OS: Windows_NT x64 10.0.19045
    Sandbox: No

    nRF Kconfig v2023.4.17
    nRF Terminal v2023.4.15
    nRF DeviceTree v2023.4.61
    nRF Connect for VS Code v2023.2.56
    nRF Connect for VS Code Extension Pack v2022.9.6

    All SDK's are installed under "D:\Nordic".
    VSCode is installed under "C:\Program Files\Microsoft VS Code"

    Best Regards

    Marko

Reply
  • Hi Priyanka,

    there was an update of VSCode last week, but there was no problem. The problem only appeared today with the update of the extension.

    In the meantime I have downgrade the "nRF Connect for VS Code" extension to v2023.2.56 and can work with it again.

    Here are my version data (where it works):
    Version: 1.77.3 (system setup)
    Commit: 704ed70d4fd1c6bd6342c436f1ede30d1cff4710
    Date: 2023-04-12T09:16:02.548Z
    Electron: 19.1.11
    Chrome: 102.0.5005.196
    Node.js: 16.14.2
    V8: 10.2.154.26-electron.0
    OS: Windows_NT x64 10.0.19045
    Sandbox: No

    nRF Kconfig v2023.4.17
    nRF Terminal v2023.4.15
    nRF DeviceTree v2023.4.61
    nRF Connect for VS Code v2023.2.56
    nRF Connect for VS Code Extension Pack v2022.9.6

    All SDK's are installed under "D:\Nordic".
    VSCode is installed under "C:\Program Files\Microsoft VS Code"

    Best Regards

    Marko

Children
Related