<?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>Unable to Recover nRF52832 After Debugging Session</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/118575/unable-to-recover-nrf52832-after-debugging-session</link><description>Hi everyone, 
 After a debugging session using the debug tool in nRF Connect SDK with an nRF52832 on a custom board, the chip is now completely unresponsive—I can&amp;#39;t flash or erase it. 
 Steps I&amp;#39;ve Tried and fails: 
 
 Erase All using nRF Connect 
 Running</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 12 Nov 2025 22:17:58 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/118575/unable-to-recover-nrf52832-after-debugging-session" /><item><title>RE: Unable to Recover nRF52832 After Debugging Session</title><link>https://devzone.nordicsemi.com/thread/554193?ContentTypeID=1</link><pubDate>Wed, 12 Nov 2025 22:17:58 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b30e182f-83f3-46cb-975f-cdb5774014ce</guid><dc:creator>EricF1</dc:creator><description>&lt;p&gt;If anyone else is having issues and this solution does not work, try out this setup using an nRF52 DK and your custom board. I did not have any luck with the batch script but using the nRF52 DK worked &lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/14058/external-programming-using-nrf52-dk?ReplySortBy=CreatedDate&amp;amp;ReplySortOrder=Ascending"&gt;https://devzone.nordicsemi.com/f/nordic-q-a/14058/external-programming-using-nrf52-dk?ReplySortBy=CreatedDate&amp;amp;ReplySortOrder=Ascending&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Unable to Recover nRF52832 After Debugging Session</title><link>https://devzone.nordicsemi.com/thread/530887?ContentTypeID=1</link><pubDate>Mon, 07 Apr 2025 19:46:03 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:31d8cd82-1a95-4ecd-84c2-180c18b87d74</guid><dc:creator>tr-Puck</dc:creator><description>&lt;p&gt;This also saved me with my nrf52840 DK. Thank you!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Unable to Recover nRF52832 After Debugging Session</title><link>https://devzone.nordicsemi.com/thread/521117?ContentTypeID=1</link><pubDate>Mon, 03 Feb 2025 13:23:32 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:8dd4ae36-2a65-4055-bc97-3a8012191658</guid><dc:creator>H&amp;#229;kon Alseth</dc:creator><description>&lt;p&gt;Glad to hear it worked out!&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Kind regards,&lt;/p&gt;
&lt;p&gt;Håkon&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Unable to Recover nRF52832 After Debugging Session</title><link>https://devzone.nordicsemi.com/thread/521112?ContentTypeID=1</link><pubDate>Mon, 03 Feb 2025 13:14:17 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f6e29736-0634-45d7-aedc-1eca78d6373d</guid><dc:creator>Red J.</dc:creator><description>&lt;p&gt;Hi H&amp;aring;kon,&lt;br /&gt;&lt;br /&gt;After loads of attempts, it finally recovered.&lt;br /&gt;&lt;br /&gt;Thank you for your help!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Unable to Recover nRF52832 After Debugging Session</title><link>https://devzone.nordicsemi.com/thread/521107?ContentTypeID=1</link><pubDate>Mon, 03 Feb 2025 12:56:49 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:999b731a-850a-46de-b61c-c20947917739</guid><dc:creator>H&amp;#229;kon Alseth</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;It sounds like your device is continuously asserting, where the default behaviour is then to do a soft-reset. If this happens early in the boot-process, it is quite hard to recover the device.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Try to run nrfjprog --recover in a loop, by creating a batch file like this (rename it to recover.bat or something):&lt;/p&gt;
&lt;p&gt;&lt;pre class="ui-code" data-mode="text"&gt;:loop
nrfjprog --recover -f nrf52
goto loop&lt;/pre&gt;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;And run this while power-cycling your DUT.&lt;/p&gt;
&lt;p&gt;Could you try this and report back if you still have issues?&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;Kind regards,&lt;/p&gt;
&lt;p&gt;Håkon&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>