<?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>nRF Connect Programmer v2.3.3 fails to detect nRF5340dk board</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/85644/nrf-connect-programmer-v2-3-3-fails-to-detect-nrf5340dk-board</link><description>Hi to All Colleagues: 
 New to Nordic and its development platform. Finished installing required tools using nRF Connect for Desktop v3.10.0. Attempting to use nRF Connect Programmer v2.3.3 to download the Heart Rate Monitor (HRM) demo application as</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 14 Mar 2022 14:00:34 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/85644/nrf-connect-programmer-v2-3-3-fails-to-detect-nrf5340dk-board" /><item><title>RE: nRF Connect Programmer v2.3.3 fails to detect nRF5340dk board</title><link>https://devzone.nordicsemi.com/thread/357969?ContentTypeID=1</link><pubDate>Mon, 14 Mar 2022 14:00:34 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:1483c85a-7ca0-4e35-9fda-94c36ba7943e</guid><dc:creator>dejans</dc:creator><description>&lt;p&gt;Hi Claudio,&lt;/p&gt;
&lt;p&gt;Which Windows version are you using?&lt;/p&gt;
[quote user="calvizuri"]&amp;quot;C:\Users\XXX\AppData\Local\Programs\nrfconnect\nRF Connect for Desktop.exe&amp;quot; --args --open-official-app pc-nrfconnect-programmer --source &amp;quot;official&amp;quot;[/quote]
&lt;p&gt;Is there any special reason why you would need to open Programmer in one command? You should open the nRF Connect Programmer application from nRF Connect for Desktop.&amp;nbsp;&lt;br /&gt;&lt;br /&gt;Best regards,&lt;br /&gt;Dejan&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF Connect Programmer v2.3.3 fails to detect nRF5340dk board</title><link>https://devzone.nordicsemi.com/thread/357747?ContentTypeID=1</link><pubDate>Fri, 11 Mar 2022 17:19:40 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e9e5b92d-ba12-4949-89c0-52343bff4084</guid><dc:creator>Claudius</dc:creator><description>&lt;p&gt;Hi Dejan,&lt;/p&gt;
&lt;p&gt;1. Here is the link:&lt;/p&gt;
&lt;p&gt;&lt;a href="https://infocenter.nordicsemi.com/index.jsp?topic=%2Fug_gsg_ncs%2FUG%2Fgsg%2Ffirst_test.html"&gt;https://infocenter.nordicsemi.com/index.jsp?topic=%2Fug_gsg_ncs%2FUG%2Fgsg%2Ffirst_test.html&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;2. We are aware of the video support, but will rather not get into the effort of learning a new tool until we can at least verify we can load pre-compiled code into our Dev Kits. The fact that the SEGGER ES tool detects the target indicates to us that there is something going on with the nRF Connect Programmer installation. We have re-installed it with same results. &lt;/p&gt;
&lt;p&gt;3. We executed the proposed commands and they did have an effect. Once executed, we got access to the CPU registers, see below:&lt;/p&gt;
&lt;p&gt;C:\Users\XXX&amp;gt;nrfjprog --readregs&lt;br /&gt;R0: 0x00000000&lt;br /&gt;R1: 0x00000000&lt;br /&gt;R2: 0x00000000&lt;br /&gt;R3: 0x00000000&lt;br /&gt;R4: 0x00000000&lt;br /&gt;R5: 0x00000000&lt;br /&gt;R6: 0x00000000&lt;br /&gt;R7: 0x00000000&lt;br /&gt;R8: 0xFFFFFFFF&lt;br /&gt;R9: 0xFFFFFFFF&lt;br /&gt;R10: 0xFFFFFFFF&lt;br /&gt;R11: 0xFFFFFFFF&lt;br /&gt;R12: 0xFFFFFFFF&lt;br /&gt;SP: 0xFFFFFFFC&lt;br /&gt;LR: 0xFFFFFFFF&lt;br /&gt;PC: 0xFFFFFFFE&lt;br /&gt;xPSR: 0xF9000000&lt;br /&gt;MSP: 0xFFFFFFFC&lt;br /&gt;PSP: 0x00000000&lt;/p&gt;
&lt;p&gt;But even after this, the nRF Connect Programmer application fails to detect the board. Are there any configuration settings for this tool that we might have missed?&lt;/p&gt;
&lt;p&gt;4. This is the shortcut installed on our system to invoke the programmer:&lt;/p&gt;
&lt;p&gt;&amp;quot;C:\Users\XXX\AppData\Local\Programs\nrfconnect\nRF Connect for Desktop.exe&amp;quot; --args --open-official-app pc-nrfconnect-programmer --source &amp;quot;official&amp;quot;&lt;/p&gt;
&lt;p&gt;Is this the correct shortcut/parameters?&lt;/p&gt;
&lt;p&gt;5. Every time the Dev Kit is connected to the computer, the computer detects the device as an external drive as shown below:&lt;/p&gt;
&lt;p&gt;&lt;img src="https://devzone.nordicsemi.com/resized-image/__size/320x240/__key/communityserver-discussions-components-files/4/pastedimage1647018781300v1.png" alt=" " /&gt;&lt;/p&gt;
&lt;p&gt;Thanks for your help, best regards&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Claudio&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF Connect Programmer v2.3.3 fails to detect nRF5340dk board</title><link>https://devzone.nordicsemi.com/thread/357702?ContentTypeID=1</link><pubDate>Fri, 11 Mar 2022 14:26:49 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:2650e0b1-fbed-4999-a122-e8fc2e293de6</guid><dc:creator>dejans</dc:creator><description>&lt;p&gt;Hi Claudio,&lt;br /&gt;&lt;br /&gt;Looking at your original post&lt;/p&gt;
[quote user=""]Attempting to use nRF Connect Programmer v2.3.3 to download the Heart Rate Monitor (HRM) demo application as recommended on&amp;nbsp; &amp;quot;Running a first test&amp;quot;[/quote]
&lt;p&gt;What is &amp;quot;Running a first test&amp;quot;? Can you provide a link?&lt;br /&gt;&lt;br /&gt;&lt;/p&gt;
[quote user="calvizuri"]We have VS Code installed, but not familiar with it. [/quote]
&lt;p&gt;We have video tutorials that can help you familiarize with nRF extension for VS Code.&amp;nbsp; Since you have VS code already installed, you can follow the video tutorial &lt;a href="https://www.youtube.com/watch?v=2cv_jjqk5hg"&gt;nRF Connect for VS Code installation&lt;/a&gt; to install nRF Connect extension for VS Code. You can find more video tutorials &lt;a href="https://www.youtube.com/watch?v=2cv_jjqk5hg"&gt;here&lt;/a&gt;.&lt;br /&gt;&lt;br /&gt;&lt;/p&gt;
[quote user="calvizuri"]We followed the recommended sequence of commands, didn&amp;#39;t correct the situation. [/quote]
&lt;p&gt;These are proper commands, so this might not be an issue. You could however, try to restart the device to see if it helps. &lt;br /&gt;&lt;br /&gt;Best regards,&lt;br /&gt;Dejan&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF Connect Programmer v2.3.3 fails to detect nRF5340dk board</title><link>https://devzone.nordicsemi.com/thread/357497?ContentTypeID=1</link><pubDate>Thu, 10 Mar 2022 16:31:43 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:36f948fb-fb13-4cd9-92e9-348d8d18aa4b</guid><dc:creator>Claudius</dc:creator><description>&lt;p&gt;Hi Dejan,&lt;/p&gt;
&lt;p&gt;Here are our answers:&lt;/p&gt;
&lt;p&gt;1. Yes, we have a second dk board, and when exercised we get the same results.&lt;/p&gt;
&lt;p&gt;2. We have VS Code installed, but not familiar with it. We can connect to the device using Segger Embedded Studio.&lt;/p&gt;
&lt;p&gt;&lt;img src="https://devzone.nordicsemi.com/resized-image/__size/320x240/__key/communityserver-discussions-components-files/4/pastedimage1646929589546v1.png" alt=" " /&gt;&lt;/p&gt;
&lt;p&gt;3. We followed the recommended sequence of commands, didn&amp;#39;t correct the situation. &lt;/p&gt;
&lt;p&gt;C:\Users\***&amp;gt;nrfjprog --recover --coprocessor CP_NETWORK&lt;br /&gt;Recovering device. This operation might take 30s.&lt;br /&gt;Writing image to disable ap protect.&lt;br /&gt;Erasing user code and UICR flash areas.&lt;/p&gt;
&lt;p&gt;C:\Users\***&amp;gt;nrfjprog --recover&lt;br /&gt;Recovering device. This operation might take 30s.&lt;br /&gt;Writing image to disable ap protect.&lt;br /&gt;Erasing user code and UICR flash areas.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Claudio&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF Connect Programmer v2.3.3 fails to detect nRF5340dk board</title><link>https://devzone.nordicsemi.com/thread/357429?ContentTypeID=1</link><pubDate>Thu, 10 Mar 2022 14:00:55 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9dec20d2-64c1-4a4f-af6a-2d0320dda70f</guid><dc:creator>dejans</dc:creator><description>&lt;p&gt;Hi Claudio,&lt;br /&gt;&lt;br /&gt;Do you have a spare board of the same type to check if the results that you are getting are the same for both boards?&lt;br /&gt;Can you connect to the device from VS Code? Can device be found in the list of connected devices in VS Code?&lt;br /&gt;&lt;br /&gt;&lt;/p&gt;
[quote user=""] issuing a &amp;quot;nrfjprog --recover&amp;quot;[/quote]
&lt;p&gt;Based on&amp;nbsp;&lt;a href="https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/ug_nrf5340.html?highlight=nrfjprog"&gt;nrfjprog documentation&lt;/a&gt;, the correct way to recover would be to first recover the network core and then the application core:&lt;br /&gt;nrfjprog --recover --coprocessor CP_NETWORK&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;br /&gt;nrfjprog --recover&lt;br /&gt;&lt;br /&gt;Best regards,&lt;br /&gt;Dejan&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>