nRF Connect SDK build error

RE: nRF Connect SDK build error

Carl Richard — Thu, 10 Dec 2020 13:51:33 GMT

I see. That's unfortunate, but I wish you best of luck! I'll update if we discover a solution to the issue here.

Best regards,
Carl Richard

RE: nRF Connect SDK build error

NickH — Thu, 10 Dec 2020 10:24:05 GMT

Carl,

I've had to switch focus back to SDK17 but unfortunately I was unable to resolve the nrfx.h not found issue after re-installing. Must be something in my set-up/environment. I'll update this thread if I manage to resolve...

Thanks for you support...

Nick

RE: nRF Connect SDK build error

Carl Richard — Thu, 03 Dec 2020 08:57:22 GMT

Hi again, Nick!

Did it help? Anyway, I will put down an effort to update the manual installation guides to reflect the issues you are facing.

Best regards,
Carl Richard

RE: nRF Connect SDK build error

NickH — Fri, 27 Nov 2020 15:49:25 GMT

I had 3.9 installed but when I checked the installation guide, 3.7 was referenced so I set up the environment to point to that. In fact https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/gs_recommended_versions.html references (for Mac) Python 3.6->3.8.2. Anyway I'm deleting 3.7...

RE: nRF Connect SDK build error

Carl Richard — Fri, 27 Nov 2020 14:43:10 GMT

I see.

What is the version of the Python executable is present at "/usr/local/bin/python3"? That is the standard location for Python installed through "brew", which should be 3.9 from what I know. However, your west package is installed for 3.7. That could maybe pose a problem.

Best regards,
Carl Richard

RE: nRF Connect SDK build error

NickH — Fri, 27 Nov 2020 14:31:29 GMT

CMake West path already added. West exists in this location and west runs OK from terminal...

Still getting nrfx.h error...

ratpro:site-packages nick$ pwd

/usr/local/lib/python3.7/site-packages

ratpro:site-packages nick$ cd west

ratpro:west nick$ ls -l

total 288

-rw-r--r-- 1 nick admin 63 22 Nov 09:11 __init__.py

-rw-r--r-- 1 nick admin 39 22 Nov 09:11 __main__.py

drwxr-xr-x 12 nick admin 384 22 Nov 09:11 __pycache__

drwxr-xr-x 7 nick admin 224 22 Nov 09:11 app

-rw-r--r-- 1 nick admin 1388 22 Nov 09:11 build.py

-rw-r--r-- 1 nick admin 7585 22 Nov 09:11 cmake.py

-rw-r--r-- 1 nick admin 14076 22 Nov 09:11 commands.py

-rw-r--r-- 1 nick admin 10835 22 Nov 09:11 configuration.py

-rw-r--r-- 1 nick admin 5844 22 Nov 09:11 log.py

-rw-r--r-- 1 nick admin 3887 22 Nov 09:11 manifest-schema.yml

-rw-r--r-- 1 nick admin 73414 22 Nov 09:11 manifest.py

-rw-r--r-- 1 nick admin 2926 22 Nov 09:11 util.py

-rw-r--r-- 1 nick admin 613 22 Nov 09:11 version.py

-rw-r--r-- 1 nick admin 1001 22 Nov 09:11 west-commands-schema.yml

RE: nRF Connect SDK build error

Carl Richard — Fri, 27 Nov 2020 13:20:17 GMT

Hi again, Nick!

I did some more digging and from what I can see SES can't find west on your path. The build log should normally show "found west", but I haven't seen that in your logs. You can read more about the issue in this thread.

Remember to put define the path to the west executable in Additional CMake Options as explained in the manual installation guide.

Best regards,
Carl Richard

RE: nRF Connect SDK build error

Carl Richard — Thu, 26 Nov 2020 11:10:22 GMT

I see. I'm quite unsure regarding what may be causing this. While I can't manage to reproduce it, I believe it may be related to the YAML issue of earlier. However, you could try to add the nrfx.h file manually (Project -> Add existing file) and ensure that it's correctly set in menuconfig (Project -> Configure nRF Connect SDK project -> Search for HAS_nRFX).

In addition, could you also post a screenshot of how the nRF Connect SDK is configured in SES. You can find this under Tools -> Options -> nRF Connect SDK.

We've just updated the Toolchain Manager of nRF Connect for Desktop to be more stable for MacOS users, so I recommend trying that if the above is unsuccessfull.

