<?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 + NCS v3.0.2: Range issue with MCUBoot</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/123938/nrf54l15-mcuboot-ncs-v3-0-2-range-issue-with-mcuboot</link><description>Hi, 
 We’re developing a BLE-based product on the nRF54L15 (InsightSIP ISP2454-LX) using nRF Connect SDK v3.0.2 , with MCUboot enabled for DFU. 
 Our BLE application is based on a custom service and configured to use +8 dBm Tx power. Initially, everything</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 02 Sep 2025 05:08:59 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/123938/nrf54l15-mcuboot-ncs-v3-0-2-range-issue-with-mcuboot" /><item><title>RE: nRF54L15 + MCUboot + NCS v3.0.2: Range issue with MCUBoot</title><link>https://devzone.nordicsemi.com/thread/547389?ContentTypeID=1</link><pubDate>Tue, 02 Sep 2025 05:08:59 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7b090106-63d0-4588-8aad-562e00ed3f8b</guid><dc:creator>ByteSpectrum</dc:creator><description>&lt;p&gt;Hi Hieu,&lt;/p&gt;
&lt;p&gt;No They are not different. Actually, those are from same build.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;I am sure it will be very difficult for you to give reason behind this behavior.&amp;nbsp;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;As I am not able to reproduce, let&amp;#39;s close this thread as of now. I will contact if issue reproduce again in future.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Thanks,&lt;/p&gt;
&lt;p&gt;Tarun&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF54L15 + MCUboot + NCS v3.0.2: Range issue with MCUBoot</title><link>https://devzone.nordicsemi.com/thread/547377?ContentTypeID=1</link><pubDate>Mon, 01 Sep 2025 19:08:47 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4fbb4382-f919-494a-953e-c48f018d5cd5</guid><dc:creator>Hieu</dc:creator><description>&lt;p&gt;Hi Tarun,&lt;/p&gt;
&lt;p&gt;Could you please compare the .bin files from the OTA payload and the merged.hex file you flash directly with the programmer? Are there any chances they are different?&lt;/p&gt;
&lt;p&gt;Regards,&lt;/p&gt;
&lt;p&gt;Hieu&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF54L15 + MCUboot + NCS v3.0.2: Range issue with MCUBoot</title><link>https://devzone.nordicsemi.com/thread/547174?ContentTypeID=1</link><pubDate>Fri, 29 Aug 2025 10:46:04 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b98ffea4-3611-4f6f-bd3d-6a69d26a1c18</guid><dc:creator>ByteSpectrum</dc:creator><description>&lt;p&gt;Hi Hieu,&lt;/p&gt;
&lt;p&gt;I have found a puzzling issue.&lt;/p&gt;
&lt;p&gt;When I updated only the application using an &lt;b&gt;Over-the-Air (OTA) update&lt;/b&gt;, the problem persists each and every time. However, when I erased whole flash and flashed both the &lt;b&gt;bootloader&lt;/b&gt; and the &lt;b&gt;application&lt;/b&gt; together using a &lt;b&gt;programmer&lt;/b&gt;, the issue disappeared. Now I am not able to reproduce it.&lt;/p&gt;
&lt;p&gt;Any ideas why this might be happening?&lt;/p&gt;
&lt;p&gt;Thanks,&lt;/p&gt;
&lt;p&gt;Tarun&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF54L15 + MCUboot + NCS v3.0.2: Range issue with MCUBoot</title><link>https://devzone.nordicsemi.com/thread/547172?ContentTypeID=1</link><pubDate>Fri, 29 Aug 2025 10:25:24 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6c53625d-42de-4cf0-b944-e01506ae53bb</guid><dc:creator>Hieu</dc:creator><description>&lt;p&gt;Hi Tarun,&lt;/p&gt;
&lt;p&gt;I checked the files. So MCUboot doesn&amp;#39;t get any BT power config applied, which is expected, because it doesn&amp;#39;t have a BT stack. However, that also means that there shouldn&amp;#39;t be any strange reason it could affect the TX Power of the main application, whose configurations are properly in place.&lt;/p&gt;
&lt;p&gt;Do you use dynamic TX Power control? If not, please try to disable&amp;nbsp;CONFIG_BT_CTLR_TX_PWR_DYNAMIC_CONTROL.&lt;/p&gt;
&lt;p&gt;If you use dynamic TX Power control, then please try to set it in code.&lt;/p&gt;
&lt;p&gt;Hieu&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF54L15 + MCUboot + NCS v3.0.2: Range issue with MCUBoot</title><link>https://devzone.nordicsemi.com/thread/546994?ContentTypeID=1</link><pubDate>Thu, 28 Aug 2025 04:33:38 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7f04a306-19f6-4194-961d-4379dc4b6343</guid><dc:creator>ByteSpectrum</dc:creator><description>&lt;p&gt;Hi Hieu,&lt;/p&gt;
&lt;p&gt;Please find attached.&lt;/p&gt;
&lt;p&gt;Thanks,&lt;/p&gt;
&lt;p&gt;Tarun&lt;/p&gt;
&lt;p&gt;&lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/pristine_5F00_build_5F00_log.txt"&gt;devzone.nordicsemi.com/.../pristine_5F00_build_5F00_log.txt&lt;/a&gt;&lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/app_2E00_config"&gt;devzone.nordicsemi.com/.../app_2E00_config&lt;/a&gt;&lt;a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/3034_2E00_mcuboot_2E00_config"&gt;devzone.nordicsemi.com/.../3034_2E00_mcuboot_2E00_config&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF54L15 + MCUboot + NCS v3.0.2: Range issue with MCUBoot</title><link>https://devzone.nordicsemi.com/thread/546982?ContentTypeID=1</link><pubDate>Wed, 27 Aug 2025 21:22:27 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6de74f0c-11d5-4ed9-8267-5ddbf3212043</guid><dc:creator>Hieu</dc:creator><description>&lt;p&gt;Hi ByteSpectrum,&lt;/p&gt;
&lt;p&gt;Could you please share the following from the build with MCUboot?&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;The application&amp;nbsp;compiled Kconfig file, located at &amp;lt;build directory&amp;gt;/&amp;lt;application name&amp;gt;/zephyr/.config&lt;/li&gt;
&lt;li&gt;The MCUboot compiled Kconfig file, located at &amp;lt;build directory&amp;gt;/mcuboot/zephyr/.config&lt;/li&gt;
&lt;li&gt;Full pristine build log&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Hieu&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>