LayerOne

LayerOne 2025

The May 24-25, 2025 LayerOne Pasadena edition whose official event and Hardware Hacking Village pages documented electronic-badge ticketing, HHV badge support, and the GLiTCh BadgE hardware-hacking platform.

Pasadena Hilton, Pasadena, California · United States · 2025

LayerOne 2025 GLiTCh BadgE

LayerOne 2025's GLiTCh BadgE was a conference electronic badge and hardware-hacking platform centered on an RP2040, iCE40 FPGA, voltage glitching, crowbar control, SWD, AVRISP, analog monitoring, multiple USB modes, and CLI-driven experiments.

Lifecycle

Add-ons & Upgrades

debug-probe firmware

CMSIS-DAP and SWD debug mode

DAP mode presents the badge as a CMSIS-DAP probe for pyOCD, OpenOCD, Keil, and SWD target debugging while keeping a CLI serial interface available.

Compatibility: LayerOne 2025 GLiTCh BadgE

fault-injection hardware

Voltage glitcher and crowbar lab

The badge docs expose voltage-glitch and crowbar controls, setup commands, trigger workflows, and target-voltage tuning through the GLiTCh BadgE CLI.

Compatibility: LayerOne 2025 GLiTCh BadgE

programming interface

AVRISP programming mode

The hardware-hacking guide documents AVRISP wiring and commands for initialization, target identification, flash reads/programming, and fuse access.

Compatibility: LayerOne 2025 GLiTCh BadgE

Operational history

Issues & Camp Impact

AI-generated documentation caveat · repository README · documented with caution

The repository README explicitly warns that later documentation may include AI-generated docs, so this pass treats the repository as useful project evidence while preferring official LayerOne pages for event claims and recording documentation limits.

Hardware and firmware features are kept to repeatedly corroborated repository and guide statements instead of overstating uncertain generated prose.

missing rights-cleared image · local project policy · needs licensed original replacement

No LayerOne 2025 badge image is published because the available official-site, repository, and GitHub-attachment visuals have not been paired with complete original-photo provenance, license, attribution, and processing notes; a May 22, 2026 repository recheck found the only tracked PNG is a script/test screenshot rather than a badge hero image.

The entry remains source-backed and image-free rather than reusing generated, teaser, attachment, screenshot, or undocumented badge imagery.

Resources

Sources