Made for AUTOSAR beginners: Practical sessions with tools

Explore electronic control units (ECUs) and how microcontrollers, sensors, and an application-specific integrated circuit process data to control systems, and how ECUs communicate over networks with other controllers.

Explore the Autosar layered architecture, detailing the basic software (bsw), runtime environment (rte), and application layer, and how standardized interfaces separate software from hardware for flexible integration.

Explore the microcontroller abstraction layer in Autosar by learning how applications access microcontroller registers only through a hardware independent standard interface, enabling hardware independent access to basic software models.

Explore the service layer in automotive software, detailing operating system functionality, network management, memory and diagnostic services, and how microcontroller interfaces provide hardware-independent application support.

Explore the AUTOSAR workflow from OEM to tier 1, detailing software component and system description files, templates, and exchange formats, and show how configuration and interfaces drive executable ECU generation.

Examine how a blind-spot detection system uses three sensors and intra- and inter-ecu communication to detect obstacles and trigger buzzer and lights.

Explore the three types of autosar interfaces and how software components communicate through them. The lecture shows internal, standardized, and c language interfaces for accessing ecu services and diagnostics.

Learn to generate xml, c, and dot h files for Autosar compliant project, and implement software components by creating ports, interfaces, runnables, and mapping them in a temperature controller application.

Create three application software components in an Autosar project—temperature control, led control, and coil control—and learn to add ports in the next video.

Configure AUTOSAR interfaces for software components, including ports and data types. Implement sender-receiver and client-server interfaces, name them, declare elements, and prepare to connect interfaces to ports.

Link ports to interfaces in autosar software components by configuring sender-receiver and client-server interfaces, setting initial values, and mapping each port to its corresponding interface.

Explore Autosar software components, their runnables, and how to define and connect runnables across components using ports, data axes, and client-server and synchronous server call points in the Cordoba tool.

Configure periodic events for software components to acquire data and update outputs every second, enabling led on/off and temperature read with threshold-based control.

Learn how Autosar composition software components aggregate atomic components, configure their connections and runnable entities, and use tools to map and link hardware abstraction modules with software components.

Walk through arxml and source files for software components, including dot c and dot h, runnables, ports, interfaces, and hardware abstraction modules, and review the contract and generation page.

Generate software component XMLs with the Cordoba tool during the RTE contract phase and build assembly connectors among control, temp control, and hardware abstraction.

Explore how RTE read and write function calls enable data flow from temp control to LED control via the TX, hardware abstraction, and driver to the hardware.