This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

A way to validate the hex file burned into device against the result (hex) of original source code

Engineerings, We are looking around to find a way to prove that the hex file burned into the device is really the result of the original source code. Is there any idea/way to validate?

How Nrfgo verify the program code burned into the device? I'm asking on program code hex structure.

Parents
  • nRFgo Studio (or other tools like nrfjprog or SEGGER J-Link/J-FLash) don't validate content of the HEX file, they simply have some input HEX file from you, flash it to the memory, immediately read back the memory addresses they used during flashing and compare read data against original HEX. These should be equal. It's as stupid as comparing two files in your PC.

Reply
  • nRFgo Studio (or other tools like nrfjprog or SEGGER J-Link/J-FLash) don't validate content of the HEX file, they simply have some input HEX file from you, flash it to the memory, immediately read back the memory addresses they used during flashing and compare read data against original HEX. These should be equal. It's as stupid as comparing two files in your PC.

Children
No Data
Related