BugCON

BugCON 2025

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.

Fronton Bucareli, Mexico City · Mexico · 2025

BugCON 2025 Linux Badge

BugCON 2025's Electronic Cats badge repository documents an open-hardware RV1106G3 Linux badge with ARM Cortex-A7, RISC-V MCU, NPU, ISP, GPIO, MIPI CSI, UART, SPI, I2C, USB hub, Ethernet path, WS2812E NeoPixels, 18650 battery support, Python scripting, and a PY32F002 add-on board.

Lifecycle

Add-ons & Upgrades

BugCON 2025 Linux Badge archived source

badge add-on

PY32F002 add-on board

The repository preserves a separate Add_On_Bugcon_2025 tree with PY32F002AA15M footprint/source material, KiCad files, decorative artwork, and firmware/libraries.

Compatibility: BugCON 2025 Linux Badge

BugCON 2025 Linux Badge source-backed

badge controller

RV1106G3 Linux badge core

The README documents an RV1106G3 platform with ARM Cortex-A7, RISC-V MCU, NPU, ISP, and Linux operating-system support.

Compatibility: BugCON 2025 Linux Badge

Operational history

Issues & Camp Impact

license scope caveat · GitHub API, repository tree, and README · documented with caution

GitHub reports no detected top-level license for `ElectronicCats/badge-bugcon-2025`, and the README says to consult license files without exposing a simple whole-repository license for hardware, firmware, photos, diagrams, or artwork.

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.

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

No BugCON 2025 badge image is published because the repository readme images, diagrams, KiCad/svg2shenzhen rasters, event-site graphics, and sponsor or ticketing artwork have not been paired with complete reusable image rights, attribution, source URL, and processing provenance for catalogue publication.

The entry remains source-backed and image-free rather than copying diagrams, screenshots, event artwork, GitHub assets, logos, or generated imagery without complete provenance.

release and source inventory · repository documentation · needs deeper artifact inventory

The README and releases document v1.0/v1.1 image tarballs, add-on firmware hex, BOM asset names, and the Luckfox SDK branch, but this pass did not audit every large release image, generated SDK artifact, dependency license, or manufacturing output.

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.

Resources

Sources