• State Verified Answer
  • Replies 2 replies
  • Subscribers 94 subscribers
  • Views 809 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 334875
Options

nRF9160DK no debugger discovered

WoutWG

Hi,

I'm using an nRF9160DK v1.0.1 (2021.26) for developing an application using the virtual COM ports for logging. All of a sudden, I saw that my console showed that the COM port was disconnected. After refreshing my devices in the nRF Connect extension, it was no longer listed there. LED5 is just constant on, even after power cycling it. 

I confirmed that it's not related to my USB cable or my computer, since hooking up an nRF52 DK is recognized and its LED5 is flickering at startup as normal.

Is there anything I can try to reset and maybe reprogram the interface MCU? I remember from the nRF52DK that there is a procedure to put the interface MCU in DFU state by power cycling the board when pressing the reset button, but since the nRF9160DK hardware architecture is different it seems that that wouldn't work anymore. I also don't seem to find any interface MCU firmware on the nRF9160DK page.

Best,

Wout

  • 0

    Hello, 

    Does the board show in e.g. nRF Connect for Desktop application i.e. Programmer app or Cellular monitor? Or through nrfjprog --ids in comman line?

    Kind regards,
    Øyvind

  • 0 in reply to Øyvind

    Hi Øyvind,

    I just powered up the board again after working for a while on another board and now it seems to work again for some reason.

    I already checked back this morning to verify that things weren't working, and while the behavior was different from when I first encountered the issue (LED5 was now blinking very fast and pretty faintly), the device was still not identified by the nRF Connect extension in vsc or py nrfjprog. I didn't try any of the desktop applications.

    Since things are working now, and there have been different forms of issues occurring since the start, I'm guessing it would be a hardware related issue, potentially related to maybe some dust/dirt in the USB connector that interfered with the data lines. Plugging and unplugging the USB connector a couple of times may have resolved this.

    I'll close this ticket.

Related
Terms of service