EB tresos Classic AUTOSAR：
Software Component (SWC) Basic Technology Analysis
Systematic basic teaching, covering the basic concepts of SWC, element composition, and practical application cases, aiming to help developers quickly master how to design and implement specific functions of ECU, improving development efficiency.
This article is based on the video content of 'EB tresos Classic AUTOSAR - Software Component (SWC) Basic Training' provided by Elektrobit (EB). The video provides systematic basic training on Software Components (SWC) in the Classic AUTOSAR software architecture, covering the basic concepts, element composition, and practical application cases of SWC, aiming to help developers quickly master how to design and implement specific functions of ECU (Electronic Control Unit) and improve development efficiency.
1. What is an AUTOSAR SWC?
In the AUTOSAR layered architecture, the top layer is the 'Application Layer', which is mainly composed of interconnected Software Components (SWC). The core design philosophy of SWC is 'hardware independence'. When designing SWCs, developers do not need to care about the hardware details of the underlying microcontroller. All data exchange and function calls are realized through the Virtual Functional Bus (VFB) and Runtime Environment (RTE). This design greatly improves the reusability and portability of automotive software.
2. Core Elements of SWC
The video details the key elements that make up an SWC, which are the focus when configuring with tools like EB tresos:
settings_input_component Ports
The interface for communication between SWCs, as well as between SWCs and the underlying Basic Software (BSW). Mainly divided into two types:
- P-Port (Provide Port)：Provide data or services.
- R-Port (Require Port)：Request data or services.
cable Interfaces
Defines the format and mechanism for data transmission through Ports. Common communication modes include:
- Sender/Receiver (S/R)：Used to transmit data (such as vehicle speed, temperature), similar to a broadcast or publish/subscribe mechanism.
- Client/Server (C/S)：Used to call services or functions (e.g., request data storage), belonging to a synchronous or asynchronous operation of question and answer.
account_tree Internal Behavior
Defines how the SWC operates internally, acting as a bridge connecting external Ports to internal code.
play_circle Runnable Entities
Short for Runnables. They are the C language functions that actually execute logic in SWCs. Runnables cannot run on their own and must be triggered by the RTE based on specific conditions.
bolt RTE Events
Conditions used to trigger the execution of Runnables. For example:
- Timing Event：Periodic triggering (e.g., executing once every 10ms).
- Data Received Event：Triggered when new data is received.
3. EB tresos' Role and Practical Cases in SWC Development
In the actual ECU development process, the toolchain plays a crucial role. Through EB tresos Studio, developers can perform the following operations:
-
check_circle
Architecture Design: Graphically create SWCs and define their Ports and Interfaces.
-
check_circle
Behavior Configuration: Configure the SWC's Internal Behavior, including setting up Runnables and binding the RTE Events that trigger these Runnables.
-
check_circle
Generation and Interfacing: After configuration is complete, EB tresos assists in generating standard XML description files (ARXML) and C language header files that interface with the RTE, allowing software engineers to focus on writing the business logic (Application Logic) inside Runnables.
Summary
Through this basic training video, you can understand that SWC in Classic AUTOSAR is the cornerstone for realizing automotive functions. By standardizing Ports and Runnables design, combined with mature configuration tools like EB tresos, the development team can modularize complex vehicle functions. This not only reduces the coupling between software and hardware but also makes the development, testing, and integration of ECU software simpler and more efficient.