Automotive

Advanced Driver Assistance Systems

Flexibility and scalability are the most prominent needs for Advanced Driver Assistance Systems (ADAS) platforms. The requirement of being pre-certified up to the highest assurance level according to ISO 26262 is self-evident. Future ADAS platforms will require robust separation of applications to run in a safe and secure manner, as well as meeting Safety & Security standards applicable for the Automotive industry.

Learn more (PDF)

AUTOSAR Adaptive

AUTOSAR Adaptive is a standard run-time environment that is getting more and more attraction for Automotive ECUs. The aim of this standard is to provide a flexible run-time environment enabling to bridge the gap between AUTOSAR Classic (hard real-time but limited in features) and rich OS such as Linux (rich feature set but not real-time). AUTOSAR Adaptive is designed to run on high-end ECUs with real-time requirements but not as demanding as AUTOSAR Classic from a deterministic point of view. AUTOSAR Adaptive opens a lot of opportunities. However, one of the key points regarding future use cases will be the capabilities to run on the same ECU next to AUTOSAR Adaptive and other applications with different Safety and/or real-time requirements. This will facilitate the design of next generation ECUs such as domain controllers by offering additional flexibility.

Learn more (PDF)   |   Watch the Webcast   |   Vector Technology Alliance

Connectivity Gateway

Today's vehicles are more and more connected and the car is more and more getting an edge device in the cloud. Connectivity is required by many different actors and some connectivity requirements are related to the user, such as being able to access mobile apps when driving. Some evolutions are pushed by the industry like accessing vehicle information remotely in order to improve predictive maintenance. Other evolutions are related to new business models such as car renting with your phone in order to open the car and start driving. Connectivity in today’s and future vehicles offer larger attack surfaces and brings new Security challenges in order to protect two major objectives: Data privacy and personel Safety.

Learn more (PDF)   |   Watch the Webcast

ECU Virtualization / Consolidation

Driver display systems (or screen boards) are becoming more and more complex, while the integration of highly critical components with commodity functions become more common. This trend will continue, leading to configurable multi-function displays (MFDs), This requires the execution of Safety-critical user interface (UI) components, which have to be certified, side-by-side with feature-rich non-critical commodity UI applications often driven by Linux or Android. These commodity applications require the use of software standard components, while focusing on a sophisticated UI representation (e.g. through 2D/3D acceleration and rendering through hardware). However, Safety-critical UI components will focus on a leaner approach in order to reduce risks and cost of the certification while using a pre-certified UI framework.

Still a car network stack needs to come up below 100 msec which cannot be fulfilled by a Linux software stack.

Learn more (PDF)

Technologies such as Advanced Driver Assistance Systems (ADAS), In-Vehicle Infotainment (IVI), Over-The-Air (OTA) updates, Tire Pressure Monitoring Systems (TPMS) and autonomous driving need a robust, lean and performant operating system. We address the needs of these technologies and those yet to invent with our robust, safe and secure separation and virtualization approach with hard real-time capabilities.

Virtualization and hard real-time operations are ensured by our real-time operating system (RTOS) and type 1 hypervisor PikeOS. It allows safe and secure functional interaction of applications with mixed-criticality. Virtualization allows to manage complexity within automotive software environment and lower maintenance efforts while being highly assured against cyber threats thanks to PikeOS Common Criteria EAL3+ certification (PikeOS 4.2.3 Build S5577 x86_64, ARM v7/8).

Functional Safety

We provide solutions that are comprehensibly and well manageably certifiable up to ISO 26262 ASIL D. PikeOS can be used as Safety Element out of Context (SEooC) as defined in ISO 26262. In addition, embedded automotive software also benefits from the very strict Safety pre-certification of our technology according to the DO-178 Avionics standard.

ISO 26262 Certification Kit

Security

The PikeOS separation kernel itself is small in terms of implementation and its little number of system calls allows comprehensive evaluation and validation. As a matter of fact, PikeOS (4.2.3 Build S5577 x86_64, ARM v7/8) has passed the Common Criteria EAL3+ certification.

Common Criteria Certification Kit

Automotive Guest OS

Because Automotive applications range from non-critical infotainment systems to highly critical control functions in the car, PikeOS accordingly provides a broad variety of Guest OSes: Our technology supports Android, AUTOSAR classic & adaptive, GENIVI or AGL (via Linux), Linux, ELinOS, PikeOS Native, POSIX®.

Automotive Architectures (Single & Multi-Core)

• ARM Cortex V7, V8 or Cortex R, M
• Intel: x86
• RISC-V
• And many more

Benefits

Automotive applications today go beyond the actual vehicle. In particular, reliable communication is needed to ensure smooth mobility. The use of PikeOS resolves a wide array of challenges at the same time: