Gateway ECU Architecture - Vehicle Networks

Gateway Routing Types

Type	Signal Decode?	Conversion?	Latency	Use Case
Signal gateway	Full decode + re-encode	Yes (scaling, unit)	1–2 CAN cycles	CAN-to-Ethernet, cross-domain signal with different scaling
PDU gateway	No (byte copy)	No	< 0.5 ms	Same-format cross-bus routing, diagnostic forwarding
Frame gateway	No (raw frame relay)	No	< 0.1 ms	Bridge two CAN segments, transparent relay

AUTOSAR PduR Routing Path Configuration

XMLPduR_RoutingTable.arxml



  Route_VehicleSpeed_CAN0_to_CAN1_ETH
  
    /CanIf/CanIfRxPduCfg/CAN0_VehicleSpeed_Pdu
  
  
    
    
      /CanIf/CanIfTxPduCfg/CAN1_VehicleSpeed_Fwd_Pdu
      FALSE
    
    
    
      /SoAd/SoAdTxPduCfg/Eth_VehicleSpeed_SomeIp_Pdu

CAN-to-Ethernet Gateway: Signal Conversion

Cgw_signal_routing.c

/* Signal gateway: VehicleSpeed CAN → SOME/IP Ethernet */
/* Called by AUTOSAR COM on reception of CAN VehicleSpeed PDU */

#include "Com.h"
#include "SomeIp_Transformer.h"

void Gateway_ProcessVehicleSpeed(void)
{
    uint16  raw_can_speed;
    float32 physical_speed;
    SomeIp_VehicleSpeed_t someip_payload;

    /* Step 1: Unpack from CAN PDU (raw uint16, factor=0.01 km/h) */
    Com_ReceiveSignal(COM_SIG_VEHICLESPEED_CAN, &raw_can_speed);
    physical_speed = (float32)raw_can_speed * 0.01f;

    /* Step 2: Range check and validity */
    if (physical_speed > 300.0f || physical_speed < 0.0f) {
        Gateway_SetSignalInvalid(GW_SIG_VEHICLESPEED);
        return;
    }

    /* Step 3: Pack into SOME/IP payload (big-endian float32) */
    someip_payload.speed_kmh       = physical_speed;
    someip_payload.validity        = GW_VALID;
    someip_payload.source_timestamp = StbM_GetCurrentTime();

    /* Step 4: Trigger SOME/IP NOTIFICATION via SoAd */
    SomeIp_TransformAndSend(SOMEIP_SERVICE_0x1234, SOMEIP_EVENT_0x8001,
                            &someip_payload, sizeof(someip_payload));
}

Gateway Latency Budget Analysis

End-to-End Latency: CAN Sensor to Ethernet Consumer

  ECU_ESC (source)          Gateway ECU           ECU_ADAS (consumer)
  ────────────────         ───────────────         ──────────────────────
  Task period: 10 ms       CAN Rx interrupt         Ethernet receive task
  Task jitter:  0-10 ms    + PduR route             period: 10 ms
                            + COM signal unpack
                            + SOME/IP transform
                            + SoAd UDP send
                            + PHY + wire: < 0.1 ms
                            = 0-2 ms gateway
  Total worst case:
  Task period + jitter + gateway + Eth receive jitter
  = 10 + 10 + 2 + 10 = 32 ms worst case

  AUTOSAR TIMEX model:
  LatencyConstraint: WheelSpeed_CAN_to_ADAS_Ethernet ≤ 30 ms
  → Must reduce CAN task period to 5 ms or add gateway task synchronisation

Summary

Gateway ECU design requires choosing the right routing type (signal for cross-bus conversion, PDU for same-format relay, frame for transparent bridging) and validating end-to-end latency with the AUTOSAR TIMEX model. The PduR 1:N routing fan-out allows one received PDU to be simultaneously forwarded to multiple destinations — body CAN and Ethernet in one routing table entry. Signal validity checking at the gateway prevents corrupted CAN values from reaching Ethernet consumers downstream.

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