Quick Start Asset Tracker v2 on nRF9160DK - Verification Failed

[timov43]

I've tried the following with the Quick Start app v1.2.0, v1.1.0 and v1.0.1.
The log below is from v1.1.0, if I recall correctly. All logs are about same.

Programmed the Asset Tracker v2 without problems but next step, Verification, is failing.
LOG:
2025-05-06T07:06:16.562Z INFO Initialising the bundled nrfutil device
2025-05-06T07:06:16.582Z DEBUG Started watching devices
2025-05-06T07:06:17.051Z INFO Using the bundled core version for nrfutil device: 8.0.0
2025-05-06T07:06:17.242Z INFO Using nrfutil-device version: 2.7.5
2025-05-06T07:06:17.243Z INFO Using nrf-device-lib version: 0.17.41
2025-05-06T07:06:17.243Z INFO Using nrfjprog DLL version: 10.24.2
2025-05-06T07:06:17.243Z INFO Using JLink version: JLink_V8.18
2025-05-06T07:06:17.245Z INFO Your version of SEGGER J-Link (8.18) is newer than the one this app was tested with (7.94i). The tested version is not required, and your J-Link version will most likely work fine. If you get issues related to J-Link with your devices, use the tested version.
2025-05-06T07:06:19.571Z DEBUG Selected device: nRF9160 DK
2025-05-06T07:06:19.651Z DEBUG Changed step: Info
2025-05-06T07:06:21.447Z DEBUG Changed step: Rename
2025-05-06T07:06:23.652Z DEBUG Changed step: Program
2025-05-06T07:07:09.207Z DEBUG Changed step: Verify
2025-05-06T07:07:12.213Z INFO Opened port with options: {"path":"/dev/ttyACM0","baudRate":115200}
2025-05-06T07:07:14.216Z ERROR Error: Received ERROR as return value from AT command
2025-05-06T07:07:14.228Z INFO Closed port: /dev/ttyACM0


When I open the serial terminal on /dev/ttyACM0 and reset the DK, the following log is printed out:

*** Booting nRF Connect SDK v2.8.0-a2386bfc8401 ***
*** Using Zephyr OS v3.7.99-0bc3393fb112 ***
Attempting to boot slot 0.
Attempting to boot from address 0x8200.
I: Verifying signature against key 0.
I: Hash: 0x2e...07
I: Firmware signature verified.
Firmware version 1
*** Booting My Application v2.1.0-dev-4594a8693738 ***
*** Using nRF Connect SDK v2.8.0-a2386bfc8401 ***
*** Using Zephyr OS v3.7.99-0bc3393fb112 ***
I: Starting bootloader
E: Failed to open flash area ID 2 (image 0 slot 1): -19, cannot continue


Any explanation for this?
Something I could do to avoid this problem?

[Hakon]

Hello,

*** Booting My Application v2.1.0-dev-4594a8693738 ***

what is this "My Application"? I thought you said you programmed asset tracker.

[timov43]

Hmm...

Well, I suggest you to ask from the person who developed and/or built the asset tracker v2 for the Quick Start application why it claims to be "My Application" and not "Asset Tracker v2".

To be sure that Quick Start app is flashing the correct image, I downloaded the "nrf9160dk_asset_tracker.hex" from here
https://github.com/NordicSemiconductor/pc-nrfconnect-quickstart/blob/v1.2.0/resources/devices/firmware/nrf9160dk_asset_tracker.hex

And then flashed it.

nrfutil device recover
️ Recovered 960098165
nrfutil device program --firmware=Downloads/nrf9160dk_asset_tracker.hex
[00:00:03] ###### 100% [2/2 960098165] Programmed
nrfutil device fw-verify --firmware Downloads/nrf9160dk_asset_tracker.hex
️ Firmware was verified on 960098165
nrfutil device reset


Same result:
*** Booting My Application v2.1.0-dev-4594a8693738 ***
*** Using nRF Connect SDK v2.8.0-a2386bfc8401 ***
*** Using Zephyr OS v3.7.99-0bc3393fb112 ***
I: Starting bootloader
E: Failed to open flash area ID 2 (image 0 slot 1): -19, cannot continue
*** Booting nRF Connect SDK v2.8.0-a2386bfc8401 ***
*** Using Zephyr OS v3.7.99-0bc3393fb112 ***
Attempting to boot slot 0.
Attempting to boot from address 0x8200.
I: Verifying signature against key 0.
I: Hash: 0x2e...07
I: Firmware signature verified.
Firmware version 1
*** Booting My Application v2.1.0-dev-4594a8693738 ***
*** Using nRF Connect SDK v2.8.0-a2386bfc8401 ***
*** Using Zephyr OS v3.7.99-0bc3393fb112 ***
I: Starting bootloader
E: Failed to open flash area ID 2 (image 0 slot 1): -19, cannot continue