Unable to configure mcuboot on sample DFU app for BL653 board

[Ubaid_M]

Hi,

I need to evaluate nordic suggested Sample DFU app on BL653 board : https://devzone.nordicsemi.com/guides/nrf-connect-sdk-guides/b/software/posts/ncs-dfu

But as soon as i enable "CONFIG_BOOTLOADER_MCUBOOT=y", the project build fails.

Please find attached the peripheral_lbs project and kindly help.

The same project upon further configuration works on nrf52833dk.

But for BL653, the build fails without generating proper errors.

peripheral_lbs_BL653.7z

 

Thanks,

[Ubaid_M]

Hi,

Here is the project build step by step as suggested in : https://devzone.nordicsemi.com/guides/nrf-connect-sdk-guides/b/software/posts/ncs-dfu

5810.peripheral_lbs_BL653.7z

The build fails for bl653 without any information of error.

Kindly suggest

[Vidar Berg]

Hi,

Please add the attached mcuboot.conf file to your child_image folder. This should override the incorrect board file configuration mentioned by Torstein in this post: https://devzone.nordicsemi.com/f/nordic-q-a/82374/hello-world-mcuboot-build-errors-out-of-the-box/343632#343632 

6114.mcuboot.conf

And the actual error message was displayed a bit further up in the log:

warning: TEMP_NRF5 (defined at drivers/sensor/nrf5/Kconfig:13) has direct dependencies HAS_HW_NRF_TEMP && (MULTITHREADING || TEMP_NRF5_FORCE_ALT) && SENSOR with value n, but is currently being y-selected by the following symbols:
 - CLOCK_CONTROL_NRF_USES_TEMP_SENSOR (defined at drivers/clock_control/Kconfig.nrf:119), with value y, direct dependencies HAS_HW_NRF_TEMP && CLOCK_CONTROL_NRF_DRIVER_CALIBRATION && CLOCK_CONTROL_NRF_K32SRC_RC_CALIBRATION && CLOCK_CONTROL_NRF && CLOCK_CONTROL (value: y), and select condition HAS_HW_NRF_TEMP && CLOCK_CONTROL_NRF_DRIVER_CALIBRATION && CLOCK_CONTROL_NRF_K32SRC_RC_CALIBRATION && CLOCK_CONTROL_NRF && CLOCK_CONTROL (value: y)

[Ubaid_M]

Hello Vidar Berg,

Vidar Berg said:

Please add the attached mcuboot.conf

Thanks for the suggest.

I was able to built and flash the board successfully.

However when I initiate DFU with the nRF connect Android app, the file transfer completes after that the mobile app disconnects and the device is no longer discoverable on the app and Board print logs as well are as below:

Please find the updated workspace as in below & kindly suggest for me to complete this sample code on BL653.

1616.peripheral_lbs_BL653.7z

Thanks,