<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Custom board with Static partitions, MCUboot and Sysbuild</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/119127/custom-board-with-static-partitions-mcuboot-and-sysbuild</link><description>Hello! 
 I am using an nRF Connect SDK V2.9.0 with a nrf54l15. I want to set up a project with a custom board. I want to add DFU in the future, so there must be MCUboot bootloader and static partitions defined. 
 I took the zephyr/samples/sysbuild/with_mcuboot</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 27 Feb 2025 09:20:31 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/119127/custom-board-with-static-partitions-mcuboot-and-sysbuild" /><item><title>RE: Custom board with Static partitions, MCUboot and Sysbuild</title><link>https://devzone.nordicsemi.com/thread/525002?ContentTypeID=1</link><pubDate>Thu, 27 Feb 2025 09:20:31 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:fb33d5c6-b075-4706-a724-cbcece8351c3</guid><dc:creator>AHaug</dc:creator><description>&lt;p&gt;Hi,&lt;br /&gt;&lt;br /&gt;Thats a good find! FYI in case you would ever need to add an external flash, you will have to increase it to 512. The reason is because the image sector size varies depending on where your secondary mcuboot partition resides. If it is present on the internal flash you will have IMG_SECTOR_SIZE = 256, whereas if you have the secondary partition on the external flash&amp;nbsp;&lt;span&gt;IMG_SECTOR_SIZE&amp;nbsp; will be&lt;/span&gt;&amp;nbsp;512 since the primary application is now 2x the size of the case when you had the secondary partition on the internal flash.&lt;/p&gt;
&lt;p&gt;I&amp;#39;ll mark the case as verified for now, and please feel free to open new cases for new questions&lt;/p&gt;
&lt;p&gt;Kind regards,&lt;br /&gt;Andreas&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Custom board with Static partitions, MCUboot and Sysbuild</title><link>https://devzone.nordicsemi.com/thread/524767?ContentTypeID=1</link><pubDate>Wed, 26 Feb 2025 09:24:51 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ce98f9b0-7f67-44f7-ac84-c05edc63bd20</guid><dc:creator>DmytroSes</dc:creator><description>&lt;p&gt;It looks like I was able to resolve the issue. The problem was with the &lt;code&gt;CONFIG_BOOT_MAX_IMG_SECTORS&lt;/code&gt;. For my custom board, the value of this property was 128. And for the devkit the value was 256 - it is defined in the &lt;code&gt;&amp;lt;sdk_root&amp;gt;/bootloader/mcuboot/boot/zephyr/boards/nrf54l15dk_nrf54l15_cpuapp.conf&lt;/code&gt; file - that&amp;#39;s why I was not able to find it, I was only looking in the nrf54l15dk board definition folder.&lt;br /&gt;I have changed the value to 256 and now my application boots.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Custom board with Static partitions, MCUboot and Sysbuild</title><link>https://devzone.nordicsemi.com/thread/524744?ContentTypeID=1</link><pubDate>Wed, 26 Feb 2025 08:25:06 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6e2e86d0-8b08-457a-907b-ea39f64dc768</guid><dc:creator>DmytroSes</dc:creator><description>&lt;p&gt;&lt;img style="height:auto;max-width:320px;" alt=" " src="https://devzone.nordicsemi.com/resized-image/__size/640x0/__key/communityserver-discussions-components-files/4/boot_5F00_issue.png" /&gt;&lt;/p&gt;
&lt;p&gt;Here on the screenshot you can see, that there is a valid magic number at &lt;code&gt;0xc000&lt;/code&gt;, but the bootloader did not parse it. When I run the bootloader compiled for the devkit target, I get some valid numbers in the &lt;code&gt;state.imgs[0][0].hdr&lt;/code&gt; structure at this step.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Custom board with Static partitions, MCUboot and Sysbuild</title><link>https://devzone.nordicsemi.com/thread/524735?ContentTypeID=1</link><pubDate>Wed, 26 Feb 2025 07:58:35 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:cd6f98e3-0a66-4398-b16f-9c18151a39cc</guid><dc:creator>DmytroSes</dc:creator><description>&lt;p&gt;So with some more investigation I have found, that the bootloader cannot properly read image headers. In both cases it reads from the &lt;code&gt;0xc000&lt;/code&gt; address and in both cases I can see the image magic number through a debugger memory view at this address. However, on my custom board the image headers structure in bootloader is for some reason empty (all the values are 0), like there is something, that prevents the bootloader reading from that area of memory. And because of that the bootloader fails to find the image.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Custom board with Static partitions, MCUboot and Sysbuild</title><link>https://devzone.nordicsemi.com/thread/524667?ContentTypeID=1</link><pubDate>Tue, 25 Feb 2025 16:05:35 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:63d1d662-a08d-4634-bb2e-cd7ec9384e20</guid><dc:creator>DmytroSes</dc:creator><description>&lt;p&gt;I have managed to solve the problem with logs. Here is what the bootloader prints for my board:&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt;*** Booting MCUboot v2.1.0-dev-12e5ee106034 ***
*** Using nRF Connect SDK v2.9.0-7787b2649840 ***
*** Using Zephyr OS v3.7.99-1f8f3dc29142 ***
I: Starting bootloader
W: Failed reading sectors; BOOT_MAX_IMG_SECTORS=128 - too small?
E: Image in the primary slot is not valid!
E: Unable to find bootable image&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;And here what it prints for the DK:&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt;I: Starting bootloader
D: Non-optimal sector distribution, slot0 has 167 usable sectors (172 assigned) but slot1 has 172 assigned
I: Primary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
I: Secondary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
I: Boot source: none
I: Image index: 0, Swap type: none
I: Bootloader chainload address offset: 0xc000
*** Booting nRF Connect SDK v2.9.0-7787b2649840 ***
*** Using Zephyr OS v3.7.99-1f8f3dc29142 ***
Partition manager is used
Address of sample 0xc800
Hello sysbuild with mcuboot! nrf54l15dk
&lt;/pre&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Custom board with Static partitions, MCUboot and Sysbuild</title><link>https://devzone.nordicsemi.com/thread/524638?ContentTypeID=1</link><pubDate>Tue, 25 Feb 2025 14:22:37 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e9d01544-cdd1-491a-b91b-10e146f031de</guid><dc:creator>DmytroSes</dc:creator><description>&lt;p&gt;Thanks for the link to partitioning explanation! I was searching for this.&lt;/p&gt;
[quote userid="107683" url="~/f/nordic-q-a/119127/custom-board-with-static-partitions-mcuboot-and-sysbuild/524542"]Have you made sure to reduce and increase any relevant gaps that occurs with the reduction of the bootloader partition?[/quote]
&lt;p&gt;The only thing I changed was the&amp;nbsp;&lt;code&gt;boot_partition&lt;/code&gt; size in the board dts file (which is, I think, is unnecessary). The &lt;code&gt;pm_static.yml&lt;/code&gt; file has all the partitions taken from the &lt;code&gt;partitions.yml&lt;/code&gt;, as described in one of the Nordic lessons. I have done no changes to the &lt;code&gt;pm_static.yml&lt;/code&gt;.&lt;br /&gt;I have also run Memory report tool for both targets (my custom board and the DK) and the partitions are completely identical there.&lt;/p&gt;
&lt;p&gt;The device sends no logs, while in Mcuboot, the logs are not even compiled (which is strange for me, because there are logs for the DK target).&lt;/p&gt;
&lt;p&gt;Here are the build logs for my custom board target:&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt; *  Executing task: nRF Connect: Build [pristine]: zephyr_sysbuild_issue/build (active) 

