Scribd Logo
Upload

Welcome to Scribd!

  • 2K views

    Automotive Embedded System Development in AUTOSAR

    Uploaded by

    kumdh
    The document discusses the AUTOSAR standard for automotive embedded systems. It begins by defining AUTOSAR, describing its goals of standardizing interfaces to increase software reuse and manage complexity. It then explains the AUTOSAR layered architecture and key concepts like software components, the runtime environment, and abstraction layers. Finally, it provides an example of a lighting system modeled in AUTOSAR, showing the software components, virtual bus, and basic software architecture.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as PPT, PDF, TXT or read online from Scribd

    Automotive Embedded System Development in AUTOSAR

    Uploaded by

    kumdh
    2K views18 pages
    The document discusses the AUTOSAR standard for automotive embedded systems. It begins by defining AUTOSAR, describing its goals of standardizing interfaces to increase software reuse and manage complexity. It then explains the AUTOSAR layered architecture and key concepts like software components, the runtime environment, and abstraction layers. Finally, it provides an example of a lighting system modeled in AUTOSAR, showing the software components, virtual bus, and basic software architecture.

    Copyright

    © Attribution Non-Commercial (BY-NC)

    Available Formats

    PPT, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    The document discusses the AUTOSAR standard for automotive embedded systems. It begins by defining AUTOSAR, describing its goals of standardizing interfaces to increase software reuse and manage complexity. It then explains the AUTOSAR layered architecture and key concepts like software components, the runtime environment, and abstraction layers. Finally, it provides an example of a lighting system modeled in AUTOSAR, showing the software components, virtual bus, and basic software architecture.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as PPT, PDF, TXT or read online from Scribd
    Download as ppt, pdf, or txt
    2K views18 pages

    Automotive Embedded System Development in AUTOSAR

    Uploaded by

    kumdh
    The document discusses the AUTOSAR standard for automotive embedded systems. It begins by defining AUTOSAR, describing its goals of standardizing interfaces to increase software reuse and manage complexity. It then explains the AUTOSAR layered architecture and key concepts like software components, the runtime environment, and abstraction layers. Finally, it provides an example of a lighting system modeled in AUTOSAR, showing the software components, virtual bus, and basic software architecture.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as PPT, PDF, TXT or read online from Scribd
    Download as ppt, pdf, or txt
    of 18
    At a glance
    Powered by AI
    The key takeaways are that AUTOSAR is a standard for automotive software development that aims to improve complexity management through increased reuse of software modules. It defines a layered architecture and methodology.

    AUTOSAR (AUTomotive Open System Architecture) is a standard developed by automakers to define a common architecture for automotive software. Its goals are to define an open reference architecture for ECU software and specify clear interfaces to enable reusability and growing software quality.

    The main components of AUTOSAR architecture are software components (SW-Cs), runtime environment (RTE), microcontroller abstraction layer (MCAL), ECU abstraction layer (EAL) and services layer.

    Automotive Embedded System

    Development in AUTOSAR
    Contents

    What is AUTOSAR

    AUTOSAR from a Technical Point of View

    Example AUTOSAR System

    Automotive Embedded System Development in AUTOSAR

    2
    What is AUTOSAR

    AUTOSAR (AUTomotive Open System Architecture)


     De-facto standard, jointly developed by automobile manufacturers, suppliers and
    tool developers.
     More than 100 member companies
     Homepage : www.autosar.org

    The idea of AUTOSAR


     Standardized and uniquely-specified interfaces basic software modules help to
    master the increasing complexity
     The consequence is reusability, efficiency and easy handling of electronic in the
    automobile

    AUTOSAR Target and Goal


     Define open reference architecture for ECU software
     Specify a clear interface between basis software components and application
     Reusability
     Growing software quality

    3
    What is AUTOSAR

    AUTOSAR partnership

    10 Core Partners
    48 Associate
    Members

    CapeWare

    52 Premium Members

    OEM Tier 1 Standard Tools Semi-


    Software conductors
    Source:

    4
    What is AUTOSAR

    AUTOSAR Project Objectives


     AUTOSAR vision is an improved complexity management of highly integrated E/E
    architectures through an increased reuse of SW modules between OEM and
    suppliers.

    5
    What is AUTOSAR

    Benefits from AUTOSAR

    6
    AUTOSAR from a Technical Point of View

    AUTOSAR Layered Architecture

    AUTOSAR Application Actuator Sensor Application


    Software
    Component
    Software
    Component
    Software
    Component
    Software
    Component AUTOSAR Software
    Component
    AUTOSAR AUTOSAR AUTOSAR Software AUTOSAR
    Interface
    Interface Interface Interface
    .............. Interface

    ECU
    AUTOSAR Runtime Environment (RTE)
    Firmware
    Standardized
    Standardized Standardized AUTOSAR AUTOSAR
    Standard AUTOSAR
    Interface Interface Interface Interface
    Interface
    Software
    ECU
    Services Communication
    Abstraction
    API 2
    VFB & RTE Standardized Standardized Standardized
    Standardized

    relevant Interface Interface Interface


    Inteface

    API 1 Complex
    Operating
    RTE Device
    System
    relevant Drivers
    Standardized
    Interface
    API 0

    API 3 Private
    Basic Software Microcontroller
    Abstraction
    Interfaces inside
    Basic Software
    possible ECU-Hardware

    7
    AUTOSAR from a Technical Point of View

    AUTOSAR Layered Architecture

    8
    AUTOSAR from a Technical Point of View

    Methodology

     Derive E/E architecture from formal descriptions of soft- and hardware components

    Functional software is described formally in


    terms of “software Components” (SW-C).

    Using “Software Component Descriptions” as


    input, the “Virtual Functional Bus” validates
    the interaction of all components and
    interfaces before software implementation.

    Mapping of “Software Components” to ECUs


    and configuration of basic software.

    The AUTOSAR Methodology supports the


    generation of an E/E architecture.

    9
    AUTOSAR from a Technical Point of View

    AUTOSAR SW-C (Software Component)


     Application is divided into SW-Cs.
     Software Components consist of
     Ports

    Interface to other SW-Cs


     Runnable Entities (or Runnables)

    Procedures which contain the actual implementation

    Triggered cyclically or on event (e.g. data reception)


     Other software components

    Composite components for hierarchical design


     Three types of SW-C
     Atomic SW-C
     Composite SW-C
     Sensor/Actuator SW-C

    10
    AUTOSAR from a Technical Point of View

    RTE (Runtime Environment)


     Implementation of Virtual Functional Bus
     Interface between SW-Cs and Basic Software
     All calls to basic software pass through the RTE
     Communication method : Send/Receive signals, Client/Server functionality
     Triggering of runnables : Cyclically or On event

    11
    AUTOSAR from a Technical Point of View

    MCAL (Microcontroller Abstraction Layer)


     MCAL is the lowest software layer of the Basic Software
     It contains internal drivers, which are software modules with direct access to the
    microcontroller internal peripherals and memory mapped microcontroller external
    devices
     Make higher software layers independent of microcontroller

    12
    AUTOSAR from a Technical Point of View

    EAL (ECU Abstraction Layer)


     The EAL interfaces the drivers of the MACL
     It also contains drivers for external devices
     It offers an API for access to peripherals and divides regardless of their location and
    their connection to the microcontroller (port pins, type of interface)
     Make higher software layers independent of ECU hardware layout

    13
    AUTOSAR from a Technical Point of View

    Services Layer
     Services Layer is the highest layer of the Basic software which also applies for its
    relevance for the application software
     The Services layer offers
     Operating system functionality
     Vehicle network communication and management services
     Memory services (NVRAM management)
     Diagnostic services
     ECU state management
     Provide basic services for application and Basic Software modules

    14
    Example AUTOSAR System : Lighting System

    Software Component View

    15
    Example AUTOSAR System : Lighting System

    Virtual Functional Bus View

    16
    Example AUTOSAR System : Lighting System

    Mapped System

    17
    Example AUTOSAR System : Lighting System

    Basic Software Architecture

    18

    You might also like