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?
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
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