Building zephyr_sysbuild_issue
west build --build-dir /home/dima/Projects/giot/workspace/zephyr_sysbuild_issue/build /home/dima/Projects/giot/workspace/zephyr_sysbuild_issue --pristine --board my_board/nrf54l15/cpuapp --sysbuild -- -DNCS_TOOLCHAIN_VERSION=NONE -DCONFIG_DEBUG_OPTIMIZATIONS=y -DCONFIG_DEBUG_THREAD_INFO=y -DBOARD_ROOT=/home/dima/Projects/giot/workspace/zephyr_sysbuild_issue

-- west build: generating a build system
Loading Zephyr module(s) (Zephyr base): sysbuild_default
-- Found Python3: /home/dima/ncs/toolchains/b77d8c1312/usr/local/bin/python3.12 (found suitable version &amp;quot;3.12.4&amp;quot;, minimum required is &amp;quot;3.8&amp;quot;) found components: Interpreter 
-- Cache files will be written to: /home/dima/.cache/zephyr
-- Found west (found suitable version &amp;quot;1.2.0&amp;quot;, minimum required is &amp;quot;0.14.0&amp;quot;)
-- Board: my_board, qualifiers: nrf54l15/cpuapp
Parsing /home/dima/ncs/v2.9.0/zephyr/share/sysbuild/Kconfig
Loaded configuration &amp;#39;/home/dima/Projects/giot/workspace/zephyr_sysbuild_issue/build/_sysbuild/empty.conf&amp;#39;
Merged configuration &amp;#39;/home/dima/Projects/giot/workspace/zephyr_sysbuild_issue/sysbuild.conf&amp;#39;
Configuration saved to &amp;#39;/home/dima/Projects/giot/workspace/zephyr_sysbuild_issue/build/zephyr/.config&amp;#39;
Kconfig header saved to &amp;#39;/home/dima/Projects/giot/workspace/zephyr_sysbuild_issue/build/_sysbuild/autoconf.h&amp;#39;
-- 
   *****************************
   * Running CMake for mcuboot *
   *****************************

Loading Zephyr default modules (Zephyr base).
-- Application: /home/dima/ncs/v2.9.0/bootloader/mcuboot/boot/zephyr
-- CMake version: 3.21.0
-- Found Python3: /home/dima/ncs/toolchains/b77d8c1312/usr/local/bin/python (found suitable version &amp;quot;3.12.4&amp;quot;, minimum required is &amp;quot;3.8&amp;quot;) found components: Interpreter 
-- Cache files will be written to: /home/dima/.cache/zephyr
-- Zephyr version: 3.7.99 (/home/dima/ncs/v2.9.0/zephyr)
-- Found west (found suitable version &amp;quot;1.2.0&amp;quot;, minimum required is &amp;quot;0.14.0&amp;quot;)
-- Board: my_board, qualifiers: nrf54l15/cpuapp
-- Found host-tools: zephyr 0.17.0 (/home/dima/ncs/toolchains/b77d8c1312/opt/zephyr-sdk)
-- Found toolchain: zephyr 0.17.0 (/home/dima/ncs/toolchains/b77d8c1312/opt/zephyr-sdk)
-- Found Dtc: /home/dima/ncs/toolchains/b77d8c1312/usr/bin/dtc (found suitable version &amp;quot;1.5.0&amp;quot;, minimum required is &amp;quot;1.4.6&amp;quot;) 
-- Found BOARD.dts: /home/dima/Projects/giot/workspace/zephyr_sysbuild_issue/boards/my_company/my_board/my_board_nrf54l15_cpuapp.dts
-- Found devicetree overlay: /home/dima/ncs/v2.9.0/bootloader/mcuboot/boot/zephyr/app.overlay
unit address and first address in &amp;#39;reg&amp;#39; (0x5004c000) don&amp;#39;t match for /soc/peripheral@50000000/vpr@4c000/mailbox@1
-- Generated zephyr.dts: /home/dima/Projects/giot/workspace/zephyr_sysbuild_issue/build/mcuboot/zephyr/zephyr.dts
-- Generated devicetree_generated.h: /home/dima/Projects/giot/workspace/zephyr_sysbuild_issue/build/mcuboot/zephyr/include/generated/zephyr/devicetree_generated.h
-- Including generated dts.cmake file: /home/dima/Projects/giot/workspace/zephyr_sysbuild_issue/build/mcuboot/zephyr/dts.cmake

warning: NRF_RTC_TIMER_USER_CHAN_COUNT (defined at soc/nordic/nrf53/Kconfig.sync_rtc:23,
drivers/timer/Kconfig.nrf_rtc:20) was assigned the value &amp;#39;0&amp;#39; but got the value &amp;#39;&amp;#39;. Check these
unsatisfied dependencies: ((NRF53_SYNC_RTC &amp;amp;&amp;amp; SOC_SERIES_NRF53X &amp;amp;&amp;amp; SOC_FAMILY_NORDIC_NRF) ||
(NRF_RTC_TIMER &amp;amp;&amp;amp; SYS_CLOCK_EXISTS)) (=n). See
http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_NRF_RTC_TIMER_USER_CHAN_COUNT and/or look
up NRF_RTC_TIMER_USER_CHAN_COUNT in the menuconfig/guiconfig interface. The Application Development
Primer, Setting Configuration Values, and Kconfig - Tips and Best Practices sections of the manual
might be helpful too.


warning: LOG_BACKEND_UART (defined at subsys/logging/backends/Kconfig.uart:4) was assigned the value
&amp;#39;y&amp;#39; but got the value &amp;#39;n&amp;#39;. Check these unsatisfied dependencies: UART_CONSOLE (=n),
(!LOG_MODE_MINIMAL) (=n). See
http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_LOG_BACKEND_UART and/or look up
LOG_BACKEND_UART in the menuconfig/guiconfig interface. The Application Development Primer, Setting
Configuration Values, and Kconfig - Tips and Best Practices sections of the manual might be helpful
too.

