Reverse engineer a console kernel with Claude Code so new controllers work on old hardware

What you end up with

Three habits carry over to any hardware job: give the agent eyes on the target (a status block and log it can read remotely), give it the tools to run build, upload and read logs alone, and turn every hard-won rule into a check that fails the build.

What you get

• A plain-language summary of the workflow
• A fill-in prompt template
• What to watch out for
• A link to the original source

Who it is for

Builders who already use AI agents and want a proven workflow they can copy into their own project.

Works with

Solid chips: the agent is named in this listing's own tools list. Dashed chip: Plain Markdown, so it also pastes into other agents such as Grok Bot, Hermes, OpenClaw or Muse. We list those as compatible by format only, not as tested.

Tools needed

Cost to run: Free with the agent plan you already use.
Time to result: One working session

How it works

1. Give the agent a decompiler MCP server, the cross-compiler and a way t

   Give the agent a decompiler MCP server, the cross-compiler and a way to upload builds

   Expected: Done before you move to the next step.

2. Have your code write a status block and a log ring the agent can read

   Have your code write a status block and a log ring the agent can read after every test

   Expected: Done before you move to the next step.

3. Port from an open reference driver instead of guessing the protocol

   Port from an open reference driver instead of guessing the protocol

   Expected: Done before you move to the next step.

4. Every rule learned the hard way becomes a build-script check

   Every rule learned the hard way becomes a build-script check

   Expected: Done before you move to the next step.

5. You stay the hands: plug, pair, reboot and report what you see

   You stay the hands: plug, pair, reboot and report what you see

   Expected: Done before you move to the next step.

Sample prompt from the pack

Apply this workflow to [your project]:
1. Give the agent a decompiler MCP server, the cross-compiler and a way to upload builds
2. Have your code write a status block and a log ring the agent can read after every test
3. Port from an open reference driver instead of guessing the protocol
4. Every rule learned the hard way becomes a build-script check
5. You stay the hands: plug, pair, reboot and report what you see
Stop and ask me before anything irreversible: deploys, payments, sends or deletes.

Free preview of the file

# Reverse engineer a console kernel with Claude Code so new controllers work on old hardware

PaperChase agent use case (free feed entry), version 1.0. Source: [u/Hot-Ad2974 on r/ClaudeAI (GitHub: Jacckii)](https://www.reddit.com/r/ClaudeAI/comments/1xgtghe/claude_code_reverseengineered_the_xbox_360_kernel/), 2026-10-27.

## What they did

The builder wanted Xbox Series X|S controllers on an Xbox 360 through Microsoft's wireless adapter for Windows. Claude Code mapped the 360 kernel's USB stack in Ghidra over MCP, ported the adapter firmware load, radio setup, pairing handshake and controller protocol from the open-source xone Linux driver into C, and wrapped it in a plugin that loads at boot. Bugs it hit and fixed include register saves that differ between 32-bit and 64-bit code (solved with small assembly thunks), no floating point allowed in deferred calls (solved with soft-float plus a build check that fails on any FP instruction), a Guide button deadlock (moved system calls to their own thread) and an adapter that was ignored if plugged in before boot (it found the kernel's rescan routine). The driver writes a status block and a log ring into memory, and Claude read them over the network after every test.

## Worth knowing

Three habits carry over to any hardware job: give the agent eyes on the target (a status block and log it can read remotely), give it the tools to run build, upload and read logs alone, and turn every hard-won rule into a check that fails the build. The human did the physical work: plugging, pairing, rebooting and describing the screen. It needs a modded console on a specific kernel and the project is early; the code is GPL-3.0.

Worth knowing

• Three habits carry over to any hardware job: give the agent eyes on the target (a status block and log it can read remotely), give it the tools to run build, upload and read logs alone, and turn every hard-won rule into a check that fails the build. The human did the physical work: plugging, pairing, rebooting and describing the screen. It needs a modded console on a specific kernel and the project is early; the code is GPL-3.0.
• Figures are as reported by the original author and were not re-measured by us.

Details

Version 1.0 · Updated Oct 27, 2026 · Markdown version of this page
License: Personal and commercial use. Credit the original source when you share the workflow. Download terms

Related

Agent use case packFree

Build a playable browser game prototype in one evening with an AI agent

by PaperChaseWebb

A step by step pack for going from a one-paragraph idea to a playable HTML5 game in a single file, then posting it on itch.io for friends to try.

Works withClaude CodeCodexCursorPlain .md

Games · Beginner · 10 min setup

Agent use case pack$19

Launch an AI-built browser game: mobile, licensing, leaderboards and the itch.io page

by PaperChaseWebb

A launch plan for a browser game built with an AI agent: performance budget, device tests, audio and touch fixes, an asset license ledger, leaderboard hardening and the itch.io page.

Works withClaude CodeCursorPlain .md

Games · Intermediate · 30 min setup