<?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>nRF52 DK Programmer issue, cannot reprogram the nRF5340 programmer of the nRF52 DK</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/127809/nrf52-dk-programmer-issue-cannot-reprogram-the-nrf5340-programmer-of-the-nrf52-dk</link><description>Hi, 
 I had some issue with my nRF52 DK PCA10040 v3.0.3, The programmer was totally unreachable also with the simplest terminal command so I tried to reprogram it trough hidden J13 Tag-Connect TC2050 just under the &amp;quot; PCA10040 v3.0.3&amp;quot; lable. 
 I was able</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Thu, 16 Apr 2026 12:49:21 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/127809/nrf52-dk-programmer-issue-cannot-reprogram-the-nrf5340-programmer-of-the-nrf52-dk" /><item><title>RE: nRF52 DK Programmer issue, cannot reprogram the nRF5340 programmer of the nRF52 DK</title><link>https://devzone.nordicsemi.com/thread/565037?ContentTypeID=1</link><pubDate>Thu, 16 Apr 2026 12:49:21 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:f288a86f-b597-479a-8a19-1f261ca989d9</guid><dc:creator>simosilva</dc:creator><description>&lt;p&gt;With the configurator no jlink other than the external jlink-ultra that&amp;nbsp;I had was visible.&lt;br /&gt;I guess we will never know.&lt;br /&gt;Thank you, bye bye.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF52 DK Programmer issue, cannot reprogram the nRF5340 programmer of the nRF52 DK</title><link>https://devzone.nordicsemi.com/thread/565033?ContentTypeID=1</link><pubDate>Thu, 16 Apr 2026 12:33:23 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:77790691-644e-405c-805d-571eb5e0c519</guid><dc:creator>Einar Thorsrud</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;That depends on what the original problem was, but that is not possible to debug now. Generally, you should never have to erase the onboard debugger. (If there is a problem with it and it needs to be updated, that can be done via the J-Link Configurator application, which then depends on the bootloader being present).&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF52 DK Programmer issue, cannot reprogram the nRF5340 programmer of the nRF52 DK</title><link>https://devzone.nordicsemi.com/thread/565031?ContentTypeID=1</link><pubDate>Thu, 16 Apr 2026 12:24:10 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0cdd8354-32e8-426c-96f2-4f5835e277ce</guid><dc:creator>simosilva</dc:creator><description>&lt;p&gt;Hi Einard thanks for the reply,&lt;/p&gt;
&lt;p&gt;So what would have been the correct process to do to not-erase completely the DK but be able to resuscitate the programmer that I couln&amp;#39;t see in any possible way with my pc?&lt;br /&gt;that will be helpful for (hopefully not) next time.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: nRF52 DK Programmer issue, cannot reprogram the nRF5340 programmer of the nRF52 DK</title><link>https://devzone.nordicsemi.com/thread/565028?ContentTypeID=1</link><pubDate>Thu, 16 Apr 2026 11:40:17 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:8bb9f149-c5cd-48df-b588-92bb70535601</guid><dc:creator>Einar Thorsrud</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;The onboard debugger is not user re-programmable. It contains a unique serial number and bootloader, which is not part of the hex file you found in the J-Link installation (JLink_OB_nRF5340_NordicSemi.bin). When you fully erased the onboard debugger that was lost, and you will need to replace the DK.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>