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.

CCS/CCSTUDIO: Bin files don't match

Part Number: CCSTUDIO

Tool/software: Code Composer Studio

I have a CCS/TFS question. I checked out a CCS project from TFS. I had to edit the PROJ_LOC and

SW_ROOT to match my laptop. When I compile the project, the bin files don't match the release file.

though the file size is identical. The performance on the mechanism is significantly different.

How can I track this down?

Thanks,

Priya

Edited to attach the difference done on the TFS server vs local machine.

  • Priya,

    Please take a look at these similar threads that suggest how to do a better comparison of binary output from CCS using the objdiff utility.

    https://e2e.ti.com/support/development_tools/compiler/f/343/t/578303

    https://e2e.ti.com/support/development_tools/compiler/f/343/t/589197

  • I started over downloading the project from TFS and re-compiled it. Now the bin files are an identical match. However the firmware performance is no where close to the release version.

    I also downloaded the cg_xml_package. Can you show me an example of how to use the objdiff.pl? Here is what I tried:

    objdiff.pl file1.obj file2.obj
    When I try this, it just pops open the objdiff.pl file.

    How would I run a script that compares all object files between two projects?

    Please help.
    Thanks,
    Priya
  • Priya,

    Please take a look at the index.htm file in the root directory of the cg_xml installation. It links to documentation for each utility that shows how to invoke the utility.

    Your command seems to be missing the ofd at the end.
  • What is the ofd command for TM4C?
    Thanks,
    Priya
  • Priya Nadathur70 said:
    What is the ofd command for TM4C?

    armofd

  • The result is just the same.
    When I try this on a term window,
    objdiff.pl ./ObjectFiles/Proj1/File1.obj ./ObjectFiles/Proj2/File2.obj armofd

    it simply pops open the objdiff.pl file editor.

    Edited to add there is a one line difference in the bin files. In the past,

    it was a lot different. Downloading project again from TFS brought it down to a one line 

    difference. This does nothing to the firmware performance.

    Priya

  • Priya Nadathur70 said:
    When I try this on a term window,
    objdiff.pl ./ObjectFiles/Proj1/File1.obj ./ObjectFiles/Proj2/File2.obj armofd

    it simply pops open the objdiff.pl file editor.

    Apparently, your system is configured to open a text editor when it executes a file that has the file extension ".pl".  That's not helpful here.

    The cg_xml package has Perl source files with the extension ".pl".  But it also has standalone executables in a /bin directory.  Try this instead.

    path/to/cg_xml/bin/objdiff ./ObjectFiles/Proj1/File1.obj ./ObjectFiles/Proj2/File2.obj armofd

    Thanks and regards,

    -George

  • George-- thank you for your reply. I want some more clarity on my setup:
    1. Release bin file downloaded a few weeks ago to my laptop.
    2. Source code project from TFS checked out to laptop.
    3. A copy of this project made for compilation. Resulting bin file is identical to that in 2.
    4. Bin file from 2, 3 differ by 1 line from bin file in 1.
    5. Chances are the obj files in 2 and 3 are identical.
    6. I have to look if I can compare obj files in TFS to that in 2 or 3. Can I compare the bin
    file in TFS to that from 1. Is some change happening during the checkout process?

    If you have pointers on this situation, please let me know ASAP.
    Thank you.
    Best Regards,
    Priya
  • George-- in trying this today:
    C:\Program Files (x86)\Texas Instruments\cg_xml\ofd>objdiff ./File1.obj ./File2.obj armofd

    The term window prints this message out:
    'objdiff' is not recognized as an internal or external command,
    operable program or batch file.

    Thanks,
    Priya
  • Priya Nadathur70 said:
    C:\Program Files (x86)\Texas Instruments\cg_xml\ofd>objdiff ./File1.obj ./File2.obj armofd

    Try running that command from the cg_xml\bin directory instead of cg_xml\ofd directory.

  • Aarti-- it didn't quite work completely.

    C:\Program Files (x86)\Texas Instruments\cg_xml>./bin/objdiff.exe ./File1.obj ./File2.obj armofd
    '.' is not recognized as an internal or external command,
    operable program or batch file.

    Any idea what this means?
    Thanks
    Priya
  • Run the command either from the bin directory as:

    C:\Program Files (x86)\Texas Instruments\cg_xml\bin>objdiff .\File1.obj .\File2.obj armofd

    Or if running from cg_xml directory:

    C:\Program Files (x86)\Texas Instruments\cg_xml>.\bin\objdiff .\File1.obj .\File2.obj armofd

    Note that the path to armofd either needs to be in your system PATH, or else you will need to specify the full path to armofd (it is within the \bin directory of the ARM code generation tools). Same for the object files, you need to give the path if they are not in the current directory.

  • Yes, that worked, thanks,
    Priya