Can't flash asset tracking sample code getting the fatal error.

Hi,
     im using nRF9160dk ,sdk version 2.5.1 .When I open the sample code of  asset tracking v2 application code I can successfully build the code but when I tried to flash the code I'm getting this fatal error ,but I can flash remaining code like nRF cloud multiservice code and all sample codes successfully and got output also but why I can't flash asset tracking code.below I shared the error.

Building asset_tracker_v2_1
C:\Windows\system32\cmd.exe /d /s /c "west build --build-dir c:/Users/mdharumalingam/aws_iot_1/asset_tracker_v2_1/build c:/Users/mdharumalingam/aws_iot_1/asset_tracker_v2_1"

[0/47] Performing build step for 'mcuboot_subimage'
ninja: no work to do.
[1/38] Performing build step for 'b0_subimage'
ninja: no work to do.
[2/35] Performing build step for 's1_image_subimage'
ninja: no work to do.
[3/27] Performing build step for 'tfm'
ninja: no work to do.
* Terminal will be reused by tasks, press any key to close it.

* Executing task: nRF Connect: Flash: asset_tracker_v2_1/build (active)

Flashing build to 960098217
C:\Windows\system32\cmd.exe /d /s /c "west flash -d c:\Users\mdharumalingam\aws_iot_1\asset_tracker_v2_1\build --skip-rebuild --dev-id 960098217"

-- west flash: using runner nrfjprog
-- runners.nrfjprog: Flashing file: c:\Users\mdharumalingam\aws_iot_1\asset_tracker_v2_1\build\zephyr\merged.hex
[ #################### ] 12.269s | Erase file - Done erasing
[ #################### ] 2.944s | Program file - Done programming
[error] [ nRF91] - Failed while performing 'Verify' operation on target address 0x00FF8130.
-160: Data does not match in address range [0x00FF8130 - 0x00FF817F] (UICR)
Expected byte value 0xDC but read 0xC0 at address 0x00FF8140.
[error] [ nRF91] - Failed while verifying device. -160: Data does not match in address range [0x00FF8130 - 0x00FF817F] (UICR)
Expected byte value 0xDC but read 0xC0 at address 0x00FF8140.
[error] [ Worker] - Data does not match in address range [0x00FF8130 - 0x00FF817F] (UICR)
Expected byte value 0xDC but read 0xC0 at address 0x00FF8140.
[error] [ Client] - Encountered error -160: Command verify_file executed for 2983 milliseconds with result -160
ERROR: Write verify failed.
NOTE: For additional output, try running again with logging enabled (--log).
NOTE: Any generated log error messages will be displayed.
FATAL ERROR: command exited with status 25: nrfjprog --program 'c:\Users\mdharumalingam\aws_iot_1\asset_tracker_v2_1\build\zephyr\merged.hex' --sectorerase --verify -f NRF91 --snr 960098217

* The terminal process terminated with exit code: 25.
* Terminal will be reused by tasks, press any key to close it.



Parents Reply
  • Hi,

      After updating, I didn't encounter the fatal error this time. Instead, I received output in the serial terminal as shown in the screenshot. So, in addition to my previous question, I'd like to confirm if I still need to perform board recovery as shown in your screenshot, considering that I didn't receive the fatal error this time. My concern remains that while the nRF Cloud multiservice sample code is working fine, only the asset tracking sample code is encountering issues.

Children
Related