Failed to boot asset tracker v2 example code

[Neel Oza]

Hello,

We can successfully build and flash the ncs/application/asset_tracker_v2 example code in nrf9160. But when trying to boot up, it throws the following error:

*** Booting nRF Connect SDK v2.7.0-5cb85570ca43 ***
*** Using Zephyr OS v3.6.99-100befc70c74 ***
Attempting to boot slot 0.
Attempting to boot from address 0x8200.
Verifying signature against key 0.
Hash: 0x6d...a2
Firmware signature verified.
Firmware version 1
*** Booting My Application v2.1.0-dev-daf2946a0f07 ***
*** Using nRF Connect SDK v2.7.0-5cb85570ca43 ***
*** Using Zephyr OS v3.6.99-100befc70c74 ***
I: Starting bootloader
E: Failed to open flash area ID 2 (image 0 slot 1): -19, cannot continue

[Hung Bui]

Hi Neel, 
Did you do any modification to the sample ? 
I assume you built for nrf9160dk_nrf9160_ns board ? 
Please try to do a full chip erase before testing.  You can try nrfjprog --recover. 
Could you send the project source ? 

[Neel Oza]

Hello Hung,

No, I haven't done any modification to the sample.

Yes, I have build for nrf9160dk_nrf9160_ns board. I also have another board for nrf91 series as nrf9151 facing the same issue in that also.

I have successfully applied full chip erase command and using the same example code in nrf-sdk ncs/v2.7.0/nrf/applications/asset_tracker_v2 .

[Hung Bui]

Hi Neel, 
It's most likely an issue with no-sysbuild build.
Could you make sure that you select sysbuild when you build the application, otherwise the external flash will not be initialized (which get configured in Kconfig.sysbuild) and result in error -19.

 

[Neel Oza]

Hii Hung,

I am using the same build option.

[Hung Bui]

Hi Neel ,
Could you tell which DK version you have ? 
Please try flashing the attached hex file to see if you still have the issue. 
If you still, please send us your project so we can compile and test here. 3162.merged.hex

You may want to try calling nrfjprog --qspieraseall 
Just in case that the external flash need to be erased. 

[Neel Oza]

Hello Hung.

The issue got resolved once disabled secure MCU boot option from configuration.

[Hung Bui]

Hi Neel, 
The default configuration for Asset tracker is with MCUBoot. And I can build and flash without problem. Please double check. Having a product without option to do DFU update may not be a good idea.