A real Zephyr ECU talking to the real Eclipse SOVD adapter, over real CAN
We wired a real EDS firmware build to the real Eclipse OpenSOVD Classic Diagnostic Adapter over a real CAN bus — discovery, a data read, a SecurityAccess unlock, a RoutineControl call. No simulator on either side.
Read →Change one line, watch every artifact move
A single YAML field change in an EDS diagnostics config, traced through generated C, pytest, the SOVD CDA descriptor, and CAPL. There's a script — try it yourself.
Read →Building the diagnostics layer for a SoDeV-style Zephyr guest
A Zephyr ECU example shaped like SoDeV's own reference app, with the diagnostics layer SoDeV leaves to you. Build it and run the campaign on your laptop.
Read →How much RAM does an ISO-TP stack actually need?
We linked a real UDS/ISO-TP ECU for Cortex-M4 and measured it: 23.3 KB flash, 68.7 KB RAM. The protocol state machine is 73 bytes. Here is where the rest goes.
Read →How to implement UDS SecurityAccess correctly
UDS SecurityAccess (service 0x27) is simple to implement and easy to get wrong. The real failure modes, what a correct implementation looks like, and how to prove yours is one.
Read →Do you need AUTOSAR for UDS?
UDS is an ISO 14229 protocol, not an AUTOSAR feature. When adopting AUTOSAR Classic for diagnostics is the right call, and when it is a platform you are paying for twice.
Read →xaloqi-tester is on PyPI: a UDS ECU in 60 seconds, no hardware
xaloqi-tester is free, Apache-2.0, and on PyPI: pip install it and get a full simulated UDS ECU with no hardware, no CAN stack, no config file.
Read →Validating UDS across Linux sleep/wake on AMP SoCs like the STM32MP2
On AMP SoCs like the STM32MP2, the UDS server on the M-core must survive Linux suspend/resume. How to test DTC persistence across sleep/wake today.
Read →From ARXML to a running UDS server in one sitting
Turn an AUTOSAR ECU Extract into a validated UDS server on Zephyr or FreeRTOS — import the ARXML, generate the C, run a campaign, no hand-transcription.
Read →Where does diagnostics fit in the AGL SoDeV stack?
AGL's SoDeV reference platform picks Zephyr for its real-time domains, and leaves the diagnostics path to the vehicle to the teams building on it. What that means in practice.
Read →From UDS to SOVD — what actually changes when diagnostics goes RESTful
What actually changes when vehicle diagnostics goes RESTful — and how one YAML config drives a UDS server, its tests, and its SOVD descriptor at once.
Read →Getting started with UDS diagnostics on Zephyr RTOS in 30 minutes
Step-by-step tutorial: ISO 14229 UDS diagnostics on Zephyr RTOS from zero to first request in 30 minutes. YAML config, codegen, Zephyr integration, and live test.
Read →ASIL-B UDS diagnostics on Zephyr RTOS — how EDS enforces safety properties at build time
How Xaloqi EDS enforces ASIL-B safety properties at build time for ISO 14229 UDS diagnostics on Zephyr RTOS and FreeRTOS.
Read →AAOS-SDV goes open source — what it means for ECU diagnostics engineers
Google open-sourced AAOS-SDV. Here's what the SOME/IP broker, SOVD, and DoIP mean for the firmware engineers building ECUs that AAOS-SDV will manage.
Read →UDS campaigns in CI — running protocol tests without hardware
Running full UDS protocol test campaigns without hardware — session control, SecurityAccess, DID reads and writes, DTC management — as part of every CI run.
Read →From CAN to DoIP — what the transport change actually involves
What the transport change from ISO-TP over CAN to DoIP actually involves for a Zephyr RTOS UDS stack, and how EDS handles it.
Read →UDS on FreeRTOS — a different integration problem than Zephyr
What integrating a production-grade UDS stack on FreeRTOS involves, and how EDS handles the parts that Zephyr normally does for you.
Read →Running a virtual SDV diagnostics stack — no hardware required
A complete virtual environment to define an ECU, generate its UDS implementation, run automated protocol campaigns, and inspect results — no hardware required.
Read →