DOCSLIB.ORG

Specification of Operating System AUTOSAR Release 4.2.2

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Specification of Operating System AUTOSAR Release 4.2.2 Specification of Operating System AUTOSAR Release 4.2.2 Document Title Specification of Operating System Document Owner AUTOSAR Document Responsibility AUTOSAR Document Identification No 034 Document Classification Standard Document Status Final Part of AUTOSAR Release 4.2.2 Document Change History Release Changed by Change Description 4.2.2 AUTOSAR Allow calls to ControlIdle from all cores Release Minor updates/clarification of descriptions Management Editorial changes 4.2.1 AUTOSAR Add support for AsilQmProtection Release Minor updates/clarification of descriptions Management Editorial changes 4.1.3 AUTOSAR Changed multiplicity of attributes in Release IocSender/ReceiverProperties Management Minor updates/clarification of descriptions Editorial changes 4.1.2 AUTOSAR Clarification on E_OS_NESTING_DEADLOCK Release Update of table 2 Management Corrected multiplicity of ECUC_Os_00393 Minor updates/clarification of descriptions Editorial changes Removed chapter(s) on change documentation 4.1.1 AUTOSAR Add support for ECU degradation Administration Changed service interface description to a formal format Several minor changes and clarifications 4.0.3 AUTOSAR Included MultiCore support from former Administration “Specification of Multi-Core OS Architecture” 3.1.5 AUTOSAR Clarification in 7.8.1 (meaning of "do nothing") Administration and 7.1.2.1 ("OSEK declarations") Minor changes as typos and rewording 3.1.4 AUTOSAR Extension of services (Chapter 12) Administration States in OS- Applications Active termination of other OS-Applications in possible (Chapter8) Legal disclaimer revised Chapter 10.4 revised 1 of 247 Document ID 034: AUTOSAR_SWS_OS - AUTOSAR confidential - Specification of Operating System AUTOSAR Release 4.2.2 Document Change History Release Changed by Change Description 3.1.2 AUTOSAR Changes in OS configuration: Administration removed "OsAppModeId" Parameter from OsAppModeContainer added optional references from OsAppModeContainer to OsAlarm, OsTask and OsScheduleTable 3.1.1 AUTOSAR Legal Disclaimer revised Administration 3.0.2 AUTOSAR Added “OsScheduleTableDuration” parameter Administration to configuration specification chapter 3.0.1 AUTOSAR Changed methods for timing protection Administration Moved configuration from OIL to AUTOSAR XML Clarrified description for synchronization and schedule tables Document meta information extended Small layout adaptations made 2.1.15 AUTOSAR Added support for SoftwareFreeRunningTimer Administration (SWFRT) incl. 2 new APIs Added API to start a schedule table synchron Misc. Corrections, Clarification and further explanations Legal disclaimer revised Release Notes added “Advice for users” revised “Revision Information” added 2.0 AUTOSAR Document structure adapted to common Administration Release 2.0 SWS Template. Major changes in chapter 10 Structure of document changed partly Other changes see chapter 14 1.0 AUTOSAR Initial Release Administration 2 of 247 Document ID 034: AUTOSAR_SWS_OS - AUTOSAR confidential - Specification of Operating System AUTOSAR Release 4.2.2 Disclaimer This specification and the material contained in it, as released by AUTOSAR, is for the purpose of information only. AUTOSAR and the companies that have contributed to it shall not be liable for any use of the specification. The material contained in this specification is protected by copyright and other types of Intellectual Property Rights. The commercial exploitation of the material contained in this specification requires a license to such Intellectual Property Rights. This specification may be utilized or reproduced without any modification, in any form or by any means, for informational purposes only. For any other purpose, no part of the specification may be utilized or reproduced, in any form or by any means, without permission in writing from the publisher. The AUTOSAR specifications have been developed for automotive applications only. They have neither been developed, nor tested for non-automotive applications. The word AUTOSAR and the AUTOSAR logo are registered trademarks. Advice for users AUTOSAR specifications may contain exemplary items (exemplary reference models, "use cases", and/or references to exemplary technical solutions, devices, processes or software). Any such exemplary items are contained in the specifications for illustration purposes only, and they themselves are not part of the AUTOSAR Standard. Neither their presence in such specifications, nor any later documentation of AUTOSAR conformance of products actually implementing such exemplary items, imply that intellectual property rights covering such exemplary items are licensed under the same rules as applicable to the AUTOSAR Standard. 3 of 247 Document ID 034: AUTOSAR_SWS_OS - AUTOSAR confidential - Specification of Operating System AUTOSAR Release 4.2.2 Table of Content 1 Introduction and functional overview ................................................................. 10 2 Acronyms and abbreviations ............................................................................. 11 2.1 Glossary of Terms ...................................................................................... 11 3 Related documentation...................................................................................... 16 3.1 Input documents ......................................................................................... 16 3.2 Related standards and norms .................................................................... 17 3.2.1 OSEK/VDX .......................................................................................... 17 3.2.2 HIS ...................................................................................................... 17 3.3 Company Reports, Academic Work, etc. .................................................... 18 3.4 Related specification .................................................................................. 18 4 Constraints and assumptions ............................................................................ 19 4.1 Existing Standards ..................................................................................... 19 4.2 Terminology ............................................................................................... 19 4.3 Interaction with the RTE ............................................................................. 19 4.4 Operating System Abstraction Layer (OSAL) ............................................. 20 4.5 Multi-Core Hardware assumptions ............................................................. 20 4.5.1 CPU Core features .............................................................................. 20 4.5.2 Memory features ................................................................................. 21 4.5.3 Multi-Core Limitations ......................................................................... 21 4.6 Limitations .................................................................................................. 22 4.6.1 Hardware............................................................................................. 22 4.6.2 Programming Language ...................................................................... 22 4.6.3 Miscellaneous ..................................................................................... 23 4.7 Applicability to car domains ........................................................................ 23 5 Dependencies to other modules ........................................................................ 24 5.1 File structure .............................................................................................. 24 5.1.1 Code file structure ............................................................................... 24 5.1.2 Header file structure ............................................................................ 24 6 Requirements Traceability ................................................................................. 26 7 Functional specification ..................................................................................... 43 7.1 Core OS ..................................................................................................... 43 7.1.1 Background & Rationale ..................................................................... 43 7.1.2 Requirements ...................................................................................... 43 7.2 Software Free Running Timer .................................................................... 46 7.3 Schedule Tables......................................................................................... 47 7.3.1 Background & Rationale ..................................................................... 47 7.3.2 Requirements ...................................................................................... 47 7.4 Schedule Table Synchronization ................................................................ 54 7.4.1 Background & Rationale ..................................................................... 54 7.4.2 Requirements ...................................................................................... 56 7.5 Stack Monitoring Facilities .......................................................................... 63 7.5.1 Background & Rationale ..................................................................... 63 4 of 247 Document ID 034: AUTOSAR_SWS_OS - AUTOSAR confidential - Specification of Operating System AUTOSAR Release 4.2.2 7.5.2 Requirements
Load more