Best regards,
Carl Richard

RE: nRF Connect SDK build error

NickH — Wed, 25 Nov 2020 14:49:26 GMT

I get the same error in blinky and hello world sample apps. Tried clean build directory option, restarting SES etc...

RE: nRF Connect SDK build error

Carl Richard — Wed, 25 Nov 2020 14:12:14 GMT

Ok. Did you open the project with the "Clean Build Directory" option? If not, try that.

Best regards,
Carl Richard

RE: nRF Connect SDK build error

NickH — Wed, 25 Nov 2020 11:51:25 GMT

I ran west as instructed and re-started SES but same error.

nrfx.h is located at /Users/nick/Development/NordicConnectSDK/ncs/modules/hal/nordic/nrfx

The project is an unmodified blinky sample app.

Nick

RE: nRF Connect SDK build error

Carl Richard — Wed, 25 Nov 2020 11:45:29 GMT

Great to hear that it works now!

When it comes to the issue with nrfx.h, could you try to do the following:
- check if the file <ncs_root>\modules\hal\nordic\nrfx\nrfx.h exists.
- run the command west update inside the NCS root directory.

Report back if it doesn't work.

For adding additional files to your project, check out my answer in this thread.

Best regards,
Carl Richard

RE: nRF Connect SDK build error

NickH — Wed, 25 Nov 2020 11:35:41 GMT

Carl,

When using the old nRF SDK, adding paths to include files was via SES options->preprocessor->user include directories - what is the equivalent in nRF Connect with the Nordic SES?

Nick

RE: nRF Connect SDK build error

NickH — Wed, 25 Nov 2020 11:25:25 GMT

Carl,

I downloaded the signed app package "gcc-arm-none-eabi-9-2020-q2-update-mac.pkg" and installed it. It installed in /Applications/ARM so I copied into /opt/gnuarmemb as otherwise the SES could not locate it (even after changing the SES GNU ARM Embedded Tool Chain directory path variable).

I tried uncommenting the python.cmake but then I got the yaml error again.

I then ran the rm -r /Users/<your_username>/Library/Caches/zephyr and restarted SES and I was then able to build OK.

I can now see the files but when I try and build/debug I get a compile error about:

nrfx.h: No such file or directory

So I guess there is still an environment issue but at least I get to the project window now.

For anyone else on a Mac, the main problem was using the "Mac OS X 64-bit Tarball" rather than the "Mac OS X 64-bit Package (Signed and notarized)" version of gcc-arm-none-eabi-9-2020-q2-update-mac

Nick

RE: nRF Connect SDK build error

Carl Richard — Tue, 24 Nov 2020 09:51:22 GMT

Hi again.

I see that this did not make things much better. Could I purpose that you remove your current installation of the gnuarmemb and download the signed app package instead? That could at least rule out any problems with Catelina's strict security. Links for download and additional instructions can be found in the manual installation guide for NCS.

The errors you get when building from the command line stems from my initial suggestion to comment out lines in python.cmake. My apologies for this. Could you uncomment them and then see which Python version is used by SES by going to Tools -> Options -> nRF Connect SDK options?

Best regards,
Carl Richard

RE: nRF Connect SDK build error

NickH — Mon, 23 Nov 2020 15:30:35 GMT

Case 1:

Case 2:

/Users/nick/Development/NordicConnectSDK/ncs/zephyr/samples/hello_world

ratpro:hello_world nick$ west build -b nrf5340pdk_nrf5340_cpuapp -p

-- west build: generating a build system

Including boilerplate (Zephyr base): /Users/nick/Development/NordicConnectSDK/ncs/zephyr/cmake/app/boilerplate.cmake

-- Application: /Users/nick/Development/NordicConnectSDK/ncs/zephyr/samples/hello_world

-- Zephyr version: 2.4.0 (/Users/nick/Development/NordicConnectSDK/ncs/zephyr)

CMake Error at /Users/nick/Development/NordicConnectSDK/ncs/zephyr/cmake/west.cmake:14 (get_filename_component):

get_filename_component called with incorrect number of arguments

Call Stack (most recent call first):

/Users/nick/Development/NordicConnectSDK/ncs/zephyr/cmake/app/boilerplate.cmake:139 (include)

/Users/nick/Development/NordicConnectSDK/ncs/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:24 (include)

/Users/nick/Development/NordicConnectSDK/ncs/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:35 (include_boilerplate)

