Warning message after custom board programming completed

[pigno5e]

Dear ,

I am currently using NCS1.8.0.

I noticed that there was warning message as shown below after I downloaded the program to my custom board via my nRF52 dev kit.

WARNING: A programming operation has been performed without --verify.
WARNING: Programming can fail without error.

Is it something I would always expect to see if I am programming my custom board via the dev kit?

Thanks and regards, Kevin

[Karl Ylvisaker]

Hello,

The reason for this warning is just to alert you that the program written was not verified after the write.
You can add --verify to the end of your programming command to have the debugger verify the written program, which will also take away this warning.

Best regards,
Karl

[pigno5e]

Dear Karl,

Thanks for your quick reply.

If I am using the vscode platform, what is the best way for me to modify the command during build and flash process?

Thanks and kind regards, Kevin

[Karl Ylvisaker]

Hello Kevin,

No problem at all, I am happy to help! :) 

pigno5e said:

If I am using the vscode platform, what is the best way for me to modify the command during build and flash process?

Oh, I see - you can modify this as shown by my colleague Vidar in this reply except that you add --verify instead of --softreset.

Best regards,
Karl

[pigno5e]

Dear Karl,

Thanks for your reply.

I added below line to the board.cmake file.

board_runner_args(nrfjprog "--verify")

However, the compiler gave the following error information.

FATAL ERROR: runner nrfjprog received unknown arguments: ['--verify']

The --softreset by the way works with no issue.

would you mind kindly help have a look?

Thanks and regards, Kevin

[Karl Ylvisaker]

Hello again, Kevin

My apologies, it seems that my previous comment was made a little too hasty.
I took a closer look at this, and it seems that it has been fixed for later releases of the nRF Connect SDK - but unfortunately it is not present in the v1.8.0 that you are working with.
Looking through the code for v1.8.0 it seems that this check was just not performed, and likely there was no warning either due to the nrfjprog being older, at the time.

However, you could patch this in your zephyr by adding it to the nrfjprog call line instead - it should then look like this, which is how it looks for the newer versions.

Give this a try, and let me know if it resolves your warning.

Best regards,
Karl