| Parameter | Value | Notes |
|---|---|---|
| Speed | 100 Mbit/s full-duplex | Simultaneous TX and RX on one pair |
| Line encoding | PAM3 (3-level pulse amplitude) | 3 symbols/cycle; DC-balanced; no separate clock line |
| Symbol rate | 66.67 MBaud | 100 Mbit/s ÷ 1.5 bits/symbol (PAM3) |
| Cable | Single UTP pair (STP optional) | Unshielded twisted pair, 15m max; STP for EMC-sensitive runs |
| Connector | IEC 63171-6 (H-MTD), Rosenberger H-MTD, or RJ45 in lab | 2-pin differential; not standard RJ45 in vehicle |
| Standard | IEEE 802.3bw-2015 (merged into 802.3-2018) | OPEN Alliance BroadR-Reach compatible |
| Typical ECUs | ADAS camera ECUs, gateway ECUs, TCU | Low-cost, widely deployed since ~2016 |
100BASE-T1 — IEEE 802.3bw
1000BASE-T1 — IEEE 802.3bp
| Parameter | Value | Notes |
|---|---|---|
| Speed | 1000 Mbit/s (1 Gbit/s) full-duplex | 10× 100BASE-T1 |
| Line encoding | PAM3 with 4D-PAM3 trellis coding | More complex DSP; 3-level × 4 dimensions |
| Symbol rate | 750 MBaud | Higher frequency → tighter EMC requirements |
| Cable | STP (shielded twisted pair) recommended at 1 Gbit/s | 15m channel budget; shielding above 750 MHz matters |
| Standard | IEEE 802.3bp-2016 | OPEN Alliance TC12 for 1000BASE-T1 |
| Typical ECUs | Domain controllers, central gateways, LiDAR ECUs | High-bandwidth applications |
PHY Layer Architecture (PCS/PMA/MDI)
Textphy_layers.txt
OSI Layer 1 (Physical) split for automotive Ethernet PHY:
┌────────────────────────────────────────────────────────────┐
│ MAC (Media Access Control) — Layer 2 boundary │
├────────────────────────────────────────────────────────────┤
│ MII / RGMII / SGMII / XGMII │ ← CPU↔PHY interface
├────────────────────────────────────────────────────────────┤
│ PCS (Physical Coding Sublayer) │
│ ├── Scrambling / descrambling (DC balance) │
│ ├── 4B6B or PAM3 symbol encoding │
│ └── Error detection (CRC-8 for 100BASE-T1) │
├────────────────────────────────────────────────────────────┤
│ PMA (Physical Medium Attachment) │
│ ├── Echo cancellation (full-duplex on 1 pair) │
│ ├── Adaptive equaliser (compensates cable loss) │
│ └── Clock recovery (embedded clock; no separate CLK) │
├────────────────────────────────────────────────────────────┤
│ MDI (Medium Dependent Interface) │
│ └── Differential pair TX/RX (simultaneous on same pair) │
└────────────────────────────────────────────────────────────┘
Key: Echo cancellation is what enables full-duplex on a single pair
TX signal leaks into RX path; DSP in PMA subtracts the known TX pattern
Residual = actual remote signal. Must cancel 30–40 dB of echo.
PHY chips: NXP TJA1100 (100BASE-T1), TJA1102 (dual-port 100BASE-T1),
Marvell 88Q2112 (1000BASE-T1), Marvell 88Q222x (100BASE-T1)Channel Requirements and Connector Standards
| Spec | 100BASE-T1 | 1000BASE-T1 |
|---|---|---|
| Max channel length | 15 m | 15 m (STP); 10 m (UTP) |
| Return loss | ≥ 12 dB up to 66 MHz | ≥ 12 dB up to 600 MHz |
| Insertion loss | ≤ 11 dB at 66 MHz | ≤ 11 dB at 600 MHz |
| EMC radiated emissions | CISPR 25 Class 5 | CISPR 25 Class 5 (STP required for Class 5 at 1G) |
| Connector | IEC 63171-6 (H-MTD), FAKRA, RJ45 | Same; STP connector preferred for 1G |
Summary
The defining innovation of automotive Ethernet PHYs is full-duplex communication over a single twisted pair — achieved through echo cancellation in the PMA sublayer. The PHY chip implements all of this in silicon; the host processor connects to the PHY via a standard MII/RGMII/SGMII interface, the same interface used for standard Ethernet PHYs. NXP TJA1100 for 100BASE-T1 and Marvell 88Q2112 for 1000BASE-T1 are the most widely deployed automotive PHY chips. OPEN Alliance TC8 defines the ECU-level compliance test suite for interoperability verification between PHYs from different vendors.
🔬 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.