MCUboot DIRECT_XIP

RE: MCUboot DIRECT_XIP

Sigurd Hellesvik — Thu, 18 Aug 2022 07:16:12 GMT

Hi,

Configuration options for our fork of MCUBoot can be found in https://github.com/nrfconnect/sdk-mcuboot/blob/main/boot/zephyr/Kconfig, so have a look for XIP_REVERT in there.

Regards,
Sigurd Hellesvik

RE: MCUboot DIRECT_XIP

BvdP4Celsius — Wed, 17 Aug 2022 14:09:07 GMT

Sigurd,

Is the MCUBOOT_DIRECT_XIP_REVERT supported also? I can not find much info about this here.

RE: MCUboot DIRECT_XIP

BvdP4Celsius — Wed, 17 Aug 2022 13:26:03 GMT

Thanks Sigurd, this seems to do the trick!

b.t.w., I ignored the error:

CMake Warning (dev) at ....\build_1\image_preload.cmake:8 (set):
Syntax error in cmake code at
....\build_1\image_preload.cmake:8
when parsing string
...\toolchains\v2.0.0\opt\bin\python.exe
Invalid escape sequence \U
Policy CMP0010 is not set: Bad variable reference syntax is an error. Run
"cmake --help-policy CMP0010" for policy details. Use the cmake_policy
command to set the policy and suppress this warning.
This warning is for project developers. Use -Wno-dev to suppress it.

RE: MCUboot DIRECT_XIP

Sigurd Hellesvik — Wed, 17 Aug 2022 10:26:59 GMT

[quote user="BvdP4Celsius"]I added mcuboot.conf as you suggested and added CONFIG_BOOT_BUILD_DIRECT_XIP_VARIANT=y in that file.[/quote]

CONFIG_BOOT_BUILD_DIRECT_XIP_VARIANT is to tell your buildto include extra files in the build/zephyr folder. See Using MCUboot in nRF Connect SDK:
"

When you use MCUboot in the execute-in-place (XIP) mode, enable CONFIG_BOOT_BUILD_DIRECT_XIP_VARIANT to let the build system generate an additional set of files for the second application slot. These .hex files are identical to the ones listed above, but their names also use the mcuboot_secondary_ prefix. For example, mcuboot_secondary_app_signed.hex is created and placed in the second slot on the target device when the app_signed.hex file is placed in the first slot.
"

[quote user="BvdP4Celsius"]warning: ignoring malformed line 'BOOT_DIRECT_XIP=y'[/quote]

Kconfig defines are configured in prj.conf files by adding CONFIG_ to them.

To make this work:

prj.conf: CONFIG_BOOT_BUILD_DIRECT_XIP_VARIANT=y

child_image/mcuboot.conf: CONFIG_BOOT_DIRECT_XIP=y

Regards,
Sigurd Hellesvik

RE: MCUboot DIRECT_XIP

BvdP4Celsius — Wed, 17 Aug 2022 09:32:11 GMT

Hi Sigurd,

I am afraid the answer did not solve my issue yet.

There is a folder child_image in my blinky_slot1_dfu project.

I added mcuboot.conf as you suggested and added CONFIG_BOOT_BUILD_DIRECT_XIP_VARIANT=y in that file.
This results in errors during the build process.
warning: BOOT_BUILD_DIRECT_XIP_VARIANT (defined at
...\v2.0.0\nrf\modules\mcuboot\Kconfig:26) was assigned the value 'y' but got the
value 'n'. Check these unsatisfied dependencies: BOOTLOADER_MCUBOOT (=n). See..(dead link..)
(The same warning is shown when setting this in the ./blinky_slot1_dfu /mcuboot/prj.conf file)

Then replaced the CONFIG_BOOT_BUILD_DIRECT_XIP_VARIANT=y with the BOOT_DIRECT_XIP=y defined in the link you provided. But that was not recognized (warning: ignoring malformed line 'BOOT_DIRECT_XIP=y').

Any tips how to build the application for use with dirext_xip mode?

RE: MCUboot DIRECT_XIP

Sigurd Hellesvik — Tue, 16 Aug 2022 09:06:03 GMT

Hi,

To add configuration overlays to the mcuboot child image, add them to <APP>/child_image/mcuboot.conf.

See Multi-image builds, specifically this:

The MCUBoot configurations are not listed in our Kconfig search, but you can find them at ncs/bootloader/mcuboot/zephyr/Kconfig.

Does this answer your question?

Regards,
Sigurd Hellesvik