<?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>nRF54L15 + NCS 3.2.3: Secure boot chain with upgradable MCUboot fails in B0/NSIB validation</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/127720/nrf54l15-ncs-3-2-3-secure-boot-chain-with-upgradable-mcuboot-fails-in-b0-nsib-validation</link><description>Hi, 
 I am trying to set up a secure boot chain on nRF54L15dk with NCS 3.2.3 and an upgradable bootloader . 
 My intended boot chain is: 
 
 B0 / NSIB 
 S0 / S1 for the second-stage bootloader ( MCUboot , so that MCUboot itself is upgradable) 
 mcuboot_primary</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 08 Apr 2026 12:26:13 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/127720/nrf54l15-ncs-3-2-3-secure-boot-chain-with-upgradable-mcuboot-fails-in-b0-nsib-validation" /><item><title>RE: nRF54L15 + NCS 3.2.3: Secure boot chain with upgradable MCUboot fails in B0/NSIB validation</title><link>https://devzone.nordicsemi.com/thread/564619?ContentTypeID=1</link><pubDate>Wed, 08 Apr 2026 12:26:13 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f1210a3c-f72e-4451-82cc-8ab7a8a349b9</guid><dc:creator>Daniel01234</dc:creator><description>&lt;p&gt;&lt;strong&gt;EDIT: I resolved the issue:&amp;nbsp;&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;At first, it looked like a key generation or provisioning problem, but the real root cause was my &lt;/span&gt;&lt;code class="language-PlainText"&gt;&lt;span&gt;pm_static.yml&lt;/span&gt;&lt;/code&gt;&lt;span&gt;. I had placed the &lt;/span&gt;&lt;code class="language-PlainText"&gt;&lt;span&gt;provision&lt;/span&gt;&lt;/code&gt;&lt;span&gt; partition in &lt;/span&gt;&lt;code class="language-PlainText"&gt;&lt;span&gt;flash_primary&lt;/span&gt;&lt;/code&gt;&lt;span&gt;, while the working Nordic layout expects it in the &lt;/span&gt;&lt;code class="language-PlainText"&gt;&lt;span&gt;otp&lt;/span&gt;&lt;/code&gt;&lt;span&gt; region for this setup. Because of that, B0/NSIB effectively read invalid or erased values like &lt;/span&gt;&lt;code class="language-PlainText"&gt;&lt;span&gt;0xFFFF&lt;/span&gt;&lt;/code&gt;&lt;span&gt; from the provisioned data and rejected the images. After adjusting the partition layout to match the correctly generated one, the bootloader chain worked as expected.&lt;/span&gt;&lt;/p&gt;
&lt;ul class=""&gt;&lt;!--ScriptorEndFragment--&gt;&lt;/ul&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>