This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

SES Blinky build error

I'm trying to build the blinky zephyr sample for nRF Connect SDK and get the following failure:
Creating solution blinky.emProject
/usr/local/bin/cmake -GNinja -DBOARD=nrf52840dk_nrf52840 -DBOARD_DIR=/Users/denis/sandbox/ncs/zephyr/boards/arm/nrf52840dk_nrf52840 -B/Users/denis/sandbox/ncs/zephyr/samples/basic/blinky/build_nrf52840dk_nrf52840 -S/Users/denis/sandbox/ncs/zephyr/samples/basic/blinky -DZEPHYR_TOOLCHAIN_VARIANT=gnuarmemb -DGNUARMEMB_TOOLCHAIN_PATH=/Users/denis/sandbox/gcc-arm-none-eabi-9-2019-q4-major -DPYTHON_EXECUTABLE=/usr/local/bin/python3 -DCMAKE_MAKE_PROGRAM=/usr/local/bin/ninja -DDTC=/usr/local/bin/dtc -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/denis/sandbox/ncs/zephyr/samples/basic/blinky
-- Zephyr version: 2.4.0 (/Users/denis/sandbox/ncs/zephyr)
-- Board: nrf52840dk_nrf52840
-- Cache files will be written to: /Users/denis/Library/Caches/zephyr
-- Found dtc: /usr/local/bin/dtc (found suitable version "1.6.0", minimum required is "1.4.6")
-- Found toolchain: gnuarmemb (/Users/denis/sandbox/gcc-arm-none-eabi-9-2019-q4-major)
-- Found BOARD.dts: /Users/denis/sandbox/ncs/zephyr/boards/arm/nrf52840dk_nrf52840/nrf52840dk_nrf52840.dts
-- Configuring incomplete, errors occurred!
Including boilerplate (Zephyr base (cached)): /Users/denis/sandbox/ncs/zephyr/cmake/app/boilerplate.cmake
Traceback (most recent call last):
File "/Users/denis/sandbox/ncs/zephyr/scripts/dts/gen_defines.py", line 29, in <module>
import edtlib
File "/Users/denis/sandbox/ncs/zephyr/scripts/dts/edtlib.py", line 78, in <module>
import yaml
ModuleNotFoundError: No module named 'yaml'
CMake Error at /Users/denis/sandbox/ncs/zephyr/cmake/dts.cmake:246 (message):
gen_defines.py failed with return code: 1
Call Stack (most recent call first):
/Users/denis/sandbox/ncs/zephyr/cmake/app/boilerplate.cmake:590 (include)
/Users/denis/sandbox/ncs/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:24 (include)
/Users/denis/sandbox/ncs/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:40 (include_boilerplate)
CMakeLists.txt:4 (find_package)
error: cmake failed
create_nordic_project.py failed (1)
If I try to install the package it can't seem to find, it appears it is already installed:
$ pip3 install pyyaml --user
Requirement already satisfied: pyyaml in /usr/local/lib/python3.8/site-packages (5.3.1)
I can build other zephyr projects from the command line ok.
SEGGER Embedded Studio for ARM Release 5.10d  Build 2020101613.44003 macOS x64
Any idea what might be the issue here?
Parents
  • Do you have several versions of python installed? It may be that zephyr/scripts/dts/edtlib.py is looking somewhere else for the package. Take a look at your environment variables, and remove the ones you're not using.

    Could you try to run the following commands:

    cd <sourcecode_root>\ncs
    pip3 install -r zephyr\scripts\requirements.txt
    pip3 install -r nrf\scripts\requirements.txt
    pip3 install -r bootloader\mcuboot\scripts\requirements.txt

    You could also try to install NCS through the Toolchain Manager (TM), and open SES from TM?

    Please tell me if you encounter any issues with this approach (which you may do, since the TM is experimental for macOS), and I will help get it to work with the Manual approach.

    Best regards,

    Simon

Reply
  • Do you have several versions of python installed? It may be that zephyr/scripts/dts/edtlib.py is looking somewhere else for the package. Take a look at your environment variables, and remove the ones you're not using.

    Could you try to run the following commands:

    cd <sourcecode_root>\ncs
    pip3 install -r zephyr\scripts\requirements.txt
    pip3 install -r nrf\scripts\requirements.txt
    pip3 install -r bootloader\mcuboot\scripts\requirements.txt

    You could also try to install NCS through the Toolchain Manager (TM), and open SES from TM?

    Please tell me if you encounter any issues with this approach (which you may do, since the TM is experimental for macOS), and I will help get it to work with the Manual approach.

    Best regards,

    Simon

Children
No Data
Related