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

identical compiles produce different size images

our units use dual images for upgrade safety which only differ in address locations.
each image uses the same source with project files (.uvproj) that only change the scatter
file used for linking. When doing a full compile of each image I've recently started
noticing that the images differ by 4 bytes. This appears to happen during linking and compiling on one of our other systems doesn't produce this issue so I suspect something has
been corrupted on my laptop.
This is very disconcerting.
Any ideas??

Parents
  • again. tried using the same scatter file for both (i.e. same addressing) and the second project file is a copy of the first with just pre & post processing files switched.
    Pre, normally just copies over the the correct scatter to a file with a common name
    and post is a lot of moving files about and format conversions which is why I wondered about the cygwin objcopy which is just converting a hex file to a binary and like I've said running on our official build machine produces the correct result.
    Thanks at least for giving a thought out answer unlike the previous trolls smart ass responses.
    I should probably try a full reinstall of uvision since it seems more like an environment corruption issue. Just thought maybe someone had run into this before and could maybe get a quick answer. This product is 7 years old and other than the one time because of an option chosen this is the first time this has happened.

Reply
  • again. tried using the same scatter file for both (i.e. same addressing) and the second project file is a copy of the first with just pre & post processing files switched.
    Pre, normally just copies over the the correct scatter to a file with a common name
    and post is a lot of moving files about and format conversions which is why I wondered about the cygwin objcopy which is just converting a hex file to a binary and like I've said running on our official build machine produces the correct result.
    Thanks at least for giving a thought out answer unlike the previous trolls smart ass responses.
    I should probably try a full reinstall of uvision since it seems more like an environment corruption issue. Just thought maybe someone had run into this before and could maybe get a quick answer. This product is 7 years old and other than the one time because of an option chosen this is the first time this has happened.

Children