khian
Filesystem README credits khian for Asteroids.
SourceGreyCTF Summit 2025 · Singapore · 2025
Singapore RP2350 and ECP5 FPGA challenge badge
NUS Greyhats' public GreyBadge archive identifies the 2025 GreyCTF badge as GreyMecha/Army, with RP2350-side CircuitPython firmware, KiCad hardware files, an ECP5U_25 FPGA schematic, GC9A01 SPI display, Li-ion power-path circuitry, summit UF2/filesystem releases, and named challenge apps.
People
Filesystem README credits khian for Asteroids.
SourceFilesystem README credits sayomaki for Bad Apple and also lists sayomaki among people who helped with technical advice.
SourceFilesystem README credits Fieash for the Bricked Up challenge.
SourceFilesystem README thanks caprinux for initiating the GreyHats badge effort.
SourceFilesystem README credits itsme-zeix for PCB work around RP2350, LiPo, and power, plus Leaky Pin and firmware work.
SourceRepository structure and filesystem README credit shuqing for badge artwork and animations.
SourceOfficial summit publisher and GitHub organization hosting the public GreyBadge repository.
SourceFilesystem README credits Hackin7 for main badge system design, concept, artwork and animations, PCB power/FPGA/connectivity work, and firmware.
SourceFilesystem README credits Codekrodile for mirrortune.
SourceFilesystem README credits sunshinefactory for zip file work.
SourceIt adds a current Singapore Greyhats lineage after X-CTF, showing a more ambitious local badge with an RP2350 application processor, FPGA challenge surface, public production files, and summit/finals release trail while keeping image and license limits explicit.
The repository README points to hardware artwork, KiCad files, JLCPCB production files, a Prototype 3 order release, and a hardware ordering guide. The schematic trail includes RP2350 sheets, an ECP5U_25 CABGA256 FPGA sheet, a GC9A01 IPS SPI display, USB-friendly Li-ion battery charger and power-path management, D-pad, buzzer, PMOD expansion, FPGA programming, and RP2350-FPGA interlink notes.
The README setup flow flashes `circuitpython_frozen_leaky.uf2`, mounts the badge as CIRCUITPYTHON, and copies the `firmware/rp2350/filesystem` contents. The filesystem README says the RP-side firmware is based on CircuitPython and includes GreyCTF finals challenges such as Hornet Revenge, Leaky Pin, Bricked Up, Shooting Flags, Secure Memory, and CatCore, while the ECP5 directory keeps FPGA projects and tests with yosys, nextpnr-ecp5, fpga-trellis, and openFPGALoader tooling notes.
The badge used the GreyMecha/Army theme and a mix of finals and summit release assets. The firmware README credits Hackin7 for concept, artwork, PCB, and firmware; itsme-zeix for RP2350, LiPo, power, Leaky Pin, and firmware work; shuqing for artwork and animations; and additional contributors for challenges, apps, and initiating the GreyHats badge effort.
Lifecycle
The hardware tree includes an ECP5U_25 CABGA256 schematic and the firmware tree includes ECP5 projects, tests, and a UART coprocessor example with open FPGA tooling notes.
SourceThe repository setup flow flashes a CircuitPython UF2, then copies the RP2350 filesystem to CIRCUITPYTHON for the badge runtime.
SourceThe filesystem README names the Grey finals challenges as Hornet Revenge, Leaky Pin, Bricked Up, Shooting Flags, Secure Memory, and CatCore.
SourceThe main schematic includes a GC9A01 IPS SPI display, while the firmware README describes user-customizable 240x240 JPG/GIF badge images.
SourceThe releases page preserves Prototype 3 BOM/CPL/Gerber/schematic assets plus summit_v1 and summit_v2 firmware and filesystem release files.
SourceOperational history
The event and badge are included, but distribution and admission-credential claims remain conservative.
The Singapore record remains source-backed and image-free rather than copying repository artwork, social media, slides, screenshots, or generated badge art.
Repository files are cited as public evidence, but local reuse is limited: no repository images, artwork, hardware files, firmware, or slides are copied into the catalogue as licensed assets.
Software claims stay limited to the recovered repository, filesystem README, and release assets.