NRF5340DK not enumerating properly on USB

[dnear1]

I have issues with my NRF5340DK devices that I'm hoping to get support on. Several devices appear to be bricked, stuck in a boot loop or otherwise unable to program using the latest NRF Connect utility v3.12.0, on Windows 10 64 bit and updated JLink drivers.  Devices either don't enumerate as a USB device, reboot too often for me to erase it or alternatively, shows up as a Jlink device instead of NRF5340DK so that NRFConnect's Programmer v3.0.4 doesn't recognize it as a compatible device.  I've removed the project shield I created so I'm just working with the board itself, switched power to USB and ensured the power switch is "ON".  The last device shows up as a JLink USB thumb drive and in Programmer shows as J-Link with only 2 comm ports instead of 3.  I tried holding Reset while powering on but it does not show up as "Bootloader".  I tried copying j-link-ob-sam3u128-v2-nordicsemi-170724.bin to the existing storage device and power cycling but that also didn't do anything useful.  I'm looking for specific instructions to restore these devices to factory defaults so they will work again.

[dnear1]

NRFJ Programmer output for 1.0..0 board, it won't recognize the unit as J-link despite being named "J-link"

NRFJ Programmer Screenshot

14:13:41.244

Using nrf-device-lib-js version: 0.4.13

14:13:41.244

Using nrf-device-lib version: 0.12.8

14:13:41.244

Using nrfjprog DLL version: 10.16.0

14:13:41.244

Using JLink version: JLink_V7.66a

14:20:05.640

Unsupported device. The detected device could not be recognized as neither JLink device nor Nordic USB device

Both --recover and --recover --coprocessor CP_Network returns a bunch of "reported -1, unknown error"

2.0.0 Log output 2nd file

[Amanda Hsieh]

For v2.0.0.0DK, please switch to VDD as the v1.0.0. and then generate the log and upload again. Thanks. 

-Amanda

[dnear1]

When 2.0.0 unit is set to VDD, I get no "USB enumeration" sound from Windows, LED5 is dark, no devices are listed for Ports (COM & LPT) in Device Manager.  Attached is new log.log

log.log

[Amanda Hsieh]

Hi, 

I think you should just go through all switches, and make sure that they are in the correct position. Please refer to the following picture to check the setting of the board.  You can place a jumper on P22 in case of you may have cut SB40 but later forgot. 

If it still doesn't work it sounds like the DK is bricked. 

-Amanda H.

[dnear1]

SB40 is still factory-jumpered.  SW10 and SW6 are in off and default positions.  Is there any way to use a working NRF5340DK to reflash a bricket NRF5340DK?

[Amanda Hsieh]

Hi, 

From the team, the log on v1 seems work, but I am not sure why it cannot work with nRFConnect. 

Are you able to run the following commands on v1? Does it throuw error? If not, please try again with nRF Connect.   

nrfjprog --recover --coprocessor CP_NETWORK
nrfjprog --recover

On v2 we're able to successfully communicate with the J-Link OB, but can't access the debug port on the target device.

This typically means the target device isn't powered, or there's an issue with the SWD lines.

Since we're able to load the J-Link DLL successfully in both cases I don't think it's a problem with the J-Link SW installation. That's the reason I ask to check the switches on the DK. If that still cannot work, it might be broken. 

-Amanda H.

[dnear1]

I tried nrfjprog --log --recover --coprocessor CP_Network, attached is the log

log.log

it fails with the -1 unknown error

SB40 uncut, SW10 off, SW6 "Default", power source set to VDD

[Amanda Hsieh]

Is that log from v1?

[dnear1]

Line 52 in log file confirms S/N 96015657 which is 1.0.0 board

[Amanda Hsieh]

Hi, 

From all the information we got from you, it seems these two DKs are bricked to us. Sorry to inform you that. 

-Amadna H.