[NCS 2.7.0] Sysbuild + MCUBOOT. Including out of tree driver with MCUBOOT sysbuild?

[SimonBursten]

I am currently migrating from ncs 2.5.0 to 2.7.0 and am trying to move to using sysbuild instead of child / parent image. I have an out of tree flash driver that currently gets built and configured as part of the mcuboot child image build.

So far, organising the configs and overlays for mcuboot and my app is pretty straightforward (they are organized under sysbuild/), but when I try to enable my out of tree flash driver in sysbuild/mcuboot/boards/[board].conf it says my config symbols are undefined.

In the child / parent image set up we simple did something like this in app/CMakeLists.txt

list(append zephyr_extra_modules ${cmake_current_list_dir}/../drivers/flash/my_out_of_tree_driver/)

this doesn't seem to work. neither does adding another CMakeLists.txt file in the sysbuild/mcuboot directory. What's the best way to let the mcuboot sysbuild know about the location of my driver?

[SimonBursten]

just noticed a mistake, the CMakeLists.txt line we are using is actually:

list(append mcuboot_DTS_ROOT ${cmake_current_list_dir}/../drivers/flash/my_out_of_tree_driver/)

[Marte Myrvold]

Hi,

Can you share the full build log?

Best regards,
Marte

[SimonBursten]

I've narrowed it down. in my application devicetree.h I can see bindings were taken from my driver directory, where as for mcuboot they weren't.

for example, here is my devictree.h header before moving to sysbuild

and after

At the moment i'm setting these variable in sysbuild.cmake which seems to allow sysbuild to actually build, but the devicetree for mcuboot isnt taking it into account. How can I manipulate DTS_ROOT for the mcubuild portion of the sysbuild?