<?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>MCUBOOT with nrf9161-sica</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/127924/mcuboot-with-nrf9161-sica</link><description>I’m working on a custom board based on the nRF9160 (SICA variant) and trying to enable MCUboot + TF-M with sysbuild. I’m running into an issue where the system never reaches the application after MCUboot hands over control. 
 
 Environment 
 
 
 NCS version</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 26 May 2026 12:51:29 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/127924/mcuboot-with-nrf9161-sica" /><item><title>RE: MCUBOOT with nrf9161-sica</title><link>https://devzone.nordicsemi.com/thread/566876?ContentTypeID=1</link><pubDate>Tue, 26 May 2026 12:51:29 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:90a77bc5-30de-4f48-83bc-35e602cc6b0d</guid><dc:creator>&amp;#216;yvind</dc:creator><description>&lt;p&gt;Are you using &lt;a href="https://devzone.nordicsemi.com/nordic/nordic-blog/b/blog/posts/sysbuild-a-solution-to-multi-image-build-complexity"&gt;Sysbuild in your application&lt;/a&gt;? Our AI chatbot provides the following explanation on MCUboot and Sysbuild:&lt;/p&gt;
&lt;h2&gt;MCUboot and Sysbuild&lt;/h2&gt;
&lt;p&gt;Sysbuild and MCUboot are closely integrated in the nRF Connect SDK. Here&amp;#39;s how they relate:&lt;/p&gt;
&lt;h3&gt;Sysbuild manages MCUboot as an extra image&lt;/h3&gt;
&lt;p&gt;Sysbuild is a higher-level build system that can combine multiple build systems — including MCUboot — into a single hierarchical build. MCUboot is one of the pre-made images available in nRF Connect SDK that can be pulled into the build via Sysbuild. [&lt;a href="https://docs.nordicsemi.com/bundle/ncs-latest/page/zephyr/build/sysbuild/index.html"&gt;Sysbuild overview&lt;/a&gt;]&lt;/p&gt;
&lt;h3&gt;Enabling MCUboot via Sysbuild&lt;/h3&gt;
&lt;p&gt;To add MCUboot to your application, you simply enable it in the &lt;code&gt;sysbuild.conf&lt;/code&gt; file in your project root:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;SB_CONFIG_BOOTLOADER_MCUBOOT=y
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;This single option instructs Sysbuild to build MCUboot alongside your application, flash both images, and link your application as an MCUboot-bootable image. [&lt;a href="https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/app_dev/bootloaders_dfu/mcuboot_nsib/bootloader_adding_sysbuild.html#adding_mcuboot_as_an_immutable_bootloader"&gt;Adding MCUboot&lt;/a&gt;]&lt;/p&gt;
&lt;h3&gt;Configuring MCUboot through Sysbuild&lt;/h3&gt;
&lt;p&gt;Sysbuild Kconfig options (prefixed with &lt;code&gt;SB_CONFIG_&lt;/code&gt;) generally &lt;strong&gt;override&lt;/strong&gt; MCUboot&amp;#39;s own Kconfig options, ensuring a coherent environment for the entire system. [&lt;a href="https://docs.nordicsemi.com/bundle/ncs-latest/page/nrf/app_dev/bootloaders_dfu/mcuboot_nsib/bootloader_main_config.html"&gt;MCUboot config&lt;/a&gt;]&lt;/p&gt;
&lt;p&gt;To apply MCUboot-specific configuration, create a &lt;code&gt;sysbuild/mcuboot.conf&lt;/code&gt; file in your project. For example, to disable serial logging in MCUboot:&lt;/p&gt;
&lt;pre&gt;&lt;code&gt;CONFIG_SERIAL=n
&lt;/code&gt;&lt;/pre&gt;
&lt;p&gt;[&lt;a href="https://devzone.nordicsemi.com/nordic/nordic-blog/b/blog/posts/sysbuild-a-solution-to-multi-image-build-complexity#mcetoc_1ivs4vuoc2"&gt;Adding MCUboot&lt;/a&gt;]&lt;/p&gt;
&lt;h3&gt;Key roles MCUboot can play (configured via Sysbuild)&lt;/h3&gt;
&lt;p&gt;| Role | Sysbuild options | |---|---| | Immutable first-stage bootloader | &lt;code&gt;SB_CONFIG_BOOTLOADER_MCUBOOT=y&lt;/code&gt; | | Upgradable second-stage bootloader | &lt;code&gt;SB_CONFIG_BOOTLOADER_MCUBOOT=y&lt;/code&gt; + &lt;code&gt;SB_CONFIG_SECURE_BOOT_APPCORE=y&lt;/code&gt; | | Firmware loader mode | &lt;code&gt;SB_CONFIG_BOOTLOADER_MCUBOOT=y&lt;/code&gt; + &lt;code&gt;SB_CONFIG_MCUBOOT_MODE_FIRMWARE_UPDATER=y&lt;/code&gt; |&lt;/p&gt;
&lt;p&gt;[&lt;a href="https://docs.nordicsemi.com/bundle/ncs-latest/page/mcuboot/readme-ncs.html"&gt;MCUboot in NCS&lt;/a&gt;]&lt;/p&gt;
&lt;h3&gt;Configuration rules&lt;/h3&gt;
&lt;p&gt;Importantly, Sysbuild can configure MCUboot and the application, but &lt;strong&gt;MCUboot and the application cannot configure Sysbuild or each other&lt;/strong&gt;. This provides a clear separation of ownership. [&lt;a href="https://devzone.nordicsemi.com/nordic/nordic-blog/b/blog/posts/sysbuild-a-solution-to-multi-image-build-complexity#Enter-Sysbuild:-The-high-level-build-solution"&gt;Sysbuild blog&lt;/a&gt;]&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Kind regards,&lt;br /&gt;Øyvind&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: MCUBOOT with nrf9161-sica</title><link>https://devzone.nordicsemi.com/thread/566806?ContentTypeID=1</link><pubDate>Sat, 23 May 2026 18:25:33 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:09f46586-5ebe-4b3d-a03b-2ad7942f7a40</guid><dc:creator>Uri Rotshtein</dc:creator><description>&lt;p&gt;The application runs perfectly on my custom board when compiled without MCUboot. However, when I enable MCUboot, the boot process hangs right when it is supposed to jump to my application. Note: I haven&amp;#39;t tested this on the official dev board yet.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: MCUBOOT with nrf9161-sica</title><link>https://devzone.nordicsemi.com/thread/565595?ContentTypeID=1</link><pubDate>Tue, 28 Apr 2026 07:22:23 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5669b006-a295-409d-a44c-894061a6d42f</guid><dc:creator>&amp;#216;yvind</dc:creator><description>[quote user="oys"]are you able to build for nrf9160dk/nrf9160/ns and test the same application on that board?&amp;nbsp;[/quote]
&lt;p&gt;Does the nRF9160DK fail with MCUBOOT as well?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: MCUBOOT with nrf9161-sica</title><link>https://devzone.nordicsemi.com/thread/565564?ContentTypeID=1</link><pubDate>Mon, 27 Apr 2026 18:45:41 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:06a2f8fd-5395-44b1-ad5b-7be1cf37890e</guid><dc:creator>Uri Rotshtein</dc:creator><description>&lt;p&gt;Yes, I can build my application and it is running perfect without any error or warning during the build. Once I tried to add the MCUBOOT to support 2 images I started to had the problem. Without the MCUBOOT every thing is working fine&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: MCUBOOT with nrf9161-sica</title><link>https://devzone.nordicsemi.com/thread/565542?ContentTypeID=1</link><pubDate>Mon, 27 Apr 2026 12:32:05 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b5c32319-ddd9-4613-a190-e0df33042782</guid><dc:creator>&amp;#216;yvind</dc:creator><description>&lt;p&gt;Hello,&amp;nbsp;&lt;/p&gt;
&lt;p&gt;are you able to build for nrf9160dk/nrf9160/ns and test the same application on that board?&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Are you getting any warnings/errors in the build log while building for your custom board?&amp;nbsp;How is you custom board configured?&lt;/p&gt;
&lt;p&gt;Kind regards,&lt;br /&gt;Øyvind&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>