<?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>Nrf desktop hid mcuboot development</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/128121/nrf-desktop-hid-mcuboot-development</link><description>I want to expand the flash allocated to mcuboot on the NRF desktop, but it failed to start after compilation 
 The following is a flash layout that can be successfully launched 
 # 原始分区（mcuboot 28KB） app: address: 0x7800 region: flash_primary size: 0xb8800</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 26 Jun 2026 13:29:20 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/128121/nrf-desktop-hid-mcuboot-development" /><item><title>RE: Nrf desktop hid mcuboot development</title><link>https://devzone.nordicsemi.com/thread/568490?ContentTypeID=1</link><pubDate>Fri, 26 Jun 2026 13:29:20 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f3f5ad1e-b8c1-4229-b4b1-d938f92184e4</guid><dc:creator>SwRa</dc:creator><description>&lt;p&gt;Hi Jiale,&lt;/p&gt;
&lt;p&gt;It&amp;nbsp;is a known issue. FPROTECT can support locking up to 62 KB of RRAM on nRF54L SoCs&amp;nbsp;when used by immutable MCUboot. Either the partition declared for MCUboot or its size might be too large for using FPROTECT. Your MCUboot partition is&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;strong&gt;64 KB (0x10000)&lt;/strong&gt;, which exceeds the supported limit. The RRAMC hardware on nRF54L only provides two regions (3 and 4) for protection:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;div&gt;&lt;span&gt;Up to&amp;nbsp;31 KB&amp;nbsp;→ uses RRAMC region 4 alone&lt;/span&gt;&lt;/div&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;div&gt;&lt;span&gt;Between&amp;nbsp;31 KB and 62 KB&amp;nbsp;→ uses both regions 3 and 4 (requires&amp;nbsp;&lt;code dir="ltr"&gt;CONFIG_FPROTECT_ALLOW_COMBINED_REGIONS&lt;/code&gt;)&lt;/span&gt;&lt;/div&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;div&gt;&lt;span&gt;Above 62 KB&amp;nbsp;→&amp;nbsp;not supported, causes a static assertion failure&lt;/span&gt;&lt;/div&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Refer:&amp;nbsp;&lt;a href="https://nrfconnectdocs.nordicsemi.com/ncs/latest/nrf/app_dev/device_guides/nrf54l/dfu_config.html#nvm-protections"&gt;https://nrfconnectdocs.nordicsemi.com/ncs/latest/nrf/app_dev/device_guides/nrf54l/dfu_config.html#nvm-protections&lt;/a&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;You will either need to decrease the partition size to less than 62 KB or Disable FPROTECT as you did. You can disable it by setting&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;code dir="ltr"&gt;CONFIG_FPROTECT=n&lt;/code&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;in your MCUboot configuration, but this removes write protection from the bootloader region, which is a security risk in production firmware.&lt;/p&gt;
&lt;p&gt;Best Regards,&lt;/p&gt;
&lt;p&gt;Swathy&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Nrf desktop hid mcuboot development</title><link>https://devzone.nordicsemi.com/thread/566491?ContentTypeID=1</link><pubDate>Tue, 19 May 2026 04:09:18 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7b24a3f9-e174-4fc8-a7ee-98be6e79cfb8</guid><dc:creator>CJL</dc:creator><description>&lt;p&gt;I have already adjusted the alignment to 4KB, but this may not be the root cause. I commented out the code below and it can run. What is the problem?&lt;/p&gt;
&lt;p&gt;D:\ncs\v3.1.1\nrf\lib\fprotect\fprotect_rram.c&lt;/p&gt;
&lt;p&gt;int fprotect_area(uint32_t start, size_t size)&lt;/p&gt;
&lt;p&gt;&lt;img style="max-height:240px;max-width:320px;" src="https://devzone.nordicsemi.com/resized-image/__size/640x480/__key/communityserver-discussions-components-files/4/1560.png" alt=" " /&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Nrf desktop hid mcuboot development</title><link>https://devzone.nordicsemi.com/thread/566461?ContentTypeID=1</link><pubDate>Mon, 18 May 2026 12:10:54 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:108e12e4-ef7c-4288-8ae8-acfe6a12f5b2</guid><dc:creator>SwRa</dc:creator><description>&lt;p&gt;Hi Jiale,&lt;/p&gt;
&lt;p&gt;&lt;span&gt;It is essential that your slot partitions for mcuboot (primary, secondary) are both aligned at their start address on a flash erase sector boundary AND that their size is ALSO aligned on an erase boundary. Please refer the discussion in the following thread:&amp;nbsp;&amp;nbsp;&lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/115046/dfu-using-usb-file-system-not-serial-emulation"&gt;DFU using USB file system (not serial emulation)?&lt;/a&gt;&amp;nbsp;&amp;nbsp;Your mcuboot_primary_size of 0xb4800&amp;nbsp;is also not 4KB-aligned. please try fixing it.&amp;nbsp;&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Best Regards,&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Swathy&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Nrf desktop hid mcuboot development</title><link>https://devzone.nordicsemi.com/thread/566354?ContentTypeID=1</link><pubDate>Thu, 14 May 2026 00:53:16 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:52753110-3cc0-48f0-ac3f-e8a63b4ba07c</guid><dc:creator>CJL</dc:creator><description>&lt;p&gt;ncs sdk version:3.1.1&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>