How to restore the device?

RE: How to restore the device?

Hieu — Mon, 17 Mar 2025 08:47:46 GMT

Hi Toni,

[quote user="avchizhov"]

But, to tell the truth, I am completely lost.

Please, tell me: what exactly should I do to restore your device?

Please tell me: which exact file should I pick up using the Programmer application, and to put it on your device?

The last message you wrote using "nrf9160dk_mfw-1.3.7_sdk-2.8.0.zip", but just previous message you wrote, that the used Fw has the "sdk-2.8.0 suffix", when the Asset Tracker has the "2021 prefix", and they do not fit each other. Do you offer to flash the device, that has the Fw sdk-2.8.0 with the Fw sdk-2.8.0? It sounds illogical, if it is that.

[/quote]

The idea is simply to use the model firmware and the application firmware from the same hex file release. They have been tested together, so we can expect it to work.

Before, you used model firmware built for SDK v2.8.0 with an application firmware that is built for an SDK version much earlier than v2.8.0. I could only guess that's what is wrong.

I am asking you to use a pair of hex files from the same image release, nrf9160dk_mfw-1.3.7_sdk-2.8.0.zip.

Your newest issue shows that your PC is having trouble communicating with the debugger.

Can you try running nrfutil device recover from the command line? If the nRF9160 DK isn't the only J-Link device connected to your computer, you will also need to specify the serial number by adding the --serial-number <SN> argument.

If that fails the first time, please try again after resetting the board, and if necessary, your PC. Resetting the PC is considered because rarely the J-Link driver is put into a bad state and cannot recover from it.

BR,

Hieu

RE: How to restore the device?

avchizhov — Fri, 14 Mar 2025 11:24:51 GMT

Hieu, greetings.

Thank you for your answer.

But, to tell the truth, I am completely lost.

Please, tell me: what exactly should I do to restore your device?

Please tell me: which exact file should I pick up using the Programmer application, and to put it on your device?

Moreover, the Quick Start application flashes a device with the latest Fw v1.3.7:

After we get this:

The immediate log contains the next records:

---