CMakeLists.txt:5 (find_package)

CMake Error at /Users/nick/Development/NordicConnectSDK/ncs/zephyr/cmake/west.cmake:42 (if):

if given arguments:

"NOT" "(" "/usr/local/Cellar/python@3.7/3.7.9_2/Frameworks/Python.framework/Versions/3.7/bin/python3.7" "STREQUAL" ")"

Unknown arguments specified

Call Stack (most recent call first):

/Users/nick/Development/NordicConnectSDK/ncs/zephyr/cmake/app/boilerplate.cmake:139 (include)

/Users/nick/Development/NordicConnectSDK/ncs/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:24 (include)

/Users/nick/Development/NordicConnectSDK/ncs/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:35 (include_boilerplate)

CMakeLists.txt:5 (find_package)

-- Configuring incomplete, errors occurred!

FATAL ERROR: command exited with status 1: /usr/local/bin/cmake -DWEST_PYTHON=/usr/local/opt/python@3.7/bin/python3.7 -B/Users/nick/Development/NordicConnectSDK/ncs/zephyr/samples/hello_world/build -S/Users/nick/Development/NordicConnectSDK/ncs/zephyr/samples/hello_world -GNinja -DBOARD=nrf5340pdk_nrf5340_cpuapp

ratpro:hello_world nick$

RE: nRF Connect SDK build error

Carl Richard — Mon, 23 Nov 2020 14:32:33 GMT

The output in CMakeError.txt is not always very informative as there is likely other issues leading to said CMakeError.

As a next step I would like you to close SES and call the following command:

rm -r /Users/<your_username>/Library/Caches/zephyr

This removes the CMake cache used by Zephyr, and will hopefully rid you of any inherited errors. In addition I want you to make sure that your environment is set correctly. Confirm the following environment variables are set "ZEPHYR_TOOLCHAIN_VARIANT=gnuarmemb" and "GNUARMEMB_TOOLCHAIN_PATH=/opt/gnuarmemb/" and that you've called "source <ncs_root>/zephyr/zephyr-env.sh".

When all of this is done and confirmed. Try to build again. If it fails would also like you to try building from the command line. Go to a sample of choice <ncs_root>/zephyr/samples/hello_world for example and call the following command:

west build -b nrf5340pdk_nrf5340_cpuapp -p

Please report the build logs back to me in both cases. Thanks!

Best regards,
Carl Richard

RE: nRF Connect SDK build error

NickH — Mon, 23 Nov 2020 14:11:55 GMT

the CMakeError.log referenced above contains:

Compiling the C compiler identification source file "CMakeCCompilerId.c" failed.
Compiler: /opt/gnuarmemb/bin/arm-none-eabi-gcc
Build flags:
Id flags:

The output was:
1
clang: error: unknown argument '-meabi=5'; did you mean '-mabi=5'?

Which doesn't seem terribly positive...

RE: nRF Connect SDK build error

NickH — Mon, 23 Nov 2020 14:02:28 GMT

Carl,

Thanks for the quick response - I’ve been trying to solve this for several days now as I’m trying to decide whether to port my code from SDK17 to NRF Connect…

I tried commenting out the line and opening Blinky sample for the 5340 PDK board I have - it got further but still failed.

I haven’t looked in any of the cmake logs mentioned yet. I get the same error with Hello World as well.

RE: nRF Connect SDK build error

Carl Richard — Mon, 23 Nov 2020 13:29:57 GMT

Hi, Nick!

Could you try to apply the fix Ian has proposed for a similar issue? I.e, comment out line 44 and 45 of the <ncs_root>/zephyr/cmake/python.cmake file like so:

#find_package(Python3 ${PYTHON_MINIMUM_REQUIRED} REQUIRED ${PYTHON_EXACT})
#set(PYTHON_EXECUTABLE ${Python3_EXECUTABLE})

Please report back if this works for you or not!

And thank you for reaching out. We are aware that the installation procedure for MacOS is not currently satisfactory.

Best regards,
Carl Richard

RE: nRF Connect SDK build error

NickH — Mon, 23 Nov 2020 09:30:09 GMT

I actually fixed the dependency issue with 'click' and 'pyyaml' but still have the 'yaml module not found' issue.

I wrote a simple python script that imports the yaml library and this runs from the command line which would imply that PATHs are OK so I'm not clear why SES is having issues....

Anyone got any pointers for what is probably a simple environment issue?