Hands-On: TSN Stream Configuration - Automotive Ethernet

Lab Scope: TSN Stream Configuration

Component	Detail
Platform	Linux with linuxptp (ptp4l) + tc qdisc for TAS; or NXP SJA1110 EVB
Goal	gPTP sync < 1 µs; TAS gate for safety stream; verify worst-case latency
Tools	ptp4l, phc2sys, tc (traffic control), ethtool, Wireshark

Exercise 1: gPTP with linuxptp

Bashgptp_setup.sh

#!/bin/bash
# Set up gPTP clock sync using linuxptp on Linux with hardware timestamping

IFACE="eth0"
PTP_CONFIG="automotive_gptp.cfg"

# Verify hardware timestamping capability
ethtool -T $IFACE | grep "hardware-transmit\|hardware-receive\|hardware-raw-clock"
# Must show: hardware-transmit, hardware-receive (software is not sufficient)

# Create automotive gPTP config (802.1AS profile)
cat > $PTP_CONFIG << 'EOF'
[global]
dataset_comparison         G.8275.x
G.8275.defaultDS.localPriority 128
twoStepFlag                1
priority1                  128
priority2                  128
clockClass                 135
clockAccuracy              0xFE
offsetScaledLogVariance    0xFFFF
domainNumber               0
free_running               0
freq_est_interval          1

# Automotive: hardware timestamping mandatory
tx_timestamp_timeout       10
logAnnounceInterval        0     # 1 s
logSyncInterval            -3    # 125 ms (automotive profile)
logMinPdelayReqInterval    0     # 1 s
announceReceiptTimeout     3

[eth0]
delay_mechanism            P2P   # peer-to-peer (802.1AS mandatory)
network_transport          L2    # Ethernet (no UDP/IP for gPTP)
ptp_dst_mac                01:80:C2:00:00:0E
EOF

# Start ptp4l as slave (time receiver) — use -m for master
ptp4l -f $PTP_CONFIG -i $IFACE -s &  # -s = slave only
PTP_PID=$!

# Sync PHC to system clock (or vice versa)
phc2sys -a -rr -O 0 &   # slave system clock to PHC

sleep 5
# Check offset (should be < 1000 ns = 1 µs after convergence)
pmc -u -b 0 'GET CURRENT_DATA_SET' | grep -E "offsetFromMaster|meanPathDelay"

Exercise 2: TAS Gate List on Linux

Bashtas_linux.sh

#!/bin/bash
# Configure TAS (TAPRIO qdisc) on Linux using tc
# Requires: kernel 5.4+ with taprio support; hardware timestamping

IFACE="eth0"
CYCLE_NS=1000000  # 1 ms cycle

# Configure TAPRIO (Time-Aware Priority scheduler) with hardware offload
tc qdisc replace dev $IFACE parent root handle 100 taprio \
  num_tc 8 \
  map 0 1 2 3 4 5 6 7 \  # 8 traffic classes (one per 802.1Q PCP priority)
  queues 1@0 1@1 1@2 1@3 1@4 1@5 1@6 1@7 \  # 1 queue per TC
  base-time 0 \           # start immediately (aligned to gPTP via phc)
  sched-entry S 0x80 50000 \   # Q7 open for 50 µs (safety)
  sched-entry S 0x60 100000 \  # Q6+Q5 for 100 µs (video+signalling)
  sched-entry S 0x1F 850000 \  # Q0–Q4 for 850 µs (best effort)
  clockid CLOCK_TAI \          # use PHC synced to gPTP grandmaster
  flags 0x2                    # use hardware offload (flags=2)

# Verify gate schedule was applied
tc qdisc show dev $IFACE

# Tag safety traffic with PCP=7 using VLAN and DSCP marking
# On Linux: use iproute2 tc filter with skb_prio or VLAN tag

Summary

The linuxptp + tc TAPRIO stack provides a functional TSN implementation on standard Linux hardware, making it ideal for lab validation and algorithm development before porting to automotive switch hardware. The critical step is hardware timestamping verification: ethtool -T must confirm hardware-transmit and hardware-receive — software timestamping achieves only 10–100 µs accuracy. For production automotive switches (SJA1110, 88Q5072), the TAS configuration is loaded via AUTOSAR EthSwt SPI configuration or NETCONF/YANG from the Central Network Configurator during ECU startup.

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