• State Not Answered
  • Replies 3 replies
  • Subscribers 94 subscribers
  • Views 81 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 361590
Options

NRF5340 DK Cannot be recognized

Neo Yang

My NRF5340 DK evaluation board suddenly stopped being recognized by the computer. The LED5 doesn't light up, and there is no JLINK device in the computer's device manager. Is the firmware lost? How can we solve this problem?

Parents Reply Children
  • 0 in reply to Øyvind

    I tried replacing the USB data cable, but it didn't work. The P22 was not removed.

  • 0 in reply to Neo Yang

    Could you please provide some more details on how you were using the board prior to it stopping? Did you try programming anything special when it stopped? 

    Are you able to provide a picture of you board, both front and back? 

    How can we solve this problem?

    I fear that there is not much we can do. When LED5 (the interface MCU LED) doesn't light up and no J-Link device appears in Device Manager, this typically points to an issue with the interface MCU (IMCU) rather than application MCU. 

    You might need to reach out to your local sales representative or the distributor where you got the board in order to replace it.

    Steps to Try

    1. Power cycle the DK – Disconnect USB, wait a few seconds, and reconnect. This is the first fix for MSD-related unresponsiveness. [MSD issues]

    2. Try different USB cables and ports – Use a known-good USB cable and a different USB port or computer.

    3. Try the IMCU bootloader mode – Press and hold the IF BOOT/RESET button (SW5) while plugging in the USB cable to force the interface MCU into bootloader mode.

    4. Recover using nRF Util – If the board is partially detected, you can attempt recovery:

    5. Check for readback protection – On the nRF5340, APPROTECT requires firmware to explicitly enable debugger access after every reset. If no firmware is present to unlock it, the nrfjprog --recover (or nrfutil device recover) command handles the ERASEALL via CTRL-AP automatically. [Debugger access blog]

    Let me know how this works for you.

    Kind regards,
    Øyvind

Related
Terms of service