2025-03-14T11:19:15.247Z INFO Initialising the bundled nrfutil device
2025-03-14T11:19:15.299Z DEBUG Started watching devices
2025-03-14T11:19:16.953Z INFO Using the bundled core version for nrfutil device: 7.13.0
2025-03-14T11:19:17.661Z INFO Using nrfutil-device version: 2.7.5
2025-03-14T11:19:17.661Z INFO Using nrf-device-lib version: 0.17.41
2025-03-14T11:19:17.661Z INFO Using nrfjprog DLL version: 10.24.2
2025-03-14T11:19:17.661Z INFO Using JLink version: JLink_V7.94i
2025-03-14T11:19:28.274Z DEBUG Selected device: nRF9160 DK
2025-03-14T11:19:28.333Z DEBUG Changed step: Info
2025-03-14T11:19:31.133Z DEBUG Changed step: Rename
2025-03-14T11:19:32.853Z DEBUG Changed step: Program
2025-03-14T11:19:37.797Z ERROR [ProbeLib] [2025-03-14 11:19:37.797303Z] {jlink_usb_000960035269} J-Link: Not supported by current CPU + target interface combination.
2025-03-14T11:19:38.388Z ERROR [jlink] [NRFJPROG][JLink][000960035269] Not supported by current CPU + target interface combination.
2025-03-14T11:19:38.487Z ERROR [jlink] [NRFJPROG][JLink][000960035269] Not supported by current CPU + target interface combination.
2025-03-14T11:19:38.589Z ERROR [jlink] [NRFJPROG][JLink][000960035269] Not supported by current CPU + target interface combination.
2025-03-14T11:19:38.686Z ERROR [jlink] [NRFJPROG][JLink][000960035269] Not supported by current CPU + target interface combination.
2025-03-14T11:19:38.786Z ERROR [jlink] [NRFJPROG][JLink][000960035269] Not supported by current CPU + target interface combination.
2025-03-14T11:19:38.888Z ERROR [jlink] [NRFJPROG][JLink][000960035269] Not supported by current CPU + target interface combination.
2025-03-14T11:19:38.990Z ERROR [jlink] [NRFJPROG][JLink][000960035269] Not supported by current CPU + target interface combination.
2025-03-14T11:19:39.088Z ERROR [jlink] [NRFJPROG][JLink][000960035269] Not supported by current CPU + target interface combination.
2025-03-14T11:19:39.196Z ERROR [jlink] [NRFJPROG][JLink][000960035269] Not supported by current CPU + target interface combination.
2025-03-14T11:19:39.295Z ERROR [jlink] [NRFJPROG][JLink][000960035269] Not supported by current CPU + target interface combination.
2025-03-14T11:19:39.394Z ERROR [jlink] [NRFJPROG][JLink][000960035269] Not supported by current CPU + target interface combination.
2025-03-14T11:19:39.493Z ERROR [jlink] [NRFJPROG][JLink][000960035269] Not supported by current CPU + target interface combination.
2025-03-14T11:20:17.464Z DEBUG Changed step: Verify
2025-03-14T11:20:20.470Z INFO Opened port with options: {"path":"COM8","baudRate":115200}
2025-03-14T11:20:22.472Z ERROR Error: Received ERROR as return value from AT command
2025-03-14T11:20:22.478Z INFO Closed port: COM8
2025-03-14T11:20:53.307Z DEBUG Changed step: Program
2025-03-14T11:21:00.534Z ERROR [ProbeLib] [2025-03-14 11:21:00.534562Z] {jlink_usb_000960035269} J-Link: Not supported by current CPU + target interface combination.
2025-03-14T11:21:01.086Z ERROR [jlink] [NRFJPROG][JLink][000960035269] Not supported by current CPU + target interface combination.
2025-03-14T11:21:01.182Z ERROR [jlink] [NRFJPROG][JLink][000960035269] Not supported by current CPU + target interface combination.
2025-03-14T11:21:01.284Z ERROR [jlink] [NRFJPROG][JLink][000960035269] Not supported by current CPU + target interface combination.
2025-03-14T11:21:01.385Z ERROR [jlink] [NRFJPROG][JLink][000960035269] Not supported by current CPU + target interface combination.
2025-03-14T11:21:01.484Z ERROR [jlink] [NRFJPROG][JLink][000960035269] Not supported by current CPU + target interface combination.
2025-03-14T11:21:01.585Z ERROR [jlink] [NRFJPROG][JLink][000960035269] Not supported by current CPU + target interface combination.
2025-03-14T11:21:01.683Z ERROR [jlink] [NRFJPROG][JLink][000960035269] Not supported by current CPU + target interface combination.
2025-03-14T11:21:01.781Z ERROR [jlink] [NRFJPROG][JLink][000960035269] Not supported by current CPU + target interface combination.
2025-03-14T11:21:01.891Z ERROR [jlink] [NRFJPROG][JLink][000960035269] Not supported by current CPU + target interface combination.
2025-03-14T11:21:01.988Z ERROR [jlink] [NRFJPROG][JLink][000960035269] Not supported by current CPU + target interface combination.
2025-03-14T11:21:02.091Z ERROR [jlink] [NRFJPROG][JLink][000960035269] Not supported by current CPU + target interface combination.
2025-03-14T11:21:02.189Z ERROR [jlink] [NRFJPROG][JLink][000960035269] Not supported by current CPU + target interface combination.
2025-03-14T11:22:02.363Z DEBUG Changed step: Verify
2025-03-14T11:22:05.378Z INFO Opened port with options: {"path":"COM8","baudRate":115200}
2025-03-14T11:22:07.379Z ERROR Error: Received ERROR as return value from AT command
2025-03-14T11:22:07.384Z INFO Closed port: COM8
2025-03-14T11:22:24.344Z DEBUG Changed step: SIM
2025-03-14T11:22:25.532Z DEBUG Changed step: Evaluate
2025-03-14T11:22:26.453Z DEBUG Changed step: Learn
2025-03-14T11:22:27.087Z DEBUG Changed step: Develop
2025-03-14T11:22:28.503Z DEBUG Changed step: Apps
2025-03-14T11:22:29.866Z DEBUG Changed step: Finish

---

Please provide us with a correct instruction, if you mention some other steps.

Br., Toni.

RE: How to restore the device?

Hieu — Thu, 13 Mar 2025 16:25:42 GMT

Hi Toni,

In nrf9160dk_mfw-1.3.7_sdk-2.8.0.zip, which you previously used, you can find both a modem firmware in mfw_nrf9160_1.3.7.zip, and an Asset Tracker v2 pre-built application in img_app_bl. Please use them.

