Jeroen Domburg
Sprite_tm's writeup documents the SHA2017 badge Gameboy emulator work.
SourceSHA2017 · Netherlands · 2017
Dutch camp Badge.Team milestone
A Badge.Team-supported Dutch camp badge with ESP32, e-paper, WiFi, Hatchery apps, WebUSB install paths, production lore, and a lasting role in European badge culture.
People
Sprite_tm's writeup documents the SHA2017 badge Gameboy emulator work.
SourceListed by media.ccc.de as a SHA2017 Badge talk speaker.
SourceListed by media.ccc.de as a SHA2017 Badge talk speaker.
SourceNiek Blankers' retrospective says ALLNET sponsored enough ESP32-WROVER modules for all badges.
SourceNiek Blankers' retrospective describes PCBWay producing boards after the original supplier could not deliver.
SourceListed in the SHA2017 team section.
SourceListed in the SHA2017 team section.
SourceListed in the SHA2017 team section.
SourceListed in the SHA2017 team section.
SourceListed in the SHA2017 team section.
SourceListed in the SHA2017 team section.
SourceListed in the SHA2017 team section.
SourceListed in the SHA2017 team section.
SourceListed in the SHA2017 team section.
SourceSHA2017 helped establish Badge.Team as a durable European badge platform and volunteer network, bridging event identity, MicroPython-style apps, web installation, and post-camp reuse.
Public docs describe ESP32-WROVER, a 296x128 e-paper display, six RGB LEDs, MPR121 touch controller, joystick, USB-C, LiPo charger, MicroSD, 6-pin SAO header, IRDA receive/transmit, audio output, and CC BY-SA 4.0 hardware design files.
Badge.Team documentation covers drivers, WebUSB installer paths, Hatchery app installation, appfs, OTA updates, a menu/launcher, REST-style APIs, IRC/game/social apps, and a firmware/software repository trail.
The team credits list reads like a who's who of later Dutch badge work, including people who shaped MCH2022 and the wider Badge.Team ecosystem. Production retrospectives remember hundreds of PCB revisions, a PCBWay scramble after a first supplier failed, and tens of thousands of LEDs placed by hand.
Lifecycle
SHA2017 used the Badge.Team Hatchery path for discoverable badge applications, and the current Hatchery index still exposes SHA2017-compatible project records.
SourceThe SHA2017 docs and Hack42 WebUSB installer preserve the browser-based badge installation path used by the Badge.Team platform.
SourceBadge.Team's ESP32 platform firmware repository anchors SHA2017 in the reusable firmware lineage later Badge.Team records build on.
SourceThe hardware docs record a 6-pin SAO connector and IR receive/transmit hardware, giving SHA2017 both badge-add-on and badge-to-badge interaction surfaces.
SourceSprite_tm documented adapting a Gameboy emulator to the SHA2017 badge's e-paper display, preserving a concrete example of post-camp app hacking under unusual display constraints.
SourceSHA2017 sits in the early Badge.Team lineage where apps, contributed code, documentation, and post-event platform work became central.
SourceThe event wiki links appfs as the way applications were stored and loaded on the badge, making installable apps part of the platform instead of just firmware demos.
SourceOperational history
SHA2017 is remembered as successful, but its production story still shows the logistics risk behind ambitious camp badges.
The badge's visual polish came with substantial volunteer assembly effort that belongs in the compendium's production history.
The page should keep multiple source links instead of pretending there is one complete canonical source.
This is useful lore for app-store records: the badge could run surprising software, but display technology shaped what was practical.
The badge facts and visual provenance are now aligned: the image record preserves source URL, CC BY-SA 4.0 license, attribution, and cutout-processing notes.
The install workflow was accessible for many users, but the compendium records it as an ecosystem dependency rather than firmware alone.