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.

TMS320F280021: Generating coverage data for concerning compiler

Part Number: TMS320F280021
Other Parts Discussed in Thread: C2000-CGT,

Hallo,

I'm trying to collect coverage data for compiler-qualification of C2000-CGT 20.2.5.LTS.

In the document "TI Compiler Qualification Kit - Coverage Testing User’s Guide" on page 2, it says:

"NOTE: due to a limitation on the length of COVFILELIST, place the paths for below compiler tools first:
armcl.cov, armacpia.cov, armopt.cov, armcg.cov, armasm.cov, armlnk.cov, armilk.cov, armhex.cov"

Since this files do not exist for the used compiler, I'm wondering if an analog rule (regarding different files) must be followed.

Also, is it correct/acceptable if not all *.cov-files are updated during this process? After my first tests, some files seem to be untouched (timestamp does not change).

Thanks for your help

Greetings

Stephan

PS: Would it be possible to unlock the following topic, since solving the regarding problem is still relevant for me.

"TMS320F280021: Conflict between "f28002x_headers_nonbios.cmd" and "dcsm.cmd"

  • I notified the Compiler Qualification Kit experts about your questions.

    Regarding ...

    Would it be possible to unlock the following topic, since solving the regarding problem is still relevant for me.

    I notified the C2000 experts about your request.  I expect they will unlock it soon.  I don't think you will receive any automatic notification when that happens.  So, unfortunately, you will need to check back on that thread once in a while.

    Thanks and regards,

    -George

  • Stephan,

    It is correct that not all *.cov files will have updated timestamps. Only those binaries that are exercised will get new time stamps.

    For coverage compare data, we typically only see updated *.cov files for the main compiler tool chain tools
      cl2000 shell
      acpia2000 parser
      opt2000 optimizer
      cg2000 codegen
      asm2000 assembler
      lnk2000 linker

    And yes apologies for the ARM compiler example in the instructions.  For C28 there will not be any "arm" named binaries. Instead the entire COVFILELIST should only include the *.cov files in the bincov folder you downloaded for your particular C28 release.

    Regards,
    Greg

  • Stephan,

    I've unlocked the above post as requested.  I'll watch it, it may re-lock if there not activity in a certain time frame.

    Best,

    Matthew

  • Thanks for your very quick answer, it helped me a lot.

    Just thinking: Maybe it would be a good idea to provide "TI Compiler Qualification Kit - Coverage Testing User’s Guide" on https://www.ti.com/tool/SAFETI_CQKIT#tech-docs, since without it, I had no glue how to use the instrumented compilers.

    I only found the document via google (was linked in a topic of TI-Forum).

    Greetings

    Stephan

  • Stephan,

    The coverage user guide is available on the C28 QKIT download page:
        https://www.ti.com/tool/download/C2000_CLA_SAFETI_CQKIT_RV#release-notes
    At the top of the page prior to the listings for each QKIT version

    Thanks
    Greg