Unbricking a nrf9160-DK

RE: Unbricking a nrf9160-DK

Naeem Maroof — Tue, 20 Jun 2023 14:21:50 GMT

Hi Seth,

I am note sure about it, as I haven't bricked my DK. But, if the DK (hardware) is working correctly, and you change / update configurations, you could always check in ./build/zephyr/.config that which configurations are going to take place with this built.

RE: Unbricking a nrf9160-DK

Seth_Kazarians — Fri, 16 Jun 2023 15:37:31 GMT

Agreed.

Is there a way to know which Kconfig settings will not be reverted when removed?

RE: Unbricking a nrf9160-DK

Naeem Maroof — Fri, 16 Jun 2023 10:18:11 GMT

[quote user="Seth_Kazarians"]because the Kconfig settings were all reverted and built cleanly on the https_client example[/quote]

could be the case.

Good to know that your issue is resolved either way.

RE: Unbricking a nrf9160-DK

Seth_Kazarians — Thu, 15 Jun 2023 16:38:52 GMT

I have been updating my apps (nRF Connect, LTE Link Monitor, Programmer, etc.). I did update to the v3.0.9 Programmer, and that didn't solve the issue.

I tried programming a different example (at_client), and that seems to have gotten the modem responding to AT commands again. I'm not sure what's going on that's causing this issue, because the Kconfig settings were all reverted and built cleanly on the https_client example.

RE: Unbricking a nrf9160-DK

Naeem Maroof — Thu, 15 Jun 2023 14:27:27 GMT

Hi Seth,

Thank you for contacting DevZone at NordicSemi.

I am not sure what has happened, or how to fully resolve it.

Were there any changes / updates to the JLink?

We can see that the programmer detects the DK, but the error is coming from the JLink DLL

This case was also having similar error, and changing jlink-connector resolved their problem.

You can also try updating to latest tools (like programmer v3.0.9)

BR,

Naeem