ID 025C: An Introduction to the OSEK Operating System Version 1.0 1 An Introduction to OSEK l JRD l ETAS-STV/PRM-E l 2010 © ETAS GmbH 2008. All rights reserved. The names and designations used in this document are trademarks or brands belonging to their respective owners. James Dickie • Product Manager for Embedded Software • Real-time operating systems • AUTOSAR software components • Software logic analyzer • Experience: • 10 years working in Automotive software engineering • Previous experience of real-time and embedded software engineering in the Oil & Gas and Telecoms industries • Education: • Ph.D. in Digital Signal Processing, University of Strathclyde, Scotland • B. Eng. in Electronic Engineering, University of Strathclyde, Scotland 2 An Introduction to OSEK l JRD l ETAS-STV/PRM-E l 2010 © ETAS GmbH 2008. All rights reserved. The names and designations used in this document are trademarks or brands belonging to their respective owners. Renesas Technology and Solution Portfolio Microcontrollers & Microprocessors #1 Market share worldwide * SolutionsSolutions forfor InnovationInnovation ASIC, ASSP Analog and & Memory Power Devices #1 Market share Advanced and in low-voltage proven technologies MOSFET** * MCU: 31% revenue basis from Gartner "Semiconductor Applications Worldwide Annual Market Share: Database" 25 March 2010 ** Power MOSFET: 17.1% on unit basis from Marketing Eye 2009 (17.1% on unit basis). 3 An Introduction to OSEK l JRD l ETAS-STV/PRM-E l 2010 © ETAS GmbH 2008. All rights reserved. The names and designations used in this document are trademarks or brands belonging to their respective owners. Renesas Technology and Solution Portfolio Microcontrollers & Microprocessors #1 Market share worldwide * SolutionsSolutions forfor InnovationInnovation ASIC, ASSP Analog and & Memory Power Devices Advanced and #1 Market share proven technologies in low-voltage MOSFET** * MCU: 31% revenue basis from Gartner "Semiconductor Applications Worldwide Annual Market Share: Database" 25 March 2010 ** Power MOSFET: 17.1% on unit basis from Marketing Eye 2009 (17.1% on unit basis). 4 An Introduction to OSEK l JRD l ETAS-STV/PRM-E l 2010 4 © ETAS GmbH 2008. All rights reserved. The names and designations used in this document are trademarks or brands belonging to their respective owners. Microcontroller and Microprocessor Line-up Up to 1200 DMIPS, 45, 65 & 90nm process Superscalar, MMU, Multimedia Video and audio processing on Linux Server, Industrial & Automotive Up to 500 DMIPS, 150 & 90nm process High Performance CPU, Low Power 600uA/MHz, 1.5 uA standby Medical, Automotive & Industrial Up to 165 DMIPS, 90nm process High Performance CPU, FPU, DSC 500uA/MHz, 2.5 uA standby Ethernet, CAN, USB, Motor Control, TFT Display Legacy Cores Next-generation migration to RX General Purpose Ultra Low Power Embedded Security Up to 10 DMIPS, 130nm process Up to 25 DMIPS, 150nm process Up to 25 DMIPS, 180, 90nm process 350 uA/MHz, 1uA standby 190 uA/MHz, 0.3uA standby 1mA/MHz, 100uA standby Capacitive touch Application-specific integration Crypto engine, Hardware security 5 Microcontroller and Microprocessor Line-up Up to 1200 DMIPS, 45, 65 & 90nm process Superscalar, MMU, Multimedia Video and audio processing on Linux Server, Industrial & Automotive Up to 500 DMIPS, 150 & 90nm process High Performance CPU, Low Power 600uA/MHz, 1.5 uA standby Medical, Automotive & Industrial Up to 165 DMIPS, 90nm process High Performance CPU, FPU, DSC 500uA/MHz, 2.5 uA standby Ethernet, CAN, USB, Motor Control, TFT Display Legacy Cores Next-generation migration to RX General Purpose Ultra Low Power Embedded Security Up to 10 DMIPS, 130nm process Up to 25 DMIPS, 150nm process Up to 25 DMIPS, 180, 90nm process 350 uA/MHz, 1uA standby 190 uA/MHz, 0.3uA standby 1mA/MHz, 100uA standby Capacitive touch Application-specific integration Crypto engine, Hardware security 6 Innovation Take control of embedded projects with an OS and tools designed for the job 7 An Introduction to OSEK l JRD l ETAS-STV/PRM-E l 2010 © ETAS GmbH 2008. All rights reserved. The names and designations used in this document are trademarks or brands belonging to their respective owners. An Introduction to the OSEK Operating System Agenda • What is an OSEK operating system? • Why use OSEK OS • Overview of OSEK OS objects and configuration • How to build applications with OSEK OS • OSEK OS: The future 8 An Introduction to OSEK l JRD l ETAS-STV/PRM-E l 2010 © ETAS GmbH 2008. All rights reserved. The names and designations used in this document are trademarks or brands belonging to their respective owners. What is an OSEK Operating System? • An operating system allows you to partition and control applications running on a CPU, whilst responding efficiently to interrupts • OSEK OS gives • A very efficient scheduler for tasks and interrupts • Creation of critical code sections • Time-based triggering of tasks • Support for debugging • It does not provide • Drivers for graphics, file systems or networks • The ability to spawn new tasks • Memory protection • Support for multicore processors 9 An Introduction to OSEK l JRD l ETAS-STV/PRM-E l 2010 © ETAS GmbH 2008. All rights reserved. The names and designations used in this document are trademarks or brands belonging to their respective owners. Why use an OSEK Operating System? Motivation • Embedded software development is often very product or project focussed… New Hardware Deadlines Reduce Costs Code Reuse New Shorter Features Maintenance Development Cycles …resulting in a loss of control in software development and direction 10 An Introduction to OSEK l JRD l ETAS-STV/PRM-E l 2010 © ETAS GmbH 2008. All rights reserved. The names and designations used in this document are trademarks or brands belonging to their respective owners. Why use an OSEK Operating System? Benefits • Specification of standard interfaces • Savings in costs and development time • Enhanced quality of control unit software • Independence from individual implementations • Efficient design architecture: configurable and scaleable • Hardware and compiler abstraction • Static configuration gives low overheads • Better partitioning and maintenance of application software • Mature standard • Used in millions of ECUs worldwide • Used in all classes of vehicle electronics • Body controllers • Powertrain • Chassis • Multimedia 11 An Introduction to OSEK l JRD l ETAS-STV/PRM-E l 2010 © ETAS GmbH 2008. All rights reserved. The names and designations used in this document are trademarks or brands belonging to their respective owners. OSEK Origins • OSEK/VDX resulted from the joining of French and German standardization efforts • OSEK = “Offene Systeme und deren Schnittstellen für die Elektronik im Kraftfahrzeug” • Open Systems and the Corresponding Interfaces for Automotive Electronics • VDX = Vehicle Distributed eXecutive • OSEK is a joint project of the automotive industry • “Industry standard for an open-ended architecture for distributed control units in vehicles” • The resulting specifications are open for anyone to use • OSEK has been standardised by the ISO • ISO 17356 • Road vehicles -- Open interface for embedded automotive applications 12 An Introduction to OSEK l JRD l ETAS-STV/PRM-E l 2010 © ETAS GmbH 2008. All rights reserved. The names and designations used in this document are trademarks or brands belonging to their respective owners. The OSEK Specifications Overview • OSEK is more than just the operating system! • A number of complimentary specifications exist • A Binding is used to identify sets of specifications that work together • Certification is available • See www.osek-vdx.org for full details 13 An Introduction to OSEK l JRD l ETAS-STV/PRM-E l 2010 © ETAS GmbH 2008. All rights reserved. The names and designations used in this document are trademarks or brands belonging to their respective owners. The OSEK Specifications Operating System • There are three specifications around the OS • OSEK OS • An event-driven operating system • OSEK Implementation Language (OIL) • A text-based description of an OSEK configuration • Portable between development tools • OSEK Run Time Interface (ORTI) • An interface that allows a suitable debugger to see the OS status 14 An Introduction to OSEK l JRD l ETAS-STV/PRM-E l 2010 © ETAS GmbH 2008. All rights reserved. The names and designations used in this document are trademarks or brands belonging to their respective owners. The OSEK Specifications Communications • OSEK also provides specifications for communication • OSEK COM • Allows communication over a CAN bus • OSEK Network Management (NM) • Serves as the basis for distributed control functions • OSEK Time • Time-triggered environment for highly-dependable systems • OSEK Fault Tolerant COM (FTCOM) • Provides interfaces and protocols for the fault tolerant transfer of data within networks 15 An Introduction to OSEK l JRD l ETAS-STV/PRM-E l 2010 © ETAS GmbH 2008. All rights reserved. The names and designations used in this document are trademarks or brands belonging to their respective owners. OSEK OS Objects Overview • Tasks • Allow blocks of functionality to be called at runtime • ISRs • Handlers for interrupts • Events • Allow synchronisation of tasks • Resources • Create critical sections of code, giving atomic access to data or peripherals • Counters & alarms • Allow time-based triggering of tasks 16 An Introduction to OSEK l JRD l ETAS-STV/PRM-E l 2010 © ETAS GmbH 2008. All rights reserved. The names and designations used in this document