Autosar
Training

Making students industry-ready with
application-oriented training program!

Eligibility

BE / B. Tech / ME / M. Tech

Duration

4 Weeks

Autosar
Overview
State Management and System Services
Operating System
Basic of RTE
Basic of Software Components (SWE)
CAN Protocol
Comstack
Autosar Methodology
Autosar Configuration Parameters
UDS Protocol
UDS Services
DCM

Program Modules

Session 1

Autosar Overview

Automotive Basic Introduction (ADAS, Active/Passive Safety)

AUTOSAR Methodology
  • Motivation, Organization
  • SDLC
  • AUTOSAR Concept
  • AUTOSAR Layer Model
  • Approach for developing AUTOSAR software
  • Data exchange mechanism between development partners
    • Autosar XML
    • System Description
    • SWC Description
    • System Extract
    • ECU Extract
      • Autosar interface
      • Introduction to Autosar Tools
      • Autosar work products from OEM to Tier 1

Session 2

State Management and System Services

  • BSW initialization
  • Interaction with SW-C and other BSW modules
  • Mode Management
  • Sleep and Wakeup Handling

Session 3

Operating system

Tasks, Alarm, Counter and Events

Basic of RTE

ISR Configuration

Basic of Software Components (SWC)

Relation to RTE

  • OS Scalability Class
  • RTE introduction and VFB concepts
  • SWC

Session 4

CAN Protocol

CAN Protocol

COMSTACK

COMSTACK

Autosar Configuration parameters

Autosar Configuration parameters

Session 5

UDS Protocol

UDS Protocol

UDS Services

UDS Services

DCM

DCM

Have Any Questions?

1. Is AUTOSAR a software?

Automotive Open System Architecture (AUTOSAR) is an open and standardized automotive software architecture, which supports standardization in interfaces between application software and basic vehicular functions and it helps in establishing common ECU software architecture for all the AUTOSAR members.

2. What are the AUTOSAR tools?

System and Software Authoring, RTE configuration and ECU Extracting with ISOLAR-A.
Configuration of ECU software / BSW modules with ISOLAR-B.
Behaviormodeling of software components with ASCET.
Software validation on the PC with ISOLAR-EVE.
Reliable ECU basic software with RTA.

3. Why do we use AUTOSAR?

AUTOSAR allows the implementation of innovative electronic systems, which can improve safety, environmental friendliness, and overall performance. The standard is set to prepare the industry for upcoming technologies and lower costs without compromising quality.

4. What is AUTOSAR ECU?

AUTOSAR (AUTomotive Open System ARchitecture) is an open and standardized automotive software architecture, jointly developed by automobile manufacturers, suppliers, and tool developers. Its main goal is to introduce a standardized layer between application software and the hardware of an electronic control unit (ECU).

5. What is basic software in AUTOSAR?

Basic Software (AUTOSAR BSW): Basic Software is the standardized software layer, which provides services to the AUTOSAR Software Components and is necessary to run the functional part of the software.

6. Can you stack AUTOSAR?

What is CAN Communication Stack in AUTOSAR Architecture? When the target Bus type for an AUTOSAR compliant software is CAN, the ComStack implementation is executed with respect to CAN Bus. Right from the Interface (IF) and State Manager to low-level drivers, each of these modules need to be configured for CAN Bus.

7. What is ASW and BSW?

It has to invoke startup and shutdown functions of the software component. It acts as layer of separation between ASW (application software) and BSW (base software). The BSW modules are free to call any API functions or other modules directly. Whereas ASW components can only communicate via ports.

8. CAN protocol driver?

Protocol. CAN is a message-based protocol, designed specifically for automotive applications but now also used in other areas such as industrial automation and medical equipment. CAN is one of five protocols used in the OBD-II vehicle diagnostics standard.

9. Why is AUTOSAR adaptive?

The benefits of Adaptive AUTOSAR More efficient development for all manufacturers. Increased speed of development. Reduced development time for interfaces between vehicle sub-systems. Improved safety through standardization.

Apply Online Quick Enquiry Chat with us