EB tresos Classic AUTOSAR：
Basic Software (BSW) Basic Technology Analysis
In-depth exploration of an important part of the Basic Software (BSW) layer in the AUTOSAR software architecture, including the communication stack and configuration principles, helping you understand the standardized and modular design of vehicle network communication.
This article is based on the video content of 'EB tresos Classic AUTOSAR BSW-Communication stack Basic Training' provided by Elektrobit. The video introduces an important part of the Basic Software (BSW) layer in the AUTOSAR software architecture—the Communication stack and its configuration principles overview, bus-independent BSW modules, and bus-specific BSW sub-stacks. It can help you understand and implement standardized and modular design for vehicle network communication, thereby creating, designing, and implementing specific ECU functions, enabling you to develop simply and efficiently.
1. Positioning of BSW in the Architecture
In the AUTOSAR layered architecture, the Basic Software (BSW) is located below the Run-Time Environment (RTE) and interacts directly with the Microcontroller (MCU) hardware. Its main task is to provide standardized, hardware-independent services to upper-layer applications.
2. Four Sub-layers of BSW
The video emphasizes that the BSW internally consists of four main parts, which are also the core modules when configuring EB tresos:
| Layer Name | Abbreviation | Core Functions | Example Modules |
|---|---|---|---|
| Services Layer | Services | Provides operating system, network management, memory management, and diagnostic services. | OS, DCM, NvM |
| ECU Abstraction Layer | ECU Abstraction | The intermediate layer, converting hardware-specific pins into logical signals. | CanIf, PduR |
| Microcontroller Abstraction Layer | MCAL | The lowest layer, directly driving MCU registers to achieve hardware independence. | Can, Spi, Dio |
| Complex Drivers | CDD | Handles highly time-sensitive or non-standard special hardware functions. | PWM Output, Special Sensing |
3. BSW Configuration and Generation Process
When developing with the EB tresos tool, the implementation of BSW follows this logic:
Module Selection
Select corresponding BSW modules based on project requirements (e.g., whether CAN communication or EEPROM access is needed).
Parameter Configuration
Configure specific parameters for each module (e.g., baud rate, timer period, memory address).
Code Generation
The tool generates compliant C source code based on the configuration, which is linked with the RTE and finally compiled into the ECU firmware.
4. Key Technical Points
-
hardware
Hardware Abstraction: Through the MCAL layer, when switching to a different brand of chip (e.g., from Infineon to NXP), the upper-layer application code requires almost no modification.
-
api
Standardized Interfaces: All BSW modules follow AUTOSAR-specified API interfaces, ensuring interoperability between software modules from different suppliers.