• State Verified Answer
  • Locked Locked
  • Replies 19 replies
  • Subscribers 75 subscribers
  • Views 3044 views
  • Users 0 members are here
Attachments (1) Download All
Nordic Case Info
  • Case ID: 289191
Options
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

Frikkie Badenhorst

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 Reply Children
  • 0 in reply to Charlie

    Hi Charlie, thanks for the response and I hope you had a good holiday.

    I have connected a different devkit to my PC this morning and everything is working fine, hence the problem should be on the devkit of the original device.

    I will try to reprogram the device and keep you updated, but I suspect this is not going to be successful as we can not connect to the 9160 at all.

  • 0 in reply to Frikkie Badenhorst

    Hi Charlie,

    We are not able to reprogram the default firmware as described in the link. We are only able to program the nrf52.

    When connecting the DK with the SW10 in the nrf52 position, we connect successfully and the following log appears below:

    11:35:21.564	Using @nordicsemiconductor/nrf-device-lib-js to communicate with target via JLink
11:35:21.564	JLink OB firmware version J-Link OB-K22-NordicSemi compiled Jul 2 2021 10:44:28
11:35:21.566	Device family NRF52
11:35:21.567	Device version NRF52840_xxAA_REV2
11:35:21.569	Board version PCA10090
11:35:21.570	Loading readback protection status for Application core
11:35:22.258	Readback protection status: NRFDL_PROTECTION_STATUS_NONE
11:35:22.882	Parse memory regions for Application core
11:35:22.889	Update files regions according to Application core
11:35:22.889	Parse memory regions for file
11:35:22.898	Device is loaded and ready for further operation

    When connecting the DK with SW10 in the nrf91 position, we are not able to connect to the devkit at all (the Jlink shows up, but is not seen as the DK):

    When selecting the JLink, we get the following log"

    11:39:02.064	Unsupported device. The detected device could not be recognized as neither JLink device nor Nordic USB device.
    And we are not able to program the device:

  • 0 in reply to Frikkie Badenhorst

    Hi Frikkie,

    Frikkie Badenhorst said:
    I have connected a different devkit to my PC this morning and everything is working fine, hence the problem should be on the devkit of the original device.

    Do you mean another nRF9160DK?

    Frikkie Badenhorst said:
    11:39:02.064 Unsupported device. The detected device could not be recognized as neither JLink device nor Nordic USB device.

    Could you share the full log file like in this ticket so I can learn more about your environment?

    Frikkie Badenhorst said:
    We have recently played around with the VDD_IO switch (SW9) on the DK. According to this post this can also cause issues?

    If you suspect something wrong happened during your operation(like an unintentional short circuit), this may cause the chip dead, and you can verify if the chip has the correct power input or unusually high temperature. Its hardware file can be downloaded here: nRF9160 DK - Downloads - nordicsemi.com

    Best regards,

    Charlie

  • 0 in reply to Charlie

    Hi Charlie,

    Charlie said:
    Do you mean another nRF9160DK?

    Yes

    Charlie said:
    If you suspect something wrong happened during your operation(like an unintentional short circuit), this may cause the chip dead,

    The chip is not completely dead as I am still able to communicate to it via the external pins.

    Charlie said:
    Could you share the full log file like in this ticket so I can learn more about your environment?

    Here is the log from Programmer app 

    2022-05-18T11:27:09.954Z DEBUG Application data folder: C:\Users\xxxx\AppData\Roaming\nrfconnect\pc-nrfconnect-programmer
2022-05-18T11:27:10.063Z INFO Using nrf-device-lib-js version: 0.4.5
2022-05-18T11:27:10.063Z INFO Using nrf-device-lib version: 0.11.0
2022-05-18T11:27:10.064Z INFO Using nrfjprog DLL version: 10.15.1
2022-05-18T11:27:10.064Z INFO Using JLink version: JLink_V7.58b
2022-05-18T11:27:10.145Z DEBUG App pc-nrfconnect-programmer v3.0.0 official
2022-05-18T11:27:10.145Z DEBUG App path: C:\Users\xxxx\.nrfconnect-apps\node_modules\pc-nrfconnect-programmer
2022-05-18T11:27:10.145Z DEBUG nRFConnect 3.11.0, required by the app is (^3.10.0)
2022-05-18T11:27:10.145Z DEBUG nRFConnect path: C:\Users\xxxx\AppData\Local\Programs\nrfconnect\resources\app.asar
2022-05-18T11:27:10.145Z DEBUG HomeDir: C:\Users\xxxx
2022-05-18T11:27:10.145Z DEBUG TmpDir: C:\Users\xxxx~1\AppData\Local\Temp
2022-05-18T11:27:11.470Z DEBUG iface: Ethernet
2022-05-18T11:27:11.470Z DEBUG IP4: 
2022-05-18T11:27:11.470Z DEBUG IP6: 
2022-05-18T11:27:11.470Z DEBUG MAC: c0:3e:ba:75:cb:15
2022-05-18T11:27:11.471Z DEBUG Client Id: d50b4c3884463e72376ff503bcfe62405907ae47
2022-05-18T11:27:11.471Z DEBUG Google Analytics for category pc-nrfconnect-programmer has initialized
2022-05-18T11:27:14.821Z ERROR Unsupported device.
            The detected device could not be recognized as
            neither JLink device nor Nordic USB device.

Related
Terms of service