• State Not Answered
  • Replies 1 reply
  • Subscribers 67 subscribers
  • Views 30 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 337090
Options

MCU Boot Build Warnings

dcmccall

I am currently trying to add MCU boot to my application using sysbuild. I have done the following : 

Created sysbuild.conf in application root

SB_CONFIG_BOOTLOADER_MCUBOOT=y

Created sysbuild folder in application root

Created mcuboot.conf within sysbuild folder which contains the following

CONFIG_MCUBOOT_LOG_LEVEL_DBG=y
CONFIG_BOOT_UPGRADE_ONLY=y
CONFIG_MCUBOOT_DOWNGRADE_PREVENTION=y
CONFIG_DISABLE_FLASH_PATCH=y
CONFIG_REBOOT=y

I have also updated the application's prj.conf file to contain

CONFIG_BOOTLOADER_MCUBOOT=y

When building the application, I use the following command from within the application root, and compilation is successful, the images are generated, and it seems to work.

west build -b board_name_1 --sysbuild -p

But I do end up with Kconfig warnings that I need to eliminate, but have not been able to figure out how. These warnings appear while building the application and NOT mcuboot

warning: UPDATEABLE_IMAGE_NUMBER (defined at
/home/daniel/Documents/ULC2-Workspace/nrf/samples/common/mcumgr_bt_ota_dfu/Kconfig:89,
subsys/dfu/Kconfig:95) was assigned the value '1' but got the value ''. Check these unsatisfied
dependencies: (((BOARD_THINGY53_NRF5340_CPUAPP || BOARD_THINGY53_NRF5340_CPUAPP_NS) &&
SOC_SERIES_NRF53X && NCS_SAMPLE_MCUMGR_BT_OTA_DFU) || (!MCUBOOT && IMG_MANAGER)) (=n). See
http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_UPDATEABLE_IMAGE_NUMBER and/or look up
UPDATEABLE_IMAGE_NUMBER in the menuconfig/guiconfig interface. The Application Development Primer,
Setting Configuration Values, and Kconfig - Tips and Best Practices sections of the manual might be
helpful too.


warning: MCUBOOT_UPDATE_FOOTER_SIZE (defined at subsys/dfu/Kconfig:54) was assigned the value
'0x2000' but got the value ''. Check these unsatisfied dependencies: MCUBOOT_IMG_MANAGER (=n),
IMG_MANAGER (=n). See
http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_MCUBOOT_UPDATE_FOOTER_SIZE and/or look up
MCUBOOT_UPDATE_FOOTER_SIZE in the menuconfig/guiconfig interface. The Application Development
Primer, Setting Configuration Values, and Kconfig - Tips and Best Practices sections of the manual
might be helpful too.

It almost looks as though my application is including sample code from the workspace for some reason, but this has never been an issue in the past... What Kconfig values do I need to add to my application(prj.conf) and/or mcuboot(mcuboot.conf) to make these warnings go away? I have tried some combinations of the suggested dependencies, but continue to get the issue. 

Thanks!

 
Related