• State Not Answered
  • Replies 16 replies
  • Subscribers 98 subscribers
  • Views 319 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.

Parents Reply Children
  • 0 in reply to Emlyn

    Note: If you attach a j-link to reprogram the On Board Debugger (nRF5340) to the pins under the label then you will brick the DK and it won't be recoverable so that is a hard NO.

    Normally these kind of issues is caused by USB connectivity issues so check cable and connector on the DK.

  • 0 in reply to PaKa

    The device appears to be bricked already. Are you saying that with the new boards, there's no way to re-flash the firmware if the device is non-responsive over USB?


    Does this only apply to the app processor?
    devzone.nordicsemi.com/.../program-a-nrf52-dk-with-another-nrf52-dk

    There's also random questionable things like this too: https://gist.github.com/cszuo/22a08e3263fcfd397bf9bd91ce5168b0


  • 0 in reply to Emlyn

    The first case is for programming the nRF52 on the board, that is still OK with the new board. What you can't do is program the nRF5340 debugger chip.

    The second looks to be is how to recover the nRF52 if you have locked it and want to reprogram it, again it's for the nRF52 so OK. 

    We do not see cases where there is a need to reprogram the nRF5340 on the DKs, the issues are "always" something else that has happened. The common issues are incorrectly set switches, USB cable, PC side issues (both USB HW and driver SW), mechanical damage to the DK, USB connector. No chance of ESD damage? 

    Couldn't see any but have you by chance modifed any of the cutstraps? Not uncommon to see questions about non-functional boards where this is forgotten :-)

  • 0 in reply to PaKa

    The board has not had any switches / cutstraps changed. Is there something I should / could try here?

    It was happy as a clam until it wasn't - but I was seeing the BTle connection for a bit with my software, flashed via the debug chip and using RTT.

    I don't see how ESD could have happened with mat and wrist strap- also never had an issue here previously.

    I've tried a few different cables and PCs and the behaviour is the same- on insertion of the cable, there's a brief flash on LED5 and then off.

  • 0 in reply to Emlyn
    Hello Emlyn,
    Thank you for the picture of the kit. It's not a common issue, but with the number of kits we do have in the market, sometimes things do go wrong. Unfortunately it can come down to board switches set incorrectly (hence the picture request), often it is related to USB port and cable along with non-windows environment. Some then try to peel of the sticker and re-program the On Board Debugger. As indicated by Paal below here as well.
    • Did you try to reprogram the ODB on the kit through the JTAG header under the sticker?
    • The behaviour you're describing does indicate that the FW on the nRF5340 ODB has been changed and this isn't something we have a clear path understand on how it could be. What sort of OS environment are you working with? What versions of Segger SW and tools are you using?
    Best regards
    Asbjørn
Related
Terms of service