RE: Having Trouble getting the nRF-Connected SDK running

Carl Richard — Mon, 07 Dec 2020 08:32:23 GMT

I see! Glad I could help!

Best regards,
Carl Richard

RE: Having Trouble getting the nRF-Connected SDK running

Rudolph Aschmoneit — Mon, 30 Nov 2020 15:02:51 GMT

Hey, yes I Did call the source zephyr-env.sh but I always used the icon, and there is the problem, it is not the same terminal like this where the source zephyr-env.sh happend, opening the Segger Studio from the same terminal via "open -a" works. Thanks a lot for your help and this Tip! So In my Opinion this thread could be closed or marked as resolved.

RE: Having Trouble getting the nRF-Connected SDK running

Carl Richard — Mon, 30 Nov 2020 14:47:05 GMT

Hi again!

Did you call "source zephyr-env.sh" again aswell? There shouldn't be any more temporary outside the build folder (except the zephyr cache under Library/Caches, but it shouldn't be necessary to delete that often).

Do you open SES from the terminal or with the app icon? If the latter, could you try to open it from the terminal, after calling "source zephyr-env.sh" first?

Best regards,
Carl Richard

RE: Having Trouble getting the nRF-Connected SDK running

Rudolph Aschmoneit — Mon, 30 Nov 2020 13:17:53 GMT

Hy, thanks for your reply,

I tried the solution you mentioned before, but I tried it now another time:

I get the following Error:

