Getting Write verify failed every time when try to debug or write without erase.

[Jithin A]

Hi,

We are working with nRF5340 with SDK v2.5.2.

Each time we try to program the board, we get below error.

[ #################### ]  12.131s | Erase file - Done erasing                                                          
[ #################### ]   1.269s | Program file - Done programming                                                    
[ #################### ]   1.299s | Verify file - Done verifying                                                       
[ #################### ]  14.504s | Erase file - Done erasing                                                          
[ #################### ]   2.654s | Program file - Done programming                                                    
[error] [ Client] - Encountered error -160: Command verify_file executed for 2719 milliseconds with result -160        
[error] [  nRF53] - Failed while performing 'Verify' operation on target address 0x00FF8128.                           
-160: Data does not match in address range [0x00FF8128 - 0x00FF8177] (APP UICR)
Expected byte value 0xFF but read 0xFC at address 0x00FF8150.
[error] [  nRF53] - Failed while verifying device. -160: Data does not match in address range [0x00FF8128 - 0x00FF8177] (APP UICR)
Expected byte value 0xFF but read 0xFC at address 0x00FF8150.
[error] [ Worker] - Data does not match in address range [0x00FF8128 - 0x00FF8177] (APP UICR)
Expected byte value 0xFF but read 0xFC at address 0x00FF8150.
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 'd:\project\..\build\zephyr\GENERATED_CP_APPLICATION_merged_domains.hex' --sectorerase --verify -f NRF53 --coprocessor CP_APPLICATION --snr 960130361

We do not see this error if we try Erase and Flash option from VS Code. We observe the same issue even with the nRF5340DK board.

This is very annoying us as we cannot debug or program without erasing. Please help us solving the issue.

We are using VS Code with NRF Connect extensions. SDK v2.5.2.

[Jithin A]

Any update on this?

Please let me know if any additional information is needed.

Thank you in advance

[Michal]

Hello,

Are you using a watchdog timer in your code by change?

Best regards,

Michal

[Maria Gilje]

Hi Jithin,

This error is expected. The PSA template sample is only meant to be programmed to the board once, and then the next firmware updates are done with DFU, not by flashing. See the Firmware update section for the sample for details.

Best regards,

Maria

[Jithin A]

Hi Maria,

We did some research on the issue.

We found that we are getting the issue when we enable DFU target.

Let me explain,

First, we build TFM_secure_peripheral example using SDK v2.2.0 as we found no debug issue from this SDK.
The build works well no error found when we try to debug.
Later, we updated the SDK to 2.6.0 and made all the necessary changes. No issues with the debug.
The only difference from the TFM sample application to ours is DFU enabled.
So, we enabled the DFU target by adding below configuration into the prj.conf file.

CONFIG_BUILD_WITH_TFM=y
CONFIG_TFM_PROFILE_TYPE_NOT_SET=y
CONFIG_TFM_IPC=y
CONFIG_NRF_TIMER1_SECURE=y
CONFIG_NRF_SPIM3_SECURE=y
CONFIG_NRF_GPIOTE0_SECURE=y
CONFIG_TFM_ISOLATION_LEVEL=1

# Added DFU functionality-------------------------------
# Setup secure bootloader
# Flash configurations
CONFIG_FLASH=y
CONFIG_FLASH_PAGE_LAYOUT=y
CONFIG_FLASH_MAP=y

# Enable MCUboot and secure bootloader for sgining the image
CONFIG_BOOTLOADER_MCUBOOT=y
CONFIG_SECURE_BOOT=y
CONFIG_SB_SIGNING_KEY_FILE="key.pem"

# Enable DFU target
CONFIG_DFU_TARGET=y
CONFIG_IMG_MANAGER=y
CONFIG_DFU_TARGET_MCUBOOT=y
CONFIG_DFU_TARGET_STREAM=y
CONFIG_STREAM_FLASH_ERASE=y
CONFIG_STREAM_FLASH=y
# Do not add any config below this line as below are added from kconfig
CONFIG_B0_MIN_PARTITION_SIZE=y
CONFIG_NRF53_UPGRADE_NETWORK_CORE=n

Flash the code, works well. NOW, we try to debug we get the error.

To confirm, we disabled the DFU in our project and debug works without need for the sector erase.

Can you please look into this.

Please let me know we are configuring anything wrong or any additional info needed.

Thank you in advance.

[Jithin A]

Hi Maria,

Any update on this?

We get the same error if we build the project from SDK v2.5.0 or greater.

Let me explain our observations.

1. Create a new sample (TF-M secure peripheral) from the SDK v2.5.0 or greater.
2. Build and program, works well.
3. Try debug after programming, works well.
4. Enable DFU using below config

   # Added DFU functionality-------------------------------
   # Setup secure bootloader
   # Flash configurations
   CONFIG_FLASH=y
   CONFIG_FLASH_PAGE_LAYOUT=y
   CONFIG_FLASH_MAP=y
   
   # Enable MCUboot and secure bootloader for sgining the image
   CONFIG_BOOTLOADER_MCUBOOT=y
   CONFIG_SECURE_BOOT=y
   CONFIG_SB_SIGNING_KEY_FILE="key.pem"
   
   # Enable DFU target
   CONFIG_DFU_TARGET=y
   CONFIG_IMG_MANAGER=y
   CONFIG_DFU_TARGET_MCUBOOT=y
   CONFIG_DFU_TARGET_STREAM=y
   CONFIG_STREAM_FLASH_ERASE=y
   CONFIG_STREAM_FLASH=y
   # Do not add any config below this line as below are added from kconfig
   CONFIG_B0_MIN_PARTITION_SIZE=y
   CONFIG_NRF53_UPGRADE_NETWORK_CORE=n

5. Build and program, works well.
6. Try debug after programming, we get the error.

Please help us to solve the issue ASAP. Please let me know if any additional information required.

[Jithin A]

Hi Maria,

Any update on this.

[Maria Gilje]

Hi Jithin,

Apologies for the wait.

I assume that you are using the VS Code extension for debugging. When selecting the Debug action, your board will be flashed first before starting the debugging session. After programming your project, APPROTECT will be enabled on reset, which is I suspect is the cause for the error when debugging. To circumvent this you have two possibilities:

1. Select the option "Attach Debugger to Target" which is available when hovering over the Debug action and clicking the three dots.
   

   

2. Add "flash": false to the Launch Configuration for your project, for example
   

   {
   	"version": "0.2.0",
   	"configurations": [
   		{
   			"type": "nrf-connect",
   			"request": "launch",
   			"name": "Launch tfm_secure_peripheral\\build",
   			"config": "${workspaceFolder}/build",
   			"runToEntryPoint": "main",
               "flash": false
   		}
   	]
   }

Best regards,

Maria

[Jithin A]

Hi Maria,

Thanks for the suggestion, option #2 worked for me.

I assume the above option works as debug without flash.

I need to flash the changes.

Is there any option to combine 2 tasks say first, program the code and then perform the debug task?

If so, please guide me to configure the task.

[Jithin A]

Hi Maria,

I modified launch.json and created tasks to flash the build to the board by ignoring verify status.

Now I can flash and debug the changes.

Yet I see the warning that verification failed and since I am ignoring the write verification, I am able to debug, I think this is not the actual solution but for the time being I can flash and debug the latest build without any need of the sector erase.

Thank you.

Please let me know if we have any complete solution.

[Maria Gilje]

Hi Jithin,

--verify will fail if the contents in flash, RAM, UICR, or XIP differs from the provided hex file (source: https://docs.nordicsemi.com/bundle/ug_nrf_cltools/page/UG/cltools/nrf_nrfjprogexe_reference.html). Since provisioning is required to be programmed before the application, the application hex will not be the same as the full contents of the device so the verification will fail.

So in conclusion: your solution is good.

Best regards,

Maria