1 FUNCTIONAL OVERVIEW

The Safety Library is designed to help customers achieve functional safety requirements for automotive electronic controller products. It is highly extensible and can be configured and redeveloped according to different customer project requirements, ultimately meeting their functional safety requirements.

The Safety Library is used to implement software safety mechanisms for MCU chips, including testing of internal MCU modules and driving hardware safety mechanisms.

Currently, ZC has provided support for the following chips:                                             

2 APPLICATION FIELD

The Safety Library can be applied to controllers with functional safety level requirements. For example:

Ø  Motor Controllers

Ø  Battery Management System (BMS)

Ø  Chassis System Application

Ø  Electronic Stability Control (ESC)

Ø  Electric Power Steering (EPS)

Ø  Airbag and Sensor Integration Application

Ø  Radar Application

By integrating the Safety Library into automotive electronic controller products, compliance with the ISO 26262 ASIL-D level can be achieved.

3 TECHNICAL SERVICE

3.1 Project Implementation

In addition to providing standard products, ZC can also collaborate with customer projects for implementation, which mainly includes requirement analysis, configuration implementation, software integration, integration testing, and software release. The detailed process is shown in the following diagram, with a single project implementation cycle of 12 to 24 working weeks.

Project Implementation Outputs:

3.2 Custom Development

ZC can also provide custom development services. For software modules not listed in the existing product list, or for new chip models, the development cycle and cost will be negotiated between both parties, with the principle of not exceeding the aforementioned licensing fees.

3.3 Product Porting

If customers have purchased the corresponding software license and wish to use the software on the same series of chips (with the same core, but differences in ROM, RAM size, and port quantity), or with other compilers (including different software versions), different compiler options, ZC will re-perform software unit testing, software integration testing, and software functionality testing. The development cycle is 4 to 6 working weeks.

Click to download the product manual