• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 82 subscribers
  • Views 96 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

TMS320F28P650SH: different HEX

Sky Kao
Intellectual 630 points
Part Number: TMS320F28P650SH
Other Parts Discussed in Thread: SYSCONFIG, C2000WARE

Tool/software:

Hello Support Team,

I’m running into an issue while developing code for the C2000. I’ve found that the same source code, when compiled on different computers, generates different HEX files. I’ve already made sure that both computers are using the same compiler version, the same C2000WARE version, and the same SysConfig settings.

Could you please help check if there are any other settings—besides what’s shown in the image below—that I might have overlooked?

Thank you!

  • 0
    TI__Guru**** 251820 points

    I have two experiments to suggest.  You are welcome to use one, or both, experiments.

    Experiment one ... Compare the build logs.  To capture the build log on one computer, rebuild the entire project.  One way to do that is to right-click on the name of the project and select Rebuild Project.  Then save the contents of the Console (not Problems) view to a text file.  Use the icon named Copy Build Log (older versions of CCS) or Save build log to file (newer versions of CCS).  After you have captured the build logs on each computer, compare them.  Some differences will be meaningless.  But others could point to the cause of the problem.

    Experiment two ... This experiment presumes at least one function has a different size.  Please understand this presumption might be wrong.  Please follow the directions in the article Find Source of Code Size Increase.  But with one difference: you are interested in any function that has a different size.  Pick one of those functions.  Carefully investigate the build of the associated source file, which is likely to point to the cause of the problem.

    Thanks and regards,

    -George