CCS/TMS570LS3134: *.out file differences when ARM Hex Utility is enabled

Koichiro Tashiro

Part Number: TMS570LS3134

Tool/software: Code Composer Studio

Hi,

My customer found *.out file contents are different when ARM Hex Utility is Enabled.
Customer compares *.out files with/without Hex Utility in binary editor.

Other part of source codes, compiler options, linker options are the same.

These *.out files work exactly the same?

Thanks and regards,
Koichiro Tashiro

over 3 years ago

0 George Mock over 3 years ago

TI__Guru**** 232880 points

Exactly how does the customer know this ...

Koichiro Tashiro said:
*.out file contents are different

... happened? What is examined? With what tools?

Thanks and regards,

-George

0 Koichiro Tashiro over 3 years ago in reply to George Mock

TI__Mastermind 21150 points

Hi George,

I will send their comparison results offline.

Thanks and regards,
Koichiro Tashiro

0 George Mock over 3 years ago in reply to Koichiro Tashiro

TI__Guru**** 232880 points

I received the comparison results. Thank you.

I am not completely certain, but I'm very confident the difference is not related to whether the hex utility is used. The difference appears to be the name of a temporary file. This file name is encoded in the object file. It is different on every build, regardless of whether the hex utility is used.

One way to avoid this temporary file name is to build with the compiler option --keep_asm. For the details, please see this forum post.

Another solution to consider ... Instead of changing the build, change the compare. Use the utility objdiff from the Code Generation Tools XML Processing Utilities. By default, it ignores meta-data such as the name of this temporary file.

Thanks and regards,

-George

Code Composer Studio™︎

Code Composer Studio forum

CCS/TMS570LS3134: *.out file differences when ARM Hex Utility is enabled