Parsing /home/dima/ncs/v2.9.0/bootloader/mcuboot/boot/zephyr/Kconfig
Loaded configuration &amp;#39;/home/dima/Projects/giot/workspace/zephyr_sysbuild_issue/boards/my_company/my_board/my_board_nrf54l15_cpuapp_defconfig&amp;#39;
Merged configuration &amp;#39;/home/dima/ncs/v2.9.0/bootloader/mcuboot/boot/zephyr/prj.conf&amp;#39;
Merged configuration &amp;#39;/home/dima/Projects/giot/workspace/zephyr_sysbuild_issue/sysbuild/mcuboot.conf&amp;#39;
Merged configuration &amp;#39;/home/dima/Projects/giot/workspace/zephyr_sysbuild_issue/build/mcuboot/zephyr/.config.sysbuild&amp;#39;
Configuration saved to &amp;#39;/home/dima/Projects/giot/workspace/zephyr_sysbuild_issue/build/mcuboot/zephyr/.config&amp;#39;
Kconfig header saved to &amp;#39;/home/dima/Projects/giot/workspace/zephyr_sysbuild_issue/build/mcuboot/zephyr/include/generated/zephyr/autoconf.h&amp;#39;
-- Found GnuLd: /home/dima/ncs/toolchains/b77d8c1312/opt/zephyr-sdk/arm-zephyr-eabi/arm-zephyr-eabi/bin/ld.bfd (found version &amp;quot;2.38&amp;quot;) 
-- The C compiler identification is GNU 12.2.0
-- The CXX compiler identification is GNU 12.2.0
-- The ASM compiler identification is GNU
-- Found assembler: /home/dima/ncs/toolchains/b77d8c1312/opt/zephyr-sdk/arm-zephyr-eabi/bin/arm-zephyr-eabi-gcc
-- Setting build type to &amp;#39;MinSizeRel&amp;#39; as none was specified.
-- Using ccache: /home/dima/ncs/toolchains/b77d8c1312/usr/bin/ccache
-- Configuring done
CMake Warning at /home/dima/ncs/v2.9.0/zephyr/CMakeLists.txt:952 (message):
  No SOURCES given to Zephyr library: drivers__clock_control

  Excluding target from build.


MCUBoot bootloader key file: /home/dima/ncs/v2.9.0/bootloader/mcuboot/root-rsa-2048.pem
-- Generating done
-- Build files have been written to: /home/dima/Projects/giot/workspace/zephyr_sysbuild_issue/build/mcuboot
-- 
   *******************************************
   * Running CMake for zephyr_sysbuild_issue *
   *******************************************

Loading Zephyr default modules (Zephyr base).
-- Application: /home/dima/Projects/giot/workspace/zephyr_sysbuild_issue
-- CMake version: 3.21.0
-- Found Python3: /home/dima/ncs/toolchains/b77d8c1312/usr/local/bin/python (found suitable version &amp;quot;3.12.4&amp;quot;, minimum required is &amp;quot;3.8&amp;quot;) found components: Interpreter 
-- Cache files will be written to: /home/dima/.cache/zephyr
-- Zephyr version: 3.7.99 (/home/dima/ncs/v2.9.0/zephyr)
-- Found west (found suitable version &amp;quot;1.2.0&amp;quot;, minimum required is &amp;quot;0.14.0&amp;quot;)
-- Board: my_board, qualifiers: nrf54l15/cpuapp
-- Found host-tools: zephyr 0.17.0 (/home/dima/ncs/toolchains/b77d8c1312/opt/zephyr-sdk)
-- Found toolchain: zephyr 0.17.0 (/home/dima/ncs/toolchains/b77d8c1312/opt/zephyr-sdk)
-- Found Dtc: /home/dima/ncs/toolchains/b77d8c1312/usr/bin/dtc (found suitable version &amp;quot;1.5.0&amp;quot;, minimum required is &amp;quot;1.4.6&amp;quot;) 
-- Found BOARD.dts: /home/dima/Projects/giot/workspace/zephyr_sysbuild_issue/boards/my_company/my_board/my_board_nrf54l15_cpuapp.dts
unit address and first address in &amp;#39;reg&amp;#39; (0x5004c000) don&amp;#39;t match for /soc/peripheral@50000000/vpr@4c000/mailbox@1
-- Generated zephyr.dts: /home/dima/Projects/giot/workspace/zephyr_sysbuild_issue/build/zephyr_sysbuild_issue/zephyr/zephyr.dts
-- Generated devicetree_generated.h: /home/dima/Projects/giot/workspace/zephyr_sysbuild_issue/build/zephyr_sysbuild_issue/zephyr/include/generated/zephyr/devicetree_generated.h
-- Including generated dts.cmake file: /home/dima/Projects/giot/workspace/zephyr_sysbuild_issue/build/zephyr_sysbuild_issue/zephyr/dts.cmake

warning: UPDATEABLE_IMAGE_NUMBER (defined at
/home/dima/ncs/v2.9.0/nrf/samples/common/mcumgr_bt_ota_dfu/Kconfig:89, subsys/dfu/Kconfig:95) was
assigned the value &amp;#39;1&amp;#39; but got the value &amp;#39;&amp;#39;. Check these unsatisfied dependencies:
(((BOARD_THINGY53_NRF5340_CPUAPP || BOARD_THINGY53_NRF5340_CPUAPP_NS) &amp;amp;&amp;amp; SOC_SERIES_NRF53X &amp;amp;&amp;amp;
NCS_SAMPLE_MCUMGR_BT_OTA_DFU) || (!MCUBOOT &amp;amp;&amp;amp; IMG_MANAGER)) (=n). See
http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_UPDATEABLE_IMAGE_NUMBER and/or look up
UPDATEABLE_IMAGE_NUMBER in the menuconfig/guiconfig interface. The Application Development Primer,
Setting Configuration Values, and Kconfig - Tips and Best Practices sections of the manual might be
helpful too.


warning: MCUBOOT_UPDATE_FOOTER_SIZE (defined at subsys/dfu/Kconfig:54) was assigned the value
&amp;#39;0x3000&amp;#39; but got the value &amp;#39;&amp;#39;. Check these unsatisfied dependencies: MCUBOOT_IMG_MANAGER (=n),
IMG_MANAGER (=n). See
http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_MCUBOOT_UPDATE_FOOTER_SIZE and/or look up
MCUBOOT_UPDATE_FOOTER_SIZE in the menuconfig/guiconfig interface. The Application Development
Primer, Setting Configuration Values, and Kconfig - Tips and Best Practices sections of the manual
might be helpful too.

Parsing /home/dima/ncs/v2.9.0/zephyr/Kconfig
Loaded configuration &amp;#39;/home/dima/Projects/giot/workspace/zephyr_sysbuild_issue/boards/my_company/my_board/my_board_nrf54l15_cpuapp_defconfig&amp;#39;
Merged configuration &amp;#39;/home/dima/Projects/giot/workspace/zephyr_sysbuild_issue/prj.conf&amp;#39;
Merged configuration &amp;#39;/home/dima/Projects/giot/workspace/zephyr_sysbuild_issue/build/zephyr_sysbuild_issue/zephyr/misc/generated/extra_kconfig_options.conf&amp;#39;
Merged configuration &amp;#39;/home/dima/Projects/giot/workspace/zephyr_sysbuild_issue/build/zephyr_sysbuild_issue/zephyr/.config.sysbuild&amp;#39;
Configuration saved to &amp;#39;/home/dima/Projects/giot/workspace/zephyr_sysbuild_issue/build/zephyr_sysbuild_issue/zephyr/.config&amp;#39;
Kconfig header saved to &amp;#39;/home/dima/Projects/giot/workspace/zephyr_sysbuild_issue/build/zephyr_sysbuild_issue/zephyr/include/generated/zephyr/autoconf.h&amp;#39;
-- Found GnuLd: /home/dima/ncs/toolchains/b77d8c1312/opt/zephyr-sdk/arm-zephyr-eabi/arm-zephyr-eabi/bin/ld.bfd (found version &amp;quot;2.38&amp;quot;) 
-- The C compiler identification is GNU 12.2.0
-- The CXX compiler identification is GNU 12.2.0
-- The ASM compiler identification is GNU
-- Found assembler: /home/dima/ncs/toolchains/b77d8c1312/opt/zephyr-sdk/arm-zephyr-eabi/bin/arm-zephyr-eabi-gcc
-- Setting build type to &amp;#39;MinSizeRel&amp;#39; as none was specified.
-- Using ccache: /home/dima/ncs/toolchains/b77d8c1312/usr/bin/ccache
CMake Warning at /home/dima/ncs/v2.9.0/zephyr/CMakeLists.txt:952 (message):
  No SOURCES given to Zephyr library: drivers__clock_control

  Excluding target from build.


