nRF Connect SDK build error

[NickH]

Hi,

I am trying to configure the nRF Connect SDK on a Mac running Catalina for the first time and have followed the nRf Connect v3.6.0 - Getting Started Assistant.

I am getting errors when running "pip3 install -r zephyr/scripts/requirements.txt"

ERROR: nrfutil 5.2.0 has requirement click~=7.0, but you'll have click 6.7 which is incompatible.

ERROR: nrfutil 5.2.0 has requirement pyyaml~=4.2b1, but you'll have pyyaml 5.3.1 which is incompatible.

I am not sure how to resolve these dependency errors.

When I complete the SDK installation, it verifies each step with no errors but when I launch the SES (Nordic Edition) V5.10d with a nRF5340 PDK connected, I get a build error:

File "/Users/nick/Development/NordicConnectSDK/ncs/zephyr/scripts/dts/gen_defines.py", line 29, in <module>    import edtlib

File "/Users/nick/Development/NordicConnectSDK/ncs/zephyr/scripts/dts/edtlib.py", line 78, in <module>     import yaml

ModuleNotFoundError: No module named 'yaml'

The yaml module is in "/usr/local/lib/python3.7/site-packages/yaml" and the $PATH includes "/usr/local/lib/python3.7/site-packages".

I'm not sure if the pyyaml dependency error running the requirements script is related to this build error but I I would welcome any suggestions as I can't get past this point and build any of the sample apps.

Thanks!

Nick

[Carl Richard]

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

[NickH]

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.  

[Carl Richard]

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

[NickH]

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

[NickH]

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

[Carl Richard]

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

[NickH]

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

[Carl Richard]

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

Best regards,
Carl Richard

[NickH]

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

[Carl Richard]

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

[Carl Richard]

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

[NickH]

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