| Scheme | Range | Automotive Use | Pros/Cons |
|---|---|---|---|
| Static assignment | e.g., 169.254.x.x (AUTOSAR) | AUTOSAR Classic: ECU IP assigned in ARXML at design time | Deterministic; no DHCP server needed; rigid to change |
| AUTOSAR AutoIP | 169.254.1.0/16 (link-local) | Default for AUTOSAR Adaptive ECUs without DHCP | Fast (≤500 ms); works without infrastructure; limited to /16 |
| DHCP (RFC 2131) | Any private range (10.x, 172.16.x, 192.168.x) | Infotainment, OTA backend, cloud-connected ECUs | Flexible; requires DHCP server ECU; startup delay |
| IPv6 Link-Local | fe80::/10 | AUTOSAR Adaptive, V2X | Stateless; mandatory for IPv6; not routable beyond L2 segment |
IP Addressing Schemes in Vehicles
AutoIP and Static Configuration
Cip_config.c
/* AUTOSAR Classic: static IP from ARXML-generated configuration */
/* TcpIp module in EthStack; configured at build time */
/* Generated from ARXML (EthStack/TcpIp module):
169.254.1.100 (ECU static IP)
255.255.0.0 (/16 for AutoIP range)
169.254.1.1 (gateway IP)
*/
#include "TcpIp.h"
/* AUTOSAR TcpIp init: called by EthSM during network startup */
void TcpIp_InitIpAddress(void)
{
TcpIp_LocalAddrIdType addr_id = TCPIP_LOCAL_ADDR_STATIC;
/* Assign static IP to local address ID */
TcpIp_IpAddrType local_ip = { .addr = {169u, 254u, 1u, 100u} };
TcpIp_NetmaskType netmask = { .addr = {255u, 255u, 0u, 0u} };
TcpIp_IpAddrType gw_ip = { .addr = {169u, 254u, 1u, 1u} };
(void)TcpIp_RequestIpAddrAssignment(addr_id,
TCPIP_IPADDR_REQUEST_STATIC,
&local_ip, 16u, &gw_ip);
}
/* AUTOSAR AutoIP: RFC 3927 link-local (169.254.x.x/16)
If static IP conflicts detected (ARP probe): shift to another address
Typical startup: 500 ms including ARP probe (2× 150 ms + random delay) */Inter-VLAN Routing and L3 Gateway
L3 Gateway: Inter-VLAN Routing
VLAN 10 (ADAS): 169.254.10.0/24
VLAN 20 (PT): 169.254.20.0/24
VLAN 30 (Diag): 169.254.30.0/24
Camera ECU: 169.254.10.100 ──── (VLAN 10) ──── [Switch] ──┐
Engine ECU: 169.254.20.100 ──── (VLAN 20) ──── [Switch] ──┤
OBD port: 169.254.30.200 ──── (VLAN 30) ──── [Switch] ──┤
│
[Gateway ECU]
169.254.10.1 (VLAN 10 interface)
169.254.20.1 (VLAN 20 interface)
169.254.30.1 (VLAN 30 interface)
│
Routing table:
169.254.10/24 → VLAN 10
169.254.20/24 → VLAN 20
169.254.30/24 → VLAN 30
DoIP from OBD tester (169.254.30.200) to Engine ECU (169.254.20.100):
Packet: src=30.200 dst=20.100 → Gateway routes from VLAN30→VLAN20Summary
AUTOSAR Classic ECUs use static IP addresses configured in ARXML — this is the most common automotive deployment. The 169.254.x.x/16 (AutoIP) range is the default because it requires no DHCP server infrastructure. Inter-VLAN routing is required for any packet that crosses a VLAN boundary (e.g., diagnostic tester on the diagnostic VLAN reaching an ECU on the ADAS VLAN) and is performed by the central gateway ECU, which implements a software IP router or has a hardware L3 switch. The gateway is also where firewall rules are applied to prevent cross-domain access.
🔬 Deep Dive — Core Concepts Expanded
This section builds on the foundational concepts covered above with additional technical depth, edge cases, and configuration nuances that separate competent engineers from experts. When working on production ECU projects, the details covered here are the ones most commonly responsible for integration delays and late-phase defects.
Key principles to reinforce:
- Configuration over coding: In AUTOSAR and automotive middleware environments, correctness is largely determined by ARXML configuration, not application code. A correctly implemented algorithm can produce wrong results due to a single misconfigured parameter.
- Traceability as a first-class concern: Every configuration decision should be traceable to a requirement, safety goal, or architecture decision. Undocumented configuration choices are a common source of regression defects when ECUs are updated.
- Cross-module dependencies: In tightly integrated automotive software stacks, changing one module's configuration often requires corresponding updates in dependent modules. Always perform a dependency impact analysis before submitting configuration changes.
🏭 How This Topic Appears in Production Projects
- Project integration phase: The concepts covered in this lesson are most commonly encountered during ECU integration testing — when multiple software components from different teams are combined for the first time. Issues that were invisible in unit tests frequently surface at this stage.
- Supplier/OEM interface: This is a topic that frequently appears in technical discussions between Tier-1 ECU suppliers and OEM system integrators. Engineers who can speak fluently about these details earn credibility and are often brought into critical design review meetings.
- Automotive tool ecosystem: Vector CANoe/CANalyzer, dSPACE tools, and ETAS INCA are the standard tools used to validate and measure the correct behaviour of the systems described in this lesson. Familiarity with these tools alongside the conceptual knowledge dramatically accelerates debugging in real projects.
⚠️ Common Mistakes and How to Avoid Them
- Assuming default configuration is correct: Automotive software tools ship with default configurations that are designed to compile and link, not to meet project-specific requirements. Every configuration parameter needs to be consciously set. 'It compiled' is not the same as 'it is correctly configured'.
- Skipping documentation of configuration rationale: In a 3-year ECU project with team turnover, undocumented configuration choices become tribal knowledge that disappears when engineers leave. Document why a parameter is set to a specific value, not just what it is set to.
- Testing only the happy path: Automotive ECUs must behave correctly under fault conditions, voltage variations, and communication errors. Always test the error handling paths as rigorously as the nominal operation. Many production escapes originate in untested error branches.
- Version mismatches between teams: In a multi-team project, the BSW team, SWC team, and system integration team may use different versions of the same ARXML file. Version management of all ARXML files in a shared repository is mandatory, not optional.
📊 Industry Note
Engineers who master both the theoretical concepts and the practical toolchain skills covered in this course are among the most sought-after professionals in the automotive software industry. The combination of AUTOSAR standards knowledge, safety engineering understanding, and hands-on configuration experience commands premium salaries at OEMs and Tier-1 suppliers globally.