<?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>Raytac MDBT53(nRF5340) custom board SWD not responding after erase</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/112388/raytac-mdbt53-nrf5340-custom-board-swd-not-responding-after-erase</link><description>Hello, 
 I am building basic board on nRF5340(based on Raytac MDBT53 module) and after &amp;quot;Erase&amp;quot; operation in nRF Connect Programmer I cannot access chip anymore. 
 
 Board schematics are based on the basic example from MDBT53 documentation (see screenshot</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 02 Jul 2024 06:34:19 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/112388/raytac-mdbt53-nrf5340-custom-board-swd-not-responding-after-erase" /><item><title>RE: Raytac MDBT53(nRF5340) custom board SWD not responding after erase</title><link>https://devzone.nordicsemi.com/thread/491730?ContentTypeID=1</link><pubDate>Tue, 02 Jul 2024 06:34:19 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9d34a595-85b0-4625-8843-2ea1cbd26f1d</guid><dc:creator>ffenix</dc:creator><description>&lt;p&gt;Hello Runar,&lt;/p&gt;
&lt;p&gt;Thank you for the proposed solution. While I cannot test it directly, I was able to produce another board and build a configuration with DCDC off based on &lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/72855/how-to-turn-on-nrf5340-dcdc/300196"&gt;this&lt;/a&gt; comment. On this new board and with disabled DCDC the board does not become bricked, and I think this particular issue is resolved.&lt;/p&gt;
&lt;p&gt;I cannot recover the bricked boards at this time, but your solution should work.&lt;/p&gt;
&lt;p&gt;Thank you.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Raytac MDBT53(nRF5340) custom board SWD not responding after erase</title><link>https://devzone.nordicsemi.com/thread/490290?ContentTypeID=1</link><pubDate>Mon, 24 Jun 2024 12:38:53 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:cebc5099-f73b-4eb7-bbed-5d943336ef11</guid><dc:creator>runsiv</dc:creator><description>&lt;p&gt;Hi&lt;/p&gt;
&lt;p&gt;I will take a look at your case.&amp;nbsp;&lt;/p&gt;
[quote user=""]&lt;p&gt;Could this be because of missing LF crystal? And if so - would &lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/93836/using-the-internal-lfrc-oscillator-with-nrf-connect-sdk/395453"&gt;this&lt;/a&gt; solution fix the issue?&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;[/quote]
&lt;p&gt;The use of internal LF cystall should solve the issue with the application not starting. However you should still be able to flash the device without any issue.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;I suspect it might be that the module is missing the coil for DCDC, and if that is the case you can have a look at this &lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/108869/unable-to-recover-nrf5340-flashed-with-invalid-dcdc-configuration"&gt;case&lt;/a&gt; on how to recover the device.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Regards&lt;/p&gt;
&lt;p&gt;Runar&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Raytac MDBT53(nRF5340) custom board SWD not responding after erase</title><link>https://devzone.nordicsemi.com/thread/490116?ContentTypeID=1</link><pubDate>Sun, 23 Jun 2024 15:05:21 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:77f280bb-3a00-4f7b-8a0d-10ce5625ba66</guid><dc:creator>ffenix</dc:creator><description>&lt;p&gt;A bit of clarification: after the &amp;quot;erase &amp;amp; write&amp;quot; the chip will output 1.8V, but SWD is not accessible not like that, not while connecting DKs VDD to custom board&amp;#39;s VDD, making it output 3V.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>