AUTOSAR

The opener of the IEEE 1722 series: what AVTP is, which AVTPDU formats exist (AAF, CRF, IIDC, RVF), and how native Ethernet framing differs from optional UDP encapsulation.

The opening post of the EthSwt tutorial series: the module's state machine, the configuration classes as defined by the SWS, and where EthSwt sits between EthIf and the switch ports in the AUTOSAR stack.

The opening post of the EthTrcv series: what an Ethernet transceiver is, how EthTrcv sits in the AUTOSAR Layered Architecture Model between EthIf and PHY hardware, and which PHY chips show up in real projects.

ACF in the AUTOSAR module IEEE1722Tp: ACF_CAN and ACF_LIN, TSCF vs. NTSCF, bundling multiple field-bus messages, and why it matters for zonal architectures — including a clear boundary against Open1722's broader format scope.

The concrete EthSwt function calls: the init sequence with its background task, port modes, link state, and what to watch for when EthSwt interacts with EthTrcv on switch ports.

How EthTrcv gets from UNINIT to ACTIVE: the state machine, the initialization sequence in the EcuM context, and the key API functions with error handling.

The real container structure of IEEE1722Tp in the ARXML per Chapter 10 of the SWS: IEEE1722TpStream, PDU pools, stream subtypes — and why stream-to-switch-port mapping runs indirectly through generic PDU routing.

The real ARXML container structure of EthSwt: EthSwtPort, EthSwtPortIngress and the actual VLAN parameters — including a complete configuration example.

How EthTrcv maps onto the AUTOSAR configuration model — container structure, mandatory parameters, and EthIf referencing, and a complete, annotated ARXML example, exactly per the official SWS EthernetTransceiverDriver (AUTOSAR CP R25-11).

Two followable end-to-end examples with Open1722: a camera stream from capture to deterministic delivery, and a CAN subnet transparently tunneled via ACF.CAN over a TSN backbone.

Toggling VLANs at runtime, EthSwt's surprisingly powerful port-mirror configuration, MAC learning modes, and diagnostics via MIB counters.

The fourth and final part of the EthTrcv core series: WakeUp handling via PHY pin and in-band signaling, the interplay with EcuM and EthSM, and how to diagnose the most common runtime problems on the transceiver.

Cross-compiling and loading the Open1722 ACF-CAN kernel module against the Yocto kernel, and testing it between two physical BeagleBone Black boards over Ethernet — real CAN tunneling, no loopback on one machine.

The three hardware variants for switch/PHY arrangements defined by the AUTOSAR SWS, the forwarding engine, and typical switch chips in practice.

Why 100BASE-T1 links need a fixed master/slave role, how it is configured in the PHY register and in ARXML, and why a role conflict is the classic 'no link' bug in the field.

The full AVTPDU and ACF scope of IEEE 1722-2025 compared to the AUTOSAR module IEEE1722Tp (R24-11): CVF, CAN-XL, FlexRay, MOST, GBB/ABB, GISF, and more — what the standard can do that AUTOSAR doesn't (yet) define.

Host-side interfaces (RGMII/SGMII) to the switch, internal forwarding paths, PCB and power aspects of multi-port chips, and the path a frame takes through the switch.

How internal, external, and remote loopback work inside the Ethernet PHY, how EthTrcv drives them, and why they are indispensable for end-of-line testing and fault isolation.

ACF_CANXL and ACF_CAN_XL_BRIEF in detail: VCID, SDT, acceptance field, and segmentation — the new header fields from IEEE 1722-2025 that AUTOSAR (R24-11) doesn't yet know.

Typical failure patterns during EthSwt chip bring-up — from a port that won't come up to a host interface that doesn't respond — with concrete debugging paths.

Register-level MDIO diagnostics for EthTrcv: reading standard and vendor registers, interpreting link status and error flags, and a case study of a link that refuses to come up.

ACF_CAN_V2 and ACF_CAN_BRIEF_V2 in detail: an 11-bit bus ID instead of 5 bits — and why LIN_V2 so far only exists on paper.