-- Including signing script: /home/dima/ncs/v2.9.0/nrf/cmake/sysbuild/image_signing.cmake
CMake Warning at /home/dima/ncs/v2.9.0/zephyr/CMakeLists.txt:2164 (message):
  

        The CMake build type was set to &amp;#39;MinSizeRel&amp;#39;, but the optimization flag was set to &amp;#39;-Og&amp;#39;.
        This may be intentional and the warning can be turned off by setting the CMake variable &amp;#39;NO_BUILD_TYPE_WARNING&amp;#39;


-- Configuring done
-- Generating done
-- Build files have been written to: /home/dima/Projects/giot/workspace/zephyr_sysbuild_issue/build/zephyr_sysbuild_issue
-- Found partition manager static configuration : /home/dima/Projects/giot/workspace/zephyr_sysbuild_issue/pm_static.yml
Partition &amp;#39;mcuboot&amp;#39; is not included in the dynamic resolving since it is statically defined.
Partition &amp;#39;mcuboot_pad&amp;#39; is not included in the dynamic resolving since it is statically defined.
Partition &amp;#39;mcuboot_primary&amp;#39; is not included in the dynamic resolving since it is statically defined.
Partition &amp;#39;mcuboot_primary_app&amp;#39; is not included in the dynamic resolving since it is statically defined.
Partition &amp;#39;mcuboot_secondary&amp;#39; is not included in the dynamic resolving since it is statically defined.
-- Configuring done
-- Generating done
-- Build files have been written to: /home/dima/Projects/giot/workspace/zephyr_sysbuild_issue/build
-- west build: building application
[0/1] Re-running CMake...
Loading Zephyr default modules (Zephyr base (cached)).
-- Application: /home/dima/Projects/giot/workspace/zephyr_sysbuild_issue
-- CMake version: 3.21.0
-- Cache files will be written to: /home/dima/.cache/zephyr
-- Zephyr version: 3.7.99 (/home/dima/ncs/v2.9.0/zephyr)
-- Found west (found suitable version &amp;quot;1.2.0&amp;quot;, minimum required is &amp;quot;0.14.0&amp;quot;)
-- Board: my_board, qualifiers: nrf54l15/cpuapp
-- Found host-tools: zephyr 0.17.0 (/home/dima/ncs/toolchains/b77d8c1312/opt/zephyr-sdk)
-- Found toolchain: zephyr 0.17.0 (/home/dima/ncs/toolchains/b77d8c1312/opt/zephyr-sdk)
-- Found BOARD.dts: /home/dima/Projects/giot/workspace/zephyr_sysbuild_issue/boards/my_company/my_board/my_board_nrf54l15_cpuapp.dts
unit address and first address in &amp;#39;reg&amp;#39; (0x5004c000) don&amp;#39;t match for /soc/peripheral@50000000/vpr@4c000/mailbox@1
-- Generated zephyr.dts: /home/dima/Projects/giot/workspace/zephyr_sysbuild_issue/build/zephyr_sysbuild_issue/zephyr/zephyr.dts
-- Generated devicetree_generated.h: /home/dima/Projects/giot/workspace/zephyr_sysbuild_issue/build/zephyr_sysbuild_issue/zephyr/include/generated/zephyr/devicetree_generated.h
-- Including generated dts.cmake file: /home/dima/Projects/giot/workspace/zephyr_sysbuild_issue/build/zephyr_sysbuild_issue/zephyr/dts.cmake
Parsing /home/dima/ncs/v2.9.0/zephyr/Kconfig
Loaded configuration &amp;#39;/home/dima/Projects/giot/workspace/zephyr_sysbuild_issue/build/zephyr_sysbuild_issue/zephyr/.config&amp;#39;
Merged configuration &amp;#39;/home/dima/Projects/giot/workspace/zephyr_sysbuild_issue/build/zephyr_sysbuild_issue/zephyr/.config.sysbuild&amp;#39;
No change to configuration in &amp;#39;/home/dima/Projects/giot/workspace/zephyr_sysbuild_issue/build/zephyr_sysbuild_issue/zephyr/.config&amp;#39;
No change to Kconfig header in &amp;#39;/home/dima/Projects/giot/workspace/zephyr_sysbuild_issue/build/zephyr_sysbuild_issue/zephyr/include/generated/zephyr/autoconf.h&amp;#39;
-- Using ccache: /home/dima/ncs/toolchains/b77d8c1312/usr/bin/ccache
CMake Warning at /home/dima/ncs/v2.9.0/zephyr/CMakeLists.txt:952 (message):
  No SOURCES given to Zephyr library: drivers__clock_control

  Excluding target from build.


-- Including signing script: /home/dima/ncs/v2.9.0/nrf/cmake/sysbuild/image_signing.cmake
CMake Warning at /home/dima/ncs/v2.9.0/zephyr/CMakeLists.txt:2164 (message):
  

        The CMake build type was set to &amp;#39;MinSizeRel&amp;#39;, but the optimization flag was set to &amp;#39;-Og&amp;#39;.
        This may be intentional and the warning can be turned off by setting the CMake variable &amp;#39;NO_BUILD_TYPE_WARNING&amp;#39;


-- Configuring done
-- Generating done
-- Build files have been written to: /home/dima/Projects/giot/workspace/zephyr_sysbuild_issue/build/zephyr_sysbuild_issue
[1/129] Preparing syscall dependency handling

[5/129] Generating include/generated/zephyr/version.h
-- Zephyr version: 3.7.99 (/home/dima/ncs/v2.9.0/zephyr), build: v3.7.99-ncs2
[129/129] Linking C executable zephyr/zephyr.elf
Memory region         Used Size  Region Size  %age Used
           FLASH:       15540 B       686 KB      2.21%
             RAM:        4176 B       188 KB      2.17%
        IDT_LIST:          0 GB        32 KB      0.00%
Generating files from /home/dima/Projects/giot/workspace/zephyr_sysbuild_issue/build/zephyr_sysbuild_issue/zephyr/zephyr.elf for board: my_board
image.py: sign the payload
image.py: sign the payload
[3/270] Preparing syscall dependency handling

