MCUBOOT

RE: MCUBOOT

Øivind — Thu, 16 Feb 2023 13:38:05 GMT

How Kconfig configuration files, fragments, and devicetree overlays can be passed to child images:
https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/app_dev/multi_image/index.html#image-specific-variables

RE: MCUBOOT

jhc — Thu, 16 Feb 2023 07:56:51 GMT

Thank you, is there related link for this?

RE: MCUBOOT

Øivind — Wed, 15 Feb 2023 13:21:39 GMT

Add a folder to your project called "child_image", and add a conf file named mcuboot.conf to this folder.

In mcuboot.conf, you should disable all the configs for the modules.

RE: MCUBOOT

jhc — Wed, 15 Feb 2023 07:34:05 GMT

Yes, it already was, but it didn't work.

RE: MCUBOOT

Øivind — Tue, 14 Feb 2023 12:37:34 GMT

How do the CMakeLists.txt files for the extra modules look? You could add a config for each module in your project's Kconfig file, and in each module's CMakeLists.txt file, you can add an if-block around the contents:

if(CONFIG_MODULE_NAME)

    //contents

endif()

RE: MCUBOOT

jhc — Fri, 10 Feb 2023 07:28:53 GMT

Hello, Øivind

I found that an extra module is also built (as shown above) with errors during the mcuboot_subimage build step.

But in fact, this extra module should only be built in my application as I specify this extra module to be built in application CMakefiles.txt (located in my application root directory):

Would the value of ZEPHYR_EXTRA_MODULES various defined in application CMakefile.txt be also available to mcuboot sub-project?

How to handle it?

Thank you!

RE: MCUBOOT

jhc — Thu, 09 Feb 2023 07:42:57 GMT

Hello, Øivind

Are there any updates or comments?

Thanks!

RE: MCUBOOT

jhc — Wed, 08 Feb 2023 02:01:24 GMT

Have not mcuboot.conf

