Cannot find Zephyr-sdkConfig.cmake

RE: Cannot find Zephyr-sdkConfig.cmake

Einar Thorsrud — Mon, 19 Sep 2022 07:57:42 GMT

Hi Jan,

Thanks for letting me know! The toolchain manager is tested with zsh, which is the default shell in recent macOS versions, but not other shells. I have forwarded your comments about the missing documentation about ZEPHYR_SDK_INSTALL_DIR so that it can be added for a future release.

RE: Cannot find Zephyr-sdkConfig.cmake

Jan Rychter — Mon, 19 Sep 2022 07:36:49 GMT

Ok, so this took a while, but I did figure this out. The short answer is that what was missing in my environment was a variable called "ZEPHYR_SDK_INSTALL_DIR" which needs to be set to "/opt/nordic/ncs/toolchains/v2.1.0/opt/zephyr-sdk".

What seems to be a clear bug in the Toolchain Manager is that this variable DOES NOT get set if the user's shell is "/bin/tcsh". I suspect it was only tested with "/bin/bash" and assumes that this is the shell that everyone uses.

I would also suggest that is is perhaps worth checking why this crucial variable isn't mentioned in the documentation much. I checked:

Installing manually https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/gs_installing.html
Migration notes for nRF Connect SDK v2.0.0 https://developer.nordicsemi.com/nRF_Connect_SDK/doc/2.1.0/nrf/migration/migration_guide_1.x_to_2.x.html
Environment Variables https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/zephyr/develop/env_vars.html#env-vars-important
Developing with Zephyr » Application Development https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/zephyr/develop/application/index.html#important-build-vars

none of these contain the string "ZEPHYR_SDK_INSTALL_DIR", which I think is a problem. I am not sure how I am supposed to discover that this variable needs to be set and what it should be set to.

RE: Cannot find Zephyr-sdkConfig.cmake

Einar Thorsrud — Mon, 19 Sep 2022 07:11:38 GMT

I am not able to reproduce, but looking et the errors there seems to still be problems with the environment variables. You can verify this by echoing the relevant environment variables and checking with what value they should have by lookin in /opt/nordic/ncs/toolchains/v2.1.0/environment.json which lists all variables and their content (this is what is used by the toolchain manager when opening a terminal).

As these are set by the toolchain manager I suspect you change some of them after opening the terminal via the Toolchain manager (deliberately or not)?

RE: Cannot find Zephyr-sdkConfig.cmake

Jan Rychter — Fri, 16 Sep 2022 15:40:46 GMT

So I launched nRF Connect for Desktop, which upgraded itself to v3.12.1, which seems to be the newest released version. I then launched Toolchain Manager 1.1.3 from within it. I used "Open Terminal", cd'd to the sample directory and I get the same thing:

[17:34] jwr-macbook-pro:/opt/nordic/ncs/v2.1.0/nrf/samples/peripheral/lpuart>west build -b nrf52840dk_nrf52840 --pristine
-- west build: making build dir /opt/nordic/ncs/v2.1.0/nrf/samples/peripheral/lpuart/build pristine
-- west build: generating a build system
Loading Zephyr default modules (Zephyr base).
-- Application: /opt/nordic/ncs/v2.1.0/nrf/samples/peripheral/lpuart
-- Using NCS Toolchain 2.1.0 for building. (/opt/nordic/ncs/toolchains/v2.1.0/cmake)
-- Found Python3: /opt/nordic/ncs/toolchains/v2.1.0/bin/python3 (found suitable exact version "3.9.6") found components: Interpreter
-- Cache files will be written to: /Users/jwr/Library/Caches/zephyr
-- Zephyr version: 3.1.99 (/opt/nordic/ncs/v2.1.0/zephyr)
-- Found west (found suitable version "0.14.0", minimum required is "0.7.1")
-- Board: nrf52840dk_nrf52840
CMake Error at /opt/nordic/ncs/v2.1.0/zephyr/cmake/modules/verify-toolchain.cmake:84 (find_package):
Could not find a package configuration file provided by "Zephyr-sdk"
(requested version 0.13.1) with any of the following names:

Zephyr-sdkConfig.cmake
zephyr-sdk-config.cmake

Add the installation prefix of "Zephyr-sdk" to CMAKE_PREFIX_PATH or set
"Zephyr-sdk_DIR" to a directory containing one of the above files. If
"Zephyr-sdk" provides a separate development package or SDK, be sure it has
been installed.
Call Stack (most recent call first):
/opt/nordic/ncs/v2.1.0/zephyr/cmake/modules/zephyr_default.cmake:121 (include)
/opt/nordic/ncs/v2.1.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:66 (include)
/opt/nordic/ncs/v2.1.0/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:92 (include_boilerplate)
CMakeLists.txt:9 (find_package)