Recommended publications
  • Cobia Database Articles Final Revision 2.0, 2-1-2017
    Revision 2.0 (2/1/2017) University of Miami Article TITLE DESCRIPTION AUTHORS SOURCE YEAR TOPICS Number Habitat 1 Gasterosteus canadus Linné [Latin] [No Abstract Available - First known description of cobia morphology in Carolina habitat by D. Garden.] Linnaeus, C. Systema Naturæ, ed. 12, vol. 1, 491 1766 Wild (Atlantic/Pacific) Ichthyologie, vol. 10, Iconibus ex 2 Scomber niger Bloch [No Abstract Available - Description and alternative nomenclature of cobia.] Bloch, M. E. 1793 Wild (Atlantic/Pacific) illustratum. Berlin. p . 48 The Fisheries and Fishery Industries of the Under this head was to be carried on the study of the useful aquatic animals and plants of the country, as well as of seals, whales, tmtles, fishes, lobsters, crabs, oysters, clams, etc., sponges, and marine plants aml inorganic products of U.S. Commission on Fisheries, Washington, 3 United States. Section 1: Natural history of Goode, G.B. 1884 Wild (Atlantic/Pacific) the sea with reference to (A) geographical distribution, (B) size, (C) abundance, (D) migrations and movements, (E) food and rate of growth, (F) mode of reproduction, (G) economic value and uses. D.C., 895 p. useful aquatic animals Notes on the occurrence of a young crab- Proceedings of the U.S. National Museum 4 eater (Elecate canada), from the lower [No Abstract Available - A description of cobia in the lower Hudson Eiver.] Fisher, A.K. 1891 Wild (Atlantic/Pacific) 13, 195 Hudson Valley, New York The nomenclature of Rachicentron or Proceedings of the U.S. National Museum Habitat 5 Elacate, a genus of acanthopterygian The universally accepted name Elucate must unfortunately be supplanted by one entirely unknown to fame, overlooked by all naturalists, and found in no nomenclator.
    [Show full text]
  • Managing Files with Sterling Connect:Direct File Agent 1.4.0.1
    Managing Files with Sterling Connect:Direct File Agent 1.4.0.1 IBM Contents Managing Files with Sterling Connect:Direct File Agent.......................................... 1 Sterling Connect:Direct File Agent Overview.............................................................................................. 1 How to Run Sterling Connect:Direct File Agent.......................................................................................... 2 Sterling Connect:Direct File Agent Logging.................................................................................................3 Sterling Connect:Direct File Agent Configuration Planning........................................................................ 3 Sterling Connect:Direct File Agent Worksheet ...........................................................................................4 Considerations for a Large Number of Watch Directories.......................................................................... 6 Modifying MaxFileSize............................................................................................................................ 6 Modifying MaxBackupIndex...................................................................................................................6 Considerations for a Large Number of Files in a Watch Directory..............................................................7 Sterling Connect:Direct File Agent Configuration Scenarios...................................................................... 7 Scenario:Detecting
    [Show full text]
  • An Overview of the Jumplist Configuration File in Windows 7
    Journal of Digital Forensics, Security and Law Volume 7 Number 1 Article 2 2012 An Overview of the Jumplist Configuration File in Windows 7 Harjinder S. Lallie University of Warwick, Coventry Parmjit S. Bains University of Derby, School of Computing and Mathematics Follow this and additional works at: https://commons.erau.edu/jdfsl Part of the Computer Engineering Commons, Computer Law Commons, Electrical and Computer Engineering Commons, Forensic Science and Technology Commons, and the Information Security Commons Recommended Citation Lallie, Harjinder S. and Bains, Parmjit S. (2012) "An Overview of the Jumplist Configuration File in Windows 7," Journal of Digital Forensics, Security and Law: Vol. 7 : No. 1 , Article 2. DOI: https://doi.org/10.15394/jdfsl.2012.1110 Available at: https://commons.erau.edu/jdfsl/vol7/iss1/2 This Article is brought to you for free and open access by the Journals at Scholarly Commons. It has been accepted for inclusion in Journal of Digital Forensics, Security and Law by an authorized administrator of (c)ADFSL Scholarly Commons. For more information, please contact [email protected]. Journal of Digital Forensics, Security and Law, Vol. 7(1) An Overview of the Jumplist Configuration File in Windows 7 Harjinder Singh Lalli University of Warwick, International Digital Laboratory (WMG), University of Warwick, Coventry, CV4 7AL, UK; [email protected] Parmjit Singh Bains University of Derby, School of Computing and Mathematics, Kedleston Road, Derby, DE22 1GB, UK; [email protected] ABSTRACT The introduction of Jumplists in Windows 7 was an important feature from a forensic examiners viewpoint. Jumplist configuration files can provide the examiner with a wealth of information relating to file access and in particular: dates/times, Volume GUIDs and unique file object IDs relating to those files.
    [Show full text]
  • Filesystem Hierarchy Standard
    Filesystem Hierarchy Standard LSB Workgroup, The Linux Foundation Filesystem Hierarchy Standard LSB Workgroup, The Linux Foundation Version 3.0 Publication date March 19, 2015 Copyright © 2015 The Linux Foundation Copyright © 1994-2004 Daniel Quinlan Copyright © 2001-2004 Paul 'Rusty' Russell Copyright © 2003-2004 Christopher Yeoh Abstract This standard consists of a set of requirements and guidelines for file and directory placement under UNIX-like operating systems. The guidelines are intended to support interoperability of applications, system administration tools, development tools, and scripts as well as greater uniformity of documentation for these systems. All trademarks and copyrights are owned by their owners, unless specifically noted otherwise. Use of a term in this document should not be regarded as affecting the validity of any trademark or service mark. Permission is granted to make and distribute verbatim copies of this standard provided the copyright and this permission notice are preserved on all copies. Permission is granted to copy and distribute modified versions of this standard under the conditions for verbatim copying, provided also that the title page is labeled as modified including a reference to the original standard, provided that information on retrieving the original standard is included, and provided that the entire resulting derived work is distributed under the terms of a permission notice identical to this one. Permission is granted to copy and distribute translations of this standard into another language, under the above conditions for modified versions, except that this permission notice may be stated in a translation approved by the copyright holder. Dedication This release is dedicated to the memory of Christopher Yeoh, a long-time friend and colleague, and one of the original editors of the FHS.
    [Show full text]
  • Common Errors in English by Paul Brians [email protected]
    Common Errors in English by Paul Brians [email protected] http://www.wsu.edu/~brians/errors/ (Brownie points to anyone who catches inconsistencies between the main site and this version.) Note that italics are deliberately omitted on this page. What is an error in English? The concept of language errors is a fuzzy one. I'll leave to linguists the technical definitions. Here we're concerned only with deviations from the standard use of English as judged by sophisticated users such as professional writers, editors, teachers, and literate executives and personnel officers. The aim of this site is to help you avoid low grades, lost employment opportunities, lost business, and titters of amusement at the way you write or speak. But isn't one person's mistake another's standard usage? Often enough, but if your standard usage causes other people to consider you stupid or ignorant, you may want to consider changing it. You have the right to express yourself in any manner you please, but if you wish to communicate effectively you should use nonstandard English only when you intend to, rather than fall into it because you don't know any better. I'm learning English as a second language. Will this site help me improve my English? Very likely, though it's really aimed at the most common errors of native speakers. The errors others make in English differ according to the characteristics of their first languages. Speakers of other languages tend to make some specific errors that are uncommon among native speakers, so you may also want to consult sites dealing specifically with English as a second language (see http://www.cln.org/subjects/esl_cur.html and http://esl.about.com/education/adulted/esl/).
    [Show full text]
  • Learning the Vi Editor
    Learning the vi Editor en.wikibooks.org December 29, 2013 On the 28th of April 2012 the contents of the English as well as German Wikibooks and Wikipedia projects were licensed under Creative Commons Attribution-ShareAlike 3.0 Unported license. A URI to this license is given in the list of figures on page 103. If this document is a derived work from the contents of one of these projects and the content was still licensed by the project under this license at the time of derivation this document has to be licensed under the same, a similar or a compatible license, as stated in section 4b of the license. The list of contributors is included in chapter Contributors on page 101. The licenses GPL, LGPL and GFDL are included in chapter Licenses on page 107, since this book and/or parts of it may or may not be licensed under one or more of these licenses, and thus require inclusion of these licenses. The licenses of the figures are given in the list of figures on page 103. This PDF was generated by the LATEX typesetting software. The LATEX source code is included as an attachment (source.7z.txt) in this PDF file. To extract the source from the PDF file, you can use the pdfdetach tool including in the poppler suite, or the http://www. pdflabs.com/tools/pdftk-the-pdf-toolkit/ utility. Some PDF viewers may also let you save the attachment to a file. After extracting it from the PDF file you have to rename it to source.7z.
    [Show full text]
  • "AUTOSAR Proofs to Be the Automotive Software Platform For
    AUTOSAR proofs to be THE automotive software platform for intelligent mobility Dr.-Ing. Thomas Scharnhorst AUTOSAR Spokesperson Simon Fürst, BMW AG Tony Jaux, PSA Peugeot Citroën Stefan Rathgeber, Continental Corporation Thomas Rüping, Robert Bosch GmbH Lorenz Slansky, Daimler AG Kenji Nishikawa, Toyota Motor Company Frank Kirschke-Biller, Ford Motor Company Dr. Carsten Krömke, Volkswagen AG Rick Flores, General Motors ELIV, Bonn Germany October 18th -19th 2017 Overview ➢ Introduction Overview and achievements ➢ New challenges and use cases ➢ The Adaptive Platform Overview 1st release of the Adaptive Platform 17-03 Roadmap ➢ New cooperation model Agile development Collaboration with other standardization bodies ➢ Summary 2 19-October-2017 ELIV VDI Congress Bonn 2017 E/E innovations in vehicle development are increasing 90% of all innovations All major innovations Linked are driven Networks by E/E Infotainment Vehicles are connected to Electronic the back-end Mechanics Support 1970 1980 1990 2000 2010 2020 3 19-October-2017 ELIV VDI Congress Bonn 2017 AUTOSAR – Core Partners and Partners (June 2017) 29 Development Partners 9 Core Partners 44 Premium Partners 91 Associate Partners 19 Attendees General Generic Standard Tools and Semi- OEM Tier 1 Software Services conductors 4 19-October-2017 ELIV VDI Congress Bonn 2017 AUTOSAR vision AUTOSAR aims to improve complexity management of integrated E/E architectures through increased reuse and exchangeability of SW modules between OEMs and suppliers. OEM b Exchangeability between suppliers’
    [Show full text]
  • Massachusetts Institute of Technology Bulletin
    d 7I THE DEAN OF SCIEN<C OCT 171972 MASSACHUSETTS INSTITUTE OF TECHNOLOGY BULLETIN REPORT OF THE PRESIDENT 1971 MASSACHUSETTS INSTITUTE OF TECHNOLOGY BULLETIN REPORT OF THE PRESIDENT FOR THE ACADEMIC YEAR 1970-1971 MASSACHUSETTS INSTITUTE OF TECHNOLOGY BULLETIN VOLUME 107, NUMBER 2, SEPTEMBER, 1972 Published by the Massachusetts Institute of Technology 77 MassachusettsAvenue, Cambridge, Massachusetts, five times yearly in October, November, March, June, and September Second class postage paid at Boston, Massachusetts. Issues of the Bulletin include REPORT OF THE TREASURER REPORT OF THE PRESIDENT SUMMER SESSION CATALOGUE PUBLICATIONS AND THESES and GENERAL CATALOGUE Send undeliverable copies and changes of address to Room 5-133 Massachusetts Institute of Technology Cambridge,Massachusetts 02139. THE CORPORATION Honorary Chairman:James R. Killian, Jr. Chairman:Howard W. Johnson President:Jerome B. Wiesner Chancellor: Paul E. Gray Vice Presidentand Treasurer:Joseph J. Snyder Secretary:John J. Wilson LIFE MEMBERS Bradley Dewey, Vannevai Bush, James M. Barker, Thomas C. Desmond, Marshall B. Dalton, Donald F. Carpenter, Thomas D. Cabot, Crawford H. Greenewalt, Lloyd D. Brace, William A. Coolidge, Robert C. Sprague, Charles A. Thomas, David A. Shepard, George J. Leness, Edward J. Hanley, Cecil H. Green, John J. Wilson, Gilbert M. Roddy, James B. Fisk, George P. Gardner, Jr., Robert C. Gunness, Russell DeYoung, William Webster, William B. Murphy, Laurance S. Rockefeller, Uncas A. Whitaker, Julius A. Stratton, Luis A. Ferr6, Semon E. Knudsen, Robert B. Semple, Ir6n6e du Pont, Jr., Eugene McDermott, James R. Killian, Jr. MEMBERS Albert H. Bowker, George P. Edmonds, Ralph F. Gow, Donald A. Holden, H. I. Romnes, William E.
    [Show full text]
  • Filesystem Hierarchy Standard
    Filesystem Hierarchy Standard Filesystem Hierarchy Standard Group Edited by Rusty Russell Daniel Quinlan Filesystem Hierarchy Standard by Filesystem Hierarchy Standard Group Edited by Rusty Russell and Daniel Quinlan Published November 4 2003 Copyright © 1994-2003 Daniel Quinlan Copyright © 2001-2003 Paul ’Rusty’ Russell Copyright © 2003 Christopher Yeoh This standard consists of a set of requirements and guidelines for file and directory placement under UNIX-like operating systems. The guidelines are intended to support interoperability of applications, system administration tools, development tools, and scripts as well as greater uniformity of documentation for these systems. All trademarks and copyrights are owned by their owners, unless specifically noted otherwise. Use of a term in this document should not be regarded as affecting the validity of any trademark or service mark. Permission is granted to make and distribute verbatim copies of this standard provided the copyright and this permission notice are preserved on all copies. Permission is granted to copy and distribute modified versions of this standard under the conditions for verbatim copying, provided also that the title page is labeled as modified including a reference to the original standard, provided that information on retrieving the original standard is included, and provided that the entire resulting derived work is distributed under the terms of a permission notice identical to this one. Permission is granted to copy and distribute translations of this standard into another language, under the above conditions for modified versions, except that this permission notice may be stated in a translation approved by the copyright holder. Table of Contents 1. Introduction........................................................................................................................................................1 1.1.
    [Show full text]
  • The OS/2 Warp 4 CID Software Distribution Guide
    SG24-2010-00 International Technical Support Organization The OS/2 Warp 4 CID Software Distribution Guide January 1998 Take Note! Before using this information and the product it supports, be sure to read the general information in Appendix D, “Special Notices” on page 513. First Edition (January 1998) This edition applies to OS/2 Warp 4 in a software distribution environment and to NetView Distribution Manager/2 (NVDM/2) with Database 2 (DB2) Version 2.11 for OS/2 and Tivoli TME 10 Software Distribution 3.1.3 for OS/2 (SD4OS2) software distribution managers. This edition also applies to OS/2 Warp 4 subcomponents, such as TCP/IP 4.0, MPTS, NetFinity 4.0, Peer Services, and LAN Distance, and to OS/2- related products, such as eNetwork Personal Communications for OS/2 Warp, eNetwork Communications Server for OS/2 Warp, Transaction Server, Lotus Notes, and Lotus SmartStuite 96 for OS/2 Warp. Comments may be addressed to: IBM Corporation, International Technical Support Organization Dept. DHHB Building 045 Internal Zip 2834 11400 Burnet Road Austin, Texas 78758-3493 When you send information to IBM, you grant IBM a non-exclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you. © Copyright International Business Machines Corporation 1998. All rights reserved Note to U.S Government Users – Documentation related to restricted rights – Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corp. Contents Figures. .xiii Tables. xvii Preface. .xix How This Redbook in Organized .
    [Show full text]
  • Objective Is
    Lehigh Preserve Institutional Repository Design of a microprocessor-based emulsion polymerization process control facility Dimitratos, John N. 1987 Find more at https://preserve.lib.lehigh.edu/ This document is brought to you for free and open access by Lehigh Preserve. It has been accepted for inclusion by an authorized administrator of Lehigh Preserve. For more information, please contact [email protected]. Design of a Microprocessor-based Emulsion Polymerization Process Control Facility A research report written in partial fulfillment of the requirements for the degree of Master of Science in Chemical F:ngim·ering, Lehigh University, Bethlehem, Pennsylvania by John N. Dimitratos June 1987 ,. Design of a Microprocessor-based Emulsion Polymerization .. ,_.,,-•• ·, ,, -i •:>:.·.:':' Process Control Facility ' A research report written in partial fulfillment of the requirements for the degree of Master of Science in Chemical Engineering, Lehigh University, Bethlehem, Pennsylvania by John N. Dimitratos June 1987 •1 to my father and my brother there art times when it is hard to decide what should be chosen at what price, and what endured in return for what reward. Perhaps it is still harder to stick to the decision Aristotle (384-322 B.C) Ethics, Book Ill. Abstract The explosion of microcomputer technology and the recent developments in software and hardware products introduce a new horizon of capabilities for the process control engineer. However, taking advantage of this new technology is not something easily done. H the process control engineer has to undertake such a project soon he will have to deal with the different languages the software engineer and the plant operator use.
    [Show full text]
  • ID 025C: an Introduction to the OSEK Operating System Version 1.0
    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
    [Show full text]