Creating solution asset_tracker.emProject
/usr/local/Cellar/cmake/3.19.1/bin/cmake -GNinja -DBOARD=nrf9160dk_nrf9160ns -DBOARD_DIR=/Users/RudolphAschmoneit/Documents/Arbeit/VRaktion/nordic/nRFConnectedSDK/ncs/zephyr/boards/arm/nrf9160dk_nrf9160 -B/Users/RudolphAschmoneit/Documents/Arbeit/VRaktion/nordic/nRFConnectedSDK/ncs/nrf/applications/asset_tracker/build_nrf9160dk_nrf9160ns -S/Users/RudolphAschmoneit/Documents/Arbeit/VRaktion/nordic/nRFConnectedSDK/ncs/nrf/applications/asset_tracker -DZEPHYR_TOOLCHAIN_VARIANT=gnuarmemb -DGNUARMEMB_TOOLCHAIN_PATH=/Applications/ARM -DPYTHON_EXECUTABLE=/Users/RudolphAschmoneit/.pyenv/shims/python -DCMAKE_MAKE_PROGRAM=/usr/local/Cellar/ninja/1.10.1_3/bin/ninja -DDTC=/usr/local/Cellar/dtc/1.6.0/bin/dtc -D WEST=/Users/RudolphAschmoneit/.pyenv/shims/west -DEXTRA_KCONFIG_TARGETS=menuconfig_ses -DEXTRA_KCONFIG_TARGET_COMMAND_FOR_menuconfig_ses=/Applications/arm_segger_embedded_studio_v520b_macos_x64_nordic/html/configure_nordic_project_menuconfig.py
-- Application: /Users/RudolphAschmoneit/Documents/Arbeit/VRaktion/nordic/nRFConnectedSDK/ncs/nrf/applications/asset_tracker
-- Zephyr version: 2.4.0 (/Users/RudolphAschmoneit/Documents/Arbeit/VRaktion/nordic/nRFConnectedSDK/ncs/zephyr)
-- Found Python3: /Users/RudolphAschmoneit/.pyenv/versions/3.9.0/bin/python3.9 (found suitable exact version "3.9.0") found components: Interpreter
-- Found west (found suitable version "0.8.0", minimum required is "0.7.1")
-- Board: nrf9160dk_nrf9160ns
-- Cache files will be written to: /Users/RudolphAschmoneit/Library/Caches/zephyr
-- Found dtc: /usr/local/Cellar/dtc/1.6.0/bin/dtc (found suitable version "1.6.0", minimum required is "1.4.6")
-- Found toolchain: gnuarmemb (/Applications/ARM)
-- Found BOARD.dts: /Users/RudolphAschmoneit/Documents/Arbeit/VRaktion/nordic/nRFConnectedSDK/ncs/zephyr/boards/arm/nrf9160dk_nrf9160/nrf9160dk_nrf9160ns.dts
-- Generated zephyr.dts: /Users/RudolphAschmoneit/Documents/Arbeit/VRaktion/nordic/nRFConnectedSDK/ncs/nrf/applications/asset_tracker/build_nrf9160dk_nrf9160ns/zephyr/zephyr.dts
-- Generated devicetree_unfixed.h: /Users/RudolphAschmoneit/Documents/Arbeit/VRaktion/nordic/nRFConnectedSDK/ncs/nrf/applications/asset_tracker/build_nrf9160dk_nrf9160ns/zephyr/include/generated/devicetree_unfixed.h
Parsing /Users/RudolphAschmoneit/Documents/Arbeit/VRaktion/nordic/nRFConnectedSDK/ncs/nrf/applications/asset_tracker/Kconfig
Loaded configuration '/Users/RudolphAschmoneit/Documents/Arbeit/VRaktion/nordic/nRFConnectedSDK/ncs/zephyr/boards/arm/nrf9160dk_nrf9160/nrf9160dk_nrf9160ns_defconfig'
Merged configuration '/Users/RudolphAschmoneit/Documents/Arbeit/VRaktion/nordic/nRFConnectedSDK/ncs/nrf/applications/asset_tracker/prj.conf'
Configuration saved to '/Users/RudolphAschmoneit/Documents/Arbeit/VRaktion/nordic/nRFConnectedSDK/ncs/nrf/applications/asset_tracker/build_nrf9160dk_nrf9160ns/zephyr/.config'
Kconfig header saved to '/Users/RudolphAschmoneit/Documents/Arbeit/VRaktion/nordic/nRFConnectedSDK/ncs/nrf/applications/asset_tracker/build_nrf9160dk_nrf9160ns/zephyr/include/generated/autoconf.h'
-- The C compiler identification is GNU 9.3.1
-- The CXX compiler identification is GNU 9.3.1
-- The ASM compiler identification is GNU
-- Found assembler: /Applications/ARM/bin/arm-none-eabi-gcc
-- Application: /Users/RudolphAschmoneit/Documents/Arbeit/VRaktion/nordic/nRFConnectedSDK/ncs/nrf/samples/spm
-- Zephyr version: 2.4.0 (/Users/RudolphAschmoneit/Documents/Arbeit/VRaktion/nordic/nRFConnectedSDK/ncs/zephyr)
-- Found Python3: /Users/RudolphAschmoneit/.pyenv/versions/3.9.0/bin/python3.9 (found suitable exact version "3.9.0") found components: Interpreter
-- Found west (found suitable version "0.8.0", minimum required is "0.7.1")
-- Board: nrf9160dk_nrf9160
-- Cache files will be written to: /Users/RudolphAschmoneit/Library/Caches/zephyr
-- Found toolchain: gnuarmemb (/Applications/ARM)
-- Found BOARD.dts: /Users/RudolphAschmoneit/Documents/Arbeit/VRaktion/nordic/nRFConnectedSDK/ncs/zephyr/boards/arm/nrf9160dk_nrf9160/nrf9160dk_nrf9160.dts
-- Found devicetree overlay: /Users/RudolphAschmoneit/Documents/Arbeit/VRaktion/nordic/nRFConnectedSDK/ncs/nrf/samples/spm/nrf9160dk_nrf9160.overlay
-- Generated zephyr.dts: /Users/RudolphAschmoneit/Documents/Arbeit/VRaktion/nordic/nRFConnectedSDK/ncs/nrf/applications/asset_tracker/build_nrf9160dk_nrf9160ns/spm/zephyr/zephyr.dts
-- Generated devicetree_unfixed.h: /Users/RudolphAschmoneit/Documents/Arbeit/VRaktion/nordic/nRFConnectedSDK/ncs/nrf/applications/asset_tracker/build_nrf9160dk_nrf9160ns/spm/zephyr/include/generated/devicetree_unfixed.h
Parsing /Users/RudolphAschmoneit/Documents/Arbeit/VRaktion/nordic/nRFConnectedSDK/ncs/zephyr/Kconfig
Loaded configuration '/Users/RudolphAschmoneit/Documents/Arbeit/VRaktion/nordic/nRFConnectedSDK/ncs/zephyr/boards/arm/nrf9160dk_nrf9160/nrf9160dk_nrf9160_defconfig'
Merged configuration '/Users/RudolphAschmoneit/Documents/Arbeit/VRaktion/nordic/nRFConnectedSDK/ncs/nrf/applications/asset_tracker/spm.conf'
Merged configuration '/Users/RudolphAschmoneit/Documents/Arbeit/VRaktion/nordic/nRFConnectedSDK/ncs/nrf/applications/asset_tracker/build_nrf9160dk_nrf9160ns/spm/zephyr/misc/generated/extra_kconfig_options.conf'
Configuration saved to '/Users/RudolphAschmoneit/Documents/Arbeit/VRaktion/nordic/nRFConnectedSDK/ncs/nrf/applications/asset_tracker/build_nrf9160dk_nrf9160ns/spm/zephyr/.config'
Kconfig header saved to '/Users/RudolphAschmoneit/Documents/Arbeit/VRaktion/nordic/nRFConnectedSDK/ncs/nrf/applications/asset_tracker/build_nrf9160dk_nrf9160ns/spm/zephyr/include/generated/autoconf.h'
-- Configuring incomplete, errors occurred!
See also "/Users/RudolphAschmoneit/Documents/Arbeit/VRaktion/nordic/nRFConnectedSDK/ncs/nrf/applications/asset_tracker/build_nrf9160dk_nrf9160ns/spm/CMakeFiles/CMakeOutput.log".
-- Configuring incomplete, errors occurred!
See also "/Users/RudolphAschmoneit/Documents/Arbeit/VRaktion/nordic/nRFConnectedSDK/ncs/nrf/applications/asset_tracker/build_nrf9160dk_nrf9160ns/CMakeFiles/CMakeOutput.log".
See also "/Users/RudolphAschmoneit/Documents/Arbeit/VRaktion/nordic/nRFConnectedSDK/ncs/nrf/applications/asset_tracker/build_nrf9160dk_nrf9160ns/CMakeFiles/CMakeError.log".
Including boilerplate (Zephyr base): /Users/RudolphAschmoneit/Documents/Arbeit/VRaktion/nordic/nRFConnectedSDK/ncs/zephyr/cmake/app/boilerplate.cmake
nrf9160dk_nrf9160ns.dts.pre.tmp:357.32-361.5: Warning (simple_bus_reg): /soc/cryptocell-sw: missing or empty reg/ranges property
nrf9160dk_nrf9160ns.dts.pre.tmp:56.42-68.3: Warning (unique_unit_address_if_enabled): /soc/peripheral@40000000/flash-controller@39000: duplicate unit-address (also used in node /soc/peripheral@40000000/kmu@39000)
nrf9160dk_nrf9160ns.dts.pre.tmp:305.19-311.3: Warning (unique_unit_address_if_enabled): /soc/peripheral@40000000/clock@5000: duplicate unit-address (also used in node /soc/peripheral@40000000/power@5000)
Changed board to secure nrf9160dk_nrf9160 (NOT NS)

