What is RTE
AUTOSAR RTE (Run Time Environment) implements the virtual function bus (VFB) in the AUTOSAR system, providing the access interface between SWC (Software Component) and the SWC's access interface to BSW resources. RTE provides an interface for Runnable in SWC to communicate with other SWC or BSW modules. RTE maps Runnable to OS Tasks and manages the triggering mechanism of Runnable. Therefore, RTE function can be mainly divided into two parts:
- Communication between SWCs
- SWC Scheduling
The simplified AUTOSAR architecture diagram is as follows
As shown in the figure above, the AUTOSAR architecture is designed in layers, and its concept is to decouple software from hardware so that software can be redistributed and reused, all of which rely on RTE. However, RTE is not reusable because RTE matches application requirements, so if the application modifies RTE, it also needs to be modified. Except for sensor/actuator type SWCs that are highly dependent on ECU hardware, all other SWCs are easy to transplant and reuse. RTE is generated after SWC integration, so the RTE service ensures communication between SWCs and between SWCs and BSWs, thereby ensuring that the system works as expected regardless of where the SWC is deployed. RTE supports both source code type SWC and object code SWC. RTE does not support runtime reconfiguration, and all communications are static after configuration generation.
Uses or applications of RTE
-
Implemented a virtual function bus to connect the communication between internal and external SWC of ECU
-
Implemented the communication path between SWC and BSW modules, using ports and inte