• State Not Answered
  • Replies 19 replies
  • Subscribers 74 subscribers
  • Views 3340 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 297377
Options

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.

  • 0

    Hi, 

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

    What is the borad version on the white sticker?

    NRFConnect's Programmer v3.0.4 doesn't recognize it as a compatible device.

    Please provide the log form nRF Connect/Programmer. 

    I'm just working with the board itself, switched power to USB

    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.

  • 0

    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.

  • 0 in reply to Amanda Hsieh

    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.

  • 0

    Second board sticker is PCA10095, 1.0.0, 2021.9, 9601566657

  • 0 in reply to dnear1

    Hi,

    dnear1 said:
    --version reports 1015.4 external, Jlinkarm.dll version 7.82

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

    dnear1 said:
    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.

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

    Regards,
    Amanda

Related
Terms of service