<?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>Issue flashing firmware</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/118386/issue-flashing-firmware</link><description>Hello. 
 
 I have been successfully flashing the nrf52840 dongle using the nrfjprog comand. I have been successfully able to reset and erase as well. Recently however, none of my boards have been able to flash, erase or reset. Here is the error that it</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 09 Jun 2025 13:20:51 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/118386/issue-flashing-firmware" /><item><title>RE: Issue flashing firmware</title><link>https://devzone.nordicsemi.com/thread/538555?ContentTypeID=1</link><pubDate>Mon, 09 Jun 2025 13:20:51 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:02020a55-aabb-4e69-bdb9-6837144aa853</guid><dc:creator>Luna Harris</dc:creator><description>&lt;p data-start="73" data-end="82"&gt;Hi Colby!&lt;/p&gt;
&lt;p data-start="84" data-end="315"&gt;It sounds like you&amp;rsquo;ve run into a common issue when working with the nRF52840 dongle. The error you&amp;rsquo;re seeing (&lt;code data-start="194" data-end="234"&gt;unexpected debug port ID 0, expected 2&lt;/code&gt; and &lt;code data-start="239" data-end="270"&gt;Could not connect to CPU core&lt;/code&gt;) typically points to one of two main causes:&lt;/p&gt;
&lt;p data-start="317" data-end="560"&gt;&amp;nbsp;1. Access Port (AP) protection enabled&lt;br data-start="361" data-end="364" /&gt; This happens when the device has had AP (Access Port) protection set, preventing further debug access. To fix this, you might need to use Recover mode instead of Erase.&lt;br data-start="540" data-end="543" /&gt; Try this command:&lt;/p&gt;
&lt;div&gt;
&lt;div class="flex items-center text-token-text-secondary px-4 py-2 text-xs font-sans justify-between h-9 bg-token-sidebar-surface-primary dark:bg-token-main-surface-secondary select-none rounded-t-2xl"&gt;css&lt;/div&gt;
&lt;div class="sticky top-9"&gt;
&lt;div class="absolute end-0 bottom-0 flex h-9 items-center pe-2"&gt;
&lt;div class="bg-token-sidebar-surface-primary text-token-text-secondary dark:bg-token-main-surface-secondary flex items-center gap-4 rounded-sm px-2 font-sans text-xs"&gt;&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;div class="overflow-y-auto p-4" dir="ltr"&gt;&lt;code class="whitespace-pre!"&gt;nrfjprog &lt;span class="hljs-attr"&gt;--recover&lt;/span&gt; -f nrf52&amp;nbsp;&lt;span style="color:#ffffff;"&gt;&lt;a style="color:#ffffff;" href="https://dummynationgames.com"&gt;dummynation&lt;/a&gt;&lt;/span&gt;&lt;/code&gt;&lt;/div&gt;
&lt;/div&gt;
&lt;p data-start="599" data-end="674"&gt;This will attempt to reset the device to a state where you can re-flash it.&lt;/p&gt;
&lt;p data-start="676" data-end="731"&gt;&amp;nbsp;2. Hardware or connection issue&lt;br data-start="713" data-end="716" /&gt; Double-check:&lt;/p&gt;
&lt;ul data-start="732" data-end="975"&gt;
&lt;li data-start="732" data-end="781"&gt;
&lt;p data-start="734" data-end="781"&gt;Are your USB cables and connections reliable?&lt;/p&gt;
&lt;/li&gt;
&lt;li data-start="782" data-end="843"&gt;
&lt;p data-start="784" data-end="843"&gt;If using a debugger (like J-Link), is it firmly attached?&lt;/p&gt;
&lt;/li&gt;
&lt;li data-start="844" data-end="905"&gt;
&lt;p data-start="846" data-end="905"&gt;Try re-plugging the dongle or using a different USB port.&lt;/p&gt;
&lt;/li&gt;
&lt;li data-start="906" data-end="975"&gt;
&lt;p data-start="908" data-end="975"&gt;Consider updating your nrfjprog tool and SEGGER J-Link drivers.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p data-start="977" data-end="1048"&gt;If the above doesn&amp;rsquo;t work, enable detailed logging for further insight:&lt;/p&gt;
&lt;div&gt;
&lt;div class="flex items-center text-token-text-secondary px-4 py-2 text-xs font-sans justify-between h-9 bg-token-sidebar-surface-primary dark:bg-token-main-surface-secondary select-none rounded-t-2xl"&gt;css&lt;/div&gt;
&lt;div class="sticky top-9"&gt;
&lt;div class="absolute end-0 bottom-0 flex h-9 items-center pe-2"&gt;
&lt;div class="bg-token-sidebar-surface-primary text-token-text-secondary dark:bg-token-main-surface-secondary flex items-center gap-4 rounded-sm px-2 font-sans text-xs"&gt;&lt;/div&gt;
&lt;/div&gt;
&lt;/div&gt;
&lt;div class="overflow-y-auto p-4" dir="ltr"&gt;&lt;code class="whitespace-pre!"&gt;nrfjprog &lt;span class="hljs-attr"&gt;--recover&lt;/span&gt; -f nrf52 &lt;span class="hljs-attr"&gt;--log&lt;/span&gt;
&lt;/code&gt;&lt;/div&gt;
&lt;/div&gt;
&lt;p data-start="1093" data-end="1154"&gt;This might show you more specific clues about what&amp;rsquo;s failing.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Issue flashing firmware</title><link>https://devzone.nordicsemi.com/thread/527930?ContentTypeID=1</link><pubDate>Wed, 19 Mar 2025 04:52:02 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0d7feb4e-6668-4399-9506-ed5f2a5275d6</guid><dc:creator>benjimann</dc:creator><description>&lt;p&gt;Thank you, luckily I was able to read your comment.&lt;/p&gt;
&lt;p&gt;&lt;span style="color:#ffffff;"&gt;&lt;a style="color:#ffffff;" href="https://infinitecraftrecipes.io"&gt;infinite craft&lt;/a&gt;&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Issue flashing firmware</title><link>https://devzone.nordicsemi.com/thread/520488?ContentTypeID=1</link><pubDate>Wed, 29 Jan 2025 05:43:43 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c817f68e-11d0-49cd-b064-bb4609ed1a63</guid><dc:creator>Colby G</dc:creator><description>&lt;p&gt;Hello, thanks for getting back to me. I was using a J-Link EDU Mini to flash the boards. This had been working fine until it just stopped working with the dongles for some reason. I also have custom boards with the nRF52840 chipset which the EDU mini can still flash so it is very weird. I have managed to flash the boards however, I ended up using a J-Link Base Compact and was able to flash the boards successfully.&lt;/p&gt;
&lt;p&gt;Thanks for the assistance.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Issue flashing firmware</title><link>https://devzone.nordicsemi.com/thread/520184?ContentTypeID=1</link><pubDate>Mon, 27 Jan 2025 13:42:57 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:8b7327ad-392e-4392-87af-912ea6c67369</guid><dc:creator>Einar Thorsrud</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;I wonder if there is a problem with powering the nRF? Or that the regulator is back in 1.8 V which is the default? If so, please see the Using an external debugger in the &lt;a href="https://devzone.nordicsemi.com/guides/short-range-guides/b/getting-started/posts/nrf52840-dongle-programming-tutorial"&gt;nRF52840 Dongle Programming Tutorial&lt;/a&gt;, and particularily the last part,&amp;nbsp;Recover after an accidental UICR erase.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>