<?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>Changes in the DTS file don&amp;#39;t apply after DFU</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/113123/changes-in-the-dts-file-don-t-apply-after-dfu</link><description>I have an array of LEDs on my custom board. One of the LEDs is set on a UART0 RTS pin, which is GPIO(0,5), and we are using ground as common. To avoid any conflicts, I disabled the UART0 node in my overlay file, but this LED still glows before any other</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 31 Jul 2024 10:35:57 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/113123/changes-in-the-dts-file-don-t-apply-after-dfu" /><item><title>RE: Changes in the DTS file don't apply after DFU</title><link>https://devzone.nordicsemi.com/thread/496387?ContentTypeID=1</link><pubDate>Wed, 31 Jul 2024 10:35:57 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:97180713-6a07-4255-9542-4e76039cae28</guid><dc:creator>Priyesh Shahi</dc:creator><description>&lt;p&gt;Hello&amp;nbsp;&lt;span&gt;Abhijith&lt;/span&gt;,&lt;/p&gt;
&lt;p&gt;I apologize for the delay in getting back to you.&lt;/p&gt;
&lt;p&gt;I appreciate your suggestion regarding the &lt;code&gt;mcuboot.overlay&lt;/code&gt; file. I&amp;#39;m pleased to inform you that your solution works effectively and resolves the issue. It is indeed a better approach compared to the temporary solution I had found earlier.&lt;/p&gt;
&lt;p&gt;Thank you for your assistance.&lt;/p&gt;
&lt;p&gt;Kind regards,&lt;/p&gt;
&lt;p&gt;Priyesh&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Changes in the DTS file don't apply after DFU</title><link>https://devzone.nordicsemi.com/thread/495250?ContentTypeID=1</link><pubDate>Tue, 23 Jul 2024 14:08:01 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5b533484-c5a1-465e-a865-92487eb38c22</guid><dc:creator>Menon</dc:creator><description>&lt;p&gt;Hello Priyesh,&lt;/p&gt;
&lt;p&gt;I apologize for the delay in getting back to you. It’s summer vacation here in Norway, and the workload is a bit high due to being understaffed.&lt;/p&gt;
&lt;p&gt;Regarding your issue, it might be related to the initial state or configuration of the pin at startup, even before the UART0 node is disabled or any code is executed. This can happen when pins are configured by default as part of the boot process or have default states that cause unintended behavior. I reviewed the device tree, and I can see that UART0 is already disabled, which is correct.&lt;/p&gt;
&lt;p&gt;Assuming you are using MCUboot as the bootloader, I recommend creating an `mcuboot.overlay` file (`&lt;a href="https://github.com/NordicDeveloperAcademy/ncs-inter/tree/main/lesson8/inter_less8_exer2_solution/child_image#:~:text=4%20months%20ago-,mcuboot.overlay,-init%20commit"&gt;child_image--&amp;gt;mcuboot.overlay&lt;/a&gt;`) and configuring the UART0 RTS pin typically as an output, setting it low to prevent the LED from glowing. Let me know if this approach makes any difference.&lt;/p&gt;
&lt;p&gt;Kind regards,&lt;/p&gt;
&lt;p&gt;Abhijith&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Changes in the DTS file don't apply after DFU</title><link>https://devzone.nordicsemi.com/thread/494457?ContentTypeID=1</link><pubDate>Thu, 18 Jul 2024 04:13:00 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6d290ee7-9163-4d18-bb12-60cf7d31c330</guid><dc:creator>Priyesh Shahi</dc:creator><description>&lt;p&gt;Hello Abhijith,&lt;/p&gt;
&lt;p&gt;Thank you for your query.&lt;/p&gt;
&lt;p&gt;I am using the nRF52840 DK board for evaluation purposes. The custom board we&amp;#39;ve designed also uses the nRF52840 SoC. The primary difference between the DK board and our custom board is in the power configuration: the DK board uses VCC as the common reference, while our custom board uses ground as the common reference.&lt;/p&gt;
&lt;p&gt;To clarify the devices mentioned:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;My device&lt;/strong&gt;: This refers to our custom board with the nRF52840 SoC and ground as the common reference.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The other device&lt;/strong&gt;: This refers to the nRF52840 DK board used for initial evaluation.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Regarding the SDK version, the application is built on NCS version 2.5.1.&lt;/p&gt;
&lt;p&gt;Please let me know if you need any more information or assistance.&lt;/p&gt;
&lt;p&gt;Kind Regards,&lt;/p&gt;
&lt;p&gt;Priyesh&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Changes in the DTS file don't apply after DFU</title><link>https://devzone.nordicsemi.com/thread/494369?ContentTypeID=1</link><pubDate>Wed, 17 Jul 2024 12:58:49 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a6d083f7-bcd5-40fe-9355-744b3b0556c5</guid><dc:creator>Menon</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
[quote user=""]When I flashed it on my device, the problem got solved. However, when I used DFU to flash the same firmware on another device, the firmware updates successfully, but the problem remains the same.[/quote]
&lt;p&gt;Could you tell me which two devices are mentioned here? Specifically, which chip or development kit (DK) is referred to as my device, and which one is the other device? Could you also share the SDK version on which the application is built?&lt;/p&gt;
&lt;p&gt;Kind Regards,&lt;/p&gt;
&lt;p&gt;Abhijith&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>