[7/270] Generating include/generated/zephyr/version.h
-- Zephyr version: 3.7.99 (/home/dima/ncs/v2.9.0/zephyr), build: v3.7.99-ncs2
[270/270] Linking C executable zephyr/zephyr.elf
Memory region         Used Size  Region Size  %age Used
           FLASH:       27042 B        48 KB     55.02%
             RAM:       22192 B       188 KB     11.53%
        IDT_LIST:          0 GB        32 KB      0.00%
Generating files from /home/dima/Projects/giot/workspace/zephyr_sysbuild_issue/build/mcuboot/zephyr/zephyr.elf for board: my_board
[20/20] Generating ../merged.hex
 *  Terminal will be reused by tasks, press any key to close it. &lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;And here are the build logs for the DK target:&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt; *  Executing task: nRF Connect: Build [pristine]: zephyr_sysbuild_issue/build_devkit (active) 

Building zephyr_sysbuild_issue
west build --build-dir /home/dima/Projects/giot/workspace/zephyr_sysbuild_issue/build_devkit /home/dima/Projects/giot/workspace/zephyr_sysbuild_issue --pristine --board nrf54l15dk/nrf54l15/cpuapp -- -DNCS_TOOLCHAIN_VERSION=NONE -DCONFIG_DEBUG_OPTIMIZATIONS=y -DCONFIG_DEBUG_THREAD_INFO=y -DBOARD_ROOT=/home/dima/Projects/giot/workspace/zephyr_sysbuild_issue

-- west build: generating a build system
Loading Zephyr module(s) (Zephyr base): sysbuild_default
-- Found Python3: /home/dima/ncs/toolchains/b77d8c1312/usr/local/bin/python3.12 (found suitable version &amp;quot;3.12.4&amp;quot;, minimum required is &amp;quot;3.8&amp;quot;) found components: Interpreter 
-- Cache files will be written to: /home/dima/.cache/zephyr
-- Found west (found suitable version &amp;quot;1.2.0&amp;quot;, minimum required is &amp;quot;0.14.0&amp;quot;)
-- Board: nrf54l15dk, qualifiers: nrf54l15/cpuapp
Parsing /home/dima/ncs/v2.9.0/zephyr/share/sysbuild/Kconfig
Loaded configuration &amp;#39;/home/dima/Projects/giot/workspace/zephyr_sysbuild_issue/build_devkit/_sysbuild/empty.conf&amp;#39;
Merged configuration &amp;#39;/home/dima/Projects/giot/workspace/zephyr_sysbuild_issue/sysbuild.conf&amp;#39;
Configuration saved to &amp;#39;/home/dima/Projects/giot/workspace/zephyr_sysbuild_issue/build_devkit/zephyr/.config&amp;#39;
Kconfig header saved to &amp;#39;/home/dima/Projects/giot/workspace/zephyr_sysbuild_issue/build_devkit/_sysbuild/autoconf.h&amp;#39;
-- 
   *****************************
   * Running CMake for mcuboot *
   *****************************

Loading Zephyr default modules (Zephyr base).
-- Application: /home/dima/ncs/v2.9.0/bootloader/mcuboot/boot/zephyr
-- CMake version: 3.21.0
-- Found Python3: /home/dima/ncs/toolchains/b77d8c1312/usr/local/bin/python (found suitable version &amp;quot;3.12.4&amp;quot;, minimum required is &amp;quot;3.8&amp;quot;) found components: Interpreter 
-- Cache files will be written to: /home/dima/.cache/zephyr
-- Zephyr version: 3.7.99 (/home/dima/ncs/v2.9.0/zephyr)
-- Found west (found suitable version &amp;quot;1.2.0&amp;quot;, minimum required is &amp;quot;0.14.0&amp;quot;)
-- Board: nrf54l15dk, qualifiers: nrf54l15/cpuapp
-- Found host-tools: zephyr 0.17.0 (/home/dima/ncs/toolchains/b77d8c1312/opt/zephyr-sdk)
-- Found toolchain: zephyr 0.17.0 (/home/dima/ncs/toolchains/b77d8c1312/opt/zephyr-sdk)
-- Found Dtc: /home/dima/ncs/toolchains/b77d8c1312/usr/bin/dtc (found suitable version &amp;quot;1.5.0&amp;quot;, minimum required is &amp;quot;1.4.6&amp;quot;) 
-- Found BOARD.dts: /home/dima/ncs/v2.9.0/zephyr/boards/nordic/nrf54l15dk/nrf54l15dk_nrf54l15_cpuapp.dts
-- Found devicetree overlay: /home/dima/ncs/v2.9.0/bootloader/mcuboot/boot/zephyr/app.overlay
unit address and first address in &amp;#39;reg&amp;#39; (0x5004c000) don&amp;#39;t match for /soc/peripheral@50000000/vpr@4c000/mailbox@1
-- Generated zephyr.dts: /home/dima/Projects/giot/workspace/zephyr_sysbuild_issue/build_devkit/mcuboot/zephyr/zephyr.dts
-- Generated devicetree_generated.h: /home/dima/Projects/giot/workspace/zephyr_sysbuild_issue/build_devkit/mcuboot/zephyr/include/generated/zephyr/devicetree_generated.h
-- Including generated dts.cmake file: /home/dima/Projects/giot/workspace/zephyr_sysbuild_issue/build_devkit/mcuboot/zephyr/dts.cmake

warning: FPROTECT_ALLOW_COMBINED_REGIONS (defined at
/home/dima/ncs/v2.9.0/nrf/lib/fprotect/Kconfig:76) was assigned the value &amp;#39;y&amp;#39; but got the value &amp;#39;n&amp;#39;.
Check these unsatisfied dependencies: FPROTECT (=n). See
http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_FPROTECT_ALLOW_COMBINED_REGIONS and/or look
up FPROTECT_ALLOW_COMBINED_REGIONS in the menuconfig/guiconfig interface. The Application
Development Primer, Setting Configuration Values, and Kconfig - Tips and Best Practices sections of
the manual might be helpful too.


warning: NRF_RTC_TIMER_USER_CHAN_COUNT (defined at soc/nordic/nrf53/Kconfig.sync_rtc:23,
drivers/timer/Kconfig.nrf_rtc:20) was assigned the value &amp;#39;0&amp;#39; but got the value &amp;#39;&amp;#39;. Check these
unsatisfied dependencies: ((NRF53_SYNC_RTC &amp;amp;&amp;amp; SOC_SERIES_NRF53X &amp;amp;&amp;amp; SOC_FAMILY_NORDIC_NRF) ||
(NRF_RTC_TIMER &amp;amp;&amp;amp; SYS_CLOCK_EXISTS)) (=n). See
http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_NRF_RTC_TIMER_USER_CHAN_COUNT and/or look
up NRF_RTC_TIMER_USER_CHAN_COUNT in the menuconfig/guiconfig interface. The Application Development
Primer, Setting Configuration Values, and Kconfig - Tips and Best Practices sections of the manual
might be helpful too.