For more information, please refer to the CONTENTS.txt file.

Best regards,

Hieu

RE: How to restore the device?

avchizhov — Wed, 12 Mar 2025 09:28:40 GMT

Hieu, greetings.

Could you suggest us: which Fw do you recommend us to use for the restoring?

Br., Toni.

RE: How to restore the device?

Hieu — Mon, 10 Mar 2025 22:02:25 GMT

Hello Toni,

[quote user="avchizhov"]

We have tried with the latest Fw:

nrf9160dk_mfw-1.3.7_sdk-2.8.0 [Latest Version]

and with the latest Asset Tracker v1:

2021-12-15_cfedfdfa (v1.3.1)

The both do not work for us.

[/quote]

The MFW you tried has a sdk-2.8.0 suffix, indicating that it was built for nRF Connect SDK (NCS) v2.8.0. Meanwhile, your Asset Tracker app has a 2021 prefix, indicating that it was built in 2021, which is before NCS v2.8.0 is released.
What I mean is, those two files are likely not released and tested together.

I recommend using firmware from the same package release, such as 2024-03-13_af2b60d2.
After you recover your device to working condition, I recommend following our Quick Start guides to continue. See:
https://docs.nordicsemi.com/bundle/ug_nrf9160_dk/page/UG/nrf91_DK/intro.html

Best regards,

Hieu

RE: How to restore the device?

avchizhov — Wed, 05 Mar 2025 11:28:00 GMT

Greetings to everybody.

I have, occassionally, found, that the device (Hw v1) reports something to the Serial Terminal app (v1.4.3):

---

*** Booting Zephyr OS build v2.7.0-ncs1 ***
[00:02:34.510,131] <err> at_cmd: Failed to open AT socket (err:-117)
[00:02:34.517,211] <wrn> at_notif: Already initialized. Nothing to do
[00:02:34.524,505] <inf> asset_tracker: Asset tracker started
[00:02:34.530,670] <inf> watchdog: Watchdog timeout installed. Timeout: 60000
[00:02:34.538,269] <inf> watchdog: Watchdog started
[00:02:34.544,281] <err> nrf_cloud_client_id: Failed to obtain IMEI, error: -1
[00:02:34.552,154] <err> nrf_cloud_transport: Could not obtain configured client ID, error: -1
[00:02:34.561,523] <err> asset_tracker: Cloud backend could not be initialized, error: -1
[00:02:34.570,465] <err> asset_tracker: LTE link disconnect
[00:02:34.576,751] <err> asset_tracker: lte_lc_power_off failed: -14
*** Booting Zephyr OS build v2.7.0-ncs1 ***down modem
I: Starting bootloader
I: Primary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
I: Secondary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
I: Boot source: none
I: Swap type: none
I: Bootloader chainload address offset: 0x10000
*** Booting Zephyr OS build v2.7.0-ncs1 ***
Flash regions Domain Permissions
00 03 0x00000 0x20000 Secure rwxl
04 31 0x20000 0x100000 Non-Secure rwxl

Non-secure callable region 0 placed in flash region 3 with size 32.

SRAM region Domain Permissions
00 07 0x00000 0x10000 Secure rwxl
08 31 0x10000 0x40000 Non-Secure rwxl

Peripheral Domain Status
00 NRF_P0 Non-Secure OK
01 NRF_CLOCK Non-Secure OK
02 NRF_RTC0 Non-Secure OK
03 NRF_RTC1 Non-Secure OK
04 NRF_NVMC Non-Secure OK
05 NRF_UARTE1 Non-Secure OK
06 NRF_UARTE2 Secure SKIP
07 NRF_TWIM2 Non-Secure OK
08 NRF_SPIM3 Non-Secure OK
09 NRF_TIMER0 Non-Secure OK
10 NRF_TIMER1 Non-Secure OK
11 NRF_TIMER2 Non-Secure OK
12 NRF_SAADC Non-Secure OK
13 NRF_PWM0 Non-Secure OK
14 NRF_PWM1 Non-Secure OK
15 NRF_PWM2 Non-Secure OK
16 NRF_PWM3 Non-Secure OK
17 NRF_WDT Non-Secure OK
18 NRF_IPC Non-Secure OK
19 NRF_VMC Non-Secure OK
20 NRF_FPU Non-Secure OK
21 NRF_EGU0 Non-Secure OK
22 NRF_EGU1 Non-Secure OK
23 NRF_EGU2 Non-Secure OK
24 NRF_EGU3 Non-Secure OK
25 NRF_EGU4 Non-Secure OK
26 NRF_EGU5 Non-Secure OK
27 NRF_DPPIC Non-Secure OK
28 NRF_REGULATORS Non-Secure OK
29 NRF_PDM Non-Secure OK
30 NRF_I2S Non-Secure OK
31 NRF_GPIOTE1 Non-Secure OK

