S32K3 Certification Tools

[shivchopra5]

We are trying to start the process of certification for our product using the S32K34x series and are looking at all the tools we need for certification.

I know that the S32 Design Studio is not certified. Can we still use the pin wizard and driver config tools which generate the code in the design studio and then move that code to a certified compiler? Or, is there an external tool that NXP recommends to use to generate these files.

Are there certified static analysis and run time analysis tools that NXP has or recommends?

I just wanted to know if NXP has a safety strategy or recommendations of tools to use for the whole process other than just the real time drivers.

Thank you!

[naveenm]

Hi,

In our evaluation, both S32 Design Studio and EB Tresos are TCL1.

For static analysis, we recommend Synopsis Coverity. It is certified for use in Functional Safety products.

Hope it helps.

Regards,

NaveenM

[koabra]

Hi Naveen,

Thank you very much for your reply. I had some further queries that would help our organization get certification for our product.

(a) A use-case of NXP DS generating a configuration file related to drivers can have an impact on the software and therefore would ideally be "Tool Impact" TI2. From your response, I infer that all use-cases like this that have higher impact on the software, will have a highest-level "Tool Error Detection" mechanism of TD1 for the Design Studio software including the software's ability to understand if the appropriate source code has been modified as per the user's input or not. Is that a true understanding?

(b) In the event that someone purchases the Software Safety Framework from NXP, will they get access (for documentation purposes) to the "Tool Classification Report" of the Design Studio that lead to your evaluation to TCL1?

Thank you for your kind support.

[naveenm]

Hi,

Please find the answers to your questions below (in italics

(a) A use-case of NXP DS generating a configuration file related to drivers can have an impact on the software and therefore would ideally be "Tool Impact" TI2. From your response, I infer that all use-cases like this that have higher impact on the software, will have a highest-level "Tool Error Detection" mechanism of TD1 for the Design Studio software including the software's ability to understand if the appropriate source code has been modified as per the user's input or not. Is that a true understanding?

In case of Design Studio, "Tool Impact" is TI1, but Configuration Tool has "Tool Impact" TI2. We are evaluating them separately.

According to ISO 26262 standard, “Tool error Detection” (TD)  express the confidence in measures that prevent the software tool from malfunctioning and producing corresponding erroneous output, or in measures that detect that the software tool has malfunctioned and has produced corresponding erroneous output.

In our case (NXP runtime software), we are implementing measures, like testing and review to detect if the Design Studio software tool has malfunctioned and has produced corresponding erroneous output.

(b) In the event that someone purchases the Software Safety Framework from NXP, will they get access (for documentation purposes) to the "Tool Classification Report" of the Design Studio that lead to your evaluation to TCL1?

We only have the result of Design Studio tool evaluation from ISO 26262 TCL perspective done for NXP runtime software. NXP evaluation of Tool Confidence Level can be different than the evaluation of other Design Studio users. Anyone using, should rely on its own analysis and tool evaluation.

Hope it helps.

Regards,

NaveenM

[shivchopra5]

Hi @naveenm,

Thank you for your answer, it was a big help.
Is there a document or certificate which we can use to show that the S32 Design Studio is TCL1.