• State Verified Answer
  • Replies 19 replies
  • Answers 1 answer
  • Subscribers 98 subscribers
  • Views 489 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 362100
Options

nRF52-DK Non-responsive

Emlyn

I have been using a NRF52-DK board to develop a BTle solution for the past week.
Today, midway through a debug session, the board vanished from my BT interfaces.

It also no longer shows up on USB when plugged in, neither directly or when attempting to put into DFU mode (holding the reset button down and powering on over USB).

Is there something in software I can do, or is this a hardware fault somewhere?

LED5 is not on.

Nothign is seen on USB.

  • 0 in reply to PjGlasso

    This implies that you can see the board on USB.
    It is not connectable.

  • 0 in reply to Emlyn

    Hi there,

    Ok, I see what you mean However he does say it flips LED5 on/OFF so I'm inclined to think its not completely doa, Perhaps the HOLD RESET and PLUG IN USB while doing so. ?

    Has he tried that too?

    HTH

    GL :-) PJ :v:

  • 0 in reply to Emlyn

    That LED5 has me curious...

    So I know you said no switches have moved but seemed as though it failed suddenly and unconventionally. That in mind, I 'll post these things to try if you want and others have found them useful.

     

    Since the interface MCU (OBD) is unresponsive, the only ways to access or recover the board are:

    1. Bypass the On-Board Debugger via External J-Link (Target Direct SWD):

      • If the main nRF52 target application chip is fine, bypass the dead nRF5340 debugger completely.

      • Connect an external standalone J-Link programmer (or another working nRF52/53 DK operating as a debug probe via Debug Out) directly to the SWD header pins (SWDIO, SWDCLK, GND, VTG) routed to the target chip on the DK.

      • From there, issue a standard recover command targeting the external probe:

    ok

    nrfjprog --recover -f nrf52

    2. Isolate Hardware / Power Faults on the DK:

    • Power Supply Mode: Ensure the power source switch (SW10) is set strictly to VDD or USB depending on which port is plugged in.

    • Cut Straps & Switches: Double-check that no trace cut-straps (like nRF_POWER or SWD) were modified or bridging adjacent traces.

    • USB Controller Reset: Disconnect all power, hold down the RESET button, and plug in the USB cable. If the board was stuck in a degraded power state, this can occasionally force the nRF5340 OBD back into a valid boot state.

    3.... RMA / Replacement: If the nRF5340 interface MCU suffered an ESD strike or flash corruption on its USB stack (hence brief flash of LED5 before shutting off), Nordic support typically treats the kit as damaged hardware requiring an RMA replacement.

    GL :-) PJ :v:

  • +1
    Hello Emlyn,
    My bad for making the assumption you had these already, sorry about that.
    What you seem to have measured across R9 and C35 is what I expect. 
    Across C36 you measure 0V on both sides, this is not what I expected. It means the USB regulator on the nRF5340 isn't on, indicating the ODB is missing somehow. 
    If I understand this correctly, you've been in touch with DigiKey about this already. Contact them with regard to replacement in this case.
    Best regards
    Asbjørn
Related
Terms of service