Automotive Ethernet Switches - Automotive Ethernet

Automotive Ethernet Switch Architecture

Multi-Port Switch: Internal Architecture

  External ports (PHY-facing):          CPU port (uplink to SoC):
  ┌────┐ ┌────┐ ┌────┐ ┌────┐             ┌────────┐
  │P0  │ │P1  │ │P2  │ │P3  │             │CPU/Mgmt│
  │PHY │ │PHY │ │PHY │ │PHY │             │ Port   │
  └──┬─┘ └──┬─┘ └──┬─┘ └──┬─┘             └────┬───┘
     │      │      │      │                    │
  ┌──┴──────┴──────┴──────┴────────────────────┴──┐
  │              Switch Fabric                     │
  │  ┌─────────────────────────────────────────┐  │
  │  │  FDB (Forwarding Database)              │  │
  │  │  VLAN table (802.1Q)                    │  │
  │  │  QoS / Shaping (TAS, CBS)               │  │
  │  │  mirroring / snooping / MSTP            │  │
  │  └─────────────────────────────────────────┘  │
  └────────────────────────────────────────────────┘

  Per-port egress queues (8 queues, one per 802.1Q PCP class):
  Q7[safety] Q6[video] Q5[signalling] Q4–Q0[bulk/best-effort]
  Scheduler: Strict Priority (SP) or Weighted Round Robin (WRR)

Frame Forwarding and Forwarding Database (FDB)

Operation	Trigger	Action
Learning	Any frame received on port P with source MAC X	FDB: add X → port P with age timer (300s default)
Forwarding (known)	Destination MAC found in FDB	Unicast forward to learned port only (no flooding)
Flooding (unknown)	Destination MAC not in FDB	Forward to all ports in same VLAN (except ingress port)
Multicast	Destination MAC is multicast	Forward to all VLAN members unless IGMP snooping enabled
Broadcast	FF:FF:FF:FF:FF:FF	Forward to all VLAN members
FDB flush	MSTP topology change or management command	All dynamic entries deleted; temporary flooding until re-learned

Egress Queue Architecture and Priority

Textqueue_arch.txt

Egress queue priority for an automotive switch port:

  Ingress frame (PCP=6) → 8-level classifier → Queue 6

  Strict Priority (SP) scheduler:
  Queue 7 (empty) → Queue 6 → served first → Queue 5 → ... → Queue 0

  ┌───────────────────────────────────────────────────────────┐
  │  Q7: Safety (PCP=7)        ████  ← drained first always  │
  │  Q6: Video (PCP=6)         ████████                       │
  │  Q5: Signalling (PCP=5)    ████                           │
  │  Q4: Control (PCP=4)       ████████████                   │
  │  Q3: Diagnostics (PCP=3)   ████████                       │
  │  Q2: OTA/Background (PCP=2)████████████████               │
  │  Q1: (PCP=1)               ████                           │
  │  Q0: Best-effort (PCP=0)   ██████████████████████████████ │
  └───────────────────────────────────────────────────────────┘
  → Q0 only gets service when all higher queues are empty

  With TAS (Time-Aware Shaper, IEEE 802.1Qbv):
  Gate List controls which queues are allowed to transmit each µs slot
  Safety queue gets guaranteed 50 µs window every 1 ms period

Automotive Switch Chips

Chip	Vendor	Ports	TSN Support	Typical Use
SJA1110	NXP	8× 100/1000M + 1G uplink	802.1Qbv, 802.1Qav, 802.1AS	Domain controller, ADAS backbone
88Q5072/5050	Marvell	4–8× 1G + 10G cascade	Full TSN suite	Central gateway, zonal architecture
TC9563	Toshiba	4× 100M	802.1Qav (CBS)	Body domain, entry gateway
BCM89811	Broadcom	4× 1G	802.1Qbv, 802.1Qav	High-end ADAS platform

Summary

Automotive Ethernet switches implement the same IEEE 802.1 switching standards as enterprise switches, with added automotive hardening (−40°C to +125°C, AEC-Q100) and TSN gate support. The FDB learning/aging mechanism means that after a network topology change or node reset, there will be a brief flooding period while entries are re-learned — safety-critical streams must use static FDB entries (never aged out) to avoid this flooding. Per-port egress queue depth is typically 4–16 kB per queue; queue overflow causes tail-drop of the lowest-priority frames first.

🔬 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.