boot: zephyr: boards: nrf54h20dk cpuapp add chosen code part

[bjarki-andreasen]

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

[JarmouniA]

already here

mcuboot/boot/zephyr/app.overlay

Line 3 in 713b98b

zephyr,code-partition = &boot_partition;

, Am I missing something?

[nordicjm]

already here

mcuboot/boot/zephyr/app.overlay

Line 3 in 713b98b

zephyr,code-partition = &boot_partition;

, Am I missing something?

A board overlay file is used instead of app.overlay

[JarmouniA]

already here

mcuboot/boot/zephyr/app.overlay

Line 3 in 713b98b

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]

already here

mcuboot/boot/zephyr/app.overlay

Line 3 in 713b98b

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]

already here

mcuboot/boot/zephyr/app.overlay

Line 3 in 713b98b

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]

already here

mcuboot/boot/zephyr/app.overlay

Line 3 in 713b98b

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]

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 😶