Skip to content

Conversation

@bjarki-andreasen
Copy link
Contributor

Add the required zephyr,code-partition which is typically included by the common app.overlay to the nrf54h20dk_nrf54h20_cpuapp board overlay.

Add the required zephyr,code-partition which is typically included
by the common app.overlay to the nrf54h20dk_nrf54h20_cpuapp board
overlay.

Signed-off-by: Bjarki Arge Andreasen <[email protected]>
@JarmouniA
Copy link
Contributor

already here

zephyr,code-partition = &boot_partition;
, Am I missing something?

@nordicjm
Copy link
Collaborator

already here

zephyr,code-partition = &boot_partition;

, Am I missing something?

A board overlay file is used instead of app.overlay

@JarmouniA
Copy link
Contributor

already here

zephyr,code-partition = &boot_partition;

, Am I missing something?

A board overlay file is used instead of app.overlay

Is that configurable somewhere? My comment was based on #2154 (comment)

@nordicjm
Copy link
Collaborator

already here

zephyr,code-partition = &boot_partition;

, Am I missing something?

A board overlay file is used instead of app.overlay

Is that configurable somewhere? My comment was based on #2154 (comment)

See details here: https://docs.zephyrproject.org/latest/build/dts/howtos.html#set-devicetree-overlays

@JarmouniA
Copy link
Contributor

already here

zephyr,code-partition = &boot_partition;

, Am I missing something?

A board overlay file is used instead of app.overlay

Is that configurable somewhere? My comment was based on #2154 (comment)

See details here: https://docs.zephyrproject.org/latest/build/dts/howtos.html#set-devicetree-overlays

Yeah I'm aware of this, my question was rather about the MCUboot side, but okey.

@nordicjm
Copy link
Collaborator

already here

zephyr,code-partition = &boot_partition;

, Am I missing something?

A board overlay file is used instead of app.overlay

Is that configurable somewhere? My comment was based on #2154 (comment)

See details here: https://docs.zephyrproject.org/latest/build/dts/howtos.html#set-devicetree-overlays

Yeah I'm aware of this, my question was rather about the MCUboot side, but okey.

It's a zephyr application, so if there is an overlay then it will be picked instead of app.overlay - note that the file here has a lot of things in it https://github.com/mcu-tools/mcuboot/blob/ce44e6b713583dda267c697bd44b1060a32fddc7/boot/zephyr/boards/nrf54h20dk_nrf54h20_cpuapp.overlay only the top part is common with app.overlay, the rest are unique for the board target

@JarmouniA
Copy link
Contributor

It's a zephyr application, so if there is an overlay then it will be picked instead of app.overlay - note that the file here has a lot of things in it https://github.com/mcu-tools/mcuboot/blob/ce44e6b713583dda267c697bd44b1060a32fddc7/boot/zephyr/boards/nrf54h20dk_nrf54h20_cpuapp.overlay only the top part is common with app.overlay, the rest are unique for the board target

I always thought, mistakingly, that app.overlay gets combined with [board].overlay, and was not aware that the search stops at the latter 😶

@nordicjm nordicjm merged commit 10a3cff into mcu-tools:main Aug 13, 2025
58 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants