Frequently asked questions

What is QNX CAR?

QNX® CAR stands for Connected Automotive Reference. The QNX CAR program provides an application platform (with sample applications, remote update capabilities, and reference implementations), a comprehensive partner ecosystem, and an enablement strategy. QNX CAR integrates QNX operating system and middleware technology with third-party technology in a way that can be simply leveraged by automotive OEMs and tier ones in their designs. The enablement process simplifies access to QNX CAR for the purposes of prototyping and proof-of-concept, and allows customers to easily migrate their prototypes to production systems.

What do you mean by “connected”?

With advances in wireless technology and in keeping with the OEMs vision, the automobile is becoming a connected device much like a smart phone is today. This connectivity is changing the way that the world looks at the car. An infotainment unit is no longer just a CD player; it is a connected computer that can dynamically consume and render content the same way that mobile devices have in the past.

The QNX vision of the connected car includes:

• Connectivity within the vehicle: front to rear seat, all modules throughout the vehicle
• Connectivity to personal devices: media players, USB sticks, portable navigation, etc.
• Connectivity around the car: lane departure, pedestrian detection, etc.
• Connectivity to the cloud, enabling downloads and updates to the vehicle, and taking full advantage of the connection for internet services, updated POIs, distributed speech recognition, etc.

Why is QNX Software Systems introducing this now?

Software complexity in the automobile is increasing at a rate that was unforeseen just a few years ago. The burden of integrating many technologies is huge and getting bigger, and it comes at a time where all programs are undergoing extreme cost scrutiny.

Traditionally, software and silicon vendors have worked loosely together, leaving all the integration work to the tier one supplier. By providing preassembled reference implementations, QNX CAR allows customers to skip first-level integration efforts and to work immediately on product development and differentiation.

QNX and its ecosystem are bringing an application platform to market that customers can leverage and reuse to cut overall program costs and accelerate time to market. As a result, customers can focus their resources on product differentiation.

What can customers use it for?

Customers can use the technologies in QNX CAR to prototype, develop, and deploy a variety of automotive systems, including:

• Rear-seat entertainment systems
• Center stack head units
• Navigation systems
• Multimedia modules
• Internet connectivity devices
• High-end radios
• Telematics devices
• Hands-free calling modules
• Digital instrument clusters

QNX CAR includes advanced support for Adobe Flash, which greatly simplifies the prototyping and customization of human-machine interfaces (HMI).

Note that while there is no charge during the prototyping phase for access to QNX CAR, product fees apply when moving to awarded production programs.

What is the new business model you are bringing to market?

The QNX CAR business model is designed to facilitate access to software and engineering expertise and greatly reduces costs and barriers for initial development and prototyping.

QNX CAR changes the rules with a first-of-its-kind business model that reduces risk for the customer by applying product charges only to those projects that go into awarded production programs.

What third parties are participating in QNX CAR?

QNX CAR is a continuously evolving program and will grow to include representative technologies from throughout the QNX ecosystem. In its initial release, QNX CAR includes technologies from Adobe, Apple, Gracenote, iAnywhere, Pandora Internet Radio, and others. Moving forward, expect to see technologies that support 2D/3D/remote navigation, city view, remote update, voice, and many other key technologies.

What QNX technologies are included in QNX CAR?

At a high level, QNX CAR technology is based on:

• QNX products
• QNX BSPs
• QNX reference implementations
• QNX technology incubator code (technologies in development that aren’t released and may not be necessarily committed for release)
• Third-party integrations

Specific products include:

• QNX Neutrino® RTOS
• QNX Aviage® HMI Player (based on Adobe Flash Lite)
• QNX Aviage Multimedia Suite
• QNX Aviage Acoustic Processing Suite
• Board Support Packages
• QNX CAR HMI and HMI framework
• Complete source for the integration (some exceptions are made for third-party technologies with licensing restrictions)

Is there something that describes QNX CAR in detail?

In addition to the technical resources available at the QNX CAR developer portal, QNX has prepared a whitepaper that discusses QNX CAR in depth. Download whitepaper

What silicon vendors work with CAR?

QNX CAR will support multiple silicon architectures, including ARM, Power, SH, and x86. QNX will work with Freescale, Renesas, Texas Instruments, Nvidia, Fujitsu, Intel and other leading vendors. BSPs currently supported by QNX CAR include:

• Freescale 5121e
• Freescale i.MX35
• Intel Atom
• Renesas 7786

How do customers get their hands on QNX CAR?

