<?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>nRF52833 Can&amp;#39;t connect after erase all</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/94102/nrf52833-can-t-connect-after-erase-all</link><description>Hi, 
 I am unable to connect and program a custom board with nRF52833 after performing &amp;#39;Erase All&amp;#39; using Segger IDE (V5.66). 
 Those boards were programmed a few months ago using nRF52840 EVB (version 2.0.2) and have been working fine. Now i had to update</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 22 Nov 2022 07:52:15 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/94102/nrf52833-can-t-connect-after-erase-all" /><item><title>RE: nRF52833 Can't connect after erase all</title><link>https://devzone.nordicsemi.com/thread/396803?ContentTypeID=1</link><pubDate>Tue, 22 Nov 2022 07:52:15 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e67feea8-f5ce-4439-8df4-8a5cac0cfd84</guid><dc:creator>Timor</dc:creator><description>&lt;p&gt;Update:&lt;/p&gt;
&lt;p&gt;I figured out that debug out connector P19 on the new PCA10056 (V3.0.0) was changed so that PIN3 is now the interface select pin and PIN5 is GND. I revised my cable and got some improvement. One board i was able connect and program. Two other boards are still not working.&lt;/p&gt;
&lt;p&gt;Using &amp;quot;nrfjprog --recover&amp;quot; i get an error saying&amp;nbsp;nrfjprog could not identify the target device. if I use --log I get: &amp;quot;[&amp;nbsp; nRFXX] - Device does not have an ARM debug port&amp;quot;.&lt;/p&gt;
&lt;p&gt;================================&lt;/p&gt;
&lt;p&gt;Update of update:&lt;/p&gt;
&lt;p&gt;Using a lower debugger clock (125KHz) I succeeded programing another board. So it appears to be a hardware problem on my boards after all.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>