ARM-CGT: TI ARM Compiler, SafeTi CQKIT, safe development : is the compiler/toolchain "safe" to use by itself, & related questions

And then, the Link I've included above says "free of charge for TI customers", and on this brochure :

https://www.ti.com/lit/ml/spnt130a/spnt130a.pdf?ts=1618287694650&ref_url=https%253A%252F%252Fwww.google.com%252F

I see $$$$$ in license mentioned.

.. Need help to understand whats needed/required.

The TI ARM compiler is not qualified to any safety standards.  The Safety Compiler Qualification Kit does not qualify the compiler.  Instead, it qualifies your use of the compiler.  Does this help?

Thanks and regards,

-George

George Mock

No, it didn't . Probably created extra questions.

Could you clarify / elaborate more on what you mean? 

I do not understand  your point, because :  'qualify the use of the compiler'  vs 'compiler qualified for the use .' (or certified, whichever is the right term..) in a safety development, the latter is what I asked, I believe.    And its the "the" compiler - very specific one.

In the end, it's not the compiler that I will insert into my product, but I use it to produce an output artifact that I will insert into the safe product.

So could you clarify with a helpful use case example of someone using TI ARM's CC compiler for an ASIL project? What needs to be done to use it validly.

Safety standards require classification for software tools used for functional safety development. Classification of TCL2,3 for ISO 26262, or T3 for IEC 61508 both require tool qualification for use in functional safety development.

TI provides our TI Compiler QKITs to enable customers to use TI compilers for functional safety development. Request download access with below site:
www.ti.com/.../SAFETI_CQKIT 

We used the qualification kit approach instead of certifying compilers. The main reason is that we did not want to limit our customers to a subset of compiler options and use cases. The QKIT approach allows for flexibility with how customers use our compilers (ie compiler options, language features, etc).

The user of the compiler must apply the compiler QKIT.

Users download the QKIT for their compiler version. Fill out some templates to capture their use case, compiler version, etc. Review outstanding bugs (required even for a certified compiler). And then for ASIL-C/D or any SIL level, they need to do a coverage check to ensure building their application does not use portions of our compiler’s that were not exercised during release validations.

Please let me know if you have any additional questions.

Regards,
Greg

Hello GregM

Thank you very much, this does explain this at a level to get started.

Is there possibility to download the QKIT to evaluate / play with it to actually see what's involved? Or is there a document showing all whats in the kit and how to use it at least, to get an overview of the process?

I seems only see option to have to send a Request to get the kit, and I'm not sure if I immediately would have to purchase it.

Click on request, then within a few hours you will have access approved. the QKIT is free

GregM

Oh I see!  Thank you will do indeed.

Thank you again.