Scribd
Upload
55 views10 pages

What Is Basic Software (BSW) in AUTOSAR

Uploaded by

rajaram.vignesh
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
55 views10 pages

What Is Basic Software (BSW) in AUTOSAR

Uploaded by

rajaram.vignesh
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 10

Complete Tutorial on

BSW (Basic Software)


in AUTOSAR

The Base Software, popularly called as


the BSW helps facilitates the functions
that help achieve hardware abstraction.
The core job of the AUTOSAR Base
Software (BSW) is to ensure that the
basic functionality of an electronic
control unit (ECU) are executed
efficiently.
Tutorial on BSW (Basic Software)

01. Introduction to AUTOSAR


AUTOSAR (AUTomotive Open System ARchitecture) is a
global development partnership of automotive interested
parties aimed at creating and establishing an open and
standardized software architecture for automotive electronic
control units (ECUs). AUTOSAR defines a layered
architecture consisting of three primary layers:

Application Layer: Contains application software


components specific to vehicle functionalities.
Basic Software (BSW): A middleware layer that provides
essential services for the Application Layer and the ECU
hardware.
Microcontroller Abstraction Layer (MCAL): Interfaces
directly with the ECU hardware.

This tutorial focuses on the Basic Software (BSW) layer in


AUTOSAR.
02. What is Basic Software (BSW)?
The BSW is a standardized software stack in AUTOSAR
responsible for providing services and functionalities that the
Application Layer needs to perform vehicle-specific
functions. It abstracts hardware details and ensures
reusability across different ECUs and vehicle platforms.

Key Features of BSW:


Hardware Independence
Scalability and modularity
Support for diagnostic, communication, and memory
services
Facilitates software reuse
03. Layers of Basic Software
The BSW layer is divided into several sub-layers:

3.1. Services Layer


The Services Layer provides high-level, hardware-independent
services required by the Application Layer. Key modules
include:
Operating System (OS): Manages task scheduling and
resource sharing.
ECU State Manager (ECU State Management): Handles
the ECU's lifecycle.
Diagnostic Event Manager (DEM): Collects and reports
diagnostic data.
NVRAM Manager (NvM): Manages non-volatile memory.
Watchdog Manager (WdgM): Monitors and handles ECU
faults.

3.2. ECU Abstraction Layer


This layer abstracts the hardware details from the software
above it. It interacts with the MCAL layer to provide uniform
access to peripherals and devices. Modules include:
ADC Driver: Abstracts analog-to-digital converters.
CAN Interface: Provides CAN communication capabilities.
PWM Interface: Manages pulse-width modulation.
03. Layers of Basic Software
3.3. Communication Stack

The Communication Stack manages in-vehicle communication


protocols and comprises:
PDU Router (PduR): Routes Protocol Data Units between
communication modules.
Communication Drivers: Includes CAN, LIN, and Ethernet
drivers.
Transport Protocol (TP): Provides segmentation and
reassembly of data.

3.4. Memory Stack

The Memory Stack facilitates memory access and includes:


FEE (Flash EEPROM Emulation): Simulates EEPROM
functionalities.
FLS (Flash Driver): Interfaces with flash memory.
MEM (Memory Abstraction): Standardized memory access.

3.5. MCAL (Microcontroller Abstraction Layer)

Though technically not part of BSW, MCAL closely interacts


with it. It provides drivers for peripherals and acts as an
interface between the hardware and higher layers.
Tutorial on BSW (Basic Software)

04. Key BSW Modules and Their Functions


4.1. COM Module
Handles signal packing/unpacking and communication
between ECUs.
Supports protocols like CAN, LIN, and FlexRay.

4.2. DEM (Diagnostic Event Manager)


Stores and retrieves diagnostic information.
Manages Diagnostic Trouble Codes (DTCs).

4.3. DCM (Diagnostic Communication Manager)


Implements the UDS protocol for external diagnostic
tools.
Facilitates ECU programming and testing.

4.4. Watchdog Manager (WdgM)


Monitors system health.
Restart the ECU if a fault occurs.

4.5. BSW Scheduler


Ensures the execution of cyclic tasks.
Synchronizes communication and diagnostic services.
Tutorial on BSW (Basic Software)

05. BSW Development Process


Developing BSW in AUTOSAR involves the following steps:

Step 1: Configuration
Use tools like EB tresos, Vector DaVinci, or KSAR to
configure BSW modules.
Generate configuration files in XML or ARXML format.

Step 2: Integration
Integrate the configured BSW modules into the
AUTOSAR stack.
Resolve interdependencies between modules.

Step 3: Testing and Validation


Test BSW functionality using simulation tools like
CANoe.
Perform HiL (Hardware-in-the-Loop) testing for real-
world validation.
Tutorial on BSW (Basic Software)

06. Advantages of Using BSW


Standardization: Enables collaboration among
automotive OEMs and suppliers.
Reusability: Reduces development time and cost.
Scalability: Supports complex ECUs with multiple
communication and diagnostic requirements.
Hardware Abstraction: Simplifies development by
decoupling software from hardware.

07. Challenges in Implementing BSW


Configuration Complexity: Requires expertise with
configuration tools.
Integration Issues: Compatibility between modules and
layers can be challenging.
Performance Overheads: BSW introduces additional
processing overhead compared to bare-metal systems.
08. Tools for BSW Development
Here are some widely used tools for BSW development:
Vector DaVinci Developer: Used for configuring
AUTOSAR BSW modules.
EB tresos Studio: Provides configuration and integration
support.
CANoe/CANalyzer: For communication testing and
simulation.
dSPACE ConfigurationDesk: For HiL testing and BSW
validation.

09. Future of BSW in Automotive Industry


With the increasing complexity of modern vehicles and the
advent of autonomous driving, BSW will play a critical role
in:
Supporting ADAS Features: Advanced Driver Assistance
Systems (ADAS) require robust and reliable BSW layers.
Over-the-Air (OTA) Updates: Efficient diagnostic and
communication stacks enable seamless OTA updates.
Electric Vehicle (EV) Development: BSW supports battery
management systems and high-voltage control modules.
Was it Like

helpful? Comment

follow for more!


Share

Chetan Shidling
@chetan_shidling_ Save

www.cselectricalandelectronics.com

You might also like