<?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 - issue when MCUBoot/Partition Manager is used on a custom board</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/125768/nrf54l15---issue-when-mcuboot-partition-manager-is-used-on-a-custom-board</link><description>Dear Team, 
 
 I am experiencing a weird issue with the firmware on my custom EV board with NRF54L15. 
 
 My firmware is using MCUBoot and partition manager (I use a separate flash partition for storage) and it runs just fine on my NRF54L15 DK board.</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 24 Nov 2025 12:47:54 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/125768/nrf54l15---issue-when-mcuboot-partition-manager-is-used-on-a-custom-board" /><item><title>RE: NRF54L15 - issue when MCUBoot/Partition Manager is used on a custom board</title><link>https://devzone.nordicsemi.com/thread/555209?ContentTypeID=1</link><pubDate>Mon, 24 Nov 2025 12:47:54 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:aab9b3cc-4455-47b7-b85c-d655a774b989</guid><dc:creator>Vidar Berg</dc:creator><description>&lt;p&gt;Thanks for the update. Yes, MCUboot will be built using the default configuration for your build target, which for the NRF54L15 DK is the LFXO. If you want to change this, you can create a folder named sysbuild in your project directory, and then add a new file in that folder named mcuboot.conf with the following line:&lt;/p&gt;
&lt;div&gt;
&lt;div&gt;&lt;span&gt;CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC=y&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;Then perform a clean build to allow the build system to detect that a new configuration file has been added ( a clean build is only needed when adding new files, not when editing existing configuration files).&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;For more details on how this works I recommend having a look at this course:&amp;nbsp;&lt;a href="https://academy.nordicsemi.com/courses/nrf-connect-sdk-intermediate/lessons/lesson-8-sysbuild/"&gt;https://academy.nordicsemi.com/courses/nrf-connect-sdk-intermediate/lessons/lesson-8-sysbuild/&lt;/a&gt;&amp;nbsp;&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;Best regards,&lt;/span&gt;&lt;/div&gt;
&lt;div&gt;&lt;span&gt;Vidar&lt;/span&gt;&lt;/div&gt;
&lt;/div&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NRF54L15 - issue when MCUBoot/Partition Manager is used on a custom board</title><link>https://devzone.nordicsemi.com/thread/555129?ContentTypeID=1</link><pubDate>Sun, 23 Nov 2025 23:26:14 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:85dddc51-610a-46f3-a00f-29d7974c0647</guid><dc:creator>Alex P</dc:creator><description>&lt;p&gt;Dear Team,&lt;/p&gt;
&lt;p&gt;It seems that as my custom board is using internal RC for LFXO (it doesn&amp;#39;t have 32 KHz crystal installed), it seems that issue might be somehow related to MCUBoot not using proper crystal selection settings. Can someone provide a guide on how to configure MCUBOOT to select internal RC for LFXO?&lt;/p&gt;
&lt;p&gt;Thanks&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>