=== child image spm - begin ===
Including boilerplate (Zephyr base): /Users/RudolphAschmoneit/Documents/Arbeit/VRaktion/nordic/nRFConnectedSDK/ncs/zephyr/cmake/app/boilerplate.cmake
CMake Error: CMake was unable to find a build program corresponding to "Ninja". CMAKE_MAKE_PROGRAM is not set. You probably need to select a different build tool.
CMake Error at ../../cmake/multi_image.cmake:214 (message):
CMake generation for spm failed, aborting. Command: 1
Call Stack (most recent call first):
../../cmake/multi_image.cmake:75 (add_child_image_from_source)
../../samples/CMakeLists.txt:22 (add_child_image)

error: cmake failed
create_nordic_project.py failed (1)

So Cmake is unable to find Ninja.

I double checked the path of Ninja in the SES Tools/Options/nRF Connect Section,

I get a similar Error when I build from Commandline too, when I forget to delete the old build folder before, I think that have something to do with the Cmake Cache Stuff ?

But I also have double checked if the build folder is deleted before opening SES. Are there Nordic specific Caches I also have to delete before? But in my understanding anything temporary goes to the build folder, am I right?

Thank you in Advance.

Many Greetings

RE: Having Trouble getting the nRF-Connected SDK running

Carl Richard — Mon, 30 Nov 2020 13:00:04 GMT

Hello, Rudolph!

Good to hear that you are managing to build now. We are aware that there is a bug in the newest version of CMake and it is being worked on!

As for building in SES, could you try the following:
1. Close SES
2. Call the following command from terminal: rm -r ~/Library/Caches/zephyr
3. Reopen SES and open your desired NCS project with a "Clean Build Folder"

Does that help?

Best regards,
Carl Richard

RE: Having Trouble getting the nRF-Connected SDK running

Rudolph Aschmoneit — Mon, 30 Nov 2020 09:34:12 GMT

Ok, I doesn't downgrade cmake, but I implemented the Workaround mentioned here:

https://github.com/zephyrproject-rtos/zephyr/pull/30272/commits/86bc6e1ae4c034f23ba6606c3aaf190dcb6c0751

Now I can build zephyr and also nRF_Connect_SDK Applications via Toolchain with this Commands:

source <NCS root folder>/zephyr/zephyr-env.sh

cd <NCS root folder>/nrf/applications/asset tracker

west build -b nrf9160dk_nrf9160ns -d build

west flash

Segger is still not working because of Kconfig but I haven't time to get deeper in to this and building via Commandline is absolutly fine for me. So let's hope that cmake will fix there error soon.

RE: Having Trouble getting the nRF-Connected SDK running

Rudolph Aschmoneit — Fri, 27 Nov 2020 16:55:16 GMT

After I got stuck here, I tried to get zephyr stand alone running, so the error I have mentioned above when building in the command line was in my opinion while there was no ZEPHYR_TOOLCHAIN_VARIANT set, in the getting started with zephyr this is explained a bit more in depth, but maybe someone could explain like Nordic is handling this, or is this handeld by segger, cause segger gets the path to the toolchain,

the other error I got, when using segger is obviously related to an buf in cmake 3.19/3.19.1 as mentioned here:
https://github.com/zephyrproject-rtos/zephyr/pull/30272/commits/86bc6e1ae4c034f23ba6606c3aaf190dcb6c0751

I will try this workaround and/or downgrade cmake and will try get nRF_Connected_SDK running again.

RE: Having Trouble getting the nRF-Connected SDK running

Rudolph Aschmoneit — Fri, 27 Nov 2020 13:34:39 GMT

Oh I forgot to mention that the nrf9160 Board I am using is working, I could update Firmware and ad a application as hex and connect it to nordic cloud, so this is fine