• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 52 subscribers
  • Views 2239 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.

code coverage issue using CGT 6.1.9 on TI C6416

olivier Paviot
Intellectual 780 points
Other Parts Discussed in Thread: TMS320C6416

Hi all,

I'm using the CGT 1.6.9. targeting a TI TMS320C6416 chip.

Using this CGT, I'd like to perform a code coverage of a "C" library by running several test regressions on it.

I was able to perform this code coverage when running a test regression from one test framework (one .out file) driving the lib.

Now I would like to perform the same code coverage when running several regression on the same lib from several (different) test frameworks (several .out files).

My problem is that I don't know how to merge or consolidate the results from several test framework.

Can someone help me solving this issue?

thanks,

Have a good day,

Br

Olivier





  • 0
    TI__Intellectual 780 points

    Hi all,

    In fact I found the solution to my problem. The following explanation is a bit detailed but anyone looking at the code coverage using the CGT tools should be able to understand it.

     

    The important thing to be able to combine several .pdat files originated from several test frameworks is to ensure that

    - The collected data are all located at the same place in memory (same address for the .ppdat section) AND

    - All runs have the same objects placed in memory.

    - Also I only applied the code coverage on the lib I want to characterize.

     

    To get this I inserted in my test framework a table of pointers pointing to the public functions of the lib to forces the linker to insert all the objects required by all test frameworks. then it is possible to combine several .ppdat files from several and different test frameworks together.

     

    Another option would be to generated the .prf file for each test framework separatly and then to write a script that parses and combine all of the prf files. This could be an easier option if the test framework can not be modified.

     

    Br,

     

    Olivier

  • 0 in reply to olivier Paviot
    TI__Intellectual 755 points

    Olivier,

    You can also get coverage for your library using Simulators. Take a look at CCS3.3 on-line help topic "Library Merge Example" .

    Regards,

    Anuradha.