LayerOne 2017 · United States · 2017

LayerOne 2017 CAN Bus Badge

STM32F4 badge for CAN bus and vehicle-hacking experiments

LayerOne 2017's electronic badge was a CAN-bus-focused STM32F4 conference badge with a TFT display, storage, USB device and host behavior, external CAN headers, audio output, rechargeable battery planning, PC-side CAN tooling, and J2534-adjacent software work.

LayerOne United States Los Angeles STM32F4 CAN Bus Vehicle Hacking TFT USB HID USB Host J2534 ST-Link Hardware Hacking Village North America

EventLayerOne 2017

SeriesLayerOne

LocationSheraton Gateway LAX, Los Angeles, California

CountryUnited States

People

Authors & Credits

badge prototype builder and collaborator

mmca

The project logs repeatedly credit mmca in prototype bring-up, badge design decisions, and build work.

Source

badge-team project author

charliex

The Hackaday.io project is published under charliex and preserves the 2017 badge development notes, architecture, and project logs.

Source

event and badge-page publisher

LayerOne

Official LayerOne HHV pages establish the public electronic-badge link trail for the 2017 badge.

Source

Why It Mattered

It captures LayerOne's car-hacking badge year as a bridge between classic soldering-village badgelife and a more instrument-like conference badge: attendees were meant to work with CAN logging, injection, ECU reflashing ideas, USB HID/CDC paths, and development workflows rather than only visible LED effects.

Hardware

The badge-team Hackaday.io project documents a 2.2 or 2.4-inch DMA-driven SPI TFT display, STM32F446/F405/F415-class LQFP64 support, SPI SD card, twin 1 Mbps CAN buses with SN65VHD230/235-family transceivers, external CAN headers, USB device and USB host support, audio output through a headphone jack, rechargeable battery work, buttons and switches, and ST-Link/SWD programming expectations.

Software & Apps

The project notes describe multiple firmware tracks, a focus on CAN-side behavior, PC-side software for CAN, J2534 202/404 mostly-compatible DLL work, simple ECU emulator experiments, CAN logger output, NES emulator memory read/write over CAN, HID or CDC output, and online or local GCC/IAR/Keil-style development paths.

Lore

LayerOne's HHV archive links the 2017 electronic badge to the badge team's project page. The project says the aim was 400 built badges after 300 hand-built 2016 badges, and it frames the badge around a long-discussed LayerOne car-hacking session.

Lifecycle

Add-ons & Upgrades

badge controller source-backed

STM32F4 badge core

The badge-team details page names STM32F446/F405/F415-class LQFP64 support as the controller direction for the 2017 badge.

Compatibility: LayerOne 2017 CAN Bus Badge

Source

badge software partial archive

CAN logger and emulator experiments

The development logs describe CAN logging, ECU reflashing experiments, J2534-adjacent PC software, NES emulator memory access over CAN, and PC-versus-badge gameplay ideas.

Compatibility: LayerOne 2017 CAN Bus Badge

Source

display and storage source-backed

DMA-driven TFT and SD storage

Project details describe a 2.2 or 2.4-inch DMA-driven SPI TFT display with ILI9341/45 support and SPI SD card storage.

Compatibility: LayerOne 2017 CAN Bus Badge

Source

programming and USB interface documented

USB host/device and SWD workflow

The badge-team notes describe USB device support, USB host, HID or CDC behavior, and ST-Link V2/SWD programming expectations.

Compatibility: LayerOne 2017 CAN Bus Badge

Source

vehicle-hacking interface source-backed

Twin CAN bus interface

The project documents twin 1 Mbps CAN buses, two transceivers, external CAN headers, MITM or dual-logging breakout, and CAN-side badge focus.

Compatibility: LayerOne 2017 CAN Bus Badge

Source

Operational history

Issues & Camp Impact

firmware-source gap note

The project logs describe firmware tracks, CAN tooling, HID/CDC behavior, and emulator experiments, but this pass did not recover a complete public final firmware repository, board-production release, or challenge/utility software archive.

Software and protocol claims are kept to the public project statements rather than treating development notes as a complete release package.

Confidence: project logs but incomplete source recovery
Status: needs artifact-level archive
Timeframe: current catalogue build
Source note: Hackaday.io LayerOne 2017 details and logs.

missing rights-cleared image note

No LayerOne 2017 badge image is published because the recovered official HHV photos, Hackaday.io project gallery images, YouTube frames, and development-log photos do not expose complete reusable image rights, attribution, and processing provenance for catalogue publication.

The entry remains source-backed and image-free rather than copying official-page images, Hackaday CDN photos, video frames, or prototype screenshots without complete provenance.

Confidence: local project policy
Status: needs licensed original replacement
Timeframe: current catalogue build
Source note: badge.gallery image policy, LayerOne HHV page, Hackaday.io project gallery/log images, and available video media.

prototype-to-final caveat note

The public Hackaday.io material is a development log with prototype revisions and feature planning, while the official HHV page establishes the year as an electronic badge without publishing a final production source package.

The catalogue records the source-backed architecture and car-hacking direction while avoiding unsupported claims about every final shipped component, firmware image, or quantity.

Confidence: badge-team logs
Status: documented with caution
Timeframe: 2017 badge development
Source note: LayerOne HHV archive, Hackaday.io project details, and project logs.

Resources

LayerOne 2017 InfoconDB entry conference archive · Conference archive source for the May 26-28, 2017 Sheraton Gateway LAX, Los Angeles event context and archived con-page trail. LayerOne 2017 badge-team project badge-team project page · Primary badge-team project source for the LayerOne 2017 badge overview, car-hacking focus, gallery/media boundary, and project log trail. LayerOne 2017 goals log development log · Project log source for feature status around CAN, USB, audio, battery, buttons, J2534 work, ST-Link programming, ECU reflashing, CAN logger behavior, and memory access over CAN. LayerOne 2017 project details hardware notes · Badge-team details page documenting TFT display, STM32F4 class controller, SD card, twin CAN, USB host/device, audio, battery, buttons, PC CAN software, and SWD/ST-Link expectations. LayerOne Hardware Hacking Village official village page · Official HHV page identifying the 2017 electronic badge and linking the badge-team Hackaday.io project page.

Sources

Hackaday.io / charliex: LayerOne 2017 Retrieved 2026-05-15 · Primary badge-team project source for LayerOne 2017 badge framing, car-hacking focus, project authorship, visible media boundary, and development-log trail. Hackaday.io / charliex: LayerOne 2017 details Retrieved 2026-05-15 · Technical project source for the STM32F4 badge architecture, TFT, SD card, twin CAN, USB, audio, battery, controls, PC CAN tooling, J2534 work, and ST-Link/SWD programming notes. Hackaday.io / charliex: How are the goals going? Retrieved 2026-05-15 · Development-log source for feature status, CAN logger and ECU reflashing experiments, HID/CDC output, NES emulator memory access over CAN, and explicit prototype-versus-final caveats. InfoconDB: LayerOne 2017 Retrieved 2026-05-15 · Conference archive source proving the May 26-28, 2017 Sheraton Gateway LAX, Los Angeles LayerOne event context. LayerOne: Hardware Hacking Village Retrieved 2026-05-15 · Official village source linking the 2017 electronic badge to the badge-team Hackaday.io project page.