<?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>JLink - nrf52832 communicaton failure</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/72441/jlink---nrf52832-communicaton-failure</link><description>Hello, 
 I have several custom 52832 bords that until recently worked fine with SDK15. 
 Yestrday I started experimenting with nrfConnect and flashed some Zephyr examples. It looks like an erroneous bin file used and now JLink cannot communicate with</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Sat, 06 Mar 2021 16:44:15 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/72441/jlink---nrf52832-communicaton-failure" /><item><title>RE: JLink - nrf52832 communicaton failure</title><link>https://devzone.nordicsemi.com/thread/298213?ContentTypeID=1</link><pubDate>Sat, 06 Mar 2021 16:44:15 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:11ab4efb-dc93-4ffb-94ed-4a6ff2fd0938</guid><dc:creator>Thanos</dc:creator><description>&lt;p&gt;ok, I think it&amp;#39;s fixed now.&lt;/p&gt;
&lt;p&gt;By using another JLink interface (the one embedded in the nrf91DK) the message &amp;quot;Could not power-up debug power domain&amp;quot; showed up. So, after digging into the relevant threads the trick was first to wire the debugger and then pulse low nRESET line (LDO mode is forced during&amp;nbsp;DEBUG). After that JLink had no problems communicating with 52832; erase, flash, and power-cycle restored everything back.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>