• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 31 subscribers
  • Views 113 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.

Original question:

SAFETI-HALCOGEN-CSP: SAFETI-HALCOGEN-CSP and SAFETI_CQKIT Safety Certificate Standards

Issue with not all .COV files being updated after build

Joseph Selva Raj
Prodigy 20 points

Part Number: SAFETI_CQKIT

Tool/software:

Good day,

My company is currently working on developing a SIL certified embedded system in the Railway Industry, and we are using the Hercules TMS570LC4357 MCU.

We are in the process of using the SAFETI_CQKIT to generate the coverage data needed for TI to generate a summary report for us, however, we face an issue where not all of the COV files are being updated/modified after each build of the project, as seen from their timestamps.  

I'll like to ask if this is an expected outcome of the coverage data collection process of the SAFETI_CQKIT that not all of the COV files will be modified in the bin file after each build?

My concern is that the generated coverage data will not be accurate for TI to generate the summary report. 

Here is the screenshot of the COV files where it shows only some are modified, while others are not.

Timestamp of some COV files are not updated after building project

Thank you.

Best regards,

Joseph

ST Engineering

  • +1
    TI__Expert 5255 points

    Joseph,

    Above results are what I would expect. The only coverage data collection files that should have updated time stamps should correspond to the compiler binaries that your use case exercised. Above timestamps indicate that you are using --opt_level=off since armopt.cov did not receive any updates (optimizer data collection file)

    Regards,
    Greg