https://devzone.nordicsemi.com/f/nordic-q-a/41131/recover-nrf52dk-bootloaderOS: Ubuntu 18. Board: nrf52-DK, PCA10040 (1.2.4) It worked well, I flashed as blink or BLE firmwares and may saw the results. I re-flashed Bootloader from nrf52-DK (by press reboot button &amp; drag&amp;drop some firmware) Currently, my PC can&#39;t recognizeen-USTelligent Community 13Wed, 14 Feb 2024 14:16:13 GMThttps://devzone.nordicsemi.com/thread/468848?ContentTypeID=1Wed, 14 Feb 2024 14:16:13 GMT137ad170-7792-4731-bb38-c0d22fbe4515:e1b4ef4a-0280-4838-864b-59de8904fa28julian24<p>Hello,</p> <p>Did you ever manage to solve this? I&#39;m having a similar issue</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/159919?ContentTypeID=1Mon, 03 Dec 2018 10:06:21 GMT137ad170-7792-4731-bb38-c0d22fbe4515:b552dda4-0c1e-4e76-953a-aabe69053088Einar Thorsrud<p>Hi,</p> <p>Pressing the reset button while power-cycling the DK puts the onboard debugger / interface MCU in DFU mode, and that is typically not something you ever need to do (unless you want to switch between mbed and jlink). Which firmware did you program to the interface MCU? You can try to recover by programming with this attached firmware (<a href="https://devzone.nordicsemi.com/cfs-file/__key/support-attachments/beef5d1b77644c448dabff31668f3a47-5c062b62a6e54333880250d3425304f6/3566.J_2D00_Link-OB_2D00_SAM3U128_2D00_V2_2D00_NordicSemi-160315.bin">devzone.nordicsemi.com/.../3566.J_2D00_Link-OB_2D00_SAM3U128_2D00_V2_2D00_NordicSemi-160315.bin</a>) in the same way as you did before (pressing reset while power-cycling, then copying to the removable drive).</p><div style="clear:both;"></div>