Andrea Youdale, VP European Operations QNX Software Systems
3 Overview Our Markets Our Competition Increasing Mind Share –The QNX Real Time Platform Initiative A Quick Overview of a Microkernel Architecture QNX in Consumer Electronics QNX in Telecoms & Datacoms A Huge Wealth of Product Modules
Consumer Electronics and Internet Devices Netpliance BT PayphonesNational Semiconductor BCI Loewe
9 Our Competition VxWorks pSOS WinCE Linux Windows NT BeOS
Platform OSs Run on friendly desktop environments and are a nightmare to move to embedded environments. (Linux, Windows NT, BeOS) Operating Systems Live in One of Two Disjoint Worlds RTOSs Run on unfriendly embedded environments and are cross-developed on platform OSs as hosts. (VxWorks, pSOS, WinCE)
QNX is unique in that it runs great on both. Platform OSs Run on friendly desktop environments and are a nightmare to move to embedded environments. (Linux, Windows NT, BeOS) RTOSs Run on unfriendly embedded environments and are cross-developed on platform OSs as hosts. (VxWorks, pSOS, WinCE)
NeutrinoPhoton Tools Applications The QNX Realtime Platform
Programmers code to specific OS APIs. Two APIs have inertia and momentum. QNX is POSIX. More importantly QNX aligns itself with Linux in interpretation and extensions. Source code portable today. Binary RSN. APIs
14 Why Choose QNX over VxWorks A self hosted development environment is more productive –We also provide cross-devopment (Windows, Solaris) We conform to the POSIX standard –VxWorks is proprietary We provide a far more advanced OS architecture –Microkernel design –Full process model MMU protection (not a hack) We have capabilities which give us key advantages –Qnet networking –Photon MicroGUI
Memory Protection Comparison Real-time Executive (VxWorks) Monolithic Kernel (NT/ LINUX) True Microkernel (QNX) Application Device Drivers TCP/IP Stack Application Device Drivers TCP/IP Stack Filesystem TCP/IP Microkernel Device Driver Kernel space User space Kernel space Application User space
16 Why Choose QNX over Linux? Embedding is hard stuff –We are embedded experts with 20 years experience –The new embedded Linux companies have no experience Embedding is an OEM business –OEM sales are the cornerstone of our business We have clear IP ownership of all core OS modules We have capabilities that give us key advantages –Qnet networking –Photon microGUI ® We have a proven business model
Provide a business model to allow for both freeware and commercial use Success Lies Between These Two Extremes
19 Increasing Mind Share (QNX is out there) Embedded systems hide the OS OEMs keep to themselves Because of this Product managers often have to sell QNX to management and their customers QNX lacks a cohesive community of developers QNX remains the secret of a select few
Give it away for free (get.qnx.com) or provide a low cost CDROM CostAvailability WEB download (hassle free) Installation Small download No need to repartition Four minute install Windows / Linux friendly Automatic hardware detection Removing Barriers to Entry
21 Barriers to Exit Getting developers to download QNX is only 1/2 the battle. Success is getting them to stay with QNX.
Enough tools and apps so you dont have to leave. It needs to be cool.
… not a toy version Barriers to Exit Developers want the real thing...
24 Support the community but more importantly… Allow the community to support itself Web-based support –knowledge database –special news groups –automatic and real easy updating of products Well-documented driver kits and published source code –drivers –libraries –applications –... Barriers to Exit
25 Barriers to Exit Open Source much of QNX Allows developers to better customize or tune the system. Shows by example how things work. Allows developers to avoid or overcome bugs in components that they didnt write. Source Code gives developers control over their lives. It makes them happy and in most cases more productive.
26 Why this is good for QNX Enthusiasts will play with it free at home –Some will be in a position to recommend it at work –Some will develop applications and drivers Engineers at work will be able to use QNX to prototype systems without getting cost approval –A working prototype shortens the sales cycle Our OEMs will become part of a community More developers which enables –more drivers –more applications –more consultants –more mind share
27 Why this is good for our OEMs More experienced engineers available More applications and drivers available More tools available QNXMore brand name recognition for their chosen OS - QNX
Networked and Distributed Disk Fsys CDROM Fsys Audio App TCP/IP Microkernel Photon GUI QNET App QNET Microkernel Messages flow transparently through QNET from one message bus to another. All applications and servers become network distributed without any special code.
Microkernel Architecture Disk Fsys CDROM Fsys Audio App TCP/IP Microkernel Photon GUI - Each process lives in its own memory protected address space - Drivers, Filesystems and protocol stacks are just processes which create names in the pathname space and accept messages (servers) - They may be started and stopped dynamically. - Processes communicate using messages open(/dev/ser1,..)sends a message to the serial driver process read(fd, …)sends a message to read data - Applications send messages to servers (clients) - Process may share memory using the standard POSIX mmap calls
32 QNET - A Fully Distributed Environment It seamlessly connects computers. Messages flow transparently between computers. Resources become network distributed. Applications can access these resources without any special code. The network can be –in a box (backplane) –over a LAN (wired and/or wireless) –over the internet
33 Consumer Electronics Internet Devices Home Gateways Automotive (driver information systems)
34 * IDC, February 2000 ** VDC, March 2000 Industry analysts agree: the market for embedded devices is enormous! –Growing to $17.8 B in next 4 years* –Estimated 416 million units to be shipped in 2003** –More information appliances than PCs by 2002 –Embedded devices will place new demands on embedded OSs the new standards are not yet defined there is NO dominant player –The success of an embedded device is measured by its pervasiveness –Time-to-market is critical Market Opportunity for Embedded Devices
35 Home Networking Internet Home PC Internet Device WebPAD Home Gateway LAN
QNET for the HOME V90 modem Cable modem DSL FLASH FSYS CDROM FSYS TCP/IP QNET Browser Photon QNET Graphics CIFS FSYS Disk Fsys
QNET for the HOME - QNET for the HOME - Super Thin Clients V90 modem Cable modem DSL FLASH FSYS CDROM FSYS TCP/IP QNET Browser Photon Browser Photon Java QNET Graphics
QNET for the HOME - QNET for the HOME - Future Gateways V90 modem Cable modem DSL FLASH FSYS CDROM FSYS TCP/IP QNET Graphics HAVI X10 Blue Tooth
39 Device Examples - Heavy Appliance 200 MHz CPU Graphics Audio USB FLASH FSYS CDROM FSYS TCP/IP Browser Photon Graphics Real Audio Flash Player Java Audio 16 or 32 Meg RAM 16 or 32 Meg FLASH
40 Device Examples - Medium Appliance FLASH FSYS CDROM FSYS TCP/IP Browser Photon Graphics Real Audio Flash Player Java Audio 200 MHz CPU Graphics Audio USB 16 or 32 Meg RAM 16 or 32 Meg FLASH Network boot from a heavy appliance or home gateway QNET Use TCP/IP stack on another device. All devices share a single IP address! Use file systems on another device.
41 Device Examples - Thin Appliance FLASH FSYS CDROM FSYS TCP/IP Browser Photon Graphics Real Audio Flash Player Java Audio 200 MHz CPU Graphics Audio USB 16 or 32 Meg RAM 16 or 32 Meg FLASH Network boot from a heavy appliance or home gateway QNET 2 or 4 Run programs on a remote device and just message input data, graphics data and sound data to the thin client over QNET
43 Internet Applications Citrix ICA Client –Access to windows applications –POP3, IMAP4, MIME attachments AOL Instant Messenger
44 Multi-Media DVD –Full Software decode based on the XING player MPEG2 and MPEG1 (VCD and VCD2) Video MPEG1 and AC3 Audio CD Audio MP3 MIDI WAV
45 Telecoms & Datacoms High Availability Through Advanced OS Architecture Your system is no more reliable than the base upon which it is build
46 QNET for Telecoms/Datacoms Systems are networked together and do not share memory. Each system runs its own operating system and applications. A fault in one system will not directly effect the others. Networking is inside the box PCI backplane, internal switching fabric LinecardLinecardLinecardControlcard
47 QNET for HA Applications Load Balanced Distribution Data is sent out the link which will deliver it the fastest. This is be based upon link speed, queue length for each link. LinecardLinecardLinecardControlcard
48 QNET for HA Applications Ordered Distribution Data is sent out a primary link. If it fails data is diverted to a secondary link. The primary link is probed and when it comes back online data is diverted back to it. LinecardLinecardLinecardControlcard
49 QNET for HA Parallel Distribution Data is sent out both links at the same time. A failure on one link will not cause a stutter. LinecardLinecardLinecardControlcard
50 SMP Support PPC 604, 750, 7400 Pentium I, II, III One copy of the kernel runs on all processors and it and all applications share memory.
51 Fault Tolerant Distributed and SMP You can build massively scalable, high performance, fault tolerant systems by combining SMP in a distributed system. LinecardLinecard Controlcard
52 QNX Architecture does make a Difference! Difference!