← All use cases

Use case P28 · Human

Conference attendee uses Gemini to make his badge play Game Boy Color games

Steve Francia (spf13) ·

The short version

What they did

Steve Francia teamed up with Gemini to write software that lets his programmable conference badge behave like a Game Boy and Game Boy Color. His account describes fixing crashes, memory handling and drawing errors before running games on the badge; his repository names the model as Gemini 4 Argon. He uses the badge’s built-in touch controls and supplies his own legally dumped game files. The code does not distribute copyrighted game files, and this case does not endorse downloading unauthorized copies.

Result (as claimed)

“Now I have a Game Boy Color hanging from my neck, running Link’s Awakening DX and Pokémon Crystal at 1:1.”

Prompt

I want to make my own [programmable badge model] run a Game Boy emulator. Here are the hardware documents and current firmware: [attach files or paste documentation]. My test game is [homebrew test ROM].

1. Check the screen, controls, memory and processor limits and explain what seems feasible.
2. Plan a small first version, starting with a screen test and then booting the test game.
3. Help write and test one part at a time, using the badge’s controls.

Give me short setup instructions and an expected result for each test. Don’t promise full speed or Game Boy Color support before testing. Ask before changing firmware or clock settings, and explain how to restore the badge. Don’t fetch commercial game files.

Do it yourself

These steps are my suggested way in, not Steve’s setup.

What you need

  • A programmable badge or small board with a screen and buttons, plus its official documents.
  • A coding assistant that can work with your files: Gemini CLI, Claude Code or Codex.
  • A free homebrew test ROM, and game files you dumped yourself from cartridges you own.

Start simple

  1. Give the assistant the hardware documents and ask, with the Prompt above, what the board can and can’t do.
  2. Ask for a tiny first program that draws a test pattern on the screen. Flash it and confirm it works.
  3. Ask for a plan that starts with an existing open-source Game Boy emulator, not one written from scratch.
  4. Get one homebrew test ROM to boot, even slowly.
  5. Commit each working step to git so you can roll back.

Take it further

  • Ask the assistant to measure frame time and find the slowest parts, then speed up one at a time.
  • Map the badge’s buttons or touch areas to the Game Boy controls.
  • Add Game Boy Color support once the original Game Boy runs well.

Check your work

  • Compare your emulator against known test ROMs that report pass or fail.
  • If a fix makes a crash go away but you don’t know why, ask the assistant to explain it before you keep it.
  • Legal and hardware: use only ROMs you made from cartridges you own, and don’t overclock or rewrite firmware without a way to restore it.

Source checked. The link, author, date and quote were confirmed against the source. The result itself has not been reproduced. Prompt adapted for this library, inspired by the case. Business size: Individual. Results are quoted as the source claimed them and never improved. Spot an error or a broken link? Email charlie@cbarmorecpa.com.

More in Games and game nights

New cases go out every Saturday in Inside AI.