SPM: NS image at 0x20200
SPM: NS MSP at 0x200258d8
SPM: NS reset vector at 0x29df1
SPM: prepare to jump to Non-Secure image.
*** Booting Zephyr OS build v2.7.0-ncs1 ***
I: Starting bootloader
I: Primary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
I: Secondary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
I: Boot source: none
I: Swap type: none
I: Bootloader chainload address offset: 0x10000
*** Booting Zephyr OS build v2.7.0-ncs1 ***
Flash regions Domain Permissions
00 03 0x00000 0x20000 Secure rwxl
04 31 0x20000 0x100000 Non-Secure rwxl

Non-secure callable region 0 placed in flash region 3 with size 32.

SRAM region Domain Permissions
00 07 0x00000 0x10000 Secure rwxl
08 31 0x10000 0x40000 Non-Secure rwxl

SPM: NS image at 0x20200
SPM: NS MSP at 0x200258d8
SPM: NS reset vector at 0x29df1
SPM: prepare to jump to Non-Secure image.
*** Booting Zephyr OS build v2.7.0-ncs1 ***
[00:02:34.510,070] <err> at_cmd: Failed to open AT socket (err:-117)
[00:02:34.517,150] <wrn> at_notif: Already initialized. Nothing to do
[00:02:34.524,475] <inf> asset_tracker: Asset tracker started
[00:02:34.530,639] <inf> watchdog: Watchdog timeout installed. Timeout: 60000
[00:02:34.538,238] <inf> watchdog: Watchdog started
[00:02:34.544,250] <err> nrf_cloud_client_id: Failed to obtain IMEI, error: -1
[00:02:34.552,154] <err> nrf_cloud_transport: Could not obtain configured client ID, error: -1
[00:02:34.561,523] <err> asset_tracker: Cloud backend could not be initialized, error: -1
[00:02:34.570,465] <err> asset_tracker: LTE link disconnect
[00:02:34.576,782] <err> asset_tracker: lte_lc_power_off failed: -14
*** Booting Zephyr OS build v2.7.0-ncs1 ***down modem
I: Starting bootloader
I: Primary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
I: Secondary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
I: Boot source: none
I: Swap type: none
I: Bootloader chainload address offset: 0x10000
*** Booting Zephyr OS build v2.7.0-ncs1 ***
Flash regions Domain Permissions
00 03 0x00000 0x20000 Secure rwxl
04 31 0x20000 0x100000 Non-Secure rwxl

Non-secure callable region 0 placed in flash region 3 with size 32.

SRAM region Domain Permissions
00 07 0x00000 0x10000 Secure rwxl
08 31 0x10000 0x40000 Non-Secure rwxl

Non-secure callable region 0 placed in flash region 3 with size 32.

SRAM region Domain Permissions
00 07 0x00000 0x10000 Secure rwxl
08 31 0x10000 0x40000 Non-Secure rwxl

SPM: NS image at 0x20200
SPM: NS MSP at 0x200258d8
SPM: NS reset vector at 0x29df1
SPM: prepare to jump to Non-Secure image.
*** Booting Zephyr OS build v2.7.0-ncs1 ***
[00:02:34.510,070] <err> at_cmd: Failed to open AT socket (err:-117)
[00:02:34.517,150] <wrn> at_notif: Already initialized. Nothing to do
[00:02:34.524,444] <inf> asset_tracker: Asset tracker started
[00:02:34.530,639] <inf> watchdog: Watchdog timeout installed. Timeout: 60000
[00:02:34.538,208] <inf> watchdog: Watchdog started
[00:02:34.544,219] <err> nrf_cloud_client_id: Failed to obtain IMEI, error: -1
[00:02:34.552,124] <err> nrf_cloud_transport: Could not obtain configured client ID, error: -1
[00:02:34.561,492] <err> asset_tracker: Cloud backend could not be initialized, error: -1
[00:02:34.570,434] <err> asset_tracker: LTE link disconnect
[00:02:34.576,721] <err> asset_tracker: lte_lc_power_off failed: -14
*** Booting Zephyr OS build v2.7.0-ncs1 ***down modem
I: Starting bootloader
I: Primary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
I: Secondary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
I: Boot source: none
I: Swap type: none
I: Bootloader chainload address offset: 0x10000
*** Booting Zephyr OS build v2.7.0-ncs1 ***
Flash regions Domain Permissions
00 03 0x00000 0x20000 Secure rwxl
04 31 0x20000 0x100000 Non-Secure rwxl

