<?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>Will this brick my 51822 chip?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/1961/will-this-brick-my-51822-chip</link><description>Executing: 
 nrf_gpio_range_cfg_input(0, 39, NRF_GPIO_PIN_NOPULL); 
 I believe it will. 
 I know the range should end at 30 but I hit the wrong key when I coded it. So far, I have 2 dead DVT boards and one dead PCA10001 that not even nRFgo Studio can</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 26 Mar 2014 04:37:28 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/1961/will-this-brick-my-51822-chip" /><item><title>RE: Will this brick my 51822 chip?</title><link>https://devzone.nordicsemi.com/thread/8426?ContentTypeID=1</link><pubDate>Wed, 26 Mar 2014 04:37:28 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:910d2a7e-86bf-429e-964e-2ba2e85e6675</guid><dc:creator>Dan Danknick</dc:creator><description>&lt;p&gt;Yep, that took care of it. Thank you for the direction!&lt;/p&gt;
&lt;p&gt;Dan&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Will this brick my 51822 chip?</title><link>https://devzone.nordicsemi.com/thread/8425?ContentTypeID=1</link><pubDate>Mon, 24 Mar 2014 08:05:46 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:b3ad81ed-4a3d-4066-bd44-cae5881842d2</guid><dc:creator>P&amp;#229;l H&amp;#229;land</dc:creator><description>&lt;p&gt;try to see if the way to reset the the chip this way helps:
&lt;a href="http://devzone.nordicsemi.com/index.php/cannot-recover-with-nrfgo-could-not-read-ahb-ap-id-could-not-connect-to-target#reply-642"&gt;devzone.nordicsemi.com/.../cannot-recover-with-nrfgo-could-not-read-ahb-ap-id-could-not-connect-to-target&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Will this brick my 51822 chip?</title><link>https://devzone.nordicsemi.com/thread/8424?ContentTypeID=1</link><pubDate>Sun, 23 Mar 2014 00:27:28 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ff8fb851-3868-4d18-9dac-1a6881136576</guid><dc:creator>Jay Tyzzer</dc:creator><description>&lt;p&gt;Dan,&lt;/p&gt;
&lt;p&gt;please upgrade to the newest Jlink software.
then look here on your hard drive for the nRFJprog.exe.&lt;br /&gt;
you may be able to do some work from there.  I am not near my dev kits or I would look myself..&lt;br /&gt;
C:\Program Files (x86)\Nordic Semiconductor\nrf51\bin&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Will this brick my 51822 chip?</title><link>https://devzone.nordicsemi.com/thread/8423?ContentTypeID=1</link><pubDate>Sat, 22 Mar 2014 22:37:09 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:dbd467ca-968d-44b4-b624-560b75b1f1cb</guid><dc:creator>Dan Danknick</dc:creator><description>&lt;p&gt;Jay,&lt;/p&gt;
&lt;p&gt;Negative. That was my go-to solution of course. I get some crazy errors reflected from the J-Flash driver while trying to execute a mass erase via the Recover option.&lt;/p&gt;
&lt;p&gt;Dan&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Will this brick my 51822 chip?</title><link>https://devzone.nordicsemi.com/thread/8422?ContentTypeID=1</link><pubDate>Sat, 22 Mar 2014 22:16:08 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7b5615b3-306a-4baf-86ed-9c99a06f3a61</guid><dc:creator>Jay Tyzzer</dc:creator><description>&lt;p&gt;Dan,
will the nRFgo Studio still erase the  flash ?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Will this brick my 51822 chip?</title><link>https://devzone.nordicsemi.com/thread/8420?ContentTypeID=1</link><pubDate>Sat, 22 Mar 2014 20:23:29 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9e434d77-0b12-4db5-85a3-bcde3ab66969</guid><dc:creator>Dan Danknick</dc:creator><description>&lt;p&gt;RK,&lt;/p&gt;
&lt;p&gt;The chip itself only has 31 GPIOs as per the spec. It&amp;#39;s probably more than most would ever need.&lt;/p&gt;
&lt;p&gt;It&amp;#39;s funny that there is not a test on parameters of that function (nor the base one it calls) as the Nordic libraries seem to parameter check just about everything else. Well, it&amp;#39;s ultimately my fault not theirs.&lt;/p&gt;
&lt;p&gt;Another theory I have is that my code was crashing and eventually ended up in NVIC_SystemReset() shortly after entering main(), causing a high speed reset loop. It may be that the Segger cannot get hold of the core via SWD in this case. I&amp;#39;ve added a nrf_delay_ms(10); as the first instruction in main() as a hedge against this ever happening again.&lt;/p&gt;
&lt;p&gt;Dan&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Will this brick my 51822 chip?</title><link>https://devzone.nordicsemi.com/thread/8421?ContentTypeID=1</link><pubDate>Sat, 22 Mar 2014 04:08:41 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:fd2f487e-479c-416e-892f-83bfeb7759b3</guid><dc:creator>RK</dc:creator><description>&lt;p&gt;Cannot answer your question about whether or not writing there would brick your chip, you&amp;#39;d hope not. I looked in the nrf51 docs to see if there was anything mapped above 0x780 but found nothing there.&lt;/p&gt;
&lt;p&gt;I did have one question though, the header file does indeed say 30 is the limit for that parameter, however there are 32 pins so surely the last one should be 31 not 30.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>