Device not turning on, however BLE works, LED5 flashes once

So I am using the NRF5340, and it has been fine for a few months now, however today, it stopped working and sending any data between the USB and laptop, the LED5 flashes once and not again. Using a multimeter, I found that there is power in the device, but it isnt recognized thorugh JLink or VS Code. However, I had flashed a BLE application onto the device before this issue, with an analog input, and when I tried it out, it worked. Please let me know what can be done!

Parents
  • Hi Aditya,

    Did you make any hardware changes on the board?

    Is your board being detected by the PC? 

    I had flashed a BLE application onto the device before this issue

    Was this any one of the nordic samples?

    Regards,

    Priyanka

  • Hi Priyanka, thanks for your response! I did not modify the hardware of the board, and my PC is not detecting the device. I had flashed the Nordic samples before, but this was a version of my own code that used a small potentiometer. The device still works with the potentio and the BLE connection with the connect app, but does not turn on LED5 or be recognized by my PC. Kindly let me know of next steps!

  • Hi @Aditya Vijay    

    This could be done only on previous DK versions where the Debug chip was a SEGGER chip. In the 5340DK and later versions of all other DKs, the Debug chip is the 5340SoC and it's not possible to re-flash the fw onto it. 

    So if the issue is with your Debug chip (which could be the case), then please try using an external debugger, or you can use the DebugIN (P18) from another DK to flash onto this one.

    -Priyanka

  • Hi Priyanka, I tried to use a J-Link Segger and unfortunately it could not read nor detect the nRF5340. I tried sending commands but it would not pick it up either. Are there any other steps beyond that?

  • Hi Glenz, thank you so much for your advice, I appreciate the support!

  • Please take a look at this Debug input and trace documentation for details on how to connect an external debugger to the SoC on the 5340DK. Please try this s that we can check if it's the debug chip's problem.

    In case you have another DK (say, maybe another 5340DK), you can use the debug chip on that in order to program is SoC as well. Please refer here for the same.

    -Priyanka

  • Hi Priyanka, could you kindly attach documentation for the first comment. I will try that and let you know. I unfortunately do not have another DK to test with, but am receiving two from Nordic support shortly.

Reply
  • Hi Priyanka, could you kindly attach documentation for the first comment. I will try that and let you know. I unfortunately do not have another DK to test with, but am receiving two from Nordic support shortly.

Children
  • Sorry for the trouble. I have added the link to the previous comment.

  • Awesome, thank you so much, Priyanka, for all the aid and support! I will follow up with further information after I attempt with your prior comment.

  • Hi Priyanka, unfortunately I used the J-Link segger by connecting to that input, and it did not work. No devices were connected or reached. I believe there is more of a MCU fault here potentially.

  • Hi Priyanka, I have arranged to have a replacement nRF5340-DK shipped to Aditya. If there is anything else that you can think of to recover the board, please let Aditya know.

    Hi Aditya, if you are ok with the board replacement solution, please close out your ticket. You should receive a notification when the unit ships out.

    Best regards,

    Robb

  • Awesome Robb, thanks again so much for the solution and call earlier, appreciate the support!