• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 54 subscribers
  • Views 849 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.

Compiler: New TI C/C++ CCS ARM compiler qualification kit (ARM_SAFETI_CQKIT_RV) usage for SIL3 development

Oliver Thimm
Intellectual 280 points

Tool/software: TI C/C++ Compiler

Dear Madam or Sir,

I have read the free Compiler Qualification Kit for the TI C/C++ compiler user guide (ARM_SAFETI_CQKIT_RV) and have some questions which can be hopefully answered or corrected, if my understanding of the process is wrong.

1.

We want to develop a safety project with the Hercules RM46 family and are in the tool qualification phase. The projects complies to IEC61508 so the tool belongs to category T3 and we have to follow the "validation-based qualification mode" described in the QKit user guide (QKUG) section 6.2.3 and the TüV Nord Report in section 1.4

Q: Is the above correct ?

2.

In QKUG section 3 this method is described the following way:

"Therefore, we apply a partial testing method that is based on a code-coverage argumentation. The goal of this method is for the user to demonstrate that the tests performed by Texas Instruments are sufficient for the user’s application.  i.e, that compiling the user’s application only uses a safe subset of the tool that has been validated by Texas Instruments. The demonstration is based on the code coverage within the TI C/C++ Compiler, i.e. if during the compiling of the application, that no parts of the tool are used that have not been tested. For this purpose, an instrumented version of the TI C/C++ Compiler is delivered to the user for generating the code coverage information."

Q: Where can I find this instrumented TI C/C++ compiler version ?

3.

The next step according to QKUG section 3 is:

"Compiling the application with the instrumented compiler will produce a coverage report that will be submitted to Texas Instruments for comparison analysis with coverage reports from Texas Instruments."

Q: What is the mail address to send the report to and is the TI report generated free of charge ?

4.

The Tool Qualification Report (TQR) according to section 6.2.1 requires

"Description of the known bugs and their relevance, eventually explaining why some of the bugs are not relevant"

Q: Where can I find updated bug lists for the tool in use ?

Best regards,

  Oliver

  • 0
    TI__Expert 5285 points

    Oliver,

    Regarding your questions:

    Q1: Yes that sounds correct.

    Q2: Instrumented TI compilers can be accessed in the same mySecureSoftware tool folder where you downloaded the QKIT installer.

    Q3: Regarding coverage analysis, please see tool folder file, coverage_testing_instructions.pdf, and there is no charge for TI to do the coverage comparison analysis.

    Q4: In the public bug tracking portal, SDOWP, please access below “Public Query” in the left “Navigator” panel, and review the open defects filed against your compiler version release stream. You can export the list to excel.

    “Public Queries -> Development Tools -> TI C-C++ Compiler -> Open Defects -> ARM -> ARM Compiler Known Issues”

    Also, you can download other compiler patch releases that were released after your particular compiler version. Subsequent releases will include more recent open/closed defect lists.

    Best Regards,

    Greg

  • 0 in reply to GregM
    Intellectual 280 points

    GregM said:

    Q1: Yes that sounds correct.

    Q2: Instrumented TI compilers can be accessed in the same mySecureSoftware tool folder where you downloaded the QKIT installer.

    Q3: Regarding coverage analysis, please see tool folder file, coverage_testing_instructions.pdf, and there is no charge for TI to do the coverage comparison analysis.

    Thank you for the clarification. I ignored the tool archives as they have "tms470" in the file names and I assumed they are for a different target architecture.

    GregM said:

    Q4: In the public bug tracking portal, SDOWP, please access below “Public Query” in the left “Navigator” panel, and review the open defects filed against your compiler version release stream. You can export the list to excel.

    “Public Queries -> Development Tools -> TI C-C++ Compiler -> Open Defects -> ARM -> ARM Compiler Known Issues”

    Also, you can download other compiler patch releases that were released after your particular compiler version. Subsequent releases will include more recent open/closed defect lists.

    If I follow this link the portal opens with the following dialog.

    with User ID / Password unchangeable and the only action I can do is "Cancel" so all further described activities are not possible.

  • 0 in reply to Oliver Thimm
    Guru 26200 points

    Just to be a bystander.

  • 0 in reply to Tomasz Kocon
    TI__Expert 5285 points

    Oliver,

    The SDOWP bug data base query fails for me as well.  IT is looking in to the issue.

    Please try again later when it's working again and let me know if you have any questions.

    Thanks
    Greg

  • 0 in reply to GregM
    TI__Expert 5285 points
    Just heard from IT that link is working again. Sorry for the inconvenience.
    Greg