build log: (Sorry to directly paste the log here dues to can't insert->code in menu)

Building hprod
west build --build-dir d:\projects\work\code\hproj\hprod\build d:\projects\work\code\hproj\hprod

[0/95] Performing build step for 'mcuboot_subimage'
[1/14] Linking C static library zephyr\kernel\libkernel.a
[2/14] Building C object modules/adapters/CMakeFiles/..__..__..__hproj__hprod__libs_ncs__adapters__zephyr.dir/ble_adp.c.obj
FAILED: modules/adapters/CMakeFiles/..__..__..__hproj__hprod__libs_ncs__adapters__zephyr.dir/ble_adp.c.obj

...

ninja: build stopped: subcommand failed.
FATAL ERROR: command exited with status 1: 'd:\projects\work\code\ncs\toolchains\v2.1.0\opt\bin\cmake.EXE' --build 'd:\projects\work\code\hproj\hprod\build'

* The terminal process terminated with exit code: 1.
* Terminal will be reused by tasks, press any key to close it.

RE: MCUBOOT

Øivind — Tue, 07 Feb 2023 15:34:56 GMT

Thank you, could I also see the full build log? And the mcuboot.conf file if you have one.

RE: MCUBOOT

jhc — Tue, 07 Feb 2023 02:02:51 GMT

NCS version: v2.1.0

pri.conf content:

CONFIG_BT=y
CONFIG_BT_CENTRAL=y
CONFIG_BT_PERIPHERAL=y

CONFIG_BT_SMP=y
CONFIG_BT_BONDING_REQUIRED=y
CONFIG_BT_SMP_SC_PAIR_ONLY=y
CONFIG_BT_SMP_APP_PAIRING_ACCEPT=y
CONFIG_BT_PRIVACY=n
CONFIG_BT_SMP_ALLOW_UNAUTH_OVERWRITE=y
CONFIG_BT_KEYS_OVERWRITE_OLDEST=y

CONFIG_BT_MAX_PAIRED=20
CONFIG_BT_MAX_CONN=20
CONFIG_BT_USER_PHY_UPDATE=y
CONFIG_BT_AUTO_PHY_UPDATE=n

CONFIG_BT_GATT_DM=y
CONFIG_BT_GATT_CLIENT=y

CONFIG_BT_DEVICE_NAME="SA-"
CONFIG_BT_DEVICE_NAME_DYNAMIC=y

CONFIG_BT_SETTINGS=y

CONFIG_BT_DIS=y
CONFIG_BT_DIS_SETTINGS=y
CONFIG_BT_DIS_MODEL="unkown model"
CONFIG_BT_DIS_MANUF="nukown manuf"
CONFIG_BT_DIS_SERIAL_NUMBER=y
CONFIG_BT_DIS_SERIAL_NUMBER_STR="0"
CONFIG_BT_DIS_SW_REV=y
CONFIG_BT_DIS_SW_REV_STR="0.1"
CONFIG_BT_DIS_FW_REV=y
CONFIG_BT_DIS_FW_REV_STR="1.0"
CONFIG_BT_DIS_HW_REV=y
CONFIG_BT_DIS_HW_REV_STR="1.0"

CONFIG_BT_BAS=y
CONFIG_BT_BAS_CLIENT=y
CONFIG_BT_GATTP=y
CONFIG_BT_ANCS_CLIENT=y
CONFIG_BT_NUS=y
CONFIG_BT_NUS_CLIENT=y

CONFIG_LOG=y
CONFIG_LOG_BACKEND_RTT=y
CONFIG_LOG_BACKEND_UART=n
CONFIG_BT_LOG_LEVEL_ERR=y
CONFIG_DEBUG_THREAD_INFO=y
CONFIG_DEBUG_OPTIMIZATIONS=y
CONFIG_LOG_BUFFER_SIZE=4096

CONFIG_LOG_PRINTK=y
CONFIG_UART_RTT=y
CONFIG_RTT_CONSOLE=y
CONFIG_CONSOLE=y
CONFIG_USE_SEGGER_RTT=y


CONFIG_HEAP_MEM_POOL_SIZE=10240
CONFIG_MAIN_STACK_SIZE=4096

CONFIG_FLASH=y
CONFIG_FLASH_PAGE_LAYOUT=y
CONFIG_FLASH_MAP=y
CONFIG_NVS=y
CONFIG_SETTINGS=y
CONFIG_SETTINGS_RUNTIME=y
CONFIG_NVS_LOG_LEVEL_WRN=y

CONFIG_PINCTRL=y
CONFIG_GPIO=y
CONFIG_PWM=y

CONFIG_MINIMAL_LIBC_RAND=y
CONFIG_SYSTEM_WORKQUEUE_STACK_SIZE=6144


CONFIG_CLOCK_CONTROL_NRF_K32SRC_XTAL=y
CONFIG_CLOCK_CONTROL_NRF_K32SRC_500PPM=y

CONFIG_NFCT_PINS_AS_GPIOS=y
CONFIG_PM_DEVICE=y

CONFIG_BT_FILTER_ACCEPT_LIST=y
CONFIG_BT_L2CAP_TX_BUF_COUNT=10


CONFIG_BT_CTLR_ADVANCED_FEATURES=y
CONFIG_BT_CTLR_CONN_RSSI=y
CONFIG_BT_CTLR_TX_PWR_DYNAMIC_CONTROL=y

CONFIG_TX_PWR=6
CONFIG_ADV_INTERVAL_MIN=990
CONFIG_ADV_INTERVAL_MAX=1010
CONFIG_CONN_INTERVAL_MIN=550
CONFIG_CONN_INTERVAL_MAX=650
CONFIG_CONN_TIMEOUT=15000
CONFIG_SCAN_INTERVAL=100
CONFIG_SCAN_WINDOW=15

CONFIG_BT_CTLR_PHY_CODED=y
CONFIG_BT_EXT_ADV=y
CONFIG_BT_CREATE_CONN_TIMEOUT=5
CONFIG_CLI_MOD=y
CONFIG_SPIIC=y
CONFIG_UART_ADP=y
CONFIG_NRFX_UARTE0=y
CONFIG_SERIAL=y
CONFIG_UART_INTERRUPT_DRIVEN=y



# Add to supporting MCUBOOT (begin)

# Enable mcumgr.
CONFIG_MCUMGR=y

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

CONFIG_MCUMGR_SMP_BT=y
CONFIG_MCUMGR_SMP_BT_AUTHEN=n

# Add to supporting MCUBOOT (end)

It could be compiled without errors if # Add to supporting MCUBOOT part is deleted.

RE: MCUBOOT

Øivind — Mon, 06 Feb 2023 14:36:50 GMT

Hi,

Which version of the nRF Connect SDK are you using?

Could I see the full prj.conf file?