No cars were harmed for this talk: Automotive Rust, amateur style
summary
Shows how a CAN bus is tapped via the OBD‑II port, decoded with an ESP32 TWAI transceiver and logged into SavvyCAN, revealing 1,000 messages per second across about 45 distinct IDs. Describes reverse‑engineering an instrument cluster by fuzzing its connector, switching bus speed from 500k to 125k to make frames appear, isolating the throttle position frame and parsing its analog payload, and building a bare‑metal microcontroller dashboard (Bevy rendering + embassy async) that ultimately works.
AI-written summary · about
chapters (11)
- 0:00Automotive Rust tinkering intro
- 2:34From wires to CAN bus
- 7:09Connecting via OBD-II
- 10:40Decoding CAN frames on ESP32
- 13:14Reverse engineering instrument cluster
- 17:26Analyzing CAN data with SavvyCAN
- 20:58Real-time car data display
- 23:29Closed ecosystems and regulations
- 26:42Privacy and security concerns
- 29:10Embedded Rust lessons
- 30:34Why try embedded Rust
related talks
49mHopping on the CAN Bus
37mAutomatic Automotive Hacking
36mCar Hacking
54mCantact: An Open Tool for Automative Exploitation
50mAdvanced CAN Injection Techniques for Vehicle Networks
58mA Survey of Remote Automotive Attack Surfaces
12mDetect Denial of Service on an Open Embedded Automotive Platform
41mIt's easier to break than to patch: a stealthy DoS attack on CAN