• State Verified Answer
  • Locked Locked
  • Replies 19 replies
  • Subscribers 75 subscribers
  • Views 3051 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
  • 0

    Hi Frikkie,

    Sorry for the late reply, just back from a national holiday vcation.

    I think you need to identify if this is an issue with nRF9160DK or something wrong on the computer side. This could be verified by either of the following solutions.

    1) Try your current DK with a new PC.

    2) Order a new DK test with your existing PC.

    If this is an issue on nRF9160DK, and its j-link has no issue to access. Could you reprogram the default nRF9160DK firmware(App+MFW) by following Getting started with nRF9160 DK — nRF Connect SDK 1.9.1 documentation (nordicsemi.com)?

    Best regards,

    Charlie

  • 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:

Reply
  • 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:

Children
No Data
Related
Terms of service