Wiki

The SDV engineering wiki

Short, beginner-friendly articles on every building block of a software-defined vehicle — each with the relevant standards and what it means for your discipline.

Show topics for
97 topics

1Foundations

E/E Architecture

The shift from domain to zonal and central architectures — what drives it, what it changes for harness, power and software, and how far the industry really is.

In-Vehicle Networks

Automotive Ethernet and TSN, CAN FD and CAN XL, 10BASE-T1S and LIN — what each bus is for, how they work together, and where the backbone is heading.

1Network basics How vehicle electronics exchange information, why cars use several kinds of network, and what matters when choosing between them. 2CAN 2.0 The robust, cheap broadcast bus that still carries most control messages in vehicles: arbitration by message ID, 8-byte payloads, up to 1 Mbit/s. 3CAN FD CAN with Flexible Data-rate: up to 64-byte payloads and a faster data phase, keeping CAN's arbitration and robustness — today's default for MCU-based ECUs. 4CAN XL The third CAN generation: up to 2,048-byte payloads and data rates of about 10–20 Mbit/s, designed to carry IP and Ethernet frames and bridge CAN and Ethernet worlds. 5J1939 The CAN-based protocol family used across commercial vehicles, agricultural and construction machines — standard parameter groups that let ECUs from different suppliers understand each other. 6LIN A cheap single-wire master/slave bus for simple sensors and actuators like mirrors, seat motors and HVAC flaps — slow, deterministic and good enough. 7Automotive Ethernet Single-pair Ethernet from 10 Mbit/s to multi-gigabit that forms the backbone of zonal architectures and carries IP, services, cameras and diagnostics. 810BASE-T1S 10 Mbit/s single-pair Ethernet with a multidrop bus topology, giving CAN-like wiring with Ethernet addressing for sensors, actuators and smart lights in zones. 9TSN A family of IEEE 802.1 standards that gives Ethernet a common clock and deterministic timing, so control traffic can share the backbone with bulk data. 10SOME/IP & DDS The middleware protocols that let software components offer and use services over Ethernet — the communication backbone of service-oriented vehicle software.

Network Management

Coordinated sleep and wake-up, partial networking and power modes — keeping always-connected vehicles available without draining their batteries.

2Compute & software

Base Software & AUTOSAR

How AUTOSAR Classic and Adaptive structure ECU and HPC software — layers, configuration, communication stacks — and where open-source platforms like Eclipse S-CORE fit in.

HPC Hardware & Software

Central and zonal compute — SoC selection, hypervisors, mixed criticality and the software stack that makes vehicles software-defined.

Software Stacks by Node Class

The same software layers — from applications down to silicon — compared across HPC application processors, safety islands, zone controllers, MCU-based ECUs and smart nodes.

HPC · application processor

1Feature services, HMI, ADAS apps The HPC application processor runs compute-heavy vehicle features, user interfaces, and driver-assistance applications that can evolve through controlled software updates. 2AUTOSAR Adaptive / SOA (SOME/IP, DDS) This layer starts and manages application processes and lets vehicle software discover services and exchange data locally or across the vehicle network. 3OTA client · SOVD · host IDS · logging Shared services on the HPC application processor update software, expose diagnostics, detect suspicious activity and collect evidence for troubleshooting. 4Linux / QNX / Android (per VM) Each virtual machine runs a guest operating system that manages its applications and resources, with Linux, QNX or Android chosen to suit the workload and assurance requirements. 5Type-1 hypervisor A type-1 hypervisor divides an HPC’s application processor into virtual machines so different operating systems and workloads can share hardware with controlled interference. 6BSP · Linux drivers · VirtIO Board support and device drivers let HPC operating systems use the physical hardware, while VirtIO provides standard virtual device interfaces for guests. 7Secure boot chain · TEE Trusted startup firmware checks the software that starts the HPC, while an isolated execution environment protects selected security services during operation. 8Cortex-A cores · GPU/NPU · LPDDR Application processors combine powerful CPU cores, specialised accelerators and external memory to support large vehicle software workloads.

MCU-based ECU

1Application SWCs (e.g. brake control) Application software components implement an ECU’s vehicle functions, turning sensor inputs and requests into controlled outputs and fault responses. 2RTE · COM The generated AUTOSAR runtime connects application components to each other and to communication software that exchanges signals with other ECUs. 3Dcm/Dem · NvM · SecOC · crypto stack These services let a control ECU answer diagnostic requests, remember important data across power cycles, authenticate selected messages and use protected cryptographic operations. 4AUTOSAR OS / RTOS A real-time operating system schedules control software and provides protection mechanisms that help safety-critical functions share an MCU with other software. 5MPU-based partitioning Hardware memory protection and operating-system controls help software of different safety criticalities share an MCU without disrupting one another. 6MCAL · ECU abstraction Microcontroller drivers and board-specific abstraction turn electrical inputs and outputs into interfaces that control software can use predictably. 7Flash bootloader · secure boot (HSM) This firmware checks that an ECU starts authorized software and installs updates, using hardware-protected keys and a controlled recovery path. 8Lockstep MCU · HSM · embedded flash An automotive microcontroller combines real-time processing, local memory, safety monitoring and protected cryptography to control functions such as braking, steering or battery management.

3Security

Automotive Cryptography

The building blocks behind SecOC, secure boot, signed updates, TLS and V2X — hashes, MACs, AES, RSA and elliptic curves, certificates and the hardware that keeps keys safe — explained for engineers who are not cryptographers.

Vehicle Cybersecurity

From CSMS and TARA to secure boot, SecOC and the vehicle SOC — how vehicles are protected across their whole lifecycle, and where the regulation is heading.

5Diagnostics & lifecycle

Diagnostics

From UDS and DoIP to SOVD — how diagnostics evolves for HPC-centric, service-oriented vehicles, and why it is also a security topic.

Software Update & OTA

Over-the-air updates, SUMS, software bills of materials and continuous delivery for vehicles in the field — and why recalls are increasingly fixed by software.