Network Management for Ethernet - Automotive Ethernet

AUTOSAR Ethernet State Manager (EthSM)

EthSM State Machine

  States:
  ┌──────────────────────────────────────────────────────────────┐
  │  OFFLINE          ←────────────────────────────────────────┐ │
  │  (PHY powered     │ Link down or                          │ │
  │   off / init)     │ CommunicationModeRequested=SILENT     │ │
  │       │           │                                        │ │
  │       ▼           │                                        │ │
  │  WAIT_TRCV_LINK   ─── PHY link up ──►  ONLINE             │ │
  │  (waiting for     │                    (PHY up, IP valid,  │ │
  │   PHY link-up)    │                     SOME/IP active)    │ │
  │                   │                        │               │ │
  │                   │                        ▼               │ │
  │                   │                    WAIT_TRCV_WAKEUP    │ │
  │                   │                    (sleep requested;   │ │
  │                   └────────────────────waiting for ECUs    │ │
  │                                         to be ready)  ─────┘ │
  └──────────────────────────────────────────────────────────────┘

  EthSM coordinates with:
  ├── EthTrcv (PHY driver): request link-up/down
  ├── TcpIp: assign/release IP address
  ├── SoAd/SOME/IP: enable/disable socket connections
  └── ComM: report network mode to application

EthSM Configuration and Link Monitoring

Cethsm_config.c

/* AUTOSAR EthSM: called by ComM when application requests network */
/* Generated from ARXML; simplified for clarity */

#include "EthSM.h"
#include "EthTrcv.h"
#include "TcpIp.h"

/* EthSM main function: called every 10 ms by SchM */
void EthSM_MainFunction(void)
{
    static EthSM_StateType s_state = ETHSM_STATE_OFFLINE;
    EthTrcv_LinkStateType link;

    switch (s_state) {
        case ETHSM_STATE_OFFLINE:
            /* Wait for ComM to request network */
            break;

        case ETHSM_STATE_WAIT_TRCV_LINK:
            EthTrcv_GetLinkState(ETHTRCV_INDEX_0, &link);
            if (link == ETHTRCV_LINK_STATE_ACTIVE) {
                TcpIp_RequestIpAddrAssignment(TCPIP_LOCALADDRID_0,
                    TCPIP_IPADDR_REQUEST_STATIC, &g_static_ip, 16u, &g_gw_ip);
                s_state = ETHSM_STATE_ONLINE;
                ComM_BusSM_ModeIndication(COMM_CHANNEL_ETH, COMM_FULL_COMMUNICATION);
            } else {
                /* Start link-down timer */
                if (g_link_down_ticks++ > (ETHSM_LINK_TIMEOUT_MS / 10u)) {
                    Dem_ReportErrorStatus(DEM_ETH_LINK_DOWN, DEM_EVENT_STATUS_FAILED);
                }
            }
            break;

        case ETHSM_STATE_ONLINE:
            /* Monitor for link loss */
            EthTrcv_GetLinkState(ETHTRCV_INDEX_0, &link);
            if (link != ETHTRCV_LINK_STATE_ACTIVE) {
                s_state = ETHSM_STATE_OFFLINE;
                ComM_BusSM_ModeIndication(COMM_CHANNEL_ETH, COMM_NO_COMMUNICATION);
            }
            break;
    }
}

Ethernet Sleep and Wake-Up Handling

Mode	PHY State	Network	Wake Trigger
ONLINE	Active; link up	Full traffic	N/A — already on
STANDBY	Link active; PHY in low-power	No user data; NM keepalive only	NM message received
SLEEP	PHY powered down; no link	No traffic	WoE (Wake-on-Ethernet) detection; or external GPIO
PARTIAL NW	Some ECUs sleep; others active	Selected services only	NM partial network request

Summary

EthSM is the AUTOSAR coordination module between PHY driver (EthTrcv), IP stack (TcpIp), and application (ComM). Its primary function is ensuring orderly startup (wait for link, assign IP, enable sockets) and shutdown (notify application, disable sockets, release IP, power down PHY). The link monitoring function must report persistent link failures to DEM — a 100 ms link interruption may be acceptable, but a permanent link down with no DEM event makes the vehicle undriveable without a root cause indicator. Ethernet NM (Network Management) coordinates sleep/wake across multiple ECUs to prevent one ECU from holding the network awake when all others want to sleep.

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