<?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>Issue with Unknown Device detection on nRF5340 – Flashing works, but Debugging/Recovery fails</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/127342/issue-with-unknown-device-detection-on-nrf5340-flashing-works-but-debugging-recovery-fails</link><description>I am currently developing a project using an nRF5340DK and a custom board. 
 For some unknown reason, the device is being identified as an &amp;quot;Unknown device.&amp;quot; The ironic part is that flashing the firmware still works successfully, even though the device</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 18 Mar 2026 06:09:07 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/127342/issue-with-unknown-device-detection-on-nrf5340-flashing-works-but-debugging-recovery-fails" /><item><title>RE: Issue with Unknown Device detection on nRF5340 – Flashing works, but Debugging/Recovery fails</title><link>https://devzone.nordicsemi.com/thread/563518?ContentTypeID=1</link><pubDate>Wed, 18 Mar 2026 06:09:07 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:58d4f89e-fa18-424f-bee1-425b530e0278</guid><dc:creator>Vidar Berg</dc:creator><description>&lt;p&gt;Your overlay is correct, so if it is being applied it should not be an issue with the regulator settings. If you want to confirm that it is being applied, you can check the final DT configuration in the zephyr.dts file generated for your application in the build folder. You can also try to read the regulator&amp;nbsp;registers with nrfutil (if it doesn&amp;#39;t fail to connect).&lt;/p&gt;
&lt;p&gt;Reading&amp;nbsp;&lt;a href="https://docs.nordicsemi.com/bundle/ps_nrf5340/page/regulators.html#d1610e340"&gt;VREGMAIN.DCDCEN&lt;/a&gt;:&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt;nrfutil device read --address 0x50004704 --direct&lt;/pre&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Issue with Unknown Device detection on nRF5340 – Flashing works, but Debugging/Recovery fails</title><link>https://devzone.nordicsemi.com/thread/563512?ContentTypeID=1</link><pubDate>Wed, 18 Mar 2026 01:51:27 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6c6c45a1-8bd3-48ba-86c5-0a468bb75280</guid><dc:creator>gwan0624</dc:creator><description>&lt;p data-path-to-node="8,0"&gt;I&amp;#39;m using LDO mode without an inductor and updated the overlay file accordingly.&lt;/p&gt;
&lt;p data-path-to-node="8,0"&gt;&lt;img style="max-height:240px;max-width:320px;" src="https://devzone.nordicsemi.com/resized-image/__size/640x480/__key/communityserver-discussions-components-files/4/pastedimage1773798702316v1.png" alt=" " /&gt;&lt;/p&gt;
&lt;p data-path-to-node="8,1"&gt;Is it possible the power instability is because the nRF5340 is still stuck in DCDC mode? Since the device fails to boot, I suspect the internal regulator registers haven&amp;#39;t actually changed to LDO mode.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Issue with Unknown Device detection on nRF5340 – Flashing works, but Debugging/Recovery fails</title><link>https://devzone.nordicsemi.com/thread/563447?ContentTypeID=1</link><pubDate>Tue, 17 Mar 2026 13:20:46 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:afbf25ae-9a32-4331-9134-30ea1040ec58</guid><dc:creator>Vidar Berg</dc:creator><description>&lt;p&gt;Does your design include the optional DCDC inductors? If you build the FW for the nRF5340 DK, the DCDC regulators will be enabled by default, and if the inductors are not included, the regulator will fail to provide a stable supply voltage internally in the chip which commonly leads to issues such as being unable to re-program the chip.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Vidar&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Issue with Unknown Device detection on nRF5340 – Flashing works, but Debugging/Recovery fails</title><link>https://devzone.nordicsemi.com/thread/563403?ContentTypeID=1</link><pubDate>Tue, 17 Mar 2026 08:11:58 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f3274d42-0c63-4b2a-bc92-12f3723cc802</guid><dc:creator>gwan0624</dc:creator><description>&lt;p&gt;Thank you for your response.&lt;/p&gt;
&lt;p&gt;Unfortunately, the recovery was unsuccessful even after following the procedure. Given the &lt;b data-path-to-node="2,0" data-index-in-node="121"&gt;unstable outputs&lt;/b&gt; on the &lt;b data-path-to-node="2,0" data-index-in-node="145"&gt;VDD and RESET pins&lt;/b&gt;, it appears the &lt;b data-path-to-node="2,0" data-index-in-node="180"&gt;MCU itself has been damaged&lt;/b&gt;.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/127341/issue-with-failing-vdd-output-is-recovery-possible-nrf5340"&gt;Issue with failing VDD output – Is recovery possible? (nRF5340)&lt;/a&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;I will need to reorder the PCB and proceed with further testing&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Best regards,&lt;br /&gt;gwan0624&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Issue with Unknown Device detection on nRF5340 – Flashing works, but Debugging/Recovery fails</title><link>https://devzone.nordicsemi.com/thread/562952?ContentTypeID=1</link><pubDate>Tue, 10 Mar 2026 15:51:38 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:278b2b77-9741-4e9f-900c-22bfd6f75cc5</guid><dc:creator>Vidar Berg</dc:creator><description>&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;Yes, as you say, nrfutil will not be able to correctly identify the chip when approtect is enabled. To unlock approtect on the nRF5340, you must perform the recovery procedure on the network core before you recover the application core. Please try this and see if the problem persists.&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt;nrfutil device recover --core network
nrfutil device recover
&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Vidar&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>