• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 52 subscribers
  • Views 675 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

CCSv4 - comparing IDE .out to command line build .out

Eddie3909
Guru 10385 points

Hi

I've followed the directions on this link

http://processors.wiki.ti.com/index.php/Projects_-_Command_Line_Build/Create

and the IDE .out is not the same as the cmd line build .out.

Most of the differences appear to be related to a timestamp (see image).

The reason I think its a timestamp is because it also is different from successive IDE builds.

The difference occurs many times and its the last numbers of teh line EVM\M2_EVM6472.opt64P:$C$L163:2:1321996950

The reason its important that the IDE and command line build match is that we need to confirm that all the optimization and build flags are correct. The difference we see above occurs many times in the code (likely as many times as there are .c files).

It there a way to turn off the timestamp? (or whatever is incrementing in the .out file)

Cheers

  • 0
    Guru 10385 points

    I solved the comparison problem by creating a .hex from the .out and thereby removing the debug info.

    "C:/Program Files/Texas Instruments/ccsv4/tools/compiler/C6000 Code Generation Tools 7.2.6/bin/hex6x.exe" -i "M2_EVM6472.out" -o "M2_EVM6472.hex" -order M -romwidth 16

    Cheers