NRF5340DK not enumerating properly on USB

RE: NRF5340DK not enumerating properly on USB

Amanda Hsieh — Mon, 14 Nov 2022 20:12:09 GMT

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.

RE: NRF5340DK not enumerating properly on USB

dnear1 — Mon, 31 Oct 2022 18:56:38 GMT

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

RE: NRF5340DK not enumerating properly on USB

Amanda Hsieh — Mon, 31 Oct 2022 18:53:48 GMT

Is that log from v1?

RE: NRF5340DK not enumerating properly on USB

dnear1 — Mon, 31 Oct 2022 17:00:19 GMT

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

RE: NRF5340DK not enumerating properly on USB

Amanda Hsieh — Mon, 31 Oct 2022 16:05:37 GMT

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.

RE: NRF5340DK not enumerating properly on USB

dnear1 — Mon, 31 Oct 2022 15:18:07 GMT

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?

RE: NRF5340DK not enumerating properly on USB

Amanda Hsieh — Fri, 28 Oct 2022 13:14:25 GMT

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.

RE: NRF5340DK not enumerating properly on USB

dnear1 — Thu, 27 Oct 2022 15:40:48 GMT

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

RE: NRF5340DK not enumerating properly on USB

Amanda Hsieh — Thu, 27 Oct 2022 14:01:22 GMT

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

-Amanda

RE: NRF5340DK not enumerating properly on USB

dnear1 — Tue, 25 Oct 2022 19:29:09 GMT

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

RE: NRF5340DK not enumerating properly on USB

Amanda Hsieh — Tue, 25 Oct 2022 18:33:23 GMT

Hi,

[quote user="dnear1"]1.0.0 reads with power source set to VDD[/quote]

Can you try to connect this DK with nRF Programmer and check again? If it still has the issue, please also provide the log from nRF Programmer.

[quote user="dnear1"]2.0.0 only reads with power source set to USB[/quote]

Please run the following commands and provide the log.log again. Thanks.

nrfjprog --recover --coprocessor CP_NETWORK
nrfjprog --recover
nrfjprog --deviceversion --log

-Amanda H.

RE: NRF5340DK not enumerating properly on USB

dnear1 — Tue, 25 Oct 2022 14:53:08 GMT

Did so, and looks like maybe that updated properly.

1.0.0 reads with power source set to VDD

960156657_log.log

2.0.0 only reads with power source set to USB

1050042215_log.log

RE: NRF5340DK not enumerating properly on USB

Amanda Hsieh — Tue, 25 Oct 2022 14:42:22 GMT

Hi,

[quote user="dnear1"]nrfjprog version: 10.18.1 external[/quote]

In your log.log, the tool version is v10.15.4. I would suggest to remove all the nRF Command Line Tool via Control Panel\Programs\Programs and Features and install the latest one. Then, provide the log.log for DK v1.0.0 and v2.0.0 seperately.

Thanks,
Amanda H.

RE: NRF5340DK not enumerating properly on USB

dnear1 — Mon, 24 Oct 2022 19:50:32 GMT

log.log file

C:\Users\dnear>nrfjprog --version
nrfjprog version: 10.18.1 external
JLinkARM.dll version: 7.82

C:\Users\dnear>nrfjprog --ids
960156657

C:\Users\dnear>nrfjprog --com
960156657    COM16    VCOM1
960156657    COM15    VCOM2
960156657    COM11    VCOM0

C:\Users\dnear>nrfjprog --deviceversion
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: JLinkARM DLL reported an error. Try again. If error condition
ERROR: persists, run the same command again with argument --log, contact Nordic
ERROR: Semiconductor and provide the generated log.log file to them.
NOTE: For additional output, try running again with logging enabled (--log).
NOTE: Any generated log error messages will be displayed.

RE: NRF5340DK not enumerating properly on USB

Amanda Hsieh — Mon, 24 Oct 2022 19:40:41 GMT

Hi,

[quote user="dnear1"]--version reports 1015.4 external, Jlinkarm.dll version 7.82[/quote]

Please install nRF Command Line Tool latest version and try again.

[quote user="dnear1"]If I rerun deviceversion with --log, I get roughly the same output, a bunch of "reported ""-1", "an unknown error" messages in similar quantity to the first board.[/quote]

Please provide log.log under executed path after installing the latest version.

Regards,
Amanda

RE: NRF5340DK not enumerating properly on USB

dnear1 — Mon, 24 Oct 2022 17:52:01 GMT

Second board sticker is PCA10095, 1.0.0, 2021.9, 9601566657

RE: NRF5340DK not enumerating properly on USB

dnear1 — Mon, 24 Oct 2022 17:50:06 GMT

Second board with power switch on VDD and J2 connected:

--com reports

960156657    COM16    VCOM1
960156657    COM15    VCOM2
960156657    COM11    VCOM0

--ids reports

960156657

--deviceversion reports:

ERROR: Unable to connect to a debugger.
ERROR: JLinkARM DLL reported an error. Try again. If error condition
ERROR: persists, run the same command again with argument --log, contact Nordic
ERROR: Semiconductor and provide the generated log.log file to them.
NOTE: For additional output, try running again with logging enabled (--log).
NOTE: Any generated log error messages will be displayed.

If I rerun deviceversion with --log, I get roughly the same output, a bunch of "reported ""-1", "an unknown error" messages in similar quantity to the first board.

RE: NRF5340DK not enumerating properly on USB

dnear1 — Mon, 24 Oct 2022 17:46:05 GMT

Sticker on the first board is PCA10005, 2.00, 2021.42, 1050042215

With power switch on VDD and J2 connected to PC:

--version reports 1015.4 external, Jlinkarm.dll version 7.82

--com returns nothing

--ids returns nothing

--deviceversion reports "Error: No debuggers were discovered"

With power switch on USB and J2 connected to PC:

--com reports

1050042215 COM20 VCOM1

1050042215 COM19 VCOM0

--ids reports 105042215

--deviceversion reports

"Error: unable to connect to a debugger.

Error JLinkARM DLL reported an error. Try again. If error condition

ERROR: persists, run the same command again with argument --log,.....

Reran and this was the output

ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: Unable to connect to a debugger.
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".
ERROR: JLinkARM DLL reported an error. Try again. If error condition
ERROR: persists, run the same command again with argument --log, contact Nordic
ERROR: Semiconductor and provide the generated log.log file to them.

RE: NRF5340DK not enumerating properly on USB

Amanda Hsieh — Mon, 24 Oct 2022 16:48:59 GMT

Hi,

Sorry to hear that. Let me try to help you.

What is the borad version on the white sticker?

[quote user=""]NRFConnect's Programmer v3.0.4 doesn't recognize it as a compatible device.[/quote]

Please provide the log form nRF Connect/Programmer.

[quote user=""]I'm just working with the board itself, switched power to USB[/quote]

Please set nRF POWER SOURCE to VDD, and Connect J2 with PC.

Please run the following commands and provide the returns:

nrfjprog --version

nrfjprog --com

nrfjprog --ids

nrfjprog --deviceversion

Enter the following commands to recover first the network core and then the application core:

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

Regards,
Amanda H.