Change is fast and competition is fierce in the automotive market. In order to create an edge, automotive manufacturers seek ways to build a competitive advantage, such as through improved vehicle performance, a better user experience and more attractive prices. The growing focus on autonomous cars gives manufacturers an additional arena in which to compete. Much of the evolution in automotive electronics is enabled by powerful hardware and sophisticated software. The QNX OS for Safety is a software solution that provides the reliable foundation necessary for building competitive automotive systems in a cost effective and safe manner.

Benefits

• Pre-certified to the highest ISO 262262 ASIL level to reduce development, certification cost and risk
• freedom from interference mechanism to enable and simplify the design of system with a mix of safety and non-safety critical functions
• Qualified c and c++ toolchain to ease the certification workload for customers
• Fully API Compactible with standard QNX Neutrino RTOs to minimize ramp up time and code to re-usage.

Safety Certified

The Growing size and complexity of the autonomous vehicle system makes functional safety a topic of paramount importance. In vehicle electronic components that manufactures rely on to built a competitive advantage often require powerful hardware and sophisticated software, whether it is an instrument with a compelling user interface or a complicated ADAS such as pedestrian avoidance.

ISO 26262, an international for functional safety, is being adopted widely by the automotive industry as the state of the art of definition for vehicle functional safety at the system, hardware and software levels. Building an automotive system complaint with ISO26262 is a significant task, especially for manufactures who are not familiar with functional in all levels of the design. To help mitigate risk of non-compliance and reduce development and certification costs. Blackberry Provides a reliable RTOS foundation that is pre-certified is the highest level of ISO26262. ASIL-D using QNX OS for safety as the building block can greatly relieve the certification burden for automotive manufactures and give them the peace of mind they when building system with safety critical requirements.

API Compactibility

The QNX OS for safety is fully API Compatible with blackberry QNXs standard RTOs release. version 2.0 of the product is compatible with QNX software development platform 7.0. Developers who are already familiers with the standard RTOs require to Ramp-up time when working with the safety-certified product and can use the same same QNX Momentics tool suite development environment to develop safety-critical system. the API compatibility not only eases the learning curve for te development team, but also make it possible for customers to leverages one common platform for safety critical and non- safety critical application, thus maximize code to reusage.

Technology

Product Package

The QNX OS for safety include software and documentation all ;pre-certified to ISO 26262 ASIL D.

Software

• QNX Neutrino RTOs microkernel, process manager with multicore support and adaptive partitioning technology
• POSIX Complaint ibc

Freedom from Interference

While functional safety requirements place emphasis on the system being deterministic and reliable, other competitive features demand the system to be more dynamic, connected and versatile. on one hand features such as pedestrian avoidance and warning symbols on instrument cluster must be developed with a certain level of safety guarantee. on the other hand , consumer are expecting a compelling and fascinating user experience from system in the vehicle cockpit. like the infotainment system and driver information display. while this two design goals are very difficult , both must be satisfied. therefore the mechanism to support the design of system with such mixed critical becomes crucial. QNX OS for safety is based on the QNZ Nutrino RTOs, which has the microkernel architecture that comes with the inherent ability to separate multiple domains spatially and temporally at the application level. This significantly eases the task of ensuring freedom from interference in system with mixed critically with sufficient separation between the safety critical and non-safety critical domains, the design can be greatly simplified. A simpler design also leads to a simpler safety case, which translates, overall, in to a lower certification effort.

Qualified Toolchains

ISO26262 not only places requirements on the hardware and software that make up the system, but also demand proper qualification of the tools that are used to create the system. tools are classified in to various categories depending on the impact they have on the safety of the work product, ranging from tool confidence level (TCL)1 to TCL 3, with TCL 3 being the highest level. understanding the importance of toolchain correctness, QNS OS for safety includes the qualification of the c and c++ toolchain to TCL 3. The c and c++ compiler linker and assembler for the ARM and X86 architecture are crucial to the correct generation of the software that will run on the microprocessor in the car. taking on the qualification of these toolchain offloads certification task that could consume a great deal of time and effort from customers and paves a smoother road to project success.

Documentation

• ISO 26262 ASIL D certificate issued by TUV Rheinland
• Safety manual
• Installation and usage guide
• Safety requirement document
• Hard and risk analysis
• Safety Case
• Release notes.

Hardware support

QNX OS Safety is supported on the 32 and 62 bit ARM and X86 architecture. The product is enabled and tested on many popular automotive hardware including intel apollo lake and NXP i MX8. The product can be Adapted to run on a customer's chosen hardware through blackberry QNX's experienced team of safety professional and technical support experts.