Apr 2026
13 Mon
14 Tue
15 Wed
16 Thu
17 Fri
18 Sat 09:00 AM – 06:00 PM IST
19 Sun 09:00 AM – 06:00 PM IST
Utsav Krishna
Submitted Mar 14, 2026
Abstract:
In automotive software development, a misconfigured ECU parameter doesn’t cause a crash in staging. It causes unexpected behaviour in a vehicle. The tooling that handles configuration correctness needs to be held to the same standard as the software it configures.
I built a CLI-based ECU configuration engine in Rust during my work in automotive SDV tooling. The system manages roughly 5000 parameters across three distinct configuration domains: Adaptive AUTOSAR, Classic AUTOSAR, and bootloader. Each domain has its own Rust crate. Each crate has its own WASM module. A core crate hosts a gRPC server. Serde handles the full serialize/deserialize round-trip at the centre of all of it and this talk is an honest account of what that looked like in practice.
Audience Takeaway:
Target Audience:
This talk is for Rust engineers who want to see Serde applied across a full production pipeline, and for anyone building developer tooling where configuration state needs to be validated, persisted, and trusted.
Speaker Bio:
Utsav Krishna is an automotive software engineer with nearly a decade of experience building ECU software across infotainment, V2X communication, cybersecurity, OTA, and SDV tooling — working across Linux, QNX, and Android Automotive at multiple Tier-1 automotive suppliers. (BOSCH, Harman International, LG Electroncs)
Most recently he has been building production Rust-based tooling for automotive ECU configuration, covering CLI tooling, WASM-based validation, and gRPC service architecture in the SDV ecosystem. He writes about automotive software architecture and open-source SDV infrastructure on LinkedIn and few arcticles upcoming on Medium.
Hosted by
{{ gettext('Login to leave a comment') }}
{{ gettext('Post a comment…') }}{{ errorMsg }}
{{ gettext('No comments posted yet') }}