<?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>Recover nrf5340 (MDBT53) custom board</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/121180/recover-nrf5340-mdbt53-custom-board</link><description>I am using custom board with MDBT53 and I&amp;#39;m stuck at a point where board does not even let me to connect the debugger so that I can refresh firmware. 
 I added MCU boot code into my existing firmware and once I flashed this mcu boot code to my board I</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 21 May 2025 13:45:37 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/121180/recover-nrf5340-mdbt53-custom-board" /><item><title>RE: Recover nrf5340 (MDBT53) custom board</title><link>https://devzone.nordicsemi.com/thread/536467?ContentTypeID=1</link><pubDate>Wed, 21 May 2025 13:45:37 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c43bf47c-1948-4caf-93ee-3ae7c29a3e51</guid><dc:creator>JONATHAN LL</dc:creator><description>&lt;p&gt;Hi, sorry for the slow response.&amp;nbsp;&lt;br /&gt;&lt;br /&gt;&lt;/p&gt;
[quote user="Hassam Arshad"]Anyway any idea how. we can recover this or make this work again?[/quote]
&lt;p&gt;To recover a board that has the been flashed with the wrong firmware you would need to supply the external pins related to DCC with power or at least get it in a state before it shuts down due to the wrong regulators being enabled. In many cases the device is bricked as the pins are not always accessible. If that is the case then it needs to be removed and either replaced or mounted to a board where all pins are available and re-programed\recovered.&amp;nbsp;&lt;br /&gt;&lt;br /&gt;Since you have a module you should be able to access the pins connected to the different regulators so this could possibly be solved.&amp;nbsp;&lt;br /&gt;&lt;br /&gt;In the code when you compile it you should be able to see if the registers for the regulators are on or off before you flash it to the device. There should be a Zephyr.dts file that is generated, maybe for the bootloader.&amp;nbsp;&lt;br /&gt;It might be that the bootloader overwrites the configs if not done correctly.&amp;nbsp;&lt;br /&gt;&lt;br /&gt;Regards,&lt;br /&gt;Jonathan&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Recover nrf5340 (MDBT53) custom board</title><link>https://devzone.nordicsemi.com/thread/534533?ContentTypeID=1</link><pubDate>Thu, 08 May 2025 21:37:30 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e54b0f09-daf1-446b-ba4a-f292021b4da4</guid><dc:creator>Muhammad</dc:creator><description>&lt;p&gt;can you give any update on it?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Recover nrf5340 (MDBT53) custom board</title><link>https://devzone.nordicsemi.com/thread/533828?ContentTypeID=1</link><pubDate>Sun, 04 May 2025 22:05:52 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:30bb8766-db50-42b8-b289-faa4bf9ee697</guid><dc:creator>Muhammad</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Thanks for quick response.&amp;nbsp;I am not sure about the circuit but&amp;nbsp;I know from my colleagues that we have explicitly disabled it in the code. like this&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt;# disable DCDC
CONFIG_BOARD_ENABLE_DCDC_APP=n
CONFIG_BOARD_ENABLE_DCDC_NET=n
CONFIG_BOARD_ENABLE_DCDC_HV=n&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;I haven&amp;#39;t done anything with code but added bootlaoder code into the current version of code and then this happened. So one thing I dont understand is why the device goes to this state as I have never seen something like this before as I did&amp;nbsp;work on mcu boot serval times.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Anyway any idea how. we can recover this or make this work again?&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Regards,&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Recover nrf5340 (MDBT53) custom board</title><link>https://devzone.nordicsemi.com/thread/533825?ContentTypeID=1</link><pubDate>Sun, 04 May 2025 21:48:11 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b8aaa522-a416-47b6-b1f6-1507f9e2cab3</guid><dc:creator>JONATHAN LL</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Foes you custom board use DCDC or LDO mode of operation?&lt;/p&gt;
&lt;p&gt;If you do not have the DCDC external components in place you will &amp;quot;brick&amp;quot; the device.&lt;/p&gt;
&lt;p&gt;&lt;img style="max-height:240px;max-width:320px;" alt=" " src="https://devzone.nordicsemi.com/resized-image/__size/640x480/__key/communityserver-discussions-components-files/4/Screenshot_5F00_2025_2D00_05_2D00_04_2D00_23_2D00_43_2D00_22_2D00_48_5F00_f541918c7893c52dbd1ee5d319333948.jpg" /&gt;&lt;/p&gt;
&lt;p&gt;Form the Raytac docs, see the recommended circuit for the DCDC mode.&lt;/p&gt;
&lt;p&gt;Regards,&lt;/p&gt;
&lt;p&gt;Jonathan&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>