This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Different hex file created for different OS

Hi all,

I am using uVision 2.02, C166 V4.02. Using file compare, I discovered that the hex file created was different on Windows 98 and Windows 2000. May I understand if there is any impact on the software execution?

Regards,
Soon Heng

Parents
  • There are many possible hex files that correspond to the same memory image. The question is whether the differences are significant or not.

    Hex files are just lots of ASCII digits. So, why not try running diff (or the equivalent) on the files, and see where they differ? That might tell you whether or not it's a significant change. Your map file will let you figure out what the changing addresses correspond to in the code, so you can target your tests for the area that might be affected.

    Also, you might try the hex2bin utility to convert them both into binary images, and then compare the two files with a binary difference tool.

    It does seem odd to me that the OS would make a difference in the output.

Reply
  • There are many possible hex files that correspond to the same memory image. The question is whether the differences are significant or not.

    Hex files are just lots of ASCII digits. So, why not try running diff (or the equivalent) on the files, and see where they differ? That might tell you whether or not it's a significant change. Your map file will let you figure out what the changing addresses correspond to in the code, so you can target your tests for the area that might be affected.

    Also, you might try the hex2bin utility to convert them both into binary images, and then compare the two files with a binary difference tool.

    It does seem odd to me that the OS would make a difference in the output.

Children