<?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>How to recover bricked nRF52832 with ST Link?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/22886/how-to-recover-bricked-nrf52832-with-st-link</link><description>Hi, 
 I was trying to write the s132 SoftDevice from the nRF5_SDK_13.0.0 onto the Sparkfun nRF52832 breakout via OpenOCD and an ST-Link v2 debugger. The SoftDevice flashed and verified successfully. After reset, I am not able to connect to the nRF52832</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 20 Jun 2017 15:07:44 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/22886/how-to-recover-bricked-nrf52832-with-st-link" /><item><title>RE: How to recover bricked nRF52832 with ST Link?</title><link>https://devzone.nordicsemi.com/thread/90006?ContentTypeID=1</link><pubDate>Tue, 20 Jun 2017 15:07:44 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:bd9d8119-2ec1-4f73-8d6a-49393786da39</guid><dc:creator>HITMAnsOFT</dc:creator><description>&lt;p&gt;My SearchFu failed me I admit, but that thread is pretty convoluted. Now that I have the chip working, a known working HEX file and a JLink as a backup, I can attempt to put together a working OpenOCD for nRF52.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to recover bricked nRF52832 with ST Link?</title><link>https://devzone.nordicsemi.com/thread/90005?ContentTypeID=1</link><pubDate>Tue, 20 Jun 2017 09:42:54 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:96bdb023-c9a5-4e21-a288-5341f7e08403</guid><dc:creator>endnode</dc:creator><description>&lt;p&gt;There actually is patch for OpenOCD to perform nRF5x recover procedure as it is designed on top of generic ARM registers. See &lt;a href="https://devzone.nordicsemi.com/question/124182/memory-protection-and-pinreset-configuration-with-openocd/"&gt;this thread&lt;/a&gt; (search in the forum is powerful tool, I hope we can close this Q&amp;amp;A then;).&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to recover bricked nRF52832 with ST Link?</title><link>https://devzone.nordicsemi.com/thread/90004?ContentTypeID=1</link><pubDate>Mon, 19 Jun 2017 16:37:46 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:06e7997e-da59-48ee-a61e-38f0264fd03f</guid><dc:creator>HITMAnsOFT</dc:creator><description>&lt;p&gt;Update: The JLink connected to the board without problem. I ran &amp;quot;nrfjprog --recover&amp;quot;. Now the OpenOCD sees the device, but I will not use it for development, because it seems unstable and may brick the board again. I&amp;#39;ll use JLink while it is available, until I find a suitable OpenOCD version to work with nrf52. I&amp;#39;m leaving this question open because no fix through OpenOCD was found.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to recover bricked nRF52832 with ST Link?</title><link>https://devzone.nordicsemi.com/thread/90003?ContentTypeID=1</link><pubDate>Mon, 19 Jun 2017 05:52:56 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:76a07e8b-ba1e-4e67-b311-c01aae53269e</guid><dc:creator>HITMAnsOFT</dc:creator><description>&lt;p&gt;Turbo J, thanks for the suggestion! I tried with the official Segger update, it says my ST-Link is not compatible. Was worth a try however, as Segger seems to squeeze more performance from the same STM32 chip than the ST themselves.&lt;/p&gt;
&lt;p&gt;endnode, the main question here is whether it is possible to perform the recover/erase all procedure with ST-link. The wiring is very simple, but the OpenOCD version that supports nRF52 doesn&amp;#39;t seem stable to me.
I might hack myself a JLink from a small STM32F103 board later, as I found a working hex file somewhere online, but first I&amp;#39;ll get a normal JLink from the office for a couple of days and check if it helps.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to recover bricked nRF52832 with ST Link?</title><link>https://devzone.nordicsemi.com/thread/90001?ContentTypeID=1</link><pubDate>Sun, 18 Jun 2017 16:07:35 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:34a44450-cc5b-46d9-8a17-62718d55a20a</guid><dc:creator>endnode</dc:creator><description>&lt;p&gt;But in general it&amp;#39;s very unlikely you &amp;quot;bricked&amp;quot; the nRF5x and even less that you&amp;#39;ve burned it just by flashing Soft Device. Usual problems when you crawl this forum are: bad wiring/other HW problem or not using the latest flashing SW or &amp;quot;go with SEGGER J-Link OB on some nRF5x DK boards or with stand-alone SEGGER programmer and use latest Nordic tools to recover/erase all&amp;quot;. Sorry for not being more specific but it&amp;#39;s almost impossible to debug this kind of issue over the forum Q&amp;amp;A...&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: How to recover bricked nRF52832 with ST Link?</title><link>https://devzone.nordicsemi.com/thread/90002?ContentTypeID=1</link><pubDate>Sun, 18 Jun 2017 15:47:33 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4cce371a-aebe-4e31-933d-ab9aed9a98c7</guid><dc:creator>Turbo J</dc:creator><description>&lt;p&gt;IIRC some of those ST-Links can be reflashed to J-Links via a firmware update from SEGGER. Might be worth a try.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>