Articles

Read our latest blog articles about Autosar.

What is the SDV Alliance and Why You Should Care

Software Defined Vehicles (SDV) inherit the concept of software upgradability from smartphones, by certralizing the vehicle functionalities, reducing the number of ECUs via zonal architectures and enhancing the upgradability of vehicles throughout their lifetime. Learn how the SDV alliance contributes to this goal.Read Now

I-PDU Multiplexer (IPduM) Overview and Transmission

I-PDU multiplexing is the ability to use the same PDU to communicate with a different layout of I-Signals / I-PDUs, according to a selector field, setting the contents of the I-PDU, hence, shaping the SDU. Learn how the I-PDU Multiplexer uses both multiplexed and container I-PDUs to communicate I-PDUs with different layouts seamlessly.Read Now

How to Implement Client-Server Communication

Client-Server communication is the form of API exchange at the VFB level, supported by ClientServerInterface, ClientServerOperation, RunnableEntity, OperationInvokedEvent, SynchronousServerCallPoint and AsynchronousServerCallPoint. Learn its intricacies and use client-server communication properly.Read Now

SoAd - Socket Adaptor Overview

The Socket Adaptor (or Adapter) opens a new world for communication in Autosar, by providing a bridge to the TCP / IP world to the intransigent and predictable run-time behaviour of automotive ECUs. Learn to leverage it and communicate via UDP and TCP seamlessly.Read Now

SwDataDefProps - Attributes and Use Cases

Data definition properties can be added to data types and data prototypes, to complement their description with various attributes. They are contained by the SwDataDefProps meta-class, which contains many attributes applicable in different use cases and its understanding is critical for taking advantage of the Autosar Meta-Model. Learn about this meta-class in this post.Read Now

ComXf - COM Based Transformer Overview and Configuration

The COM-Based Transformer (ComXf) is a serializer transformer which is used between the RTE and the COM, to transform the data elements from the application into signals and signal groups from the COM and vice-versa. Learn about the ComXf and how to use it in this post.Read Now

VSA - Variable Size Arrays for Autosar Data Types

Variable Size Array (VSA) can be defined in Autosar, via ApplicationDataTypes and ImplementationDataTypes. Learn how to create them for both cases in this post.Read Now

COM Filters - Theory and Configuration

Learn how the Autosar COM filters data upon reception, ensuring redundant data is only communicated on the sender side or processed on the receiver side by the application when required.Read Now

COM I-PDU Groups - Overview and Configuration

Learn the purpose of I-PDU groups, what defines an I-PDU group, how they can be started and stopped (and what happens in both instances), the rules for their usage and how they are configured.Read Now

COM Signal Retransmission and Retry

Learn how the Autosar COM handles Retransmission and Retry of Transmission Requests based on the different Transmission Modes, along with Deadline Monitoring and Minimum Delay Time evaluation.Read Now

OSEK OS - Resource Management and Priority Ceiling

Resource management is at the core of handling concurrent access in a multi threaded application, such as an automotive RTOS, and the OSEK OS, the base for the Autosar OS is not exception. Learn the problems that arise with resource management, such as deadlocks and priority inversion, and how the OSEK Priority Ceiling Protocol solves these issues.Read Now

SomeIpXf Overview - SOME/IP Messages and VFB Serialization in Autosar

SomeIpXf is a serializer transformer dedicated to SOME/IP. It specifies both client-server, sender-receiver and trigger communication concepts from the VFB, with the goals of fulfilling the resource consumption requirements of embedded systems, provide compatibility and scalability with different platforms and operating systems and supporting the use cases of automotive.Read Now

BSW Module Naming Convention and File Structure

Basic Software modules follow the same general specification. Even though they implement their own unique functionality, their basis is the same. In this article, we discuss all the common elements to BSW modules, namely their naming convention and file strcuture, always keeping in mind that there can be exceptions.Read Now

COM Signal Transmission and Reception Overview

Discover the intricacies of COM signal transmission and reception in Autosar. Learn about the processes involved in transmitting and receiving signals between different ECUs, including the role of APIs, endianness conversion, and transmission modes. Gain insights into reception deadline monitoring and filtering mechanisms, essential for ensuring reliable communication.Read Now

