Sysbuild support for system devicetree

[mbolivar-nordic]

Postponed

Since system devicetree support (#51830) is on hold, this issue is as well.

Parent issue

This issue is part of a larger issue: #51833

Is your enhancement proposal related to a problem?

Zephyr's sysbuild feature lets users set up and develop with multiple interrelated Zephyr- and non-Zephyr application directories. If my application directory has sysbuild integration, I can use it to build, flash, and debug all of the applications at once with command lines like this example:

$ west build --sysbuild -b board my-top-level-app-dir # builds multiple applications
$ west flash # flashes all the application images to my board

If Zephyr adopts support for system devicetree, I will need a convenient way to use it within sysbuild.

Describe the solution you'd like

Sysbuild awareness of system devicetree, especially the ability to apply system devicetree overlays at sysbuild's CMake time, to hardware (socs / boards) supported via hardware model v2 (see #51832 for details).

At a high level, I would like sysbuild to be able to manage the portions of this diagram with a white background, creating and managing the individual zephyr build systems in the shaded boxes:

I would like this enhancement to be supported in a backwards compatible way: no existing sysbuild use cases with "regular" devicetree should be broken.

Describe alternatives you've considered

Continuing to use standard devicetrees is workable, but introduces redundancy and room for error.

Change history

• 2023-05-05: split this issue apart from sysbuild support for hardware model v2

[zephyrbot]

Hi @tejlmand, @tejlmand,

This issue, marked as an Enhancement, was opened a while ago and did not get any traction. It was just assigned to you based on the labels. If you don't consider yourself the right person to address this issue, please re-assing it to the right person.

Please take a moment to review if the issue is still relevant to the project. If it is, please provide feedback and direction on how to move forward. If it is not, has already been addressed, is a duplicate, or is no longer relevant, please close it with a short comment explaining the reason.

@mbolivar-nordic you are also encouraged to help moving this issue forward by providing additional information and confirming this request/issue is still relevant to you.

Thanks!