warning: LOG_BACKEND_UART (defined at subsys/logging/backends/Kconfig.uart:4) was assigned the value
&amp;#39;y&amp;#39; but got the value &amp;#39;n&amp;#39;. Check these unsatisfied dependencies: (!LOG_MODE_MINIMAL) (=n). See
http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_LOG_BACKEND_UART and/or look up
LOG_BACKEND_UART in the menuconfig/guiconfig interface. The Application Development Primer, Setting
Configuration Values, and Kconfig - Tips and Best Practices sections of the manual might be helpful
too.

Parsing /home/dima/ncs/v2.9.0/bootloader/mcuboot/boot/zephyr/Kconfig
Loaded configuration &amp;#39;/home/dima/ncs/v2.9.0/zephyr/boards/nordic/nrf54l15dk/nrf54l15dk_nrf54l15_cpuapp_defconfig&amp;#39;
Merged configuration &amp;#39;/home/dima/ncs/v2.9.0/bootloader/mcuboot/boot/zephyr/prj.conf&amp;#39;
Merged configuration &amp;#39;/home/dima/ncs/v2.9.0/bootloader/mcuboot/boot/zephyr/boards/nrf54l15dk_nrf54l15_cpuapp.conf&amp;#39;
Merged configuration &amp;#39;/home/dima/Projects/giot/workspace/zephyr_sysbuild_issue/sysbuild/mcuboot.conf&amp;#39;
Merged configuration &amp;#39;/home/dima/Projects/giot/workspace/zephyr_sysbuild_issue/build_devkit/mcuboot/zephyr/.config.sysbuild&amp;#39;
Configuration saved to &amp;#39;/home/dima/Projects/giot/workspace/zephyr_sysbuild_issue/build_devkit/mcuboot/zephyr/.config&amp;#39;
Kconfig header saved to &amp;#39;/home/dima/Projects/giot/workspace/zephyr_sysbuild_issue/build_devkit/mcuboot/zephyr/include/generated/zephyr/autoconf.h&amp;#39;
-- Found GnuLd: /home/dima/ncs/toolchains/b77d8c1312/opt/zephyr-sdk/arm-zephyr-eabi/arm-zephyr-eabi/bin/ld.bfd (found version &amp;quot;2.38&amp;quot;) 
-- The C compiler identification is GNU 12.2.0
-- The CXX compiler identification is GNU 12.2.0
-- The ASM compiler identification is GNU
-- Found assembler: /home/dima/ncs/toolchains/b77d8c1312/opt/zephyr-sdk/arm-zephyr-eabi/bin/arm-zephyr-eabi-gcc
-- Setting build type to &amp;#39;MinSizeRel&amp;#39; as none was specified.
-- Using ccache: /home/dima/ncs/toolchains/b77d8c1312/usr/bin/ccache
MCUBoot bootloader key file: /home/dima/ncs/v2.9.0/bootloader/mcuboot/root-rsa-2048.pem
-- Configuring done
-- Generating done
-- Build files have been written to: /home/dima/Projects/giot/workspace/zephyr_sysbuild_issue/build_devkit/mcuboot
-- 
   *******************************************
   * Running CMake for zephyr_sysbuild_issue *
   *******************************************

Loading Zephyr default modules (Zephyr base).
-- Application: /home/dima/Projects/giot/workspace/zephyr_sysbuild_issue
-- CMake version: 3.21.0
-- Found Python3: /home/dima/ncs/toolchains/b77d8c1312/usr/local/bin/python (found suitable version &amp;quot;3.12.4&amp;quot;, minimum required is &amp;quot;3.8&amp;quot;) found components: Interpreter 
-- Cache files will be written to: /home/dima/.cache/zephyr
-- Zephyr version: 3.7.99 (/home/dima/ncs/v2.9.0/zephyr)
-- Found west (found suitable version &amp;quot;1.2.0&amp;quot;, minimum required is &amp;quot;0.14.0&amp;quot;)
-- Board: nrf54l15dk, qualifiers: nrf54l15/cpuapp
-- Found host-tools: zephyr 0.17.0 (/home/dima/ncs/toolchains/b77d8c1312/opt/zephyr-sdk)
-- Found toolchain: zephyr 0.17.0 (/home/dima/ncs/toolchains/b77d8c1312/opt/zephyr-sdk)
-- Found Dtc: /home/dima/ncs/toolchains/b77d8c1312/usr/bin/dtc (found suitable version &amp;quot;1.5.0&amp;quot;, minimum required is &amp;quot;1.4.6&amp;quot;) 
-- Found BOARD.dts: /home/dima/ncs/v2.9.0/zephyr/boards/nordic/nrf54l15dk/nrf54l15dk_nrf54l15_cpuapp.dts
unit address and first address in &amp;#39;reg&amp;#39; (0x5004c000) don&amp;#39;t match for /soc/peripheral@50000000/vpr@4c000/mailbox@1
-- Generated zephyr.dts: /home/dima/Projects/giot/workspace/zephyr_sysbuild_issue/build_devkit/zephyr_sysbuild_issue/zephyr/zephyr.dts
-- Generated devicetree_generated.h: /home/dima/Projects/giot/workspace/zephyr_sysbuild_issue/build_devkit/zephyr_sysbuild_issue/zephyr/include/generated/zephyr/devicetree_generated.h
-- Including generated dts.cmake file: /home/dima/Projects/giot/workspace/zephyr_sysbuild_issue/build_devkit/zephyr_sysbuild_issue/zephyr/dts.cmake

warning: UPDATEABLE_IMAGE_NUMBER (defined at
/home/dima/ncs/v2.9.0/nrf/samples/common/mcumgr_bt_ota_dfu/Kconfig:89, subsys/dfu/Kconfig:95) was
assigned the value &amp;#39;1&amp;#39; but got the value &amp;#39;&amp;#39;. Check these unsatisfied dependencies:
(((BOARD_THINGY53_NRF5340_CPUAPP || BOARD_THINGY53_NRF5340_CPUAPP_NS) &amp;amp;&amp;amp; SOC_SERIES_NRF53X &amp;amp;&amp;amp;
NCS_SAMPLE_MCUMGR_BT_OTA_DFU) || (!MCUBOOT &amp;amp;&amp;amp; IMG_MANAGER)) (=n). See
http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_UPDATEABLE_IMAGE_NUMBER and/or look up
UPDATEABLE_IMAGE_NUMBER in the menuconfig/guiconfig interface. The Application Development Primer,
Setting Configuration Values, and Kconfig - Tips and Best Practices sections of the manual might be
helpful too.


warning: MCUBOOT_UPDATE_FOOTER_SIZE (defined at subsys/dfu/Kconfig:54) was assigned the value
&amp;#39;0x5000&amp;#39; but got the value &amp;#39;&amp;#39;. Check these unsatisfied dependencies: MCUBOOT_IMG_MANAGER (=n),
IMG_MANAGER (=n). See
http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_MCUBOOT_UPDATE_FOOTER_SIZE and/or look up
MCUBOOT_UPDATE_FOOTER_SIZE in the menuconfig/guiconfig interface. The Application Development
Primer, Setting Configuration Values, and Kconfig - Tips and Best Practices sections of the manual
might be helpful too.

