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.
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
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.
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.
Hi all, Everything is fine now. A re-check shows that the library files are different.