Triggers that tell the Operating System to execute a specific Runnable Entity (e.g., Timing Events, Data Received Events).
The actual C-code functions that execute the logic within a component, triggered by specific events. 2. The Runtime Environment (RTE)
If you are researching the topics covered in Part 1 of the compendium, here are the fundamental fragments of the architecture: 🧩 The Application Layer
The is the middle layer that decouples the application software from the underlying hardware and basic software (BSW).
| Topic | Official Document (free download after login) | |--------|------------------------------------------------| | RTE | Specification of RTE (SWS_RTE) | | Application Layer | Explanation of Software Component Template | | Runnable Entities & Ports | TPS_SoftwareComponentTemplate |
SWCs interact through defined "Provider" and "Receiver" ports using specific interfaces like Sender-Receiver or Client-Server. 2. The Runtime Environment (RTE)
Smallest pieces of code within an SWC executed directly by the OS.
The AUTOSAR (Automotive Open System Architecture) compendium is a comprehensive guide that provides an in-depth overview of the AUTOSAR standard, its components, and its applications. In this article, we will focus on Part 1 of the AUTOSAR compendium, which deals with the Application Layer and the Runtime Environment (RTE). We will also provide a free printable PDF file that summarizes the key points of this part.
In AUTOSAR, the Application Layer is not a monolithic block of code. Instead, it is built from multiple .
The most famous AUTOSAR compendium is the German book: (or similar titles). English versions exist from training providers, but they are paid (e.g., Vector’s “AUTOSAR Compendium – Part 1: Application and RTE” for ~€200+).
Finding a full version of the AUTOSAR Compendium, Part 1: Application & RTE
The actual code inside an SW-C is encapsulated in .
: Explaining how software components interact with each other and how they access basic ECU hardware resources through a standardized middleware layer. 2. Structural Breakdown: Application Layer & RTE
Triggers that tell the Operating System to execute a specific Runnable Entity (e.g., Timing Events, Data Received Events).
The actual C-code functions that execute the logic within a component, triggered by specific events. 2. The Runtime Environment (RTE)
If you are researching the topics covered in Part 1 of the compendium, here are the fundamental fragments of the architecture: 🧩 The Application Layer
The is the middle layer that decouples the application software from the underlying hardware and basic software (BSW). Triggers that tell the Operating System to execute
| Topic | Official Document (free download after login) | |--------|------------------------------------------------| | RTE | Specification of RTE (SWS_RTE) | | Application Layer | Explanation of Software Component Template | | Runnable Entities & Ports | TPS_SoftwareComponentTemplate |
SWCs interact through defined "Provider" and "Receiver" ports using specific interfaces like Sender-Receiver or Client-Server. 2. The Runtime Environment (RTE)
Smallest pieces of code within an SWC executed directly by the OS. The Runtime Environment (RTE) If you are researching
The AUTOSAR (Automotive Open System Architecture) compendium is a comprehensive guide that provides an in-depth overview of the AUTOSAR standard, its components, and its applications. In this article, we will focus on Part 1 of the AUTOSAR compendium, which deals with the Application Layer and the Runtime Environment (RTE). We will also provide a free printable PDF file that summarizes the key points of this part.
In AUTOSAR, the Application Layer is not a monolithic block of code. Instead, it is built from multiple .
The most famous AUTOSAR compendium is the German book: (or similar titles). English versions exist from training providers, but they are paid (e.g., Vector’s “AUTOSAR Compendium – Part 1: Application and RTE” for ~€200+). The Runtime Environment (RTE) Smallest pieces of code
Finding a full version of the AUTOSAR Compendium, Part 1: Application & RTE
The actual code inside an SW-C is encapsulated in .
: Explaining how software components interact with each other and how they access basic ECU hardware resources through a standardized middleware layer. 2. Structural Breakdown: Application Layer & RTE