Classic AUTOSAR layers, COM stack and RTE: free, 65 minutes
A single 65-minute recorded Skill-Lync webinar led by Jegan Amirthalingam, taught with slides. It starts with why vehicle software needs an architecture, then covers the Classic AUTOSAR layered architecture, a CAN communication stack module by module, the RTE and its implementation, and application development approaches, with a Q&A at the end.
25 chapters · published 31 Aug 2023 · 29,821 views as of 19 Nov 2026 · by Skill-Lync
Free. We ask for your name and phone once before it plays here · or watch on YouTube ↗
Who is this course for?
Embedded and electronics engineers and students who know some C and want to see how a Classic AUTOSAR ECU is structured, from basic software layers to the RTE, before choosing a BSW or application path.
What will you learn?
- Explain why vehicle software has grown so large and why a standard architecture helps
- Describe the Classic AUTOSAR layers and why an upper layer calls only the layer below
- Say what the microcontroller abstraction layer, ECU abstraction and services layers each contain
- Follow a signal through the COM module, PDU router and CAN interface down to the CAN driver
- Describe how the RTE is generated from the ARXML of all software and basic software components
- Compare the top-down and bottom-up flows for building AUTOSAR application software with models
What does each part of the course cover?
9 sections, in watching order. Click a timestamp to jump the player there. The video description has no chapter list, so these chapters and timestamps were written from the video itself.
- 0:0114 min · 6 chapters
Why vehicle software needs an architecture
Jegan Amirthalingam opens by asking how many lines of code a typical vehicle carries, answers more than 100 million, and quotes about 1 billion by 2030. The talk then covers the growing share of embedded systems in vehicle cost, the shift from distributed to centralised E/E architecture, and software complexity growing faster than productivity.
Chapters
- 0:01Introduction, agenda and the lines-of-code question
- 2:17How much code a vehicle runs
- 3:41Embedded systems' share of vehicle cost and software-defined vehicles
- 5:02From distributed to domain and centralised E/E architecture
- 9:37Software complexity versus productivity
- 12:43India's opportunity in automotive software
- 14:229 min · 4 chapters
Vehicle software architecture and what Classic AUTOSAR standardises
A layered vehicle software stack is drawn, then an infotainment system is mapped onto hardware, operating system, middleware and HMI. Classic AUTOSAR is introduced as a signal-oriented standard: standard basic software with customer-specific applications on top, aiming at portable applications and reusable base software, backed by a consortium.
- 23:489 min · 2 chapters
Who gains from AUTOSAR, and legacy ECU versus AUTOSAR ECU
The speaker walks through the benefits for OEMs, tier ones and tool providers, then the exchangeability of applications between manufacturers, suppliers and vehicle platforms. A comparison of a legacy ECU with an AUTOSAR ECU contrasts super-loop software with an OS-driven stack.
- 32:194 min · 2 chapters
Layered architecture and application software components
The layers are named: microcontroller abstraction, services and ECU abstraction, RTE and application. The speaker explains with .c and .h files why an upper layer calls only the layer below. Application software is arranged as components that talk to the RTE through sender-receiver, client-server and mode switch interfaces.
- 36:144 min · 3 chapters
Basic software layer by layer, configuration tool and the CAN stack
The microcontroller abstraction layer is shown as the part that changes with hardware, with drivers for peripherals such as watchdog, timer, flash and the hardware security module. The AUTOSAR configuration tool produces an ECU description file in ARXML and generates cfg.c and cfg.h files. A CAN stack is then traced across the layers.
- 40:2010 min · 3 chapters
The communication stack: COM, PDU router and the interface modules
Going module by module down the CAN stack: the COM module packs signals into PDUs and unpacks them at the receiver, the PDU router routes PDUs to the right bus module, and the CAN interface, CAN transport protocol (segmentation above 8 bytes), CAN state manager, network management, transceiver and CAN driver follow.
- 50:313 min · 2 chapters
The RTE and how it is implemented
The RTE is described as the most complex layer, because generating it needs the ARXML of all software components and basic software. The speaker compares it to a Java virtual machine and describes generation in two phases: collect ARXML, extract ECU information, generate the RTE source and header files, compile and build the final executable.
- 54:006 min · 2 chapters
Application development approaches: top-down and bottom-up
The speaker separates configurable basic software from the application layer, which can be developed with model-based design. In the top-down approach a software component description is exported, imported into Simulink, modelled, tested, code-generated and merged back. The bottom-up approach starts from a Simulink model, and the roles of BSW integrator and architect are named.
- 59:506 min · 1 chapter
Closing Q&A
Participants' questions answered include whether the application layer may call the microcontroller abstraction layer directly, what an ARXML file contains, how much model-based design is needed, what changes when hardware changes, and whether coding knowledge is required.
Chapters
- 59:50Closing Q&A
Is the Automotive Software Architecture & Classic AUTOSAR course really free?
Yes. All 1 h 6 min of it is free on Skill-Lync's YouTube channel, with no payment. To watch it on this page with the chapter guide, leave your name and phone number once; you can also watch it directly on YouTube. It was published on 31 Aug 2023 and had 29,821 views as of 19 Nov 2026. This page adds the chapter guide, a study plan and what to learn next.
How long does the Automotive Software Architecture & Classic AUTOSAR course take to finish?
The video runs 1 h 6 min across 25 chapters. At one hour a day that is about 2 days; plan roughly twice that if you practise each exercise as you go. The longest section is "Why vehicle software needs an architecture" (14 min), so give it its own days.
Does the free AUTOSAR course come with a certificate?
The video description has a "claim your certificate" link, which now opens this page. To ask about a certificate for this course, leave your name and phone number in the form below and a Skill-Lync counsellor will call you back. The paid Skill-Lync courses linked here include a certificate along with mentor-reviewed projects.
What should I learn after this course?
The next step is Fundamentals of Embedded Systems (free lessons), then Introduction to Automotive Embedded Systems and AUTOSAR (₹40,000), then Pre-Graduate Program in Embedded Systems (₹1,50,000). The free course teaches the concepts; the paid Skill-Lync courses add graded projects, mentor feedback and, in the PG programs, placement support.
Do I need to know programming before learning AUTOSAR?
In the Q&A, Jegan Amirthalingam says yes: without a programming background it is hard to enter AUTOSAR. Configuration can be learned, but integration means reading generated and existing code, so a solid understanding of programming is needed even if you spend little time writing code.
Can the application layer call the microcontroller abstraction layer directly in Classic AUTOSAR?
No. The webinar explains that an application should not call lower layers directly. If it does, the software component can no longer be ported from one ECU to another because it depends on the microcontroller abstraction layer. Application software talks to the RTE through AUTOSAR interfaces instead.
What does an ARXML file contain, and how is it used in the RTE?
The speaker describes ARXML as a schema, like a spreadsheet in XML format: a software component's internal behaviour, interfaces, ports and names, with no code. To generate the RTE, the tool needs the ARXML of all basic software and software components, then produces the RTE source and header files.
Last updated 19 Nov 2026 · Course length, chapters, views and dates from the YouTube video on 19 Nov 2026 · Grow by Skill-Lync: free lessons from every course