Parsing /home/dima/ncs/v2.9.0/zephyr/Kconfig
Loaded configuration &amp;#39;/home/dima/ncs/v2.9.0/zephyr/boards/nordic/nrf54l15dk/nrf54l15dk_nrf54l15_cpuapp_defconfig&amp;#39;
Merged configuration &amp;#39;/home/dima/Projects/giot/workspace/zephyr_sysbuild_issue/prj.conf&amp;#39;
Merged configuration &amp;#39;/home/dima/Projects/giot/workspace/zephyr_sysbuild_issue/build_devkit/zephyr_sysbuild_issue/zephyr/misc/generated/extra_kconfig_options.conf&amp;#39;
Merged configuration &amp;#39;/home/dima/Projects/giot/workspace/zephyr_sysbuild_issue/build_devkit/zephyr_sysbuild_issue/zephyr/.config.sysbuild&amp;#39;
Configuration saved to &amp;#39;/home/dima/Projects/giot/workspace/zephyr_sysbuild_issue/build_devkit/zephyr_sysbuild_issue/zephyr/.config&amp;#39;
Kconfig header saved to &amp;#39;/home/dima/Projects/giot/workspace/zephyr_sysbuild_issue/build_devkit/zephyr_sysbuild_issue/zephyr/include/generated/zephyr/autoconf.h&amp;#39;
-- Found GnuLd: /home/dima/ncs/toolchains/b77d8c1312/opt/zephyr-sdk/arm-zephyr-eabi/arm-zephyr-eabi/bin/ld.bfd (found version &amp;quot;2.38&amp;quot;) 
-- The C compiler identification is GNU 12.2.0
-- The CXX compiler identification is GNU 12.2.0
-- The ASM compiler identification is GNU
-- Found assembler: /home/dima/ncs/toolchains/b77d8c1312/opt/zephyr-sdk/arm-zephyr-eabi/bin/arm-zephyr-eabi-gcc
-- Setting build type to &amp;#39;MinSizeRel&amp;#39; as none was specified.
-- Using ccache: /home/dima/ncs/toolchains/b77d8c1312/usr/bin/ccache
-- Including signing script: /home/dima/ncs/v2.9.0/nrf/cmake/sysbuild/image_signing.cmake
CMake Warning at /home/dima/ncs/v2.9.0/zephyr/CMakeLists.txt:2164 (message):
  

        The CMake build type was set to &amp;#39;MinSizeRel&amp;#39;, but the optimization flag was set to &amp;#39;-Og&amp;#39;.
        This may be intentional and the warning can be turned off by setting the CMake variable &amp;#39;NO_BUILD_TYPE_WARNING&amp;#39;


-- Configuring done
-- Generating done
-- Build files have been written to: /home/dima/Projects/giot/workspace/zephyr_sysbuild_issue/build_devkit/zephyr_sysbuild_issue
-- Found partition manager static configuration : /home/dima/Projects/giot/workspace/zephyr_sysbuild_issue/pm_static.yml
Partition &amp;#39;mcuboot&amp;#39; is not included in the dynamic resolving since it is statically defined.
Partition &amp;#39;mcuboot_pad&amp;#39; is not included in the dynamic resolving since it is statically defined.
Partition &amp;#39;mcuboot_primary&amp;#39; is not included in the dynamic resolving since it is statically defined.
Partition &amp;#39;mcuboot_primary_app&amp;#39; is not included in the dynamic resolving since it is statically defined.
Partition &amp;#39;mcuboot_secondary&amp;#39; is not included in the dynamic resolving since it is statically defined.
-- Configuring done
-- Generating done
-- Build files have been written to: /home/dima/Projects/giot/workspace/zephyr_sysbuild_issue/build_devkit
-- west build: building application
[0/1] Re-running CMake...
Loading Zephyr default modules (Zephyr base (cached)).
-- Application: /home/dima/Projects/giot/workspace/zephyr_sysbuild_issue
-- CMake version: 3.21.0
-- Cache files will be written to: /home/dima/.cache/zephyr
-- Zephyr version: 3.7.99 (/home/dima/ncs/v2.9.0/zephyr)
-- Found west (found suitable version &amp;quot;1.2.0&amp;quot;, minimum required is &amp;quot;0.14.0&amp;quot;)
-- Board: nrf54l15dk, qualifiers: nrf54l15/cpuapp
-- Found host-tools: zephyr 0.17.0 (/home/dima/ncs/toolchains/b77d8c1312/opt/zephyr-sdk)
-- Found toolchain: zephyr 0.17.0 (/home/dima/ncs/toolchains/b77d8c1312/opt/zephyr-sdk)
-- Found BOARD.dts: /home/dima/ncs/v2.9.0/zephyr/boards/nordic/nrf54l15dk/nrf54l15dk_nrf54l15_cpuapp.dts
unit address and first address in &amp;#39;reg&amp;#39; (0x5004c000) don&amp;#39;t match for /soc/peripheral@50000000/vpr@4c000/mailbox@1
-- Generated zephyr.dts: /home/dima/Projects/giot/workspace/zephyr_sysbuild_issue/build_devkit/zephyr_sysbuild_issue/zephyr/zephyr.dts
-- Generated devicetree_generated.h: /home/dima/Projects/giot/workspace/zephyr_sysbuild_issue/build_devkit/zephyr_sysbuild_issue/zephyr/include/generated/zephyr/devicetree_generated.h
-- Including generated dts.cmake file: /home/dima/Projects/giot/workspace/zephyr_sysbuild_issue/build_devkit/zephyr_sysbuild_issue/zephyr/dts.cmake
Parsing /home/dima/ncs/v2.9.0/zephyr/Kconfig
Loaded configuration &amp;#39;/home/dima/Projects/giot/workspace/zephyr_sysbuild_issue/build_devkit/zephyr_sysbuild_issue/zephyr/.config&amp;#39;
Merged configuration &amp;#39;/home/dima/Projects/giot/workspace/zephyr_sysbuild_issue/build_devkit/zephyr_sysbuild_issue/zephyr/.config.sysbuild&amp;#39;
No change to configuration in &amp;#39;/home/dima/Projects/giot/workspace/zephyr_sysbuild_issue/build_devkit/zephyr_sysbuild_issue/zephyr/.config&amp;#39;
No change to Kconfig header in &amp;#39;/home/dima/Projects/giot/workspace/zephyr_sysbuild_issue/build_devkit/zephyr_sysbuild_issue/zephyr/include/generated/zephyr/autoconf.h&amp;#39;
-- Using ccache: /home/dima/ncs/toolchains/b77d8c1312/usr/bin/ccache
-- Including signing script: /home/dima/ncs/v2.9.0/nrf/cmake/sysbuild/image_signing.cmake
CMake Warning at /home/dima/ncs/v2.9.0/zephyr/CMakeLists.txt:2164 (message):
  

        The CMake build type was set to &amp;#39;MinSizeRel&amp;#39;, but the optimization flag was set to &amp;#39;-Og&amp;#39;.
        This may be intentional and the warning can be turned off by setting the CMake variable &amp;#39;NO_BUILD_TYPE_WARNING&amp;#39;