-- Configuring incomplete, errors occurred!
FATAL ERROR: command exited with status 1: /opt/homebrew/bin/cmake -DWEST_PYTHON=/opt/homebrew/opt/python@3.10/bin/python3.10 -B/opt/nordic/ncs/v2.1.0/nrf/samples/peripheral/lpuart/build -GNinja -DBOARD=nrf52840dk_nrf52840 -S/opt/nordic/ncs/v2.1.0/nrf/samples/peripheral/lpuart
[17:38] jwr-macbook-pro:/opt/nordic/ncs/v2.1.0/nrf/samples/peripheral/lpuart>

RE: Cannot find Zephyr-sdkConfig.cmake

Einar Thorsrud — Fri, 16 Sep 2022 13:06:52 GMT

Ah, now I see. Now you are building for nrf52840dk_nrf52840 and that should have worked, and does when I test with SDK v2.1.0 from the toolchain manager on macOS 12.6 building from VS Code. But it seems the environment is not properly set up here. To use the toolchain manger yo would normally open the terminal from within the toolchain manager, and that would set up the environment correctly for you. That does not work in due to a bug in toolchain manger v1.1.3, though.

Until that is fixed you could either use VS Code with the nRF plugin, which will set up the toolchain automatically as long as you point to the right one, or you could configure the environment manually as you have attempted to do. The way to do this was changed in 2.0.0. We do not have a script that does it for you, but you can see everything you need in /opt/nordic/ncs/toolchains/v2.1.0/environment.json.

Update: A new release of nRF Connect for Desktop launcher (v3.13.1) for mac is just out now, and that fixes the issue with opening a terminal (and VS Code) from the toolchain manager. If you do that, the example should build as expected from the command line (does so when I test on my M1 MacBook Air).

RE: Cannot find Zephyr-sdkConfig.cmake

Jan Rychter — Fri, 16 Sep 2022 12:51:38 GMT

Hmm. Not sure if this is what you mean, but:

[14:47] jwr-macbook-pro:/opt/nordic/ncs/v2.1.0/nrf/samples/peripheral/lpuart>west build -b nrf52840dk_nrf52840 --pristine
-- west build: making build dir /opt/nordic/ncs/v2.1.0/nrf/samples/peripheral/lpuart/build pristine
-- west build: generating a build system
Loading Zephyr default modules (Zephyr base).
-- Application: /opt/nordic/ncs/v2.1.0/nrf/samples/peripheral/lpuart
-- Using NCS Toolchain 2.1.0 for building. (/opt/nordic/ncs/toolchains/v2.1.0/cmake)
-- Found Python3: /opt/nordic/ncs/toolchains/v2.1.0/bin/python3 (found suitable exact version "3.9.6") found components: Interpreter
-- Cache files will be written to: /Users/jwr/Library/Caches/zephyr
-- Zephyr version: 3.1.99 (/opt/nordic/ncs/v2.1.0/zephyr)
-- Found west (found suitable version "0.14.0", minimum required is "0.7.1")
-- Board: nrf52840dk_nrf52840
CMake Error at /opt/nordic/ncs/v2.1.0/zephyr/cmake/modules/verify-toolchain.cmake:84 (find_package):
Could not find a package configuration file provided by "Zephyr-sdk"
(requested version 0.13.1) with any of the following names:

Zephyr-sdkConfig.cmake
zephyr-sdk-config.cmake

RE: Cannot find Zephyr-sdkConfig.cmake

Einar Thorsrud — Fri, 16 Sep 2022 12:44:13 GMT

Hi,

Ah, I did not notice that you were using the lpuart sample. It also fails if I build for the nrf52840_mdk. That is not a Nordic board though, though it has a Nordic IC. So we do not test that, it is just part of Zephyr. If you try to build the sample for for intsance nrf52840dk_nrf52840, you will see that it build fine.

RE: Cannot find Zephyr-sdkConfig.cmake

Jan Rychter — Fri, 16 Sep 2022 12:06:54 GMT

Einar Thorsrud — Hmm. I read the migration notes you mentioned, but they do not seem to mention any changes in my project files related to the toolchain used. But in any case, as I've shown in the example above, I reproduced the problem using your "samples/peripheral/lpuart" example, using the toolchain installed with the toolchain manager, in the directory tree which is entirely controlled by the toolchain manager. In other words, while the environment variables might have something to do with the issue, my (old) project is in no way involved in the above example.

I also did try deleting and reinstalling the toolchain using the toolchain manager, which din't change anything.

RE: Cannot find Zephyr-sdkConfig.cmake

Einar Thorsrud — Fri, 16 Sep 2022 11:34:29 GMT

Hi,

There were a lot of changes introduces in nRF Connect SDK 2.0.0, including a new toolchain. It seems the issue here is that you have an older project and you are using it with the latest SDK release without migrating it. Depending on the goal, you should either use the nRF Connect SDK release (and accompanying toolchain) your application was built for, or you need to migrate your application to the latest release. The migration notes for nRF Connect SDK v2.0.0 will be particularily relevant here, as it seems your application was for a 1.x release.