Running a virtual SDV diagnostics stack — no hardware required
A complete environment to define an ECU, generate its UDS implementation, run automated protocol campaigns, and inspect results. No bench. No CAN adapter. The same stack that runs in CI.
Read →UDS on FreeRTOS — a different integration problem than Zephyr
FreeRTOS gives you a scheduler — everything else you bring yourself. This post covers what integrating a production-grade UDS stack on FreeRTOS actually involves, and how EDS handles it with four callbacks.
Read →From CAN to DoIP — what the transport change actually involves
New vehicle Ethernet architectures route diagnostics over TCP/IP via ISO 13400. Here's exactly what changes in your UDS stack when you move from ISO-TP over CAN to DoIP — and what stays identical.
Read →UDS campaigns in CI — running protocol tests without hardware
Session control, SecurityAccess, DID reads and writes, DTC management — as part of every CI run, against a virtual ECU, with no hardware required. Same YAML, same assertions, same pass/fail output.
Read →ASIL-B UDS diagnostics on Zephyr RTOS — how EDS enforces safety properties at build time
Getting from "the UDS stack passes integration tests" to "the UDS stack satisfies ISO 26262 Part 6" requires specific architectural choices that are very hard to retrofit. Here's what they are.
Read →