<?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 mcuboot fprotect issue</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/121275/nrf54l15-mcuboot-fprotect-issue</link><description>Hello, 
 I&amp;#39;m developing for nRF54L15 the application with the NSIB + MCUBoot. I have a problem with fprotect in mcuboot returning EINVAL error. That happens due to limitation of the max protect area size in function fprotect_area in file fprotect_rram</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 09 May 2025 08:55:10 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/121275/nrf54l15-mcuboot-fprotect-issue" /><item><title>RE: nRF54L15 mcuboot fprotect issue</title><link>https://devzone.nordicsemi.com/thread/534597?ContentTypeID=1</link><pubDate>Fri, 09 May 2025 08:55:10 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a4021c05-7e2d-4dea-a63f-546d0f60de9c</guid><dc:creator>Menon</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;For NSIB + MCUboot, I recommend using NCS version 3.0.0 or higher, as support for NSIB with the nRF54L15 is experimental in NCS versions below 3.0.0. Please refer to the &lt;a href="https://docs.nordicsemi.com/bundle/ncs-3.0.0-preview2/page/nrf/releases_and_maturity/software_maturity.html#nrf_secure_immutable_bootloader"&gt;&lt;em&gt;Software Maturity Level&lt;/em&gt; section &lt;/a&gt;for more details.&lt;/p&gt;
&lt;p&gt;Could you try creating a &lt;code&gt;pm_static&lt;/code&gt; file, which would allow you to manually define the sizes and addresses of the partitions? However, if you need the full 0xC00 of both S0 and S1, then creating a &lt;code&gt;pm_static&lt;/code&gt; file may not be a viable solution.&lt;/p&gt;
&lt;p&gt;Let me know whether creating a &lt;code&gt;pm_static&lt;/code&gt; file is an option for you.&lt;/p&gt;
&lt;p&gt;Kind regards,&lt;br /&gt; Abhijith&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>