trying to usenRF Connect SDK for the first time.
Could be because of recent upgrades to MacOS.
(I have used gcc with nRF SDKs before)
Paul
trying to usenRF Connect SDK for the first time.
Could be because of recent upgrades to MacOS.
(I have used gcc with nRF SDKs before)
Paul
Hi Paul,
Can you try to download and install gcc-arm-none-eabi-9-2020-q2-update-mac.pkg from here? That distribution is signed and sould work also with recent macOS versions.
Einar
That download installs OK. I think the error is to do with SES trying to use an older version that is still on my machine.
/opt/gnuarmemb seems to be the path it's using. Is that so?
Maybe I need to change this to wherever the correct version is?
Where is that set?
I think it should point to /Applications/ARM/bin/arm-none-eabi-gcc which reports that it's v9.3.1
Hi,
I see. I just updated to Big Sur an SES (Nordic) 5.10d and now I get the same error as you see. I have not found an explanation for this or workaround yet, though.
Hi,
Update on this. In my case the issue was that I had not updated the paths correctly (after moving things around). Perhaps you did the same, or forgot to set zephyr and toolchain base in the first place?
Before opening a NCS project you need to start SES, then go to Tools -> Options ... and select nRF Connect. Then you need to set the two Directories correctly. In my case it is like this, but you need to adjust it for your setup:
After that, you should be able to open a NCS project from File -> Open nRF Connect SDK Project...
Thx but ...
If you look further up this post you will see that I have indeed set those correctly
Hi,
Ah, sorry. I did not remember that. But now I spotted another issue, which would also give you this error. You have specified the wrong board. You ned to use nrf9160dk_nrf9160ns. It is not possible to run sample projects that use the modem in any thing other than non-secure mode (ns).
get the same error with that board. Also tried to build blinky. same error.
create_nordic_project.py failed (1).
get the same error with that board. Also tried to build blinky. same error.
create_nordic_project.py failed (1).
Hm, then I am not sure... Can you show the log form SES? (you will be able to see it in the lower part of the SES window after you click OK on the error message).
ok. after a couple of tries I got the log:
```
Creating solution blinky.emProject
/usr/local/bin/cmake -GNinja -DBOARD=nrf9160dk_nrf9160ns -DBOARD_DIR=/Users/paul_tanner/Nordic/nrfsrc/ncs/zephyr/boards/arm/nrf9160dk_nrf9160 -B/Users/paul_tanner/Nordic/nrfsrc/ncs/zephyr/samples/basic/blinky/build_nrf9160dk_nrf9160ns -S/Users/paul_tanner/Nordic/nrfsrc/ncs/zephyr/samples/basic/blinky -DZEPHYR_TOOLCHAIN_VARIANT=gnuarmemb -DGNUARMEMB_TOOLCHAIN_PATH=/Applications/ARM -DPYTHON_EXECUTABLE=/usr/local/bin/python3 -DCMAKE_MAKE_PROGRAM=/usr/local/bin/ninja -DDTC=/usr/local/bin/dtc -D WEST=/usr/local/bin/west -DEXTRA_KCONFIG_TARGETS=menuconfig_ses -DEXTRA_KCONFIG_TARGET_COMMAND_FOR_menuconfig_ses=/Applications/arm_segger_embedded_studio_v510d_macos_x64_nordic/html/configure_nordic_project_menuconfig.py
-- Application: /Users/paul_tanner/Nordic/nrfsrc/ncs/zephyr/samples/basic/blinky
-- Zephyr version: 2.4.0 (/Users/paul_tanner/Nordic/nrfsrc/ncs/zephyr)
-- Found west (found suitable version "0.7.2", minimum required is "0.7.1")
-- Board: nrf9160dk_nrf9160ns
-- Cache files will be written to: /Users/paul_tanner/Library/Caches/zephyr
-- Found dtc: /usr/local/bin/dtc (found suitable version "1.6.0", minimum required is "1.4.6")
-- Found toolchain: gnuarmemb (/Applications/ARM)
-- Found BOARD.dts: /Users/paul_tanner/Nordic/nrfsrc/ncs/zephyr/boards/arm/nrf9160dk_nrf9160/nrf9160dk_nrf9160ns.dts
-- Generated zephyr.dts: /Users/paul_tanner/Nordic/nrfsrc/ncs/zephyr/samples/basic/blinky/build_nrf9160dk_nrf9160ns/zephyr/zephyr.dts
-- Generated devicetree_unfixed.h: /Users/paul_tanner/Nordic/nrfsrc/ncs/zephyr/samples/basic/blinky/build_nrf9160dk_nrf9160ns/zephyr/include/generated/devicetree_unfixed.h
Parsing /Users/paul_tanner/Nordic/nrfsrc/ncs/zephyr/Kconfig
Loaded configuration '/Users/paul_tanner/Nordic/nrfsrc/ncs/zephyr/samples/basic/blinky/build_nrf9160dk_nrf9160ns/zephyr/.config'
No change to configuration in '/Users/paul_tanner/Nordic/nrfsrc/ncs/zephyr/samples/basic/blinky/build_nrf9160dk_nrf9160ns/zephyr/.config'
No change to Kconfig header in '/Users/paul_tanner/Nordic/nrfsrc/ncs/zephyr/samples/basic/blinky/build_nrf9160dk_nrf9160ns/zephyr/include/generated/autoconf.h'
-- Application: /Users/paul_tanner/Nordic/nrfsrc/ncs/nrf/samples/spm
-- Zephyr version: 2.4.0 (/Users/paul_tanner/Nordic/nrfsrc/ncs/zephyr)
-- Found west (found suitable version "0.7.2", minimum required is "0.7.1")
-- Board: nrf9160dk_nrf9160
-- Cache files will be written to: /Users/paul_tanner/Library/Caches/zephyr
-- Found toolchain: gnuarmemb (/Applications/ARM)
-- Found BOARD.dts: /Users/paul_tanner/Nordic/nrfsrc/ncs/zephyr/boards/arm/nrf9160dk_nrf9160/nrf9160dk_nrf9160.dts
-- Found devicetree overlay: /Users/paul_tanner/Nordic/nrfsrc/ncs/nrf/samples/spm/nrf9160dk_nrf9160.overlay
-- Generated zephyr.dts: /Users/paul_tanner/Nordic/nrfsrc/ncs/zephyr/samples/basic/blinky/build_nrf9160dk_nrf9160ns/spm/zephyr/zephyr.dts
-- Generated devicetree_unfixed.h: /Users/paul_tanner/Nordic/nrfsrc/ncs/zephyr/samples/basic/blinky/build_nrf9160dk_nrf9160ns/spm/zephyr/include/generated/devicetree_unfixed.h
Parsing /Users/paul_tanner/Nordic/nrfsrc/ncs/zephyr/Kconfig
Loaded configuration '/Users/paul_tanner/Nordic/nrfsrc/ncs/zephyr/samples/basic/blinky/build_nrf9160dk_nrf9160ns/spm/zephyr/.config'
No change to configuration in '/Users/paul_tanner/Nordic/nrfsrc/ncs/zephyr/samples/basic/blinky/build_nrf9160dk_nrf9160ns/spm/zephyr/.config'
No change to Kconfig header in '/Users/paul_tanner/Nordic/nrfsrc/ncs/zephyr/samples/basic/blinky/build_nrf9160dk_nrf9160ns/spm/zephyr/include/generated/autoconf.h'
-- Configuring incomplete, errors occurred!
See also "/Users/paul_tanner/Nordic/nrfsrc/ncs/zephyr/samples/basic/blinky/build_nrf9160dk_nrf9160ns/spm/CMakeFiles/CMakeOutput.log".
-- Configuring incomplete, errors occurred!
See also "/Users/paul_tanner/Nordic/nrfsrc/ncs/zephyr/samples/basic/blinky/build_nrf9160dk_nrf9160ns/CMakeFiles/CMakeOutput.log".
See also "/Users/paul_tanner/Nordic/nrfsrc/ncs/zephyr/samples/basic/blinky/build_nrf9160dk_nrf9160ns/CMakeFiles/CMakeError.log".
Including boilerplate (Zephyr base (cached)): /Users/paul_tanner/Nordic/nrfsrc/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 (cached)): /Users/paul_tanner/Nordic/nrfsrc/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 /Users/paul_tanner/Nordic/nrfsrc/ncs/nrf/cmake/multi_image.cmake:214 (message):
CMake generation for spm failed, aborting. Command: 1
Call Stack (most recent call first):
/Users/paul_tanner/Nordic/nrfsrc/ncs/nrf/cmake/multi_image.cmake:75 (add_child_image_from_source)
/Users/paul_tanner/Nordic/nrfsrc/ncs/nrf/samples/CMakeLists.txt:22 (add_child_image)
error: cmake failed
create_nordic_project.py failed (1)
```
Not sure how to fix it tho'
2 things bothering me. fFrstly if you look at the image showing the red error message you will see that the Toolchain version is not set (cannot be set).
Secondly in the Connect SDK there is a side panel to show settings such as ncs_tag. Should these be blank. The GnuArmEmb_path is not the one I have set.
Is this OK?
Hi,
paul_tanner said:2 things bothering me. fFrstly if you look at the image showing the red error message you will see that the Toolchain version is not set (cannot be set).
I do not see any error message. Can you clarify?
paul_tanner said:Secondly in the Connect SDK there is a side panel to show settings such as ncs_tag. Should these be blank. The GnuArmEmb_path is not the one I have set.
These are used for the getting started assistant to verify your steps. It makes sense to set them correctly when using the getting started assistant, but it does not have any other consequences.
Regarding the log, I notice "CMAKE_MAKE_PROGRAM is not set". Can you double-check that you have followed every step in the guide so that all dependencies are correctly installed? I should also note that another good guide (which I personally prefer) is the one in the nRF Connect SDK documentation under Installing the nRF Connect SDK manually. Following that in detail should give you a working setup. Just remember that there is one exception which is that you need to install a signed ARM GCC on recent macOS versions, as we have allready discussed.
Lastly, if you do not have success in getting this working, it might be worth trying the Toolchain Manager, even though it is still experimental for macOS.
The image I refer to is near the top of this post. It contains a red highlighted error message. Behind that is the field I was concerned about.
You have pointed out that settings such as ncs_tag are only needed for verification. How could I set them?
In the options for CMake Executable I have /usr/local/bin/cmake which resolves to
```
lrwxr-xr-x 1 paul_tanner admin 32 4 Jun 16:34 /usr/local/bin/cmake -> ../Cellar/cmake/3.17.3/bin/cmake
```