Does S32K14x Model_Based_Design_Toolbox support ISO26262 ?

[张无忌]

I known S32K14x MCU support ISO26262.

Does S32K14x SDK support ISO26262 ?

Does S32K14x Model_Based_Design_Toolbox support ISO26262 ?

Thank you very much.

[张无忌]

Daniel:

Thank you very much.

[张无忌]

Thank you very much.

If do not consider ISO26262, I still have 2 questions:

1.
Is 'NXP's SDK for S32K14x package' product-level?
Can it be put into mass production?

2.
If we found a bug while using NXP's SDK for S32K14x package, would you be responsible for that?

[Daniel_Popa]

This community is only for MATLAB related topics or SW tools related with MATLAB.

So, any issues related with SDK should be addressed here: S32K since this is the community with experts in that matter.

Regarding your first question please contact: Support|NXP @ Support Request. This way your question will be routed to someone that can provide an expert opinion in this matter.

 All i can find in that matter is this statement in the SDK Documentation:

Purpose and Scope
The S32 SDK is a embedded oriented development kit. It allows users to
1. Evaluate and explore the features of the S32 processors; experience how they are supported by working "out
of the box" on NXP development boards.
2. Develop embedded solutions; the NXP SDK is thoroughly tested from development to production.

Hope this helps!

Daniel

[张无忌]

Thank you very much for your helpful reply.

I think if I use s32k14x MCU, using its sdk is inevitable.
But s32k14x MCU supports 26262, sdk does not support 26262.
So how can we make our software through the 26262 certification?
Need to implement a self-consistent 26262 SDK?
Or have other MCU which MCU and its SDK are both Class A?

Can you give me some suggestion?

[Daniel_Popa]

Hello, 

There are two options I could think off:

• Option1 - NXP's solution called AUTOSAR 4.2 that is ISO26262 compliant: AUTOSAR (Classic) Version 4.2.x|NXP 
• Option2 - ARCCORE AUTOSAR solution for S32K: ARCCORE - News 

As disclaimer - i've not used any of them therefore i do not know details. You should get in touch with your NXP sale person for more details about these solution. If you give me your contact details i might be able to redirect your to an appropriate person in your area.

Hope it helps!

Daniel 

[Daniel_Popa · Accepted solution]

Hello, 

Thank you for this question. I think is a good opportunity to clarify the SW Quality Classes that are supported by the NXP Automotive software products.

There are 4 Quality Classes as shown below. Please note that only Class A is ISO26262 compliant

The NXP's SDK for S32K14x package is a mix of:

• CLASS B: SPICE/CMMI Level 3 compliant, MISRA 2012
  • all drivers & HALs
  • generated driver code (including Cpu.c & .h)
  • main.c (generated via graphical configurator)
• CLASS C & D: demo_apps & driver examples, FreeRTOS

The NXP's Model-Based Design Toolbox sits on top of the SDK for S32K14x and is using the SDK Low Level Drivers to generate the code for S32K14x Peripheral initialization and control. The MBDT is Class C Software Package.

Only generic C-code that is generated from Standard Simulink Library Blocks via the MATLAB Embedded Coder is compliant with  ISO 26262: ISO 26262 Support in MATLAB and Simulink - Automotive Industry Standards - MATLAB & Simulink 

Hope this helps!

Daniel