How IEEE 802.1AS (gPTP) distributes time across the vehicle network, why timestamp accuracy is decided inside the PHY chip, and how EthTrcv, Eth, EthTSyn, and StbM work together to deliver it.

How EthSwt accesses a switch chip via SPI: the real EthSwtSpi/EthSwtSpiSequence configuration and the generic register-access APIs that abstract MII and SPI alike.

ACF_GBB and ACF_ABB in detail: the generic request/response format from IEEE 1722-2025 for bus systems without their own ACF format — and why it matters for niche automotive protocols.

How EthTrcv fits into safety-relevant Ethernet architectures: ASIL decomposition, PHY-side fault detection, DEM integration, and what a PHY vendor's safety manual actually needs to deliver.

The real EthSwt_ReadMmd/WriteMmd API for Clause 45 register access over the SMI — including emulation via Clause 22 operations if the hardware doesn't natively support Clause 45.

How IEEE 802.1AE MACsec encrypts and authenticates Ethernet frames at Layer 2, why UN-R155 and ISO/SAE 21434 bring the topic into the vehicle, and what it means for EthTrcv configuration and the AUTOSAR Crypto Stack.

Vendor mechanisms for switch configuration via special Ethernet frames — and the important distinction from EthSwt_SetMgmtInfo, the real AUTOSAR mechanism for port-specific frame handling.

A practical guide to migrating from 100BASE-TX to 100BASE-T1: the technical differences, what changes in the AUTOSAR stack, common pitfalls, and a checklist for the transition.

How EthSwt identifies Ethernet frames as streams using AND-linked filter rules, and which filter actions (drop, block-source, VLAN modification, egress redirection) can follow.

What actually happens inside the PHY chip when EthTrcv_Init is called: the PMA/PCS/MDI architecture, link training on 100BASE-T1, and PHY-level power states — explained conceptually, without the electronics deep dive.

How EthSwt supplies the AUTOSAR Firewall module with StreamHandleIdentifiers and bucket statistics so it can raise security events to the IdsM — including the DRAFT-status APIs behind this functionality.

Cascaded egress schedulers, credit-based shaping and enhanced transmission selection, plus IEEE 802.1Q frame preemption — the core AUTOSAR mechanisms for deterministic Ethernet in the switch.

A hardware deep dive for software developers: what happens at PCB level when EthTrcv is configured — MAC interfaces, MDIO bus, line side, and the path of a frame through the PHY.

A practical troubleshooting guide for EthTrcv bring-up: seven typical failure scenarios from 'no link at all' to 'high bit error rate despite link up', each with causes and concrete debugging approaches.

How EthSwt manages secure channels and secure associations per switch port, with bypass lists for management traffic and a shared MKA key infrastructure with EthTrcv.

How EthSwt provides port-specific hardware timestamps for EthTSyn, and how cascaded switches synchronize their internal clocks over uplink ports to avoid separate path-delay measurement.

The two MAC learning modes defined by IEEE 802.1Q and AUTOSAR — SVL and IVL — the start-up learning phase, and the two-phase query pattern of EthSwt_GetArlTable.

The surprising fact-check finding: most of EthSwt's port diagnostic APIs are pure forwarders to the referenced EthTrcv instance, not switch-native functionality.

What's actually inside a switch chip's silicon? Shared-memory vs. crossbar fabric, the lookup engine, buffer architecture, egress queues in hardware, and the embedded management core.

Real switch stacking distinguished from the cascading already covered: shared FDB/management plane, dedicated stacking links, and what this means for EthSwt from an AUTOSAR perspective.

Beyond C4: defining custom element types with custom shapes in draw.io — using an AUTOSAR notation and an embedded hardware notation as examples.

EthSwt explained: when an AUTOSAR Ethernet ECU needs a switch driver instead of a plain EthTrcv, what the API looks like, and how VLANs, mirroring, and spanning tree are configured.