<?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>nrf51822 is so easy to be damaged?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/868/nrf51822-is-so-easy-to-be-damaged</link><description>Hi, Nordic
I added &amp;quot;//&amp;quot; to the srccode of main.c in project ble_app_hrs just like below 
 bond_manager_init();
 
 // ble_stack_init();
ble_error_log_init();
timers_init();
gap_params_init(); 
 then I built the project and burned it to pca10005</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 11 Mar 2016 19:03:53 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/868/nrf51822-is-so-easy-to-be-damaged" /><item><title>RE: nrf51822 is so easy to be damaged?</title><link>https://devzone.nordicsemi.com/thread/4261?ContentTypeID=1</link><pubDate>Fri, 11 Mar 2016 19:03:53 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2deb3b0e-126d-4acb-975b-9f3fe0aea780</guid><dc:creator>Andrew Wilson</dc:creator><description>&lt;p&gt;This .bat suggestion was very helpful to me -- thank you!&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf51822 is so easy to be damaged?</title><link>https://devzone.nordicsemi.com/thread/4263?ContentTypeID=1</link><pubDate>Thu, 06 Nov 2014 08:31:08 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:29bacf3a-4675-469a-86e9-37a5a3f61ec5</guid><dc:creator>Charles Chow</dc:creator><description>&lt;p&gt;Thanks Juha suggestion, my board saved.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf51822 is so easy to be damaged?</title><link>https://devzone.nordicsemi.com/thread/4258?ContentTypeID=1</link><pubDate>Wed, 21 May 2014 16:10:05 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e1e139bf-4862-43bc-b711-25051b8bbdbf</guid><dc:creator>Tim</dc:creator><description>&lt;p&gt;Juha: Thanks so much! Worked perfectly. This should really be built into the &amp;quot;recover&amp;quot; function.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf51822 is so easy to be damaged?</title><link>https://devzone.nordicsemi.com/thread/4259?ContentTypeID=1</link><pubDate>Wed, 13 Nov 2013 01:48:25 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d208a04d-edb1-42f8-b968-f6a06e587315</guid><dc:creator>Dan</dc:creator><description>&lt;p&gt;Hi Juha
Thank you for your answer,I save my board successly according to your method.&lt;/p&gt;
&lt;p&gt;best regards&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf51822 is so easy to be damaged?</title><link>https://devzone.nordicsemi.com/thread/4262?ContentTypeID=1</link><pubDate>Tue, 12 Nov 2013 12:38:08 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9be92c26-5152-4a31-8b85-7a5e756d98ff</guid><dc:creator>Juha Okkonen</dc:creator><description>&lt;p&gt;Luckily there is easier way to reset chip.
Run JLink Commander ( JLink.exe ) and in it&amp;#39;s command window give following commands;
si 1
r
h
w4 4001e504 2
w4 4001e50C 1
w4 4001e514 1
r&lt;/p&gt;
&lt;p&gt;That reset&amp;#39;s whole flash, so you need to program Softdevice again, if you have one.
Håkon, with what commands could we erase application only??&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf51822 is so easy to be damaged?</title><link>https://devzone.nordicsemi.com/thread/4260?ContentTypeID=1</link><pubDate>Tue, 12 Nov 2013 10:14:56 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:8a85d012-000e-4ac9-9c91-e365e9947d18</guid><dc:creator>H&amp;#229;kon Alseth</dc:creator><description>&lt;p&gt;As Juha says, you are most likely in a reset-loop due to assertions in your application.
I&amp;#39;ve done this a couple of times myself, and you will just have to try different combinations of power-cycling and running &amp;quot;--recover&amp;quot;.&lt;/p&gt;
&lt;p&gt;Create a batch file similar to this:
:run
nrfjprog.exe --snr XXXXXXXX --recover
ping -n 2 127.0.0.1
goto run&lt;/p&gt;
&lt;p&gt;Note that the ping is just to add a 1 sec delay.&lt;/p&gt;
&lt;p&gt;BR
Håkon&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf51822 is so easy to be damaged?</title><link>https://devzone.nordicsemi.com/thread/4255?ContentTypeID=1</link><pubDate>Tue, 12 Nov 2013 10:00:39 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:94183838-7815-4f8c-96d5-a5cb383e58c3</guid><dc:creator>Juha Okkonen</dc:creator><description>&lt;p&gt;I have identical behaviour caused by processor resetting at 44Hz.
This reset is caused by SW bug I&amp;#39;m unable to debug.&lt;/p&gt;
&lt;p&gt;I think reset comes too fast for the Segger to do anything useful with default settings.
It seems to me that some simpler halt or erase operation is needed to break vicious cycle of resets.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf51822 is so easy to be damaged?</title><link>https://devzone.nordicsemi.com/thread/4257?ContentTypeID=1</link><pubDate>Tue, 12 Nov 2013 02:27:29 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d28164b6-80d0-4122-8daf-5e8ce9a33387</guid><dc:creator>Your Name</dc:creator><description>&lt;p&gt;Hi
thanks for you reply,I am trying recover in nrfgo studio.but it gave me the infomation is as below:
Could not read AHB-AP Id,Could not cnonect to target.&lt;/p&gt;
&lt;p&gt;Running application C:/DOCUME~1/dan.sun/LOCALS~1/Temp/nrf51Studio/nrfjprog.exe --snr 518002423 --recover
System off disabled until pin reset or power on reset is done.
ERROR: An error occurred while connecting to the device&lt;/p&gt;
&lt;p&gt;I tried from command line
nrfjprog --recover
it prompt&amp;quot;
Applying pin reset if debugger is not active
System off disabled unti pin reset or power on reset is done
Halting device.
ERROR: Cannot connect to the nRF51 device&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nrf51822 is so easy to be damaged?</title><link>https://devzone.nordicsemi.com/thread/4256?ContentTypeID=1</link><pubDate>Mon, 11 Nov 2013 14:35:57 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ff322dd1-7a71-4fb8-8ba4-0d36fcfa989e</guid><dc:creator>H&amp;#229;kon Alseth</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Most likely, your device has gone into systemoff mode, and in this mode the debugger interface is detached.&lt;/p&gt;
&lt;p&gt;Try using nrfjprog from the command line to recover the device:
nrfjprog --recover&lt;/p&gt;
&lt;p&gt;If you used the nRF51 SDK installer, then nrfjprog should be located in your windows PATH (you can call it from where-ever).&lt;/p&gt;
&lt;p&gt;Best regards
Håkon&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>