The Ultimate Guide to the AUTOSAR Compendium Part 1: Application Layer & RTE (Free Printable PDF Guide) Introduction: Why Every Embedded Engineer Needs This Compendium In the rapidly evolving world of automotive embedded systems, AUTOSAR (AUTomotive Open System ARchitecture) has become the gold standard. Whether you are developing Electric Vehicle (EV) battery management systems, Advanced Driver-Assistance Systems (ADAS), or next-generation engine control units (ECUs), mastering AUTOSAR is non-negotiable. However, the official AUTOSAR specifications span thousands of pages across dozens of documents. This is where the "AUTOSAR Compendium Part 1: Application Layer & RTE" becomes an indispensable resource. This article serves as your complete roadmap to understanding, downloading, and utilizing this critical document. By the end, you will know exactly how to obtain a free printable PDF file of this compendium and how to use it to master the basics of AUTOSAR architecture. What you will learn in this Part 1 guide:
The role of the Application Layer in AUTOSAR. The Runtime Environment (RTE) – the heart of virtual functional bus. How to generate and configure RTE for your ECU. Where to download the official and community-compiled PDF versions. How to get the free printable PDF file for offline study.
Part 1: Understanding the AUTOSAR Layered Architecture Before diving into the compendium, we must establish the foundation. AUTOSAR is built on a layered architecture designed to separate hardware dependency from application logic. This separation allows for software reusability and scalability. The three main layers of classic AUTOSAR are:
Basic Software (BSW): The standardized software layer (drivers, OS, communication stacks) that provides services to the upper layers. Runtime Environment (RTE): The middleware layer that handles the communication between the application layer and the BSW. Application Layer: The top-most layer where the actual functional logic (e.g., cruise control, temperature monitoring) resides. The Ultimate Guide to the AUTOSAR Compendium Part
The AUTOSAR Compendium Part 1 focuses exclusively on the top two layers: The Application Layer and the RTE. 1.1 The Application Layer: Components and Composition In AUTOSAR, the Application Layer is not a monolithic block of code. Instead, it is built from multiple AUTOSAR Software Components (SW-Cs) .
Atomic Software Component: The smallest unit of software that can have its own runnable entities. It encapsulates specific functionality. Runnables: The actual C functions inside an SW-C that are triggered by events (e.g., a timer interrupt or a received signal). Ports and Interfaces: SW-Cs do not communicate directly with variables. They use Ports (P-Port for provider, R-Port for requester) connected to Interfaces (Sender/Receiver, Client/Server).
Why this matters: The Compendium Part 1 explains how to design your SW-Cs using tools like DaVinci Developer or Simulink, and how to generate the .arxml files that describe your application. If you are looking for a printable PDF that explains SW-C design patterns, this compendium is your answer. 1.2 The Runtime Environment (RTE): The Virtual Functional Bus The RTE is arguably the most complex and important element in AUTOSAR. It acts as the communication glue between the application and the infrastructure. The RTE achieves two monumental goals: This is where the "AUTOSAR Compendium Part 1:
ECU Independence: You can develop SW-Cs without knowing which specific ECU they will run on. The RTE maps the virtual connections to real hardware signals (CAN, LIN, Ethernet). SchM (Scheduler Management): The RTE generates task schedules and event triggers for the underlying OS (usually OSEK/VDX).
Key RTE Concepts covered in the Compendium:
RTE Generation: An automatic code generation process that creates Rte.c , Rte.h , and SchM.c files. Connectors: How SW-Cs communicate across ECUs (using RTE to BSW to CAN) or within the same ECU (direct function calls). Data Type Mapping: Converting application data types (e.g., VehicleSpeed_t ) to platform types ( uint16 ). What you will learn in this Part 1
Part 2: Deep Dive into the Compendium (What’s Inside the PDF) The "AUTOSAR Compendium Part 1 – Application & RTE" is typically a curated collection of the official specifications (SWS – Software Specification) and practical tutorials. When you search for this free printable PDF file , you are looking for a document that simplifies the official jargon. Chapter Breakdown (Typical Content) | Chapter | Topic | Key Takeaway | | :--- | :--- | :--- | | 1 | Introduction to AUTOSAR | History, Members (Core partners), version differences (Classic vs Adaptive). | | 2 | VFB (Virtual Functional Bus) | The abstract concept before real mapping. | | 3 | SW-C Types | Composition, Application, Sensor/Actuator, Ecu Abstraction, Complex Driver. | | 4 | Ports & Interfaces | S/R (1-to-many broadcasts) vs C/S (request-response for services). | | 5 | RTE API | Standardized functions: Rte_Read_<port> , Rte_Write_<port> , Rte_Call_<operation> . | | 6 | RTE Generation | Configuration for OS tasks, timing events, and inter-ECU communication. | | 7 | Error Handling | Det (Default Error Tracer) and error codes. | Why a "Printable PDF File" is Essential While many developers rely on online browsers for AUTOSAR specifications (such as the official ARTOP or AUTOSAR.org), there are significant advantages to a printable PDF :
Offline Access: Many development labs and workshops do not have continuous internet access due to security protocols (IP protection). A PDF ensures you can work from anywhere. Annotation & Notes: Engineers love to mark up documents. Printing the compendium allows you to write margin notes, highlight critical RTE configuration parameters, and pin pages to your cubicle wall. Version Control: The AUTOSAR standard updates every 6 months. Having a specific "Part 1" saved as a PDF freezes the knowledge for your specific project (e.g., AUTOSAR 4.2.x or 4.4.x). Reduced Eye Strain: Reading complex architectural diagrams is easier on high-resolution paper than on a backlit monitor.