What's more, QNX Neutrino's UPM architecture enables the developer to dynamically add software fixes, new applications, and even new device drivers without rebuilding and retesting the existing software stack - a real plus when the existing software is already installed in thousands of vehicles. ISVs can easily add custom drivers, applications, or OS services, without modifying the OS kernel and introducing potential kernel faults. From Prototype to Product in Less Time With a conventional RTOS, prototyping even a minor feature can take days, since the developer has to repeatedly recompile and relink the entire runtime image. With QNX's UPM architecture, these system rebuilds are eliminated. If you change or add a module, you just recompile that module - which typically takes seconds.
Developers can prototype several features in the time it normally takes to prototype just one.
What's more, the OS can immediately identify any module that faults - at the exact instruction. Faults that can take weeks or months to identify with a conventional RTOS often take just minutes to pinpoint. This requires proven realtime determinism - the kind that has made QNX successful in everything from medical instruments to telecom systems. QNX delivers determinism not just at the application level, but also within all subsystems, through nested hardware interrupts, preemptive prioritized context switching, and priority inheritance. Memory is Money Automakers deal in volumes - large volumes.