Autosar Architecture (Learn from Scratch with Demo)

A complete overview on all the BSW layers will be seen here.

This includes the Microcontroller Abstraction Layer (MCAL), ECU Abstraction, Services layers and Complex device driver (CDD)

This section explains how Autosar categorises the interfaces into different types

(Autosar Interface, Standardised Autosar interface, Standardised Interface). However examples of these interfaces types are also covered in the other lectures to come.

A detailed description on what a software component is and what are the different types of components that Autosar offers will be seen here. We will see this with short practical examples as well.

In this Lecture we will take a live use-case example and see how to choose the right software components from the different component types that Autosar specifies.

This lecture explains the different Ports for communication and the different interfaces that are available to be associated with a port. We will clearly see on what each port interface that is available in Autosar is used for.

In this chapter we will take a deeper look into Sender Receiver interface and understand this completely. This interface is the major interface type that will be used in the software.

In this chapter we will take a deeper look into Client Server interface and understand this completely. This interface is the second major interface type that will be used in the software.

In this lecture we will see how to choose the Ports and its interfaces based on a live example use-case which we saw for the components

We will learn what a composition is and the possible ways to connect ports. This covers the explanation of Assembly and Delegation connectors in detail.

This lecture explains the Runnables within an Internal behaviour of a software component. we will be covering all possible options where a port interface can be accessed within a runnable.

We will learn what is Events and why its important for a software component. We will also learn the various events that is specified by Autosar in detail.

We will put all we learnt together and make a consolidated view and summary of the Application software component. This explains what an component should contain and how the configuration we saw until now will be structured.

In this lecture we will be seeing what the Run Time Environment or the RTE is. How important is it in Autosar and the role of the RTE layer in the Autosar Architecture.

We will see how to create and use the RTE APIs to Read and Write a Port data using Sender Receiver Interface. We will be taking the clips of the standards to derive the API in a step by step manner.

We will see how to create and use the RTE APIs to call a server using a receiver Port with Client Server Interface. We will be taking the clips of the standards to derive the API in a step by step manner.

In this lecture we will see how RTE takes care of the communications between components and different layers

In this lecture we will see how RTE takes care of scheduling the Events from software components. A theoretical look on how the configurations will look like is also covered here

In this Lecture we will be seeing the different Autosar tools that are available and a deeper look on the RTE Generator tool outputs that is used to generate the RTE layer.

In this lecture we will see the Autosar methodology in detail with a complete explanation of each and every steps involved in the Autosar development process

In this lecture we will see a live use-case example and we will see clearly on what are the drawbacks in-case we develop this in a typical way or a non Autosar software. This will help us to understand why we need Autosar architecture

In this lecture we will see the theoretical part on how we approach the MCAL layer development from the Auotsar Architecture for our practical usecase

In this lecture we will see the Demo part on how to write a MCAL layer code from the Autosar Architecture for our practical usecase. We will refer to the Autosar standards in hand for reference and learn how to interpret the standards to write a code.

Change Hint:

At 21:00 Adc_valueGroupType is specified as signed integer in standards, but the demo is explained as unsigned integer thats wrong Please read this as "signed integer" as it is from the standards.

In this lecture we will see the theoretical part on how we approach the ECU Abstraction development from the Auotsar Architecture for our practical usecase

Before writing our ARXML configuration, its important to understand how an arxml configuration will look like and the basics out of it. In this lecture we will in general look at the arxml tag structure and how we do references in it.

In this demo we will do the initial setup for our project. We will also have a quick look in the XML editor tool as well so it will be easy for us in the upcoming demo sessions

In this demo we will see how to create the Interfaces (Sender Receiver and Client Server) that we need for our usecase example

In this Demo we will see how to configure the ECU Abstraction software component as part of the BSW layer for our sensor and actuator we have for the live use-case example.

In this Demo we will see how to develop the C file for the ECU Abstraction software component as part of the BSW layer for our sensor and actuator we have for the live use-case example.

In this demo we will be seeing how to write an arxml configuration for the application software component for our live use-case using simple XML editors

In this demo we will be seeing how to write a C fil for the application software component for our live use-case using simple notepad++ editor

In this section be will be seeing on how to write the configurations for Compositions and adding the developed components within. Additionally on how to create Assembly connectors to bind our created ports.

We will see a sample on how the RTE code will look like for our application which will give us a good understanding to RTE