Non-secure callable region 0 placed in flash region 3 with size 32.

SRAM region Domain Permissions
00 07 0x00000 0x10000 Secure rwxl
08 31 0x10000 0x40000 Non-Secure rwxl

Non-secure callable region 0 placed in flash region 3 with size 32.

SRAM region Domain Permissions
00 07 0x00000 0x10000 Secure rwxl
08 31 0x10000 0x40000 Non-Secure rwxl

SPM: NS image at 0x20200
SPM: NS MSP at 0x200258d8
SPM: NS reset vector at 0x29df1
SPM: prepare to jump to Non-Secure image.
*** Booting Zephyr OS build v2.7.0-ncs1 ***
[00:02:34.510,009] <err> at_cmd: Failed to open AT socket (err:-117)
[00:02:34.517,089] <wrn> at_notif: Already initialized. Nothing to do
[00:02:34.524,414] <inf> asset_tracker: Asset tracker started
[00:02:34.530,578] <inf> watchdog: Watchdog timeout installed. Timeout: 60000
[00:02:34.538,177] <inf> watchdog: Watchdog started
[00:02:34.544,189] <err> nrf_cloud_client_id: Failed to obtain IMEI, error: -1
[00:02:34.552,093] <err> nrf_cloud_transport: Could not obtain configured client ID, error: -1
[00:02:34.561,462] <err> asset_tracker: Cloud backend could not be initialized, error: -1
[00:02:34.570,404] <err> asset_tracker: LTE link disconnect
[00:02:34.576,721] <err> asset_tracker: lte_lc_power_off failed: -14
*** Booting Zephyr OS build v2.7.0-ncs1 ***down modem
I: Starting bootloader
I: Primary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
I: Secondary image: magic=unset, swap_type=0x1, copy_done=0x3, image_ok=0x3
I: Boot source: none
I: Swap type: none
I: Bootloader chainload address offset: 0x10000
*** Booting Zephyr OS build v2.7.0-ncs1 ***
Flash regions Domain Permissions
00 03 0x00000 0x20000 Secure rwxl
04 31 0x20000 0x100000 Non-Secure rwxl

Non-secure callable region 0 placed in flash region 3 with size 32.

SRAM region Domain Permissions
00 07 0x00000 0x10000 Secure rwxl
08 31 0x10000 0x40000 Non-Secure rwxl

SPM: NS image at 0x20200
SPM: NS MSP at 0x200258d8
SPM: NS reset vector at 0x29df1
SPM: prepare to jump to Non-Secure image.

---

It seems, like it tries booting or loading something, that is called as Zephyr.

Br., Toni.

RE: How to restore the device?

avchizhov — Wed, 05 Mar 2025 10:23:01 GMT

We have tried with the latest Fw:

nrf9160dk_mfw-1.3.7_sdk-2.8.0 [Latest Version]

and with the latest Asset Tracker v1:

2021-12-15_cfedfdfa (v1.3.1)

The both do not work for us.

Br., Toni.

RE: How to restore the device?

avchizhov — Tue, 04 Mar 2025 16:33:43 GMT

Didrik, greetings.

Please, tell us: how to use these pre-complied images?

Are all of them suitable for the Hw v1?

As is visible from the screenshots above, the device is accessible with the Programmer, when it absolutely does not respond with the Serial Terminal.

Br., Toni.

RE: How to restore the device?

Didrik Rokhaug — Mon, 11 Mar 2024 12:31:16 GMT

Hi,

You can find pre-compiled images for the nRF9160 DK here: https://www.nordicsemi.com/Products/Development-hardware/nRF9160-DK/Download#infotabs

Best regards,

Didrik