<?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>NRF52 bricked with CONFIG_GPIO_AS_PINRESET and P0.21 tied to ground?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/51363/nrf52-bricked-with-config_gpio_as_pinreset-and-p0-21-tied-to-ground</link><description>Dear Nordic Team, 
 Due to a mistake i flashed a bootloader-firmware with the compile flag CONFIG_GPIO_AS_PINRESET onto a custom board where pin P0.21 is tied to ground . 
 Now the nrfjprog output says: 
 nrfjprog -f nrf52 --program _build/nrf52811_xxaa</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 27 Aug 2019 07:09:07 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/51363/nrf52-bricked-with-config_gpio_as_pinreset-and-p0-21-tied-to-ground" /><item><title>RE: NRF52 bricked with CONFIG_GPIO_AS_PINRESET and P0.21 tied to ground?</title><link>https://devzone.nordicsemi.com/thread/206232?ContentTypeID=1</link><pubDate>Tue, 27 Aug 2019 07:09:07 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:226a2bce-a978-437d-adec-c7b9ac71e287</guid><dc:creator>Thomas N.</dc:creator><description>&lt;p&gt;Trying to use the&amp;nbsp;&lt;span&gt;CTRL-AP port seemed promising but you are right. The only way to get the board the work again, was to disconnect the reset pin from ground.&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NRF52 bricked with CONFIG_GPIO_AS_PINRESET and P0.21 tied to ground?</title><link>https://devzone.nordicsemi.com/thread/206068?ContentTypeID=1</link><pubDate>Mon, 26 Aug 2019 10:42:21 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9054ed0f-e05c-45d5-a046-6466eff9208a</guid><dc:creator>haakonsh</dc:creator><description>[quote user="rols"]If that doesn&amp;#39;t work, I think you&amp;#39;re bricked. It is not unlikely that reset is a very global signal which holds everything in the entire chip in reset until deasserted[/quote]
&lt;p&gt;I&amp;#39;m afraid this is true, it&amp;#39;s a global HW reset state where CPU and HW state machines are halted.&lt;br /&gt;&lt;br /&gt;The only way to un-brick your device is to sever your reset pin&amp;#39;s connection to ground.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NRF52 bricked with CONFIG_GPIO_AS_PINRESET and P0.21 tied to ground?</title><link>https://devzone.nordicsemi.com/thread/205969?ContentTypeID=1</link><pubDate>Sat, 24 Aug 2019 01:44:31 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1d0b1368-278e-4e0f-8556-e79f011813e0</guid><dc:creator>RK</dc:creator><description>&lt;p&gt;I suspect he was able to disconnect P0.21 from ground and that&amp;#39;s how he solved it. You of course don&amp;#39;t have that option.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;The only thing I can think of you might try is using the CTRL-AP port to reset and erase the entire chip and UICR. That&amp;#39;s what --eraseall does however I think perhaps the code there doesn&amp;#39;t like the actual chip being in reset. If you read this thread&amp;nbsp;&lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/12484/approtect-and-dap"&gt;https://devzone.nordicsemi.com/f/nordic-q-a/12484/approtect-and-dap&lt;/a&gt;&amp;nbsp;you&amp;#39;ll find the commands for using JLink to directly access the CTRL-AP port without attempting any real connection, it just sends simple SWD commands directly. No iterating access points or anything.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;If that doesn&amp;#39;t work, I think you&amp;#39;re bricked. It is not unlikely that reset is a very global signal which holds everything in the entire chip in reset until deasserted, that may well include the CTRL-AP port, unless someone cleverly thought about this kind of issue. You might want to try the above process several times just incase reset clears after a number of cycles on SWD on the AP.&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NRF52 bricked with CONFIG_GPIO_AS_PINRESET and P0.21 tied to ground?</title><link>https://devzone.nordicsemi.com/thread/205946?ContentTypeID=1</link><pubDate>Fri, 23 Aug 2019 16:23:03 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c2f91be6-1e43-4450-92de-f6753f618ce5</guid><dc:creator>Thomas N.</dc:creator><description>&lt;p&gt;Hi,&lt;br /&gt;&lt;br /&gt;Thanks for the quick answer. Unfortunately all IC related nrfjprog switches return &amp;quot;&lt;span class="s1"&gt;Segmentation fault: 11&amp;quot;&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;I found a post&amp;nbsp;about a similar&amp;nbsp;issue, though the author there did not explain how he solved the issue:&lt;br /&gt;&lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/51089/nrfjprog-10-3-0-segfault"&gt;https://devzone.nordicsemi.com/f/nordic-q-a/51089/nrfjprog-10-3-0-segfault&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: NRF52 bricked with CONFIG_GPIO_AS_PINRESET and P0.21 tied to ground?</title><link>https://devzone.nordicsemi.com/thread/205944?ContentTypeID=1</link><pubDate>Fri, 23 Aug 2019 16:05:17 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b7b700db-811a-4350-9973-f4d7e3462ac4</guid><dc:creator>Turbo J</dc:creator><description>&lt;p&gt;Try the &amp;nbsp;--eraseall or&amp;nbsp;--recover options for nrfjprog.exe - it looks to me like reset is not connected when UICR is fully erased.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>