Issue dossier

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.

A linkable camp-impact record with badge context, severity, evidence confidence, and source notes.

Back to issues index

firmware-source gap · project logs but incomplete source recovery · needs artifact-level archive

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

Badge
LayerOne 2017 CAN Bus Badge
Category
firmware-source gap
Severity
note
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.

Evidence

Related Resources

development log

LayerOne 2017 goals 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.

Badge: LayerOne 2017 CAN Bus Badge

Source trail

Evidence Sources

Hackaday.io / charliex · retrieved 2026-05-15

How are the goals going?

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.

Badge: LayerOne 2017 CAN Bus Badge

Hackaday.io / charliex · retrieved 2026-05-15

LayerOne 2017

Primary badge-team project source for LayerOne 2017 badge framing, car-hacking focus, project authorship, visible media boundary, and development-log trail.

Badge: LayerOne 2017 CAN Bus Badge

Hackaday.io / charliex · retrieved 2026-05-15

LayerOne 2017 details

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.

Badge: LayerOne 2017 CAN Bus Badge