• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 53 subscribers
  • Views 1123 views
  • Users 0 members are here
Support feedback
Options
Options

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.

Compiler: Profile Data not generating csv from prf file

ixworks
Intellectual 880 points

Tool/software: TI C/C++ Compiler

I believe I've learned its impossible to create csv's from the Code Composer IDE, so I followed the literature in SPRU187u regarding converting pdat files to prfs, then calling the cl6x tool to generate a comma-delimited file.  However, I don't see any such file. 

http://www.ti.com/lit/ug/spru187u/spru187u.pdf

Is there something I might be missing?  I have to add a bunch of stuff to the cl6x line to make it compile (like it would in the IDE).  I removed the gen_profile flag and added the --use_profile_info=*.prf and --analysis=codecov or --onlycodecov. 

Nothing makes csv files from any of the calls I try.  The PRF file *does* have data in it.   

I create my pddata on the target (C6457) using a build with full debug, and I have tried skeletal.  I turned off the -O2 flag.   Are there any flags I have to turn off that I may have missed?

Creation of pddata is using the rts libs for prof start/stop. 

Thanks

Will

Code Composer Studio 5.1

CGT 7.3.22

C6457

  • 0
    TI__Guru**** 244930 points

    When you run the instrumented executable, the profile data is written out to the file pprofout.pdat by using standard C I/O functions.  My guess is that this I/O write is failing.  Such failures are often silent.  

    I recommend you create a very simple, one source file, program.  Build with no optimization.  Try to collect code coverage on it.  I suspect that will fail.  Then try some of the suggestions from the article Tips for using printf.  Start by making the stack and heap much larger.  Once you get that to work, apply that same suggestion to your main application program.

    Thanks and regards,

    -George

  • 0 in reply to George Mock
    Intellectual 880 points

    I believe either my post was not communicating correctly, or I'm not understanding what you are telling me.

    Are you saying, that (1) the pdat file I generated, that converts properly to a prf is corrupt or void of any code coverage information?

    And, that's why cl6x <blah blah> --use_profile_info=myFile.prf and --analysis=codecov path\filename.c is not generating a CSV?

    (2) It seems like you wrote that I'm not generating a pdat file at all, which isn't the case.

    Can you please elaborate on what you said?  e.g. its #1 (bad pdat generates a prf file that is missing the necessary information to generate code coverage)

    The prf file I was able to generate has a format like :

    c:\path to debug folder/path to file\filename.c/filename

    6

    2 2 0 1 1186998



    Thanks,

    Will

  • 0 in reply to ixworks
    Intellectual 880 points
    George,
    I thought about hand-editing the file or finding some documentation on the correct format of the PRF file and found this post. It looks like my path is the same thing that is talked about in that post.
    I'll hand edit and let you know.

    e2e.ti.com/.../1927374
  • 0 in reply to ixworks
    TI__Guru**** 244930 points

    ixworks said:
    Are you saying, that (1) the pdat file I generated, that converts properly to a prf is corrupt or void of any code coverage information?

    My guess is that the pdat file contained bad data, or no data.  The path problem you found seems more likely to be the cause.  Thanks for finding it.

    Thanks and regards,

    -George