This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

URGENT: Device not found after nrf connect for desktop upgrade

Hi there,

This morning I updated to the latest version of the nrf connect for desktop, along with all the extensions (LTE Link Monitor, Programmer, Toolchain Manager).

However I cannot seem to detect my nrf9160 DK anymore. It does not pop up in the "Select device" on any of the apps. This is extremely frustrating. When we toggle the switch to the nrf52 however, the dk gets detected, but when toggling the switch to the nrf9160 position, we can not detect the DK, and only the J-link pops up within Programmer app:

Unfortunately I do not remember the previous versions of any of the app I had. Please advise a workaround for this ASAP!

Parents
  • Hi Frikkie,

    Other worthful experiments might require some HW knowledge and handwork. I am not sure if you want to digger into this or handover to hardware engineers, you decide. If your project is urgent I would suggest you continue with functional DKs for application firmware development. Here is my advice for hardware debugging:

    1) Learn about the nRF9160DK schematic and check the connections between programming/debug pins and connectors.

    2) With two nRF9160DKs on hand,  you can refer to Connectors for programming external boards to test if you can program the nRF9160 chip with JLINK OB from another board(nRF9160DK, nRF5340, any JLink debugger supporting Cortex-M33).

    Best regards,

    Charlie

  • It is for sure not worth it to spend the time hardware debugging the faulty devkit. For now will continue with the working kit rather. 

    It is however a bit concerning what might have caused this, as I will want to prevent that from happening in future. Is there any chance changing the VDD_IO from 1.8V to 3V might have caused this? 

    Kind regards,

    Frikkie

Reply
  • It is for sure not worth it to spend the time hardware debugging the faulty devkit. For now will continue with the working kit rather. 

    It is however a bit concerning what might have caused this, as I will want to prevent that from happening in future. Is there any chance changing the VDD_IO from 1.8V to 3V might have caused this? 

    Kind regards,

    Frikkie

Children
No Data
Related