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.

  • Btw. you really don't need to care much about the end because you simply compare only that memory which is written by compiled HEX. If that matches it doesn't matter what is around it (there can be Soft Device, there can be some left-over after some DFU process, there can be application data written by your app after the flashing... but who cares, if the app binary is the same then it deterministic must behave the same way)

Related