One of the major functions of the AD/ADAS domain controller involve perception and planning. Perception function drives
the requirement for very high performance (TOPS) while the subsequent path planning and actuation drives the need for
ASIL D safety requirements (DMIPS). ADAS compute may not have ASIL D capabilities, but the ASIL D decision needs to be
made in the domain controller. This is achieved by the use of a high-performance ASIL D processor called as safety
processor, which acts as a redundant path evaluating the decision made by the ADAS compute.
With advancement of ADAS technology, the implemented level of automation driving becomes increasingly higher. However, a
degraded mode to keep basic function of ADAS should be supported if any failure leads to complex ADAS application
failure. In this situation, a safety processor is needed, which supports powerful function safety features to
detect/handle failure and owns enough resource to support degrade/redundancy.
An important feature of ADAS application is that the time-sensitive data or secret data will be transferred between ECU,
domain controller and CCU, which drives the requirement that the safety processor in ADAS domain to have excellent
networking capabilities for data transactions. It should support processing and forwarding time-sensitive data via
time-bounded communication technology, for example, Time-Sensitive-Networking. To protect secret data, accelerated security
services based on hardware security engine will be required.
NXP S32G meets all the above-mentioned requirements of ADAS safety co-processor to:
- Support ASIL D applications with powerful function safety features
- Support degraded mode of ADAS
- Support requirements of different ADAS levels
- Provide networking acceleration for CAN and Ethernet with TSN support
- Protect sensitive ADAS data with HSE
- Support high-level OS for SOA applications