• State Not Answered
  • Locked Locked
  • Replies 7 replies
  • Subscribers 21 subscribers
  • Views 1552 views
  • Users 0 members are here
2025 survey

We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.

Options
Related
How was your experience today?
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

L SH

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
  • 0 in reply to Richard Collett

    Hi,

    Thank you for the reply. It was 2 different machines.

    One PC was running Windows 98 while another laptop was running Windows 2000. I copied the project folder to another laptop and attempt to recompile again. The hex file created was different. I presume, the settings should remain since the project folder is intact.

    The next thing I did was as follows :
    I copied the project folder to the server.
    The hex file created from the server is still different for the 2 machines running different OS.

    The Keil version and project options were checked to be the same.

    I had not try dual boot on 1 machine. Maybe somebody can follow-up?

    So far, the program is still executing correctly, but just a concern.

Reply
  • 0 in reply to Richard Collett

    Hi,

    Thank you for the reply. It was 2 different machines.

    One PC was running Windows 98 while another laptop was running Windows 2000. I copied the project folder to another laptop and attempt to recompile again. The hex file created was different. I presume, the settings should remain since the project folder is intact.

    The next thing I did was as follows :
    I copied the project folder to the server.
    The hex file created from the server is still different for the 2 machines running different OS.

    The Keil version and project options were checked to be the same.

    I had not try dual boot on 1 machine. Maybe somebody can follow-up?

    So far, the program is still executing correctly, but just a concern.

Children
  • 0 in reply to L SH

    If there is a difference in the hex file, then you should be able to see a difference in the generated assembly code in the LST file.
    Have a look what the difference is, and you should understand if it is worth worrying about.

  • 0 in reply to Richard Collett

    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.

  • 0 in reply to Drew Davis

    Hi all,

    Everything is fine now. A re-check shows that the library files are different.