merged.hex file built from the same code base is different.

Hello,

I noticed that if I rebuild the merged.hex file from exactly the same code base then all subsequent merged.hex files are different. This is causing us a problem at production.

I am guessing/suspecting this because the file signature/CRC has changed and the reason for its change is something like the timestamp.

Attached is a snapshot of the differences reported by 'Beyond Compare' utility. All the differences are at the end of the merged.hex file.

Q1/ Can you please explain why this is happening?

Q2/ Could you please point me to a document detailing the format of the merged.hex file.

Q3/ Is there a utility that checks only the code content of the merged.hex without including timestamp, CRC, Signature etc...?

Thank you.

Kind regards

Mohamed

Parents
  • Hi

    Q1/ Can you please explain why this is happening?

    It is as you said due to your firmware beeing modified since you have a timestamp that changes from build to build

    Q2/ Could you please point me to a document detailing the format of the merged.hex file.

    Q3/ Is there a utility that checks only the code content of the merged.hex without including timestamp, CRC, Signature etc...?

    I will have to ask around some more to see if we have something for this

    I will get back to you before the weekend.

    Kind regards,
    Andreas

Reply
  • Hi

    Q1/ Can you please explain why this is happening?

    It is as you said due to your firmware beeing modified since you have a timestamp that changes from build to build

    Q2/ Could you please point me to a document detailing the format of the merged.hex file.

    Q3/ Is there a utility that checks only the code content of the merged.hex without including timestamp, CRC, Signature etc...?

    I will have to ask around some more to see if we have something for this

    I will get back to you before the weekend.

    Kind regards,
    Andreas

Children
Related