mcuboot_smp_ble west build failed

RE: mcuboot_smp_ble west build failed

Dinesh Vaghela — Fri, 18 Oct 2024 04:12:37 GMT

For the Error as below

warning: MCUMGR (defined at subsys/mgmt/mcumgr/Kconfig:5) was assigned the value 'y' but got the
value 'n'. Check these unsatisfied dependencies: ZCBOR (=n).

Suggestion:

if you are using Zephyr >3.6.0 , upgrade to latest west.yml file and update the zephyr RTOS

the west.yml file should include ZCBOR Keyword between line number 20 to 50

After this above errors should resolve and build should work.

RE: mcuboot_smp_ble west build failed

snowuyl — Tue, 22 Aug 2023 03:05:53 GMT

devzone.nordicsemi.com/.../4263.mcuboot_5F00_smp_5F00_ble.zip

RE: mcuboot_smp_ble west build failed

snowuyl — Tue, 22 Aug 2023 03:04:02 GMT

Thanks for your great support! I can build successfully on 2.4.0.

RE: mcuboot_smp_ble west build failed

nordicator_prim3 — Fri, 18 Aug 2023 22:39:01 GMT

Here is a version of the .zip you sent that will compile for version 2.4.1 (and most likely 2.4.0).

devzone.nordicsemi.com/.../mcuboot_5F00_smp_5F00_ble_5F00_2_5F00_4_5F00_1.zip

If the attachment does not show up, then the only changes that needed to be made were in the prj.comf file:

CONFIG_NET_BUF=y
CONFIG_ZCBOR=y
CONFIG_CRC=y
CONFIG_MCUMGR=y
CONFIG_STREAM_FLASH=y
CONFIG_FLASH_MAP=y

# Ensure an MCUboot-compatible binary is generated.
CONFIG_BOOTLOADER_MCUBOOT=y

# Enable flash operations.
CONFIG_FLASH=y

# Required by the `taskstat` command.
CONFIG_THREAD_MONITOR=y

# Support for taskstat command
CONFIG_MCUMGR_GRP_OS_TASKSTAT=y

# Enable statistics and statistic names.
CONFIG_STATS=y
CONFIG_STATS_NAMES=y

# Enable most core commands.
CONFIG_FLASH=y
CONFIG_IMG_MANAGER=y
CONFIG_MCUMGR_GRP_IMG=y
CONFIG_MCUMGR_GRP_OS=y
CONFIG_MCUMGR_GRP_STAT=y

# Enable logging
CONFIG_LOG=y
CONFIG_MCUBOOT_UTIL_LOG_LEVEL_WRN=y
# Disable debug logging
CONFIG_LOG_MAX_LEVEL=3

CONFIG_BT=y
CONFIG_BT_PERIPHERAL=y

# Allow for large Bluetooth data packets.
CONFIG_BT_L2CAP_TX_MTU=498
CONFIG_BT_BUF_ACL_RX_SIZE=502
CONFIG_BT_BUF_ACL_TX_SIZE=502
CONFIG_BT_CTLR_DATA_LENGTH_MAX=251

# Enable the Bluetooth mcumgr transport (unauthenticated).
CONFIG_MCUMGR_TRANSPORT_BT=y
CONFIG_MCUMGR_TRANSPORT_BT_AUTHEN=n
CONFIG_MCUMGR_TRANSPORT_BT_CONN_PARAM_CONTROL=y

# Enable the Shell mcumgr transport.
CONFIG_BASE64=y
CONFIG_SHELL=y
CONFIG_SHELL_BACKEND_SERIAL=y
CONFIG_MCUMGR_TRANSPORT_SHELL=y

# Enable the mcumgr Packet Reassembly feature over Bluetooth and its configuration dependencies.
# MCUmgr buffer size is optimized to fit one SMP packet divided into five Bluetooth Write Commands,
# transmitted with the maximum possible MTU value: 498 bytes.
CONFIG_MCUMGR_TRANSPORT_BT_REASSEMBLY=y
CONFIG_MCUMGR_TRANSPORT_NETBUF_SIZE=2475
CONFIG_MCUMGR_GRP_OS_MCUMGR_PARAMS=y
CONFIG_MCUMGR_TRANSPORT_WORKQUEUE_STACK_SIZE=4608

# Enable the LittleFS file system.
CONFIG_FILE_SYSTEM=y
CONFIG_FILE_SYSTEM_LITTLEFS=y

# Enable file system commands
CONFIG_MCUMGR_GRP_FS=y

# Enable the storage erase command.
CONFIG_MCUMGR_GRP_ZBASIC=y
CONFIG_MCUMGR_GRP_ZBASIC_STORAGE_ERASE=y

# Disable Bluetooth ping support
CONFIG_BT_CTLR_LE_PING=n

# Disable shell commands that are not needed
CONFIG_CLOCK_CONTROL_NRF_SHELL=n
CONFIG_DEVICE_SHELL=n
CONFIG_DEVMEM_SHELL=n
CONFIG_FLASH_SHELL=n

I probably have some unneeded entries in there but this at least works for nrf52840dk.

RE: mcuboot_smp_ble west build failed

nordicator_prim3 — Fri, 18 Aug 2023 22:08:59 GMT

I've confirmed that the sample .zip you provided builds on v2.3.0 only, so apparently it was written for that. We just have to look at the changes shown in smp_svr example between 2.3.0 and 2.4.0.

RE: mcuboot_smp_ble west build failed

nordicator_prim3 — Fri, 18 Aug 2023 22:00:03 GMT

I'm dealing with the exact same error trying to upgrade my custom firmware from version 2.3.0 to 2.4.1 and my firmware includes the functionality of the smp_svr example that that github references. There were significant changes moving from v2.3.0 to v2.4.0. The smp_svr example that that github linked to was for v2.1.0 so the errors you're seeing are likely due to the differences between v2.1.0 and v2.4.0.

Some of these changes include needing CONFIG_ZCBOR=y. Also, the terminology of other configuration has changed e.g. it looks like

CONFIG_MCUMGR_CMD_IMG_MGMT=y

is being replaced by

CONFIG_IMG_MANAGER=y
CONFIG_MCUMGR_GRP_IMG=y

so the changes seem quite drastic.

If you want to see how different they are, then look at the smp_svr example from v2.3.0 and compare the .conf and src files to the same smp_svr example from v2.4.0. There were also less extreme changes I had to make to get smp_svr to work when moving from 2.1.0->2.2.0->2.3..0.

I just now ran into this problem, but am confident that this is why you are seeing these errors. I will update you on this thread once I migrate from v2.3.0 -> 2.4.1 to confirm/deny that these are the only problems.

(in short, the code you're trying to use was written [likely] for v2.1.0 and you're building with v2.4.0)

RE: mcuboot_smp_ble west build failed

snowuyl — Fri, 18 Aug 2023 07:57:31 GMT

devzone.nordicsemi.com/.../0777.mcuboot_5F00_smp_5F00_ble.zip