[intern4tional]

QNX is heavily used in industries where functional safety or particular high assurance models are required.

Sure FreeRTOS has a SafeRTOS mode, but its not sufficiently functional for a modern ADAS stack or complex robotics systems. QNX is used in all major automotive companies around the world for a reason, and a crucial part of NVIDIA's DriveOS stack.

[gmueckl]

QNX is in a space with few competitors. FreeRTOS or ThreadX are designed to provide microcontrollers with scheduling and memory management functionality. They don't depend on fancy things like MMUs or provide frameworks for networking or file systems out for the box. The flipside is that you can compile them down to maybe 30kB of machine code.

QNX is designed for more powerful and featureful hardware to drive a software stack with true process isolation and generally provide the bells and whistles of general purpose OS on top of a hard realtime core. It can run complex GUIs without sacrificing its real time capabilities. Not many competitors live in that particular space.

[karlgkk]

> and a crucial part of NVIDIA's DriveOS stack

fwiw they have been working hard to support linux as a second option, and have been major contributors to Real Time Linux

sooooooo

[daghamm]

Are there any automakers out there that use real-time Linux for anything at or above ASIL-B?

[karlgkk]

I know there are a few hypervisor vendors that do heartbeats for C and D. You can use whatever solution you like as long as there's a fallback task.