By mastering the relationships between Software Components and the generated RTE, you will possess the foundational knowledge required to design, configure, and debug modern automotive embedded software.
Quick access to architecture diagrams during embedded software development without needing an internet connection.
| Chapter | Title | Key Takeaway | |---------|-------|---------------| | 1 | AUTOSAR Layered Architecture | Overview of App, RTE, BSW, and MCAL. | | 2 | Application Software Components | Atomic SW-C, composition, ports, interfaces. | | 3 | Runnable Entities & Events | Mapping logic to timing/data triggers. | | 4 | Introduction to RTE | The middleware concept and generated API. | | 5 | RTE Generation Process | From ARXML to rte.c and rte.h . | | 6 | Inter-SW-C Communication | Sender-Receiver vs. Client-Server over RTE. | | 7 | RTE for I/O and Calibration | Accessing NVM, Dio, and ADCs via RTE. | | Appendix | Quick Reference Cards | RTE function naming, error codes, and XML tags. | | | 2 | Application Software Components |
The keyword here is . Why is this specific format important for AUTOSAR engineers?
The architecture is broadly divided into three main layers sitting above the microcontroller hardware: | | 5 | RTE Generation Process | From ARXML to rte
The smallest units of application code. They cannot be split across multiple Electronic Control Units (ECUs).
The RTE implements mechanisms like implicit and explicit reading to ensure that data remains consistent and uncorrupted throughout the execution cycle of a Runnable. 5. Core Syllabus Blueprint (Printable Quick Reference) | | 2 | Application Software Components |
Are your runnables grouped efficiently within OS tasks to minimize context-switching overhead?
