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!

[Frikkie Badenhorst]

Charlie said:

Do you test with some other external connection?

The only external connection we had was a UART connection between the nrf9160 DK and nrf5340 DK. That is however still working as mentioned

[Charlie]

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

[Frikkie Badenhorst]

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

[Charlie]

Hi Frikkie,

I totally understand your concern, some times it is also a challenge for us to debug random failures that happens in the developers' environments.

We did not see a similar ticket by far.

Best regards,

Charlie

[anicare-tero]

Hi,

I have exactly the same problem.

With nrfprog I keep having these errors:

[error] [SeggerBackend] - JLinkARM.dll reported "-1", "An unknown error.".

nrfjprog version: 10.15.4 external
JLinkARM.dll version: 7.58b

Can't connect to the device with SES or nRF Connect for Desktop either.

2022-05-25T08:12:59.468Z DEBUG Application data folder: C:\Users\OMISTAJA\AppData\Roaming\nrfconnect\pc-nrfconnect-programmer
2022-05-25T08:12:59.742Z DEBUG App pc-nrfconnect-programmer v3.0.0 official
2022-05-25T08:12:59.742Z DEBUG App path: C:\Users\OMISTAJA\.nrfconnect-apps\node_modules\pc-nrfconnect-programmer
2022-05-25T08:12:59.754Z DEBUG nRFConnect 3.11.0, required by the app is (^3.10.0)
2022-05-25T08:12:59.755Z DEBUG nRFConnect path: C:\Users\OMISTAJA\AppData\Local\Programs\nrfconnect\resources\app.asar
2022-05-25T08:12:59.755Z DEBUG HomeDir: C:\Users\OMISTAJA
2022-05-25T08:12:59.755Z DEBUG TmpDir: C:\Users\OMISTAJA\AppData\Local\Temp
2022-05-25T08:12:59.766Z INFO Using nrf-device-lib-js version: 0.4.5
2022-05-25T08:12:59.769Z INFO Using nrf-device-lib version: 0.11.0
2022-05-25T08:12:59.769Z INFO Using nrfjprog DLL version: 10.15.1
2022-05-25T08:12:59.770Z INFO Using JLink version: JLink_V7.58b
2022-05-25T08:13:02.042Z DEBUG iface: Ethernet 2
2022-05-25T08:13:02.042Z DEBUG IP4: 192.168.1.132
2022-05-25T08:13:02.042Z DEBUG IP6: 2001:14bb:67a:7071:483f:e9fc:31d5:8
2022-05-25T08:13:02.043Z DEBUG MAC: c8:5b:76:c1:50:09
2022-05-25T08:13:02.043Z DEBUG Client Id: ffa98664926d64d83fc3403302a69ea020308050
2022-05-25T08:13:02.045Z DEBUG Google Analytics for category pc-nrfconnect-programmer has initialized
2022-05-25T08:13:02.197Z ERROR Unsupported device.
            The detected device could not be recognized as
            neither JLink device nor Nordic USB device.

BR,
Tero