<?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>Couldn&amp;#39;t Flash firmware form VS code to new NRF52840DK</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/102474/couldn-t-flash-firmware-form-vs-code-to-new-nrf52840dk</link><description>Hello, 
 I bought brand new 2 Nrf52840 Development boards lately. But Visual Studio Code gives error : 
 &amp;quot; error] [SeggerBackend] - JLinkARM.dll reported &amp;quot;-1&amp;quot;, &amp;quot;An unknown error.&amp;quot;.ERROR: JLinkARM DLL reported an error. Try again. If error condition ERROR</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 03 Aug 2023 17:12:23 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/102474/couldn-t-flash-firmware-form-vs-code-to-new-nrf52840dk" /><item><title>RE: Couldn't Flash firmware form VS code to new NRF52840DK</title><link>https://devzone.nordicsemi.com/thread/439766?ContentTypeID=1</link><pubDate>Thu, 03 Aug 2023 17:12:23 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5a2a50c7-7bf3-4151-95df-35626fdcce05</guid><dc:creator>Raoul</dc:creator><description>&lt;p&gt;Hi Gan,&lt;/p&gt;
&lt;p&gt;Please see this case: &amp;nbsp;&lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/78059/problem-with-nrfjprog"&gt;Problem with nrfjprog&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Could you try running nrfjprog --recover? Hopefully that solves it.&lt;/p&gt;
&lt;p&gt;If not, are you using the on-board debugger, or an external one? For customers using external debuggers, this issue is often caused by SWD lines or power being connected wrongly.&lt;/p&gt;
&lt;p&gt;Customers report this from time to time, they usually find out that they made some mistake:&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/87006/jlinkarm-dll-returns--1-repeatedly-using-nrf52840-on-a-custom-development-board"&gt;JlinkARM.dll returns &amp;#39;-1&amp;#39; repeatedly, using nRF52840 on a custom development board&lt;/a&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/91047/issues-flashing-nrf52840"&gt;Issues Flashing nrf52840&lt;/a&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/83070/no-longer-able-to-program-custom-nrf52840-over-swd-no-idcode-detected"&gt;No longer able to program custom nRF52840 over SWD. No idcode detected&lt;/a&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/68790/jlinkarm-dll-reported--1-an-unknown-error"&gt;JLinkARM.dll reported &amp;quot;-1&amp;quot;, an unknown error&lt;/a&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/84080/jlinkarm-dll-reported--1-an-unknown-error"&gt;JLinkARM.dll reported &amp;quot;-1&amp;quot;, an unknown error&lt;/a&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;a href="https://devzone.nordicsemi.com/f/nordic-q-a/81247/cannot-recover-nrf9160-jlinkarm-dll-reported--1"&gt;Cannot recover nrf9160, JLinkARM.dll reported -1&lt;/a&gt; &lt;/p&gt;
&lt;p&gt;In some cases the interface MCU (Onboard debugger) is just faulty. Let us know if you think that&amp;#39;s the case.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Raoul&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>