Once a customer has been accepted into the program, they can access the QNX CAR develop portal on Foundry27 (www.foundry27.com). The portal provides access to source code for QNX products, technical resources, and forums; it also allows customers to download the absolutely latest QNX CAR code as it is published.

What is the business model for automotive OEMs wanting to access QNX CAR?

To access QNX CAR, OEMs must first join the QNX OIL (OEM Innovation Labs) program. For more information or to join the OIL program.

To qualify for the QNX CAR program, QNX OIL members must first complete a program application.

What is the business model for automotive tier ones wanting to access QNX CAR?

To access QNX CAR, a Tier one must first complete a program application. Once accepted, the Tier one must at a minimum download an evaluation copy of the QNX Momentics® Tool Suite and accept the clickthrough Commercial Software License Agreement.

QNX Software Systems will provide:

• the QNX CAR software pre-loaded on a hardware target. This target is loaned to the program member for no charge.
• access to the QNX CAR project on Foundry27, the QNX community portal.

For the purposes of prototyping, there is no charge to the tier one. Tier ones may develop and demonstrate prototypes to their prospective customers. However, if a tier one wishes to leave a demonstration system with a prospective customer (redistribute), they must ensure that they have acquired redistribution rights from all the software vendors whose technology is included in the demonstration system. QNX Software Systems doesn’t provide any redistribution rights for QNX CAR.

Once the project moves beyond the prototyping stage, the tier one is responsible for establishing commercial engagements with all vendors whose technology they wish to use for their production program.

Tier ones can contact their QNX sales team for additional details.

Can QNX help customize QNX CAR to meet specific customer requirements?

To help customers customize QNX CAR, QNX Software Systems has created the QNX automotive services team. This dedicated group has extensive experience working with automotive tier ones and OEMs and has successfully supported a number of SOPs.

QNX Software Systems will also provide documentation to support customization of the HMI, hardware, or other key aspects of CAR reference implementations.

What is the “apps store” and how can OEMs and their suppliers leverage it?

The concept of creating branded portals where OEMs can deliver new applications and services has garnered considerable interest in the industry. To support this, QNX is creating technology that OEMs and suppliers can use to implement their portals. QNX Software Systems will provide an implementation of an app store. The way it is customized and presented, as well as customer business model, is entirely under the control of the OEM and its suppliers.

For example, an OEM may choose to implement a fully featured, open application store that offers OEM and third-party applications. Conversely, content could be restricted and tightly controlled. Further, the portal could be used for warranty work, recall cost reduction via over-the-air field updating, or dealer application portals.

This technology is an example of technology that will first be made available via the technology incubator.

What is the automotive technology incubator?

The technology provided in QNX CAR is being developed using Foundry 27. Foundry 27 was an initiative that QNX Software Systems launched in 2007 to provide open access to the QNX source code base, and to allow for transparent development between QNX engineering staff and those in the embedded community who are interested and/or want to contribute. All development on Foundry 27 is done in the open with a live Subversion repository.

The technology incubator extends this initiative by creating new technologies applicable to the QNX CAR reference platforms and by providing the technologies first through a specialized QNX CAR Foundry 27 project. Members of QNX CAR program can access these technologies as they develop, and can provide instant feedback and suggestions, or influence the roadmap. This environment fosters rapid development and enables the customer to access bleeding-edge technologies hot off the press.

This model doesn’t eliminate the requirement for testing and creating release builds. Each preintegrated reference will undergo testing and validation with a selected combination of technologies, allowing customers to build an automotive-hardened and stable code base from general availability products. These integrations occur periodically, turning the source spun out of the technology incubator into solid, tested products, following QNX Software Systems’ ISO-certified process.

How does QNX CAR relate to the QNX OIL program?

The QNX OEM Innovation Labs program provides advanced research groups at automotive OEMs with development tools and software for the purpose of commercial development, but not for redistribution of end product. The program makes this software available at a minimal charge to the OEM. By joining the OIL program, OEMs qualify for access to QNX CAR.

How can members of the QNX ecosystem participate?

QNX has the most inclusive ecosystem enablement strategy in the industry. If a software vendor offering complementary technology wishes to port their products to QNX, they can download development seats from the QNX website at no charge. If, like many others, they see value in doing a more comprehensive integration into the QNX CAR environment, they are welcome to initiate a discussion about how best to engage. A quick email to partners@qnx.com will get things started.

What reference implementations are available now?

Currently, QNX Software Systems provides two reference implementations, a multi-node infotainment system and a digital instrument cluster. Additional reference implementations will become available over time.