-- Configuring done
-- Generating done
-- Build files have been written to: /home/dima/Projects/giot/workspace/zephyr_sysbuild_issue/build_devkit/zephyr_sysbuild_issue
[1/144] Preparing syscall dependency handling

[5/144] Generating include/generated/zephyr/version.h
-- Zephyr version: 3.7.99 (/home/dima/ncs/v2.9.0/zephyr), build: v3.7.99-ncs2
[144/144] Linking C executable zephyr/zephyr.elf
Memory region         Used Size  Region Size  %age Used
           FLASH:       27878 B       686 KB      3.97%
             RAM:        4584 B       188 KB      2.38%
        IDT_LIST:          0 GB        32 KB      0.00%
Generating files from /home/dima/Projects/giot/workspace/zephyr_sysbuild_issue/build_devkit/zephyr_sysbuild_issue/zephyr/zephyr.elf for board: nrf54l15dk
image.py: sign the payload
image.py: sign the payload
[5/282] Preparing syscall dependency handling

[7/282] Generating include/generated/zephyr/version.h
-- Zephyr version: 3.7.99 (/home/dima/ncs/v2.9.0/zephyr), build: v3.7.99-ncs2
[282/282] Linking C executable zephyr/zephyr.elf
Memory region         Used Size  Region Size  %age Used
           FLASH:       34864 B        48 KB     70.93%
             RAM:       24624 B       188 KB     12.79%
        IDT_LIST:          0 GB        32 KB      0.00%
Generating files from /home/dima/Projects/giot/workspace/zephyr_sysbuild_issue/build_devkit/mcuboot/zephyr/zephyr.elf for board: nrf54l15dk
[20/20] Generating ../merged.hex
 *  Terminal will be reused by tasks, press any key to close it. &lt;/pre&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Custom board with Static partitions, MCUboot and Sysbuild</title><link>https://devzone.nordicsemi.com/thread/524542?ContentTypeID=1</link><pubDate>Tue, 25 Feb 2025 09:58:37 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:60aeea56-4300-4d5c-81db-a107af2e54dd</guid><dc:creator>AHaug</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
[quote user="DmytroSes"]&lt;p&gt;1. If I compile the project for the &lt;code&gt;nrf54l15dk/nrf54l15/cpuapp&lt;/code&gt; board target everything works fine (pm_static.yml is left unchanged)&lt;/p&gt;
&lt;p&gt;2.&amp;nbsp;&lt;a href="https://github.com/nrfconnect/sdk-nrf/blob/v2.9.0/applications/nrf_desktop/configuration/nrf54l15dk_nrf54l15_cpuapp/pm_static.yml"&gt;Here&lt;/a&gt; in the SDK application the &lt;em&gt; mcuboot_pad&lt;/em&gt; stops at 0x7800, while the &lt;em&gt;mcuboot_primary &lt;br /&gt;&lt;/em&gt;starts at 0x7000. Which looks similar to my pm_static, but they just use smaller partition for the bootloader&lt;/p&gt;[/quote]
&lt;p&gt;Ah, yes. I was a bit too quick in my previous reply.&amp;nbsp;&amp;nbsp;&lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/115835/flash-partition-management-with-trusted-firmware-m/507911"&gt;RE: Flash Partition Management with Trusted Firmware-M&lt;/a&gt;&amp;nbsp;explains the partitioning a bit better&amp;nbsp;as well.&lt;/p&gt;
&lt;p&gt;When you apply your changes to the pm_static that works. Have you made sure to reduce and increase any relevant gaps that occurs with the reduction of the bootloader partition?&lt;/p&gt;
&lt;p&gt;Could you also paste any build and/or device logs?&lt;/p&gt;
&lt;p&gt;Kind regards,&lt;br /&gt;Andreas&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Custom board with Static partitions, MCUboot and Sysbuild</title><link>https://devzone.nordicsemi.com/thread/524356?ContentTypeID=1</link><pubDate>Mon, 24 Feb 2025 13:50:27 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c24498e3-76b1-4357-b08f-4d21b0c53a8d</guid><dc:creator>DmytroSes</dc:creator><description>&lt;p&gt;Hi!&lt;br /&gt;Thank you for the answer.&lt;br /&gt;I am not sure, that this is the problem because:&lt;br /&gt;1. If I compile the project for the &lt;code&gt;nrf54l15dk/nrf54l15/cpuapp&lt;/code&gt; board target everything works fine (pm_static.yml is left unchanged)&lt;/p&gt;
&lt;p&gt;2.&amp;nbsp;&lt;a href="https://github.com/nrfconnect/sdk-nrf/blob/v2.9.0/applications/nrf_desktop/configuration/nrf54l15dk_nrf54l15_cpuapp/pm_static.yml"&gt;Here&lt;/a&gt; in the SDK application the &lt;em&gt; mcuboot_pad&lt;/em&gt; stops at 0x7800, while the &lt;em&gt;mcuboot_primary &lt;br /&gt;&lt;/em&gt;starts at 0x7000. Which looks similar to my pm_static, but they just use smaller partition for the bootloader&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Custom board with Static partitions, MCUboot and Sysbuild</title><link>https://devzone.nordicsemi.com/thread/524034?ContentTypeID=1</link><pubDate>Fri, 21 Feb 2025 09:22:42 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:993ee972-184e-404a-a83e-98657934f77e</guid><dc:creator>AHaug</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
[quote user=""]Using a debugger, I found out that the bootloader starts, but is unable to find an image. A[/quote]
&lt;p&gt;I think I see why. In your pm_static, the bootloader pad region stops at 0xc800, while the application (mcuboot_primary) starts at 0xc000, i.e before the bootloader region (mcuboot + mcuboot pad) ends&lt;/p&gt;
&lt;p&gt;Let me know if resolving the address starts resolves the bootup issues!&lt;/p&gt;
&lt;p&gt;Also, you might already gone through these resources, but I would recommend that you have a look at the newly updated lesson 8 and lesson 9 in the academy pages w.r.t sysbuild and partitioning&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;a href="https://academy.nordicsemi.com/courses/nrf-connect-sdk-intermediate/lessons/lesson-8-sysbuild/topic/sysbuild-explained/"&gt;https://academy.nordicsemi.com/courses/nrf-connect-sdk-intermediate/lessons/lesson-8-sysbuild/topic/sysbuild-explained/&lt;/a&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;a href="https://academy.nordicsemi.com/courses/nrf-connect-sdk-intermediate/lessons/lesson-8-bootloaders-and-dfu-fota/"&gt;https://academy.nordicsemi.com/courses/nrf-connect-sdk-intermediate/lessons/lesson-8-bootloaders-and-dfu-fota/&lt;/a&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;All exercises solutions should compile out of the box for the nRF54L15.&lt;/p&gt;
&lt;p&gt;Kind regards,&lt;br /&gt;Andreas&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>