[sdiy] Comparing two compiled hex files

Justin Owen juzowen at gmail.com
Wed Jun 20 18:25:07 CEST 2018

Thanks for the input on this - much appreciated.

Converting the file to .bin using avr-objcopy didn’t reveal anything useful
- still have 2x files that match each other and 1x file generated from the
same code that doesn’t - and the differences are all through the file.

Going to look at possible compiler/config differences next.

Thankfully this isn’t a show-stopper and all the files are working as
expected - would like to understand this though!


On 19 June 2018 at 09:40:56, Justin Owen (juzowen at gmail.com) wrote:

Hello - I hope this isn’t too OT...

I’ve recently set up a gitlab repo to give a few different devs access to
code assets. I’m not a coder - so this is all still new to me.

I thought a good proof of concept that the new, cloned repos on other devs
machines were working as expected would be for them to compile/build a hex
file from existing code and for me to compare their file against the
‘master’ production file using an online utility e.g.

One of the compiled files comes up as a match using this method - but the
file I’ve built doesn’t. However, the file I’ve built uploads to a test
device in a couple of ways and seems to work just fine.

So now I’m trying to troubleshoot this.

Is my theory flawed? Is it possible that hex files from the same code built
on different machines/OS/other variables will work but won’t be an exact
file <-> file match?

Is there a reasonably simple way of isolating what the differences are -
currently I just have big chunks of hex and I have no way of knowing if
these are serious differences or something negligible.


/ Justin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://synth-diy.org/pipermail/synth-diy/attachments/20180620/a798882c/attachment.htm>

More information about the Synth-diy mailing list