Guide to the Classic Autosar Architecture

Learn about all Classic Autosar layers in this higher level overview of the architecture.Read Now

Exploring ISignal and ISignalGroup Definitions in Autosar ARXML

Dive into the intricacies of Autosar ISignal and ISignalGroup containers, unraveling their definition in ARXML, grouping mechanisms, and the seamless integration with the Communication (COM) module. Explore the elements, configurations, and transformations that define the backbone of efficient data exchange in automotive systems.Read Now

Demystifying Autosar PDU Router. A Comprehensive Guide to Routing, Handling, and Buffering

Explore the intricacies of the Autosar PDU Router in our comprehensive guide. Learn about its routing mechanisms, handling capabilities, and buffering functionalities, providing a deep understanding of this essential component in automotive communication systems.Read Now

A Comprehensive Overview of Autosar Versioning

Autosar, the Automotive Open System Architecture, follows a meticulous versioning system to manage its development lifecycle and ensure compatibility across different releases. In this article, we'll delve into the intricacies of Autosar versioning, exploring the evolution from separate releases for Classic and Adaptive Platforms to their unified approach.Read Now

COM - Demystifying I-PDU Transmission Modes

Understanding the transmission modes of I-PDUs at the Autosar COM is crucial for understanding how communication unfolds within an Autosar environment.Read Now

E2EXf - How to Use E2E Transformers in Autosar

E2EXf is a safety transformer, used to protect the communication of I-Signals. Learn how you can configure it, with the help of ARXML modeling and the RTE.Read Now

Understanding Autosar Error Types and Handling

Autosar defines various error types in the BSW modules. Learn about them and how they are handled throughout the ECU life cycle.Read Now

Arxml Files and Software Components

Arxml is the most common file type found in an Autosar. Learn how to create them hereRead Now

BSWM Actions

The Basic Software Mode Manager controls multiple parts of BSW modules through actions. Learn the available actions in this articleRead Now

BSWM Overview

The Basic Software Mode Manager implements mode management for your Autosar application based on requests, rules and actions. Learn about the BswM hereRead Now

C Memory Layout

In Autosar, MemMap takes over the memory distribution of the system. Learn about C memory layout and its particularities in Autosar hereRead Now

Calibration Overview

Calibration is an important step in ECU development. Learn the basics on how to tune parameters in an ECURead Now

CAN-FD Overview

CAN is the most widely used automotive protocol. Learn here about the variant CAN-FD (CAN Flexible Data-Rate)Read Now

CAN-TP Overview

CAN-TP is important to extend the capabilities of CAN, by enhancing the very limited PDU size, making it a crucial part in communication. Learn how it works hereRead Now

CAN Protocol Overview

CAN is the most popular protocol for automotive vehicles. Learn about the CAN protocol and its particularities in this articleRead Now

CAN Transceiver Protection

Since an automotive failure can be costly, protection is essential. Learn how you can protect the CAN busRead Now

Communication Stack Overview

The communication stack is a prime example of how the Autosar layered architecture works. Learn how to go from Software Component data to CAN bus hereRead Now

DEM Overview

Reporting of events is an important part of diagnostics. Learn how the DEM comes into play in this articleRead Now

DET Module IDs

Learning how to use the DET (Development Error Tracer) is essential while integrating Autosar modules. Learn about all the DET module IDs in this articleRead Now

DET Overview

There is nothing more frustrating than debugging a module on a giant architecture, such as Autosar. Learn how the Development Error Tracer (DET) helpsRead Now

Diagnostics on Vector CANoe - Part 1

Vector provides a solid diagnostics framework to communicate with ECU's. Take the first step into diagnostics on Vector CANoe in this articleRead Now

DIO and Port Overview

Being able to read and write digital inputs and outputs are among basic microcontroller functionalities. Learn how you can use DIO and Port to this goalRead Now

E2E Protection Overview

Valid data exchange between ECU's is essential to avoid the gnarly effects of communication faults. Learn here about E2E protectionRead Now

E2E Protocol and APIs

E2E is a crucial part of functional safety, as it protects communication. Learn in this article the E2E profiles, state machine and APIsRead Now

FIM Overview

Whenever an issue occurs within an ECU, protective measures need to be taken. Learn how FIM works to accomplish this goal hereRead Now

How NvM Works Internally

Learn what happens to your NvM variable from the moment you write itRead Now

How to Create Arxml for Software Components

Learn how to declare software components in Autosar and integrate them with the Autosar stackRead Now

Memory Mapping

Learn about the Memory Map component in Autosar and how it infuences the source codeRead Now

Memory Mapping Allocation Keywords

There are multiple keywords to map all variables on the ECU according to your application needs. Learn about them hereRead Now

Memory Stack Overview

The ability to read and write data persistently over multiple driving cycles is crucial for ECU functions. Learn how the Autosar memory stack works hereRead Now

Mode Management

Mode management is essential to synchronize all the modules in an Autosar environment. Learn what it's all aboutRead Now

Network Management Interface

Learn how NM (Network Management Interface) coordinates ECU networks to sleep synchronously, abstracting the bus NM modulesRead Now

NvM Overview

Memory operations on an ECU are achieved through the NvM. Learn how to use the module hereRead Now

OSEK OS in Practice

Last time out, we took a look at the theory behind the OSEK/VDX OS, the backbone of the Autosar OS. Today we find how we can use tasks, events and ISR's.Read Now

OSEK OS in Practice Part 2

Now that we learned how to use tasks, events and ISR's, we dive into counters, alarms, shared resources and hooks, in the backbone of the Autosar OSRead Now

OSEK OS Overview

The Autosar OS has the good old OSEK/VDX OS as a backbone. Learning about OSEK will put you on the right track to understanding the Autosar OSRead Now

Overview of Events

What events to we have at our disposal in the RTE and the BSW modules, and how should we use them?Read Now

PWM Overview

As part of the MCAL layer, learn how you can use the PWM module in Autosar for your projects that require PWM modulationRead Now

SPI Overview

SPI is one of the most popular communication protocols in microcontrollers. Learn here how to communicate via SPI on the Autosar layered architectureRead Now

The Basics of A2L Files

Why are A2L Files Used in ECU Development and Their ContentsRead Now

Types of Interfaces and Ports

Interfaces and ports are a vital part of a Software Component's ability to communicate. Learn what they are and how they're usedRead Now

Types of Software Components

Kickstart your Autosar journey by learning which software components are available and where they suit your needsRead Now

UDS Frames and NRC Codes

Analyzing the UDS frames and NRC in UDS responses allows us to learn more about the problems in our ECU. Learn about UDS frames and NRC's hereRead Now

UDS Overview

UDS is the diagnostics language all ECU's speak nowadays, linked to the Autosar DCM module. Learn its basic services hereRead Now

Vector CAPL Tutorial

Vector uses the CAPL programming language for automation and interaction with ECU's via the communication bus. Kickstart your CAPL knowledge hereRead Now

Watchdog Stack Overview

In hard real-time systems, such as automotive ECU's, a watchdog is critical to monitor its behavior. Learn about the watchdog stack hereRead Now

What are DEM, DLT, DCM and DET

These modules all sound very similar, but they could not be more different in practice. Learn what they're all about hereRead Now

What are DTC Codes

DTCs (Diagnostic Trouble Codes) are the main diagnostic malfunction output for your vehicle. Learn more about DTCs hereRead Now

What is FlexRay

FlexRay is a high performance communication protocol in the rough automotive environment. Learn more about FlexRay hereRead Now

What is Functional Safety

Functional is how a system failure does not create a dangerous hazardRead Now

What is IEEE754

Learn here how your computer deals with floating-point operations and how to take advantage of itRead Now

What is J1939

J1939 is a set of protocols that specify a higher-layer for CAN communication in heavy duty vehicles. Learn all about it hereRead Now

What is LIN

LIN is a protocol that connects to the CAN bus through a gateway and offers a cheaper communication option. Learn how to use LIN in this articleRead Now

What is MISRA C

Learn here how following MISRA guidelines can help you build portable, reliable and easier to maintain C codeRead Now

What is XCP

XCP is a standard protocol that enables calibration on modern ECU's. Learn how it works hereRead Now

XCP Commands

The XCP commands are half of the way to learn about the calibration protocol. Start mastering them in this articleRead Now

© AutosarToday —@LinkedIn