Country dossier
Mexico
Worldwide badge coverage for Mexico, grouped into seeded badges, event editions, add-ons, operational issues, resources, and evidence sources.
6 badge(s) · 6 event(s) · 3 series · 2022-2025
Back to countries
BugCON · Mexico City (CDMX) · 2022 · 1 badge(s)
The BugCON 2022 CDMX edition whose Electronic Cats badge repository and README document an RP2040 electronic badge with USB serial use, LEDs, microphone, buzzer or speaker, EdgeImpulse audio-classification context, Arduino Mbed programming notes, KiCad hardware files, and firmware examples.
BugCON · Mexico · 2023 · 1 badge(s)
The BugCON 2023 edition whose Electronic Cats badge repository and README document a resistance-themed official badge, ESP32S3 or RP2040 feature statement, UART, Bluetooth and Wi-Fi on ESP32S3, AA battery support, GPL firmware, CERN-OHL hardware files, KiCad hardware trees, and Arduino developer workflow.
BugCON · Mexico City · 2024 · 1 badge(s)
The Mexico City BugCON security conference edition whose official Electronic Cats badge repository documents community and VIP ESP32-C6 hardware variants, firmware paths, and CERN-OHL hardware release.
BSides CDMX · Ex Fabrica MX, Mexico City · 2025 · 1 badge(s)
The July 18, 2025 Mexico City Security BSides edition whose official event page documents the Ex Fabrica MX venue and whose Electronic Cats repository preserves a PY32F030 badge, role variants, Metro add-on, firmware, BOMs, and hardware renders.
BugCON · Fronton Bucareli, Mexico City · 2025 · 1 badge(s)
The November 20-21, 2025 Mexico City BugCON edition whose official event pages and Electronic Cats repository document a Linux-capable RV1106 badge with open hardware source, add-on board, and release-image flashing path.
HackGDL · Jardin Americana, Guadalajara, Jalisco · 2025 · 1 badge(s)
The March 1, 2025 Guadalajara HackGDL edition whose official pages and Electronic Cats repository document a HackGDL event badge based on the ESP32-S3 Minino platform.
badge add-on
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.
badge add-on
The repository preserves a separate Add_On_Bugcon_2025 tree with PY32F002AA15M footprint/source material, KiCad files, decorative artwork, and firmware/libraries.
badge applications
The repository and store page say the badge ships with BLE apps, Wi-Fi apps, and a digital-pet app as ready-to-use examples for the event.
badge controller
The README and store page document HackGDL 2025 as an ESP32-S3 badge based on the Minino platform.
badge controller
The README identifies the BugCON 2023 badge as an ESP32S3 or RP2040 design with UART, ESP32S3 Bluetooth/Wi-Fi, and AA battery support.
badge controller
The README lists the Puya PY32F030F28U6TR microcontroller as the badge core, and the firmware README documents the PY32F0 MCU family and Cortex-M0+ build path.
badge controller
The README lists RP2040, USB, LEDs, microphone, buzzer or speaker, and EdgeImpulse-backed machine-learning context for the BugCON 2022 badge.
badge controller
The README documents an RV1106G3 platform with ARM Cortex-A7, RISC-V MCU, NPU, ISP, and Linux operating-system support.
badge hardware
Public documentation lists 18650 battery support, buck conversion, WS2812E NeoPixels, and Python spidev examples for LED control from Linux.
badge interface
Public documentation lists NeoPixels, OLED display, two AAA battery holder, and Shitty Addon connector as badge technology.
badge interface
Public badge documentation lists an integrated OLED screen, four physical buttons, three NeoPixels, buzzer, three-AAA battery holder, USB-C, and Shitty Addon connector.
badge interfaces
The README documents broad RV1106 interfaces including GPIO, camera/sensor MIPI CSI, UART, SPI, I2C, USB hub support, and GPIO-based Ethernet path.
badge variant
The community variant used ESP32-C6 hardware with USB, two AA batteries, LEDs, and a 128x32 0.91-inch I2C SSD1306 OLED.
badge variant
The VIP variant used ESP32-C6 hardware with USB, two AA batteries, LEDs, and a 1.28-inch GC9A01 circular TFT LCD.
badge variants
The hardware tree preserves separate KiCad directories and board rasters for Community, Guest, Speaker, Sponsor, and Staff role variants.
developer workflow
The README points Arduino developers to the project wiki and links the Arduino Mbed RP2040 core as the programming route for the badge.
developer workflow
The firmware developer guide documents required Arduino libraries, RP2040 and ESP32-S3 pin edits, production pin changes, and compile/flash commands for both board targets.
firmware and production lifecycle
The releases page preserves `app.hex`, `Metro.hex`, and BOM CSVs for Community, Guest, Speaker, Staff, and Metro add-on outputs.
firmware development
The badge README points developers to the Minino firmware guide for ESP-IDF setup, modular app structure, compile, flash, and monitor workflows.
firmware examples
Separate firmware directories preserve an SSD1306 OLED DinoGame sketch and a BLE advertising Spoof sketch modified for ESP32-S3.
firmware lifecycle
The firmware tree preserves an AudioWAV sketch with USB mass-storage and PWM audio behavior plus an EdgeImpulse note linking audio-classification tutorial material.
firmware lifecycle
The Badge firmware tree preserves menu, terminal, Wi-Fi server, generated web assets, AirTag, UART, hardware-pin, and NeoPixel control source files.
firmware lifecycle
The firmware tree preserves separate Community and VIP directories, with Community firmware build guidance and VIP development framed around CircuitPython and Thonny.
firmware lifecycle
The README and releases document Rockchip/Luckfox upgrade_tool flashing for Bugcon-Badge-2025 image tarballs and the v1.0/v1.1 release path.
firmware workflow
The repository startup path tells attendees to connect the badge over USB and open the serial port at 115200 baud to see badge text.
firmware workflow
The README tells attendees to connect over USB, select the correct serial port at 115200 baud, observe terminal startup, and type `help` for additional commands.
firmware workflow
The README documents bootloader mode, ESP Tool web flashing at address 0x0, and an esptool.py console command for `HackGDL_2025.bin` on ESP32-S3.
firmware workflow
The firmware README documents GNU Arm Embedded Toolchain setup, J-Link or PyOCD programming, Makefile configuration, and make/flash commands for PY32F0 targets.
hardware archive
The ESP32-S3 schematic backs ESP32-S3-WROOM, USB-C, SSD1306 OLED, WS2812B Mini LEDs, buttons, slide switch, I2C, and battery-rail claims; the repository's SAMD11-named tree contains an RP2040 schematic with USB-C, W25Q flash, battery, OLED, WS2812B Mini LEDs, and switches.
hardware archive
The hardware tree preserves KiCad schematic and board files whose schematic names RP2040, SPH0641LM4H microphone, PAM8302AAD amplifier, W25Q16JV flash, MCP1700 regulator, battery, buzzer, LEDs, micro-USB, BOOT, and RESET elements.
software workflow
The README documents 3.3 V TTL UART2 debug serial at 115200 baud, root credentials, terminal access, Python 3.11.6, and a simple Python hello-world path.
event and firmware inventory caveat · repository metadata and decoded source files · needs archive/event-page recovery
Event and software claims stay bounded to the repository, README, developer guide, visible source tree, and decoded representative files instead of inventing event logistics or treating the repository as a fully inventoried production archive.
event-context depth caveat · repository metadata and README · needs archive/event-page recovery
Event claims stay bounded to BugCON 2022 CDMX and the public badge repository instead of inventing dates, venue, ticket tier, or distribution scope.
firmware-release scope · repository documentation · needs deeper artifact inventory
Software claims stay tied to the README, release path, and Minino documentation rather than treating the repository as a fully inventoried final production archive.
firmware-source caveat · repository tree and decoded sketches · needs deeper firmware inventory
Software claims stay tied to the README instructions, visible firmware tree, and decoded example sketches rather than treating the repository as a complete final production firmware archive.
hardware variant evidence caveat · README and repository tree · documented with caution
Hardware claims stay tied to visible source files rather than inferring which variant shipped, how many boards were produced, or whether every tree name matches the final production board identity.
image provenance upgrade · repository README license statement and exact raster source · licensed official upstream raster render applied
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.
license scope caveat · GitHub API, repository README, and license files · documented
The catalogue can cite GPL software and CERN-OHL hardware documentation while avoiding assumptions that firmware, photos, logos, screenshots, KiCad renders, trademarks, or other media all share one reuse scope.
license scope caveat · primary repository · documented
The compendium can cite the open-hardware release while avoiding assumptions that all firmware, screenshots, photos, or repository media share the same reuse terms.
license scope caveat · GitHub API, repository tree, and README · documented with caution
The catalogue can cite the open-hardware claim and public source while avoiding assumptions that firmware, SDK material, readme images, KiCad renders, logos, or event graphics are reusable publication assets.
license scope caveat · repository README and license files · documented
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.
license scope caveat · repository README and store page · documented with caution
The catalogue can cite the source and hardware release while keeping image publication and trademark reuse separate from code and hardware licensing.
license-file caveat · GitHub API and repository README · documented with caution
The catalogue can cite the README's open-hardware claim and public source while avoiding assumptions that firmware, photos, readme images, logos, KiCad renders, or other repository media are reusable publication assets.
missing rights-cleared image · local project policy · needs licensed original replacement
The entry remains source-backed and image-free rather than copying event logos, README images, GitHub assets, KiCad screenshots, social photos, or generated imagery without complete provenance.
missing rights-cleared image · local project policy · needs licensed original replacement
The entry remains source-backed and image-free rather than copying logos, screenshots, GitHub assets, KiCad outputs, event graphics, social photos, or generated imagery without complete provenance.
missing rights-cleared image · local project policy · needs licensed original replacement
The entry remains source-backed and image-free rather than copying repository or web imagery without complete provenance.
missing rights-cleared image · local project policy · needs licensed original replacement
The entry remains source-backed and image-free rather than copying diagrams, screenshots, event artwork, GitHub assets, logos, or generated imagery without complete provenance.
missing rights-cleared image · local project policy · needs licensed original replacement
The entry remains source-backed and image-free rather than copying product photos, repository screenshots, GitHub attachments, logos, or generated imagery without complete provenance.
release and source inventory · repository documentation · needs deeper artifact inventory
Software and production claims stay tied to README, release names, public hardware trees, and the named SDK branch rather than treating the repository as a fully inventoried production archive.
source inventory caveat · repository tree and releases · needs deeper artifact inventory
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.