Hashes are like checksums in that it takes an individual binary file and uses an algorithm based on the original file to generate an individual number. This number can then be compared to a reference number to determine integrity and authenticity of the file.
These hashes play an integral part in production releases of a firmware project. This includes:
- Engineering Change Notice Number – The work order that this change originated from.
- Internal Serial Number – Serial number used in internal MRP system.
- Build / Version Number – Actual build number of the firmware
- Commit Number – Number used to retrieve source code from version control locker
- Hash Number – Cryptographic hash number of binary file
From the above list. The Change Notice provides a historical path into what the change was, who approved it, and how it was validated. The Serial Number and Build number allows production to verify the
With all of this combined and implemented, with the version number marked on the product’s work ticket, there will always be full traceability in what was intended to be programed, a verification that the programming file is correct, and a direct path back to the source code and change number if issues come up while in the field. So they can be addressed quickly and efficiently by the engineering department.
Keep Calm and Hash-ON