<?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>Bricked PCA10056 nrf52840 DK</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/121952/bricked-pca10056-nrf52840-dk</link><description>I have recently bought two nrf52840dk, version 3.0.0, unboxed and plugged into usb. One would show up with a usb storage on the side and in vscode a J-link window prompted for a device update on the interface nrf5340 chip on the dk, but the other one</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 09 Jul 2025 07:30:06 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/121952/bricked-pca10056-nrf52840-dk" /><item><title>RE: Bricked PCA10056 nrf52840 DK</title><link>https://devzone.nordicsemi.com/thread/541876?ContentTypeID=1</link><pubDate>Wed, 09 Jul 2025 07:30:06 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:9e8b9d13-a513-40bf-a80c-33cac4647273</guid><dc:creator>cheston2</dc:creator><description>&lt;p&gt;Fresh eyes always works!&lt;/p&gt;
&lt;p&gt;I got inspiration from the jlink homepage (&lt;a id="" href="https://www.segger.com/products/debug-probes/j-link/tools/j-link-commander/"&gt;https://www.segger.com/products/debug-probes/j-link/tools/j-link-commander/&lt;/a&gt;) and ran&lt;/p&gt;
&lt;p&gt;./opt/SEGGER/JLink/JLinkExe&lt;/p&gt;
&lt;p&gt;It immediately brought up a prompt and told me its firmware needs refreshing. After that it works like the other DK.&lt;/p&gt;
&lt;p&gt;Cheston&lt;/p&gt;
&lt;p&gt;&lt;br /&gt;cheston@cheston:/opt/SEGGER/JLink$ ls&lt;br /&gt;DDConditionerExe&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; JLinkRegistration&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;JScopeExe&lt;br /&gt;DevProExe&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;JLinkRegistrationExe&amp;nbsp; &amp;nbsp; JTAGLoadExe&lt;br /&gt;Doc&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;JLinkRemoteServer&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;libjlinkarm.so&lt;br /&gt;ETC&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;JLinkRemoteServerCLExe&amp;nbsp; libjlinkarm.so.8Ran&amp;nbsp;&lt;br /&gt;Firmwares&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;JLinkRemoteServerExe&amp;nbsp; &amp;nbsp; libjlinkarm.so.8.18.0&lt;br /&gt;GDBServer&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;JLinkRTTClient&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; libjlinkarm_x86.so&lt;br /&gt;JFlashExe&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;JLinkRTTClientExe&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;libjlinkarm_x86.so.8&lt;br /&gt;JFlashLiteExe&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;JLinkRTTLogger&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; libjlinkarm_x86.so.8.18.0&lt;br /&gt;JFlashSPI_CL&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; JLinkRTTLoggerExe&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;libQtCore.so&lt;br /&gt;JFlashSPICLExe&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; JLinkRTTViewerExe&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;libQtCore.so.4&lt;br /&gt;JFlashSPIExe&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; JLinkSTM32&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; libQtCore.so.4.8&lt;br /&gt;JLinkConfigExe&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; JLinkSTM32Exe&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;libQtCore.so.4.8.7&lt;br /&gt;JLinkExe&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; JLinkSWOViewer&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; libQtGui.so&lt;br /&gt;JLinkGDBServer&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; JLinkSWOViewerCLExe&amp;nbsp; &amp;nbsp; &amp;nbsp;libQtGui.so.4&lt;br /&gt;JLinkGDBServerCLExe&amp;nbsp; &amp;nbsp; &amp;nbsp;JLinkSWOViewerExe&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;libQtGui.so.4.8&lt;br /&gt;JLinkGDBServerExe&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;JLinkUSBWebServerExe&amp;nbsp; &amp;nbsp; libQtGui.so.4.8.7&lt;br /&gt;JLinkGUIServerExe&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;JLinkXVCDServerExe&amp;nbsp; &amp;nbsp; &amp;nbsp; Samples&lt;br /&gt;JLinkLicenseManager&amp;nbsp; &amp;nbsp; &amp;nbsp;JMemExe&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;Script&lt;br /&gt;JLinkLicenseManagerExe&amp;nbsp; JRunExe&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;x86&lt;br /&gt;cheston@cheston:/opt/SEGGER/JLink$ ./JLinkExe&lt;br /&gt;SEGGER J-Link Commander V8.18 (Compiled Mar&amp;nbsp; 5 2025 14:47:32)&lt;br /&gt;DLL version V8.18, compiled Mar&amp;nbsp; 5 2025 14:46:29&lt;br /&gt;&lt;br /&gt;Connecting to J-Link via USB...Updating firmware:&amp;nbsp; J-Link OB-nRF5340-NordicSemi compiled Feb 11 2025 17:15:35&lt;br /&gt;Replacing firmware: J-Link OB-nRF5340-NordicSemi compiled May 18 2021 BTL&amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;br /&gt;Waiting for new firmware to boot&lt;br /&gt;New firmware booted successfully&lt;br /&gt;O.K.&lt;br /&gt;Firmware: J-Link OB-nRF5340-NordicSemi compiled Feb 11 2025 17:15:35&lt;br /&gt;Hardware version: V1.00&lt;br /&gt;J-Link uptime (since boot): 0d 00h 00m 00s&lt;br /&gt;S/N: 1050261048&lt;br /&gt;License(s): RDI, FlashBP, FlashDL, JFlash, GDB&lt;br /&gt;USB speed mode: Full speed (12 MBit/s)&lt;br /&gt;VTref=3.300V&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Type &amp;quot;connect&amp;quot; to establish a target connection, &amp;#39;?&amp;#39; for help&lt;br /&gt;J-Link&amp;gt;&lt;br /&gt;&lt;br /&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Bricked PCA10056 nrf52840 DK</title><link>https://devzone.nordicsemi.com/thread/541867?ContentTypeID=1</link><pubDate>Wed, 09 Jul 2025 06:42:36 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:d89dc289-a62c-43a4-9091-47e0813fd0d1</guid><dc:creator>cheston2</dc:creator><description>&lt;p&gt;I finally have time to come back to try fixing. So I have nRF Connect for desktop installed and ran Quick Start 1.3.&lt;/p&gt;
&lt;p&gt;Interesting to see that it can still be recognised as a nrf52840 DK but it will not go anywhere.&lt;/p&gt;
&lt;p&gt;Does the log ring any bell?&lt;/p&gt;
&lt;p&gt;2025-07-09T06:36:42.644Z INFO Initialising the bundled nrfutil device&lt;br /&gt;2025-07-09T06:36:42.658Z DEBUG Started watching devices&lt;br /&gt;2025-07-09T06:36:48.980Z INFO Using the bundled core version for nrfutil device: 8.0.0&lt;br /&gt;2025-07-09T06:36:49.054Z DEBUG Selected device: nRF52840 DK&lt;br /&gt;2025-07-09T06:36:49.094Z DEBUG Changed step: Info&lt;br /&gt;2025-07-09T06:36:49.095Z INFO Using nrfutil-device version: 2.10.2&lt;br /&gt;2025-07-09T06:36:49.096Z INFO Using nrf-device-lib version: 0.17.71&lt;br /&gt;2025-07-09T06:36:49.096Z INFO Using nrf-probe version: 0.38.0&lt;br /&gt;2025-07-09T06:36:49.096Z INFO Using JLink version: JLink_V8.18&lt;br /&gt;2025-07-09T06:37:59.285Z DEBUG Changed step: Rename&lt;br /&gt;2025-07-09T06:38:01.593Z DEBUG Changed step: Info&lt;br /&gt;2025-07-09T06:38:04.841Z DEBUG Changed step: Rename&lt;br /&gt;2025-07-09T06:38:06.285Z DEBUG Changed step: Program&lt;br /&gt;2025-07-09T06:38:18.973Z ERROR [ProbeLib] [2025-07-09 06:38:18.955244Z] Failed to initialize worker: Timed out waiting for response from worker.&lt;br /&gt;2025-07-09T06:38:23.142Z ERROR [ProbeLib] [2025-07-09 06:38:23.141505Z] Trace channel disconnected unexpectedly.&lt;br /&gt;2025-07-09T06:38:23.143Z ERROR [ProbeLib] [2025-07-09 06:38:23.142954Z] Worker terminated by signal 9.&lt;br /&gt;2025-07-09T06:38:23.143Z ERROR [ProbeLib] [2025-07-09 06:38:23.143028Z] Error output of terminated worker:&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Bricked PCA10056 nrf52840 DK</title><link>https://devzone.nordicsemi.com/thread/539074?ContentTypeID=1</link><pubDate>Thu, 12 Jun 2025 14:14:39 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a988220b-681a-4326-8655-a4e577f5549a</guid><dc:creator>cheston2</dc:creator><description>&lt;p&gt;I installed linux version of &lt;a id="" href="https://www.nordicsemi.com/Products/Development-tools/nRF-Command-Line-Tools/Download"&gt;https://www.nordicsemi.com/Products/Development-tools/nRF-Command-Line-Tools/Download&lt;/a&gt;&amp;nbsp;but am having trouble getting&amp;nbsp;nrfjprog command to work. I&amp;#39;ll try the rest a few days later. Thank you.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Bricked PCA10056 nrf52840 DK</title><link>https://devzone.nordicsemi.com/thread/539071?ContentTypeID=1</link><pubDate>Thu, 12 Jun 2025 14:03:30 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:5b309034-94f6-4263-bceb-1fdf59779400</guid><dc:creator>Sigurd Hellesvik</dc:creator><description>&lt;p&gt;Im just throwing suggestions at you right now, and hoping that maybe one of them works eventually.&lt;/p&gt;
&lt;p&gt;After nrfjprog --reset, can you install nRF Connect For Dekstop and then open the Device Configurator application? Then see if that works at all&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Bricked PCA10056 nrf52840 DK</title><link>https://devzone.nordicsemi.com/thread/539069?ContentTypeID=1</link><pubDate>Thu, 12 Jun 2025 13:54:51 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:24083367-a9c0-4e6d-933a-dd6b5f458834</guid><dc:creator>cheston2</dc:creator><description>&lt;p&gt;I only have one usb cable and am using it with the working one (top). Bottom is not working.&lt;/p&gt;
&lt;p&gt;&lt;img style="max-height:240px;max-width:320px;" alt=" " src="https://devzone.nordicsemi.com/resized-image/__size/640x480/__key/communityserver-discussions-components-files/4/IMG_5F00_6955.jpg" /&gt;&amp;nbsp;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Bricked PCA10056 nrf52840 DK</title><link>https://devzone.nordicsemi.com/thread/539066?ContentTypeID=1</link><pubDate>Thu, 12 Jun 2025 13:45:47 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:e9fc5d14-1b2a-4b96-af1f-336c4a6431e2</guid><dc:creator>Sigurd Hellesvik</dc:creator><description>[quote user="cheston2"]Is there not a way to revive it by any button?[/quote]
&lt;p&gt;Not other than the trick I told you in my first comment no.&lt;/p&gt;
[quote user="cheston2"]Also I notice that the DK reset itself after this spin. Does it tell anything?[/quote]
&lt;p&gt;This looks interesting. Can you try &amp;quot;nrfjrprog --reset&amp;quot;?&lt;/p&gt;
&lt;p&gt;Also, it could be the USB cable. Have you tried the same USB cable with both DKs?&lt;/p&gt;
&lt;p&gt;Can you send an image of the non-working DK?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Bricked PCA10056 nrf52840 DK</title><link>https://devzone.nordicsemi.com/thread/539052?ContentTypeID=1</link><pubDate>Thu, 12 Jun 2025 13:01:01 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:77fd7f5f-ae50-4823-bb79-a7efd31859d1</guid><dc:creator>cheston2</dc:creator><description>&lt;p&gt;I don&amp;#39;t think thats possible as I bought as part of a batch of corporate purchase.&lt;/p&gt;
&lt;p&gt;Is there not a way to revive it by any button?&lt;/p&gt;
&lt;p&gt;Also I notice that the DK reset itself after this spin. Does it tell anything?&lt;/p&gt;
[quote userid="145942" url="~/f/nordic-q-a/121952/bricked-pca10056-nrf52840-dk"]&lt;img style="max-height:240px;max-width:320px;cursor:zoom-in;" src="https://devzone.nordicsemi.com/resized-image/__size/640x480/__key/communityserver-discussions-components-files/4/pastedimage1748854951551v1.png" alt=" " /&gt;[/quote]&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Bricked PCA10056 nrf52840 DK</title><link>https://devzone.nordicsemi.com/thread/539034?ContentTypeID=1</link><pubDate>Thu, 12 Jun 2025 12:25:47 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:147ff7f1-d4b8-4429-abab-b93a728e6d48</guid><dc:creator>Sigurd Hellesvik</dc:creator><description>&lt;p&gt;In this case, it looks like you have received a defect Developement Kit.&lt;/p&gt;
&lt;p&gt;Can you try to contact the supplier from where you got it and get a replacement?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Bricked PCA10056 nrf52840 DK</title><link>https://devzone.nordicsemi.com/thread/539027?ContentTypeID=1</link><pubDate>Thu, 12 Jun 2025 12:09:09 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:c6d862e1-5f2b-4726-b4f2-c04bda450d23</guid><dc:creator>cheston2</dc:creator><description>&lt;p&gt;It can&amp;#39;t even be connected...&lt;br /&gt;$ nrfutil device recover&lt;br /&gt;&lt;span class="emoticon" data-url="https://devzone.nordicsemi.com/cfs-file/__key/system/emoji/274c.svg" title="X"&gt;&amp;#x274c;&lt;/span&gt;&amp;nbsp;Failed to recover 1050261048, Timed out waiting for response from worker.&lt;br /&gt;Error: One or more recover tasks failed:&lt;br /&gt;&amp;nbsp;* 1050261048: Timed out waiting for response from worker. (Generic)&lt;br /&gt;&lt;br /&gt;$ nrfutil device recover&lt;br /&gt;&lt;span class="emoticon" data-url="https://devzone.nordicsemi.com/cfs-file/__key/system/emoji/274c.svg" title="X"&gt;&amp;#x274c;&lt;/span&gt;&amp;nbsp;Failed to recover 1050261048, Timed out waiting for response from worker.&lt;br /&gt;Error: One or more recover tasks failed:&lt;br /&gt;&amp;nbsp;* 1050261048: Timed out waiting for response from worker. (Generic)&lt;br /&gt;&lt;br /&gt;$ nrfutil device erase&lt;br /&gt;&lt;span class="emoticon" data-url="https://devzone.nordicsemi.com/cfs-file/__key/system/emoji/274c.svg" title="X"&gt;&amp;#x274c;&lt;/span&gt;&amp;nbsp;Failed to erase 1050261048, Timed out waiting for response from worker.&lt;br /&gt;Error: One or more erase tasks failed:&lt;br /&gt;&amp;nbsp;* 1050261048: Timed out waiting for response from worker. (Generic)&lt;br /&gt;&lt;br /&gt;$ lsusb&lt;br /&gt;...&lt;br /&gt;Bus 003 Device 027: ID 1366:0101 SEGGER J-Link PLUS&lt;br /&gt;...&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Bricked PCA10056 nrf52840 DK</title><link>https://devzone.nordicsemi.com/thread/539017?ContentTypeID=1</link><pubDate>Thu, 12 Jun 2025 11:41:54 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4377a332-cf83-429d-95c1-b8a2294e704b</guid><dc:creator>cheston2</dc:creator><description>&lt;p&gt;They turned on exactly the same way&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Bricked PCA10056 nrf52840 DK</title><link>https://devzone.nordicsemi.com/thread/538983?ContentTypeID=1</link><pubDate>Thu, 12 Jun 2025 09:23:13 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:892f4120-f638-4303-99e0-faeadb5e3903</guid><dc:creator>Sigurd Hellesvik</dc:creator><description>&lt;p&gt;Does the LED next to the interface chip light up on both DKs the same?&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Bricked PCA10056 nrf52840 DK</title><link>https://devzone.nordicsemi.com/thread/538734?ContentTypeID=1</link><pubDate>Wed, 11 Jun 2025 04:13:47 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:7c0d79e9-c7ae-4169-8692-6d7487f24337</guid><dc:creator>cheston2</dc:creator><description>&lt;p&gt;3.0.0 is the newer version. Holding reset button doesn&amp;#39;t really work. What else could I do?&lt;/p&gt;
&lt;p&gt;```&lt;br /&gt;$ lsusb&lt;br /&gt;Bus 003 Device 010: ID 1366:0101 SEGGER J-Link PLUS&lt;br /&gt;Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub&lt;br /&gt;$ nrfutil device x-update-debug-probe-firmware&lt;br /&gt;Error: One or more update debug probe firmware tasks failed:&lt;br /&gt;&amp;nbsp;* 1050261048: Timed out waiting for response from worker. (Generic)&lt;/p&gt;
&lt;p&gt;```&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Bricked PCA10056 nrf52840 DK</title><link>https://devzone.nordicsemi.com/thread/537854?ContentTypeID=1</link><pubDate>Tue, 03 Jun 2025 11:37:17 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:4fa60b27-6154-4901-bb57-d4277f6c997a</guid><dc:creator>Sigurd Hellesvik</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;We have two versions of the On-Board debugger. One with the sticker on the chip (the old one), and one with the sticker directly on the PCB (The new version).&lt;/p&gt;
&lt;p&gt;This will work for the new version, which should be the one that you got:&lt;/p&gt;
&lt;p&gt;Hold the reset button while plugging in the USB of the DK. You will see no change, but the On-Board Debugger should now be in recovery mode.&lt;/p&gt;
&lt;p&gt;Run &amp;quot;nrfutil device x-update-debug-probe-firmware&amp;quot;&lt;/p&gt;
&lt;p&gt;This should update the firmware on the On-Board Debugger. So if it is a software problem, then this should fix it.&lt;/p&gt;
&lt;p&gt;Regards,&lt;br /&gt;Sigurd Hellesvik&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>