Why to use a Cockpit Controller?
Driver assistance technologies and infotainment, displayed on high performance graphics, have become competitive arenas for car manufacturers. As a result, the automotive industry focusses on development of the cockpit controller. This central computing unit brings together consumer electronics, driver information, convenience features and driver assistance systems on a single chip. These systems inform, assist, navigate and turn driving into an integrated driving experience.
OpenSynergy offers the precise technology to enable this combination of different functions on a single System-on-Chip (SoC). Customers can integrate and run multi-purpose operating systems, such as Linux and Android along with real-time OS or AUTOSAR-compliant software, on OpenSynergy’s COQOS Hypervisor SDK.
First hypervisor complying to the new version of ISO 26262
The certified hypervisor, as a key component of COQOS Hypervisor SDK, creates a secure separation between the software systems by generating secure virtual machines (VMs). Software systems for the instrument cluster, the infotainment systems, the Advanced Driver Assistance Systems or the AUTOSAR software, are integrated separately into each of these VMs. Computer-intensive programs for high-resolution graphics can be used as well as fast booting and real-time functions. TÜV SÜD has confirmed that the hypervisor complies to ISO 26262:2018 ASIL-B
TÜV certified Safety Concept
OpenSynergy’s Safety Concept for a Linux-based cockpit controller is based on COQOS Hypervisor SDK. TÜV SÜD has confirmed that this concept satisfies the safety requirements up to ISO 26262 ASIL-B.
Most of the information rendered on the instrument cluster display underlies higher requirements on the availability, quality-of-service and boot-times but still does not underlie any formal safety requirements. A small part of the information rendered on some displays is subject to functional safety requirements (according to ISO 26262): these typically are warning signs or “telltales”.
Telltales are warning signs that alert the driver of a malfunction in the car (e.g. warnings about airbag failure, brakes, ABS, engine failure) or a dangerous driving situation (e.g. coming from a driver assistance system). Most OEMs will give this function an ASIL level of QM, A or B. In some cases, driving suggestions (such as the recommended gear), that might impact the safety of the vehicle, will also be assigned an ASIL level.
The safety requirement (that needs to be fulfilled up to ASIL-B) is the following: in case the instrument cluster function is informed (through data coming from the vehicle network) that a telltale must be rendered (“telltale must be shown”), the relevant display must show the telltale within a certain period of time (“telltale is shown”). The unsafe situation is that a warning should have been shown but that the driver is led to believe that his instrument cluster is functioning correctly and that no telltale should have been shown. An example of an unsafe situation would be a frozen instrument cluster display in a driving situation where a warning should have been shown or tell-tales that are hidden by overlapping information from nonsafety relevant functions. To achieve a safe state, it is sufficient to make sure that the driver is made aware that his instrument cluster is not working correctly.