Currently, the electronic and electrical architecture of automobiles is becoming increasingly complex, and the safety requirements for automotive electronics are also rising. To meet the safety requirements of automobiles, functional safety is gaining more attention. When it comes to functional safety, the first thing that comes to mind is the functional safety standard ISO 26262. In particular, ISO 26262-5(2018) Clause 8 introduces two metrics: Single-point fault metric (single-point fault metric) and Latent-fault metric (latent fault metric). Depending on the required ASIL level, the single-point fault metric and latent fault metric must meet the corresponding levels.

For microcontrollers (MCU, referred to as MCU below), within the electronic and electrical system, they are designed and developed as SEooC (safety element out of context). To meet the aforementioned metric requirements, MCUs need to implement corresponding safety mechanisms. These safety mechanisms can be allocated to both hardware and software modules. The Safety Frame safety library for MCUs is the implementation of safety mechanisms allocated to software.

    1.Product Feature

ØCan be integrated as a complex driver into AUTOSAR.

ØCan be integrated into non-AUTOSAR software architectures, with flexible adaptation.

ØSupports multi-core testing and application.

ØSafety Frame has internal program flow monitoring.

ØHigh Safety: Supports self-diagnostics, and when paired with Zhicong Technology's SBC complex drivers, it can meet the high ASIL-B requirements

ØHigh scalability: Each module can be configured to meet the application requirements of different customers.

    2.Configuration Tool

To meet the varying project requirements of customers and enhance the extensibility of SafetyFrame, the CYT2B7 SafetyFrame has implemented configurable modules and has developed a configuration tool for SafetyFrame. Customers can complete the configuration of various SafetyFrame modules according to different requirements using the configuration tool, generate configuration code files, and integrate the generated configuration files into the project.

  3.Run Phase

ØPreRun Phase

This phase involves testing the safety mechanisms of the MCU, which is generally conducted before the OS starts up.

ØRun Phase

This phase takes place during task execution, while the OS is running, and some of the MCU's safety mechanisms are tested during this phase.

    4.Process Documentation

The CYT2B7 SafetyFrame is designed to assist customers in achieving functional safety requirements based on the RENESAS CYT2B7 platform. The SafetyFrame is highly scalable and can be configured and redeveloped according to different customer project requirements, ultimately meeting the functional safety requirements of the customers.

The CYT2B7 SafetyFrame is used to implement software safety mechanisms for the TRAVEO™ T2G series, including fault testing of internal MCU modules and the driving functions of hardware safety mechanisms.

The CYT2B7 SafetyFrame can be applied to controllers that have functional safety level requirements. 

For example:

ØAutomotive Body Electronics

ØAutomotive Body Control Module (BCM)

ØBody Control Module with Integrated Gateway (BCM)

ØAutomotive Gateway

ØAutomotive LED Headlights

By integrating the Safety Frame into CYT2B7 -based controls, it is possible to meet the ISO26262 ASIL-D level requirements.

Implemented functional modules:

Satisfy CYT2B7  Safety Manual中的MXS：

Functional Safety Certificate

Certificate

Click to download the product manual