<?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>nRFgo Studio: No device detected and the Recover button greyed</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/8281/nrfgo-studio-no-device-detected-and-the-recover-button-greyed</link><description>The nRFgo Studio showed &amp;quot;No device detected&amp;quot; when the nRF51-DK board was plugged to the USB port. And the Recover button was greyed. 
 When the board was plugged in, nRFgo Studio detected the Segger device and the correct Segger ID. The green LED next</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Tue, 21 Jul 2015 01:54:57 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/8281/nrfgo-studio-no-device-detected-and-the-recover-button-greyed" /><item><title>RE: nRFgo Studio: No device detected and the Recover button greyed</title><link>https://devzone.nordicsemi.com/thread/29873?ContentTypeID=1</link><pubDate>Tue, 21 Jul 2015 01:54:57 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2c5b294a-fd5d-4108-8c4d-0b6cbdd25c5c</guid><dc:creator>Johnson</dc:creator><description>&lt;p&gt;I worked out what was wrong -&amp;gt; I was an idiot!&lt;/p&gt;
&lt;p&gt;I cut SB9 and placed a 10 Ohm resistor on R6 a long time ago. Recently, the resistor was removed and so no current was going to VDD_nRF.&lt;/p&gt;
&lt;p&gt;After placing a jumper across the 2-pin header (P22), nRFgo Studio could detect the chip again.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRFgo Studio: No device detected and the Recover button greyed</title><link>https://devzone.nordicsemi.com/thread/29872?ContentTypeID=1</link><pubDate>Mon, 20 Jul 2015 13:42:28 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e09d7034-98ec-427d-8567-6976f7eac31c</guid><dc:creator>Susheel Nuguru</dc:creator><description>&lt;p&gt;use the command tool nrfjprog and try if any of the below commands work&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;nrfjprog.exe -e
2)nrfjprog.exe --recover&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;If 1) works, you do not need to do the step 2)&lt;/p&gt;
&lt;p&gt;if none of them work, then probably you have interrupted the segger firmware update.
in that case , uninstall jlink software from your computer , go to segger and download the latest jlink driver for chip.
again go to command line and type&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;nrfjprog -i&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;when it prompts you to update firmware on the chip, select ok.
It normally helps if you skip when windows is &amp;quot;Searching driver in the windows update&amp;quot; as this will make the firmware upgrade timeout.&lt;/p&gt;
&lt;p&gt;It is not very easy to destroy the chip by one wrong flash.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>