Recovering a bricked nrf52832 devkit

[Gauthier]

I entered bootloader mode (holding reset while powering up) and flashed an erroneous bin file by copying it to the mounted device in my file manager.

I suppose that to recover, I should reenter bootloader mode, and flash the appropriate bin/hex.

My question is: where can I get this file? Is it specific to this individual, since it has a serial number?

[Gauthier]

Here is the file:

https://www.nordicsemi.com/Software-and-tools/Development-Kits/nRF52-DK/Download#infotabs

[testsweng]

A procedure for unbricking DK boards

Try the following when the nrfjprog commands can no longer detect a DK board
In preparation to unbrick the DK

goto to the URL
www.nordicsemi.com/.../Download

and download the file J-Link OB-SAM3U128-V2-NordicSemi 170724.bin


All of the following is subjective as to how bd the board is screwd up.
1.  Only have the JLink usb connector inserted
2.    Press the reset button and verify that the DK board went into the BOOTLOADER mode by looking at the win explorer window on lower left
    If not keep doing it.  
        Also sometimes it requires that you start with both usb connectors inserted    
                And then slide the Voltage source switch from USB back to VDD
                And I have even used the Segger r command and write the registers.  Can't seem to find that URL on nrf dev zone
                
3.  Unplug the CDC ACM usb cable
4.  Power on the DK    
        You should then see the JLINK device in the win explorer window
        If not start over at step 1

5.  Several options from here.
6.  flash the mbr
7.  flash bootloader if that is what you are working on
8.  flash the softdevice if not using SES
9.    flash your app

Your app should then work properly
It seems that the 833 DK was more difficult than the 832 and 840

[Michael Lamming]

I have screwed up TWO dev kits over the past three days.

DK#1

Can anyone explain why nRFConnect (v3.10.0) for Desktop, using Programmer (v2.3.3) under Win11 recognises my nRF52832DK as a JLink device, but then says it can't talk to it because it isays it s NOT a JLink or Nordic device? (see image attached)  It worked fine initially and I successfully developed code for it for a while, but suddenly it just stopped cooperating. Obviously this is operator error, but after reading through all the stuff I can find, I'm flumoxed.

I have button+power-cycled + dragged and dropped "3566.J-Link OB-SAM3U128-V2-NordicSemi 160315" onto it when it shows up as a drive D:.

Zadig is in the equation too some time ago I recall.

I assume this  has something to do with the fact that when I plug it in, the device manager reports like in this image below.

I have now compromised a DH#2

They both boot, but show different stuff in the D: drive.

Usually when I describe my problem I suddenly realize the real problem and the solution.  This time I can see the problem, but not the solution.

Please throw me a line shipmates.

//Mik