• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 54 subscribers
  • Views 1538 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.

Temporary files generated with each build

Tobias Neubert
Prodigy 140 points


Hi everybody,

I am using Coder Composer Studio v4.2.1 and Code Generation Tools v7.0.3 for developing a project on TI DM6435 processor. I found out, that with each build, there are some temporary files generated in "C:\Users\<USERNAME>\AppData\Local\Temp\" (Windows 7).

These are e.g. make3432-1.bat which contains an echo command line and two binary files with names like 059842 and 054922. The binary files have a size of about 8 MB each and they do not seem to be deleted automatically. On that way, my temp directory has filled up with about 3,5 GB of data since january.

Is this normal behavior? Can I make CCS remove the files automatically?

Thanks,

Tobias

  • 0
    TI__Guru**** 251180 points

    To see if those binary files are TI object files, try running ofd6x on them.  That is the object file utility.  It is in the \bin directory of the compiler distribution.  It is a command line tool.  So, if you are on the command line in the temp directory, and the \bin directory of the compiler is in your path, if you see something like this ...

    C:\DOCUME~1\a0321429\LOCALS~1\Temp>ofd6x 058922 | more

OBJECT FILE:  058922

 Object File Information

    File Name:                 058922
    Format:                    TI-COFF Version 2
    File Type:                 unknown file type
    Time Stamp:                Fri Mar 25 11:19:26 2011
    Machine:                   TI C6x
    Machine Endian:            little endian
    Entry Point:               0x801430e0
    Vendor:                    Texas Instruments, Inc.
    Producer:                  Linker
    Linker Version:            7.2.0
...

    then we know it is a TI object file.  If you see anything else, it isn't. 

    Thanks and regards,

    -George

  • 0 in reply to George Mock
    Prodigy 140 points

    George,

    when I run this tool on such a file, I see:

    OBJECT FILE:  c:\Users\net.EMEA\AppData\Local\Temp\058922

     Object File Information

        File Name:                 c:\Users\net.EMEA\AppData\Local\Temp\058922
        Format:                    TI-COFF Version 2
        File Type:                 executable file
        Time Stamp:                Wed Mar 23 12:19:57 2011
        Machine:                   TI C6x
        Machine Endian:            little endian
        Entry Point:               0x8012e1e0
        Vendor:                    Texas Instruments, Inc.
        Producer:                  Linker
        Linker Version:            7.0.3
        Number of Sections:        61
        File Length:               8198283
        Symbol Table File Offset:  0x0067e3a9
        String Table File Offset:  0x007663cf
        TI-COFF f_flags:           0x00000163
        TI-COFF f_flag:            F_RELFLG (relocation info stripped)
        CPU Generation:            C6400+
        Control Data Endian:       little endian
        Start of .text Section:    0x80000040
        Start of .data Section:    0x81000000
        Size of .text Section:     1069696
        Size of .data Section:     0
        Size of .bss Section:      3628

    ...and a lot of section information and symbol tables. So this must be a TI object file.

    What can I do now?

    Thanks,

    -Tobias

  • 0 in reply to Tobias Neubert
    Expert 1575 points
    Hi,
    I want to open this question again.
    We run CCSV5 on a test-PC to build automatically after every code-checkin. The temporary files mentioned above consume more and more space.
    Is it possible to make CCS delete them automatically after the build?
    currently we use CCS V5.4
    thanks,
    Thomas