<?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 after wrong DCDC config on LDO-only board</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/128690/recover-nrf5340-mdbt53-after-wrong-dcdc-config-on-ldo-only-board</link><description>Hi Nordic, 
 I have a custom board using a Raytac MDBT53 module with nRF5340. The board is designed for 3.3 V / LDO mode, but during bring-up I likely flashed firmware/configuration that enabled DCDC or otherwise set the regulator mode incorrectly. 
</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 15 Jul 2026 06:49:50 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/128690/recover-nrf5340-mdbt53-after-wrong-dcdc-config-on-ldo-only-board" /><item><title>RE: Recover nRF5340 / MDBT53 after wrong DCDC config on LDO-only board</title><link>https://devzone.nordicsemi.com/thread/569097?ContentTypeID=1</link><pubDate>Wed, 15 Jul 2026 06:49:50 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1510b3ff-f721-4850-accf-b3092c1a49c7</guid><dc:creator>Kazi Afroza Sultana</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;ol start="1"&gt;
&lt;li&gt;Can wrong DCDC/regulator configuration prevent SWD access on nRF5340?&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Wrong DCDC configuration causes device to behave abnormal for example sudden reset or unresponsive.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;If the device resets or hangs or crashes at startup due to regulator misconfiguration, there is a high chance not to be reachable over SWD. As after each reset APPROTECT requires firmware re-enable debugger access before the next one. UICR includes regulator configuration registers like UICR.VREGHVOUT.&lt;/p&gt;
&lt;p&gt;2.&amp;nbsp;If SWD can be reached, will&lt;span&gt;&amp;nbsp;&lt;/span&gt;&lt;code&gt;nrfjprog --recover&lt;/code&gt;&lt;span&gt;&amp;nbsp;&lt;/span&gt;/ ERASEALL clear the bad UICR/regulator setting?&lt;/p&gt;
&lt;p&gt;Yes, nrfjprog --recover or eraseall command does eraseall operation via CTRL-AP which erases flash, SRAM and UICR (which includes regulator configuration registers like UICR.VREGHVOUT).&lt;/p&gt;
&lt;p&gt;3. Is there a recommended connect-under-reset or recovery sequence for this failure mode?&lt;/p&gt;
&lt;p&gt;You can read this blog&amp;nbsp;&lt;a href="https://devzone.nordicsemi.com/nordic/nordic-blog/b/blog/posts/allowing-debugger-access-to-an-nrf5340#mcetoc_1es29sb6t0"&gt;(+) Allowing debugger access to nRF5340 - Blogs - Nordic Blog - Nordic DevZone&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;4. I need to talk to team to be sure of this query.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Thanks.&lt;/p&gt;
&lt;p&gt;BR&lt;br /&gt;Kazi&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>