Electronic Cats
The README says the badge was designed by Electronic Cats and preserves the source, releases, hardware-license statement, and selected community-badge raster.
SourceBSides CDMX 2025 · Mexico · 2025
PY32F030 OLED and NeoPixel badge with role variants and Metro add-on
BSides CDMX 2025's Electronic Cats repository documents a Security BSides CDMX badge built around a Puya PY32F030F28U6TR, NeoPixels, OLED display, two AAA battery holder, Shitty Addon connector, role-specific KiCad hardware variants, a Metro add-on, public firmware, release HEX files, and BOM assets.
People
The README says the badge was designed by Electronic Cats and preserves the source, releases, hardware-license statement, and selected community-badge raster.
SourceOfficial publisher of the event page and schedule context used for the Mexico City Security BSides edition.
SourceIt deepens the Mexico City coverage with a Security BSides badge whose official event page, open hardware repository, firmware tree, release binaries, BOMs, and licensed upstream community-badge render make both the artifact and its public provenance unusually strong for a regional LATAM BSides event.
The README lists Puya PY32F030F28U6TR, NeoPixels, OLED display, two AAA battery holder, and Shitty Addon connector. The hardware tree preserves Community, Guest, Speaker, Sponsor, and Staff KiCad badge variants, board PNGs, silkscreen/edge-cut SVGs, footprints, STEP models, BOM release assets, and a separate Metro add-on with artwork and BOM release.
The badge ships with pre-installed firmware according to the README, with release-section binaries for reprogramming. The firmware tree is based on a Puya PY32F0 template with GNU Arm Embedded Toolchain, J-Link or PyOCD programming, Makefile build/flash flow, CMSIS/HAL/LL libraries, and release HEX assets including `app.hex` and `Metro.hex`.
The official BSides CDMX page frames the fifth edition as a free community-driven Mexico City Security BSides event on July 18, 2025 at Ex Fabrica MX. The repository gratitude section asks attendees to tag Electronic Cats and BSides CDMX with their badge, tying the hardware to the public event identity.
Lifecycle
The hardware tree and release assets preserve a Metro add-on with silkscreen/edge SVGs, source artwork, `Metro.hex`, and a Metro add-on BOM CSV.
SourceThe README lists the Puya PY32F030F28U6TR microcontroller as the badge core, and the firmware README documents the PY32F0 MCU family and Cortex-M0+ build path.
SourcePublic documentation lists NeoPixels, OLED display, two AAA battery holder, and Shitty Addon connector as badge technology.
SourceThe hardware tree preserves separate KiCad directories and board rasters for Community, Guest, Speaker, Sponsor, and Staff role variants.
SourceThe releases page preserves `app.hex`, `Metro.hex`, and BOM CSVs for Community, Guest, Speaker, Staff, and Metro add-on outputs.
SourceThe firmware README documents GNU Arm Embedded Toolchain setup, J-Link or PyOCD programming, Makefile configuration, and make/flash commands for PY32F0 targets.
SourceOperational history
The record has a rights-cleared official upstream raster with source URL, license basis, attribution, local source preservation, and optimized WebP delivery while avoiding generated, placeholder, screenshot, social-media, or conference-gallery imagery.
The catalogue can cite and publish the selected hardware render while keeping firmware/source licensing and event trademarks separate from the hardware-documentation reuse basis.
Software and production claims stay tied to README, releases, firmware README, visible hardware tree, and named release assets rather than treating the repository as a fully inventoried manufacturing archive.