Problem with zephyr build blinkly on nrf52840_dongle

Dear Nordic Community,

I want to build samples/basic/blinkly on nordic nrf52840_dongle inside my Zephyr workspace. I use Zephyr 4.2.0, but on Zephyr 4.3.0 I have similar problems. Output of `west build -b nrf52840dongle zephyr/samples/basic/blinky`

```
Loading Zephyr default modules (Zephyr base).
-- Application: /home/a.paleczny/zephyrproject/zephyr/samples/basic/blinky
-- CMake version: 3.28.1
-- Found Python3: /home/a.paleczny/zephyrproject/.venv/bin/python3 (found suitable version "3.12.3", minimum required is "3.10") found components: Interpreter 
-- Cache files will be written to: /home/a.paleczny/.cache/zephyr
-- Zephyr version: 4.2.0 (/home/a.paleczny/zephyrproject/zephyr)
-- Found west (found suitable version "1.5.0", minimum required is "0.14.0")
-- Board: nrf52840dongle, qualifiers: nrf52840
-- ZEPHYR_TOOLCHAIN_VARIANT not set, trying to locate Zephyr SDK
-- Found host-tools: zephyr 0.17.4 (/home/a.paleczny/zephyr-sdk-0.17.4)
-- Found toolchain: zephyr 0.17.4 (/home/a.paleczny/zephyr-sdk-0.17.4)
-- Found Dtc: /home/a.paleczny/zephyr-sdk-0.17.4/sysroots/x86_64-pokysdk-linux/usr/bin/dtc (found suitable version "1.7.0", minimum required is "1.4.6") 
-- Found BOARD.dts: /home/a.paleczny/zephyrproject/zephyr/boards/nordic/nrf52840dongle/nrf52840dongle_nrf52840.dts
-- Generated zephyr.dts: /home/a.paleczny/zephyrproject/build/zephyr/zephyr.dts
-- Generated pickled edt: /home/a.paleczny/zephyrproject/build/zephyr/edt.pickle
-- Generated devicetree_generated.h: /home/a.paleczny/zephyrproject/build/zephyr/include/generated/zephyr/devicetree_generated.h

warning: HAS_NORDIC_DRIVERS (defined at modules/hal_nordic/Kconfig:7) has direct dependencies 0 with value n, but is currently being y-selected by the following symbols:
 - SOC_SERIES_NRF52X (defined at soc/nordic/Kconfig.soc:30, soc/nordic/nrf52/Kconfig.soc:6, soc/nordic/nrf52/Kconfig:6), with value y, direct dependencies y (value: y), and select condition SOC_FAMILY_NORDIC_NRF (value: y)

warning: HAS_NRFX (defined at modules/hal_nordic/nrfx/Kconfig:4) has direct dependencies 0 with value n, but is currently being y-selected by the following symbols:
 - SOC_SERIES_NRF52X (defined at soc/nordic/Kconfig.soc:30, soc/nordic/nrf52/Kconfig.soc:6, soc/nordic/nrf52/Kconfig:6), with value y, direct dependencies y (value: y), and select condition SOC_FAMILY_NORDIC_NRF (value: y)

warning: NRFX_CLOCK (defined at modules/hal_nordic/nrfx/Kconfig:16) has direct dependencies HAS_NRFX && 0 with value n, but is currently being y-selected by the following symbols:
 - CLOCK_CONTROL_NRF (defined at drivers/clock_control/Kconfig.nrf:13), with value y, direct dependencies DT_HAS_NORDIC_NRF_CLOCK_ENABLED && CLOCK_CONTROL (value: y), and select condition !CLOCK_CONTROL_NRF_FORCE_ALT && DT_HAS_NORDIC_NRF_CLOCK_ENABLED && CLOCK_CONTROL (value: y)

warning: NRFX_GPIOTE0 (defined at modules/hal_nordic/nrfx/Kconfig:199) has direct dependencies HAS_NRFX && 0 with value n, but is currently being y-selected by the following symbols:
 - GPIO_NRFX (defined at drivers/gpio/Kconfig.nrfx:4), with value y, direct dependencies DT_HAS_NORDIC_NRF_GPIO_ENABLED && GPIO (value: y), and select condition HAS_HW_NRF_GPIOTE0 && DT_HAS_NORDIC_NRF_GPIO_ENABLED && GPIO (value: y)

warning: NRFX_POWER (defined at modules/hal_nordic/nrfx/Kconfig:296) has direct dependencies HAS_NRFX && 0 with value n, but is currently being y-selected by the following symbols:
 - USB_NRFX (defined at drivers/usb/device/Kconfig:108), with value y, direct dependencies DT_HAS_NORDIC_NRF_USBD_ENABLED && USB_DEVICE_DRIVER (value: y), and select condition DT_HAS_NORDIC_NRF_USBD_ENABLED && USB_DEVICE_DRIVER (value: y)

warning: NRFX_GPPI (defined at modules/hal_nordic/nrfx/Kconfig:237) has direct dependencies HAS_NRFX && 0 with value n, but is currently being y-selected by the following symbols:
 - UART_0_ENHANCED_POLL_OUT (defined at drivers/serial/Kconfig.nrfx_uart_instance:21), with value y, direct dependencies !n && HAS_HW_NRF_UARTE0 && (HAS_HW_NRF_PPI || HAS_HW_NRF_DPPIC) && (HAS_HW_NRF_UART0 || HAS_HW_NRF_UARTE0) && UART_NRFX && SERIAL (value: y), and select condition !n && HAS_HW_NRF_UARTE0 && (HAS_HW_NRF_PPI || HAS_HW_NRF_DPPIC) && (HAS_HW_NRF_UART0 || HAS_HW_NRF_UARTE0) && UART_NRFX && SERIAL (value: y)

warning: NRFX_CLOCK_LFXO_TWO_STAGE_ENABLED (defined at modules/hal_nordic/nrfx/Kconfig:22) has direct dependencies NRFX_CLOCK && HAS_NRFX && 0 with value n, but is currently being y-selected by the following symbols:
 - CLOCK_CONTROL_NRF_K32SRC_XTAL (defined at drivers/clock_control/Kconfig.nrf:41), with value y, direct dependencies <choice CLOCK_CONTROL_NRF_SOURCE> (value: y), and select condition !SOC_SERIES_BSIM_NRFXX && !CLOCK_CONTROL_NRF_FORCE_ALT && <choice CLOCK_CONTROL_NRF_SOURCE> (value: y)

warning: NRFX_CLOCK_LF_SRC_XTAL (defined at modules/hal_nordic/nrfx/Kconfig:31) has direct dependencies NRFX_CLOCK && HAS_NRFX && 0 with value n, but is currently being y-selected by the following symbols:
 - CLOCK_CONTROL_NRF_K32SRC_XTAL (defined at drivers/clock_control/Kconfig.nrf:41), with value y, direct dependencies <choice CLOCK_CONTROL_NRF_SOURCE> (value: y), and select condition !CLOCK_CONTROL_NRF_FORCE_ALT && <choice CLOCK_CONTROL_NRF_SOURCE> (value: y)

error: Aborting due to Kconfig warnings

Parsing /home/a.paleczny/zephyrproject/zephyr/Kconfig
Loaded configuration '/home/a.paleczny/zephyrproject/zephyr/boards/nordic/nrf52840dongle/nrf52840dongle_nrf52840_defconfig'
Merged configuration '/home/a.paleczny/zephyrproject/zephyr/samples/basic/blinky/prj.conf'
CMake Error at /home/a.paleczny/zephyrproject/zephyr/cmake/modules/kconfig.cmake:389 (message):
  command failed with return code: 1
Call Stack (most recent call first):
  /home/a.paleczny/zephyrproject/zephyr/cmake/modules/zephyr_default.cmake:131 (include)
  /home/a.paleczny/zephyrproject/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:66 (include)
  /home/a.paleczny/zephyrproject/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:92 (include_boilerplate)
  CMakeLists.txt:4 (find_package)
```

What is wrong and what can I change? 

Parents
  • Hi,

    The official SDK from Nordic Semiconductor is nRF Connect SDK, which includes a version of Zephyr, but also a lot on top of that. Have you tried with the latest release of the nRF Connect SDK, and built the same sample there?

    If you still want to go for pure Zephyr, then I recommend reaching out to the Zephyr community (https://www.zephyrproject.org/) regarding issues with getting unmodified Zephyr samples to run. The Zephyr documentation for the nRF52840 Dongle uses the Blinky sample for the section on how to program and debug the dongle, so if you follow these steps then it should work out-of-the-box. If not, then I would consider that a bug in Zephyr, either in code or in documentation.

    Regards,
    Terje

Reply
  • Hi,

    The official SDK from Nordic Semiconductor is nRF Connect SDK, which includes a version of Zephyr, but also a lot on top of that. Have you tried with the latest release of the nRF Connect SDK, and built the same sample there?

    If you still want to go for pure Zephyr, then I recommend reaching out to the Zephyr community (https://www.zephyrproject.org/) regarding issues with getting unmodified Zephyr samples to run. The Zephyr documentation for the nRF52840 Dongle uses the Blinky sample for the section on how to program and debug the dongle, so if you follow these steps then it should work out-of-the-box. If not, then I would consider that a bug in Zephyr, either in code or in documentation.

    Regards,
    Terje

Children
Related