Others

AUTOSAR BSW & ASW

esmJK 2022. 3. 15. 14:35

AUTOSAR

tight bond between base software and hardware leads to reduced flexibility in hardware choices 

reuse of software modules across customers is possible when abstraction via AUTOSAR standard is used

 

 

 

Run Time Environment 

middleware which realizes the communication between SW components and the basic software 

 

 

 

Basic Software Layer

 

ECU Specific Components 

- Operating System 

- MCAL (Microcontroller Abstraction Layer) 

ensures standard interface to the basic software and manages MCU peripherals 
Notification mechanism 
1. Distribution of commands 
2. Response 
3. Information

Layer Subdivision 
Controller Driver | Memory Driver | Comm Driver | IO Driver 

- Complex Device Driver 

Complex device driver is specialized layer provided by AUTOSAR in case the application needs to access the hardware in a faster way for time-critical applications

 

 

ECU Abstraction Layer

Provides software interface to the electrical values of any specific ECU 

Layer Subdivision 
On-board device abstraction | Memory hardware abstraction | Comm hardware ab | IO hardware ab 

ex) Memory hardware ab : on-chip EEPROM and external EEPROM should be accessible via equal mechanism

 

Service Layer 

Layer Subdivision 
OS services | Memory services | Comm services 

AUTOSAR Interface Predefines Function API 

ex) for reading IO pin : DIO_ReadChannel() 

 

 

ASW & BSW : Software Components 

application SW component contained in Atomic Software Component types 

RTE is not bypassed in any case 

How to choose the software component type

 

 

Example) 

1. Sensor reading from speed sensor reports maximum speed has been reached 

2. Cut off injection 

3. Diagnostics information saved to NVM 

 

 

 

Ports 

​Communication between AUTOSAR modules done via ports 

- Provider port

- Receiver port 

- Provider Receiver port 

 

Information communicated between ports 

- Sender Receiver Interface 

- Client Server Interface 

- NVData Interface 

- Parameter Interface 

- Mode Switch Interface 

- Trigger Interface 

 

Sender Receiver Interface : asynchronous communication to send or receiver data between software components 

Client Server Interface : used for function calls  

- Synchronouse call : client waits until server function runs and complets 

- Asynchronous call : trigger server function and proceeds. server results fetched when required