1.Functional Introduction

Safety Pack Software Architecture Diagram

Safety Pack Configuration Interface Diagram

1.1SAF Introduction

The S32K3 Safety Software Framework (SAF) provides mechanisms for detecting hardware failures and responding to them (single-point and latent faults). Its functions include:

Ø  BIST - Controls the MCU's STCU2 module to perform MBIST and LBIST self-tests.

Ø  eMcem - Based on the MCU's FCCU module, it performs fault collection and processing.

Ø  sCheck - Diagnoses various hardware safety mechanisms within the MCU by injecting and detecting faults.

Ø  mSel - Selects the MCU's software operating mode based on the detection and diagnosis results of BIST, eMcem, and sCheck.

Ø  sBoot - Performs static checks on certain safety-related registers to ensure their settings meet requirements.

Ø  sReco - Executes software fault recovery.

By implementing these safety mechanisms, the safety level of the customer's controller is enhanced, reducing the impact of failures.

1.2SPD Introduction

The S32K3 Safety Peripheral Driver (SPD) is a subset of SAF, including the aforementioned BIST and eMcem modules.

 1.3SCST Introduction

The S32K3 Safety Software (Structural Core Self Test) component is used to detect permanent hardware faults in the core logic. It can be regularly executed during runtime to achieve single-point fault detection. Its integration is compiler-independent, and the detection code is written in assembly language, covering the required diagnostic items without the need for expensive fault simulation tools. The safety level it can achieve is ASIL B.

2.Introduction to ZC's Test Manager Module

     The Test Manager module is a core management and scheduling module added by Zhichong when integrating the Safety Pack into actual engineering. It is used to manage the testing process of the Safety Pack and manage the interface with the application layer.

Configuration Tool Interface of MuNiu

Features include:

Ø  Scheduling of tests in the Safety Pack (SAF, SPD, and SCST).

Ø  Initialization of the Safety Pack.

Ø PreRun phase testing (during startup).

Ø  Run phase testing.

Ø  PostRun phase testing.

Ø  Feedback of the Safety Pack's detection results to the application layer.

3.Project Implementation

ZC can collaborate with customers on project implementation, which mainly includes requirement analysis, configuration implementation, software integration, integration testing, and software release. The detailed process is shown in the figure below, and the implementation period for a single project is between 8 to 12 working weeks.

The S32K3 safety software is a software package officially provided by NXP to help customers achieve the functional safety requirements of automotive electronic controller products based on the S32K3 chip. The S32K3 safety software meets most of the chip-level functional safety requirements specified in the S32K3xx Safety Manual, including SAF (safety software framework), SPD (safety peripheral driver), SCST (core self-test code), and RTD (Real-Time Drivers).

ZCcan provide integration and testing services for the S32K3 safety software of the NXP S32K3 series MCU.

Given that the S32K3 Safety software requirements to be dynamically configured according to customer safety requirements to fully cover their application requirements, we can configure it based on different customer project requirements to ultimately meet their functional safety engineering requirements.

The S32K3 safety software is used to implement the safety mechanisms of the MCU chip, including testing of internal MCU modules and driving hardware safety mechanisms.

Currently, ZC has provided services for the following chips:

The S32K3 safety software can be applied to controllers that have functional safety level requirements. For example:

Ø  Infotainment center IO controller

Ø  Automotive zone controller

Ø  Electronic shifter

Ø  Battery Management System

Ø  Electric pump

Ø  Belt-driven starter generator

Ø  Body Control Module

By integrating the S32K3 safety software into automotive electronic controller products, it can meet the highest functional safety level requirements of ISO 26262 ASIL-D.