Compiling firmware but not getting same hash

[peakPWR]

Hello,
I compiled the current version of Zombieverter VCU firmware from https://github.com/damienmaguire/Stm32- ... /tag/2.22a
it loads the deps and compiles without problems. But when I compare the Hashes (md5) of my compiled .bin and the release bin they differ.

first i compiled the master branch which obviously had some changes compared to 2.22a but also when i use the 2.22a release zip or git clone the repo and checkout the 2.22a tag the same result.

Are there any platform dependent things? I use an Arch Linux Machine with arm-none-eabi

[peakPWR]

To be more specific when I md5sum the 2.22A release bin file I get f049762ab6cfb0777ef8c31f59aeab1f
but when I compile it from commit 7a57524 (which should be the release commit, right?) I get 8d15f08ceef0c9ef8b0ed68567abb421

[royhen99]

With md5 I get the same result as you for the release bin file but different for the compiled file. With sha256 I get the same result for both files.

[peakPWR]

Thanks for testing.
Sounds like some settings are different or md5 is not suited for comparison?
I will try with SHA as well and report

[johu]

tbh I wouldn't be surprised about subtle differences when firmware is compiled with a different version of the compiler or supporting libs