Build error while running DFU over bluetooth Sample in BL653 board.

[helloble]

Hi,

I am using Nrf Connect Sdk version 1.9.1. I am trying to build the sample code for Ble DFU using BL653 board. The link of sample code is here. 

I am getting Kconfig warnings and Cmake error when I try to build the same. The error is as follows:

error: Aborting due to Kconfig warnings

CMake Error at D:/nrf/v1.9.1/zephyr/cmake/kconfig.cmake:272 (message):
  command failed with return code: 1
Call Stack (most recent call first):
  D:/nrf/v1.9.1/zephyr/cmake/app/boilerplate.cmake:544 (include)
  D:/nrf/v1.9.1/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:24 (include)
  D:/nrf/v1.9.1/zephyr/share/zephyr-package/cmake/ZephyrConfig.cmake:35 (include_boilerplate)
  CMakeLists.txt:44 (find_package)


-- Configuring incomplete, errors occurred!
CMake Error at D:/nrf/v1.9.1/nrf/cmake/multi_image.cmake:409 (message):
  CMake generation for mcuboot failed, aborting.  Command: 1
Call Stack (most recent call first):
  D:/nrf/v1.9.1/nrf/cmake/multi_image.cmake:150 (add_child_image_from_source)
  D:/nrf/v1.9.1/nrf/modules/mcuboot/CMakeLists.txt:216 (add_child_image)


-- Configuring incomplete, errors occurred!
See also "D:/learning/Project5/peripheral_lbs_BLE_DFU/build/CMakeFiles/CMakeOutput.log".
See also "D:/learning/Project5/peripheral_lbs_BLE_DFU/build/CMakeFiles/CMakeError.log".
FATAL ERROR: command exited with status 1: 'd:\nrf\v1.9.1\toolchain\opt\bin\cmake.EXE' '-DWEST_PYTHON=d:\nrf\v1.9.1\toolchain\opt\bin\python.exe' '-Bd:\learning\Project5\peripheral_lbs_BLE_DFU\build' '-Sd:\learning\Project5\peripheral_lbs_BLE_DFU' -GNinja -DBOARD=bl653_dvk -DNCS_TOOLCHAIN_VERSION:STRING=NONE -DBOARD_ROOT:STRING=d:/learning/Project5/peripheral_lbs_BLE_DFU

What could be the issue and how to solve this issue?

[Vidar Berg]

Hello,

Please try to build MCUBOOT with CONFIG_CLOCK_CONTROL_NRF_CALIBRATION_MAX_SKIP=0 as suggested in this answer RE: BL653 soft reset fails in sample DFU App . If this also fails, please upload the full build log so I can see what the Kconfig warnings were.

Best regards,

Vidar 

[helloble]

Hi Vidar Berg,

I added MCUBOOT with CONFIG_CLOCK_CONTROL_NRF_CALIBRATION_MAX_SKIP=0 in my prj.conf file. After that, I run pristine build. Still I am facing the same problem as before. I'll share the full build error log with you.

Due to some issue with the website, I am not able to upload or attach the build error log here.

 

[helloble]

Hi Vidar,

I did the changes as mentioned by you that is, adding prj.conf inside the child_image and adding CONFIG_CLOCK_CONTROL_NRF_CALIBRATION_MAX_SKIP=0 inside it. But still, I am facing the same error as before.

I am attaching the screenshot for your reference.

[Vidar Berg]

No, you need to name the config file 'mcuboot.conf' to tell the build system which image the configuration belongs to.

Vidar Berg said:

<project dir>
├── child_image
│   └── mcuboot.conf
├── CMakeLists.txt
├── Kconfig
├── prj.conf
├── README.rst
├── sample.yaml
└── src
└── main.c

[helloble]

Hi,

I changed the name to "mcuboot.conf" and then built it. Still same error is coming. Screenshot is attached for your reference.

It says "D:/learning/Projectjun1/peripheral_lbs/child_image/mcuboot.conf:6: warning: attempt to assign the value '0' to the undefined symbol CLOCK_CONTROL_NRF_CALIBRATION_SKIP".

[Vidar Berg]

It supposed to be CONFIG_CLOCK_CONTROL_NRF_CALIBRATION_MAX_SKIP, not CLOCK_CONTROL_NRF_CALIBRATION_SKIP.

[helloble]

Thanks. It's building fine now.