OGX-Mini 2026

Support development — If this firmware helps you, consider donating on Ko-fi. Donations fund hardware I can test on (see Support policy).

---

Firmware for the RP2040/RP2350, capable of emulating gamepads for several game consoles. The tree builds for many board targets from the original project (Adafruit Feather USB Host, Pi Pico / Pico 2 / Pico W / Pico 2 W, Waveshare RP2040-Zero / RP2350-USB-A / RP2350-Zero, Seeed XIAO RP2040, RP2354, Pico/ESP32 hybrid, 4-Channel RP2040-Zero, and others). Maintainer testing and issue support are limited to the boards listed in Support policy.

Support policy

Development focuses on first-party controllers that can be tested on hardware I own.

Controllers

Going forward, maintainer work is limited to first-party pads (Microsoft, Sony, Nintendo, and other first-party models listed under Supported devices), unless:

• a donation is provided specifically to purchase that controller for testing, or
• there is an existing agreement to ship hardware / boards that I already said I would support.

Unsupported third-party controllers will not be diagnosed by guesswork without that hardware. Please do not open issues asking for speculative fixes for pads I do not have.

Boards

I can only test and maintain these boards:

• Adafruit Feather USB Host
• Raspberry Pi Pico W
• Raspberry Pi Pico 2 W
• Waveshare RP2350-USB-A

I cannot purchase and validate every board variant this repo builds for. For other boards (including RP2040-Zero, RP2350-Zero, XIAO, RP2354, ESP32 hybrids, 4-channel setups, and clones): fork or clone this repository, develop and test your patches on your hardware, and open a pull request so fixes can be merged here for everyone. Maintainer-led work on an additional board still requires a GitHub issue plus a donation earmarked for that board (or shipped hardware under a prior agreement).

Unofficial clones, random AliExpress spin-offs, or homebrew PCBs that only “look like” a supported board are not guaranteed to work and are out of scope for maintainer support (you may still flash and experiment at your own risk).

How to get help

1. Confirm your controller and board are in scope above.
2. Open a GitHub issue only after reading Support issue requirements and including every required field. Incomplete reports may be closed or delayed.
3. Out-of-scope boards: clone → fix → pull request. Out-of-scope controllers: arrange donation or shipment first — otherwise the request will be closed as out of scope.

Visit the web app here to change your mappings and deadzone settings. To pair the OGX-Mini with the web app via USB, plug your controller in, then connect it to your PC, hold Start + Left Bumper + Right Bumper to enter web app mode. Click "Connect via USB" in the web app and select the OGX-Mini. You can also pair via Bluetooth, no extra steps are needed in that case.

Join the discord here!

Follow on TikTok!

Subscribe on YouTube!

Documentation

Category	Where to look
Support & contributing	Support issue requirements, Building from source, Firmware architecture, Adding supported controllers, Support policy
Feature guides	SteamOS / Bazzite, PS3/PS4 motion, Wii mode, GPIO pinouts
Reference	Wired controllers, Controller mappings
Technical notes	Firmware architecture, Planned additions, IMPROVEMENTS.md, CHANGELOG.md
Research / planning	docs/ (input research, retro wiring, other projects’ modes)

Full index (all firmware docs): Firmware/RP2040/docs/README.md

Supported platforms

• Original Xbox
• Playstation 3
• Nintendo Switch 1 & 2 (docked) — Switch Pro Controller emulation over USB
• XInput (Xbox 360, UsbdSecPatch no longer required)
• Playstation Classic
• DInput
• SteamOS / Bazzite — Linux desktop / Steam Deck (desktop mode): DualSense USB gamepad + touchpad → HID mouse (see SteamOS / Bazzite output mode)
• PS3 / PS4 motion — Sixaxis / accelerometer passthrough from DS4, DualSense, Switch Pro, and Wii Remote (see PS3 / PS4 motion controls)
• Wii U (GameCube Adapter) — only output mode tested and supported for multi-controller builds (MAX_GAMEPADS > 1; see Multi-controller builds)
• Wii (Wiimote) — Pico W / Pico 2 W only; build with -DOGXM_FIXED_DRIVER=WII. See Wii Mode Guide.
• PlayStation 1 & 2 — GPIO output to a console controller cable. Intended use: Pico W or Pico 2 W + Bluetooth pad, wired to a PS1/PS2 controller cable plugged into the console (wireless adapter). USB-A / wired USB host input on those boards does not work in these builds and is out of scope. See GPIO pinouts.
• Dreamcast — GPIO output over Maple Bus to a console controller cable. Intended use: Pico W or Pico 2 W + Bluetooth pad, wired to a Dreamcast controller cable. USB-A / wired USB host input does not work in these builds and is out of scope.
• GameCube / Wii (GameCube ports) — GPIO output over single-wire JoyBus to a console controller cable. Intended use: Pico W or Pico 2 W + Bluetooth pad, wired to a GameCube controller cable. USB-A / wired USB host input does not work in these builds and is out of scope. Build-only (no combo): use -DOGXM_FIXED_DRIVER=GAMECUBE; see below.
• Nintendo 64 — GPIO output to a console controller cable. Intended use: Pico W or Pico 2 W + Bluetooth pad, wired to an N64 controller cable plugged into the console (wireless adapter). USB-A / wired USB host input does not work in these builds and is out of scope. Build-only (no combo): use -DOGXM_FIXED_DRIVER=N64; see below.

RP2040 output modes: USB device: XInput (Xbox 360 + XSM3), DInput, PS3, PS4 (DualShock 4 USB), STEAM (SteamOS / Bazzite — DualSense + touchpad mouse), Switch Pro (Nintendo Switch Pro Controller emulation), Wii U, Wii (Wiimote, build-option only), Xbox OG (Gamepad / Steel Battalion / XRemote), PS Classic, Web App. GPIO (no USB device): PS1/PS2, Dreamcast, GameCube, N64 — intended for Pico W / Pico 2 W as a wireless bridge (Bluetooth in → GPIO out on a hacked controller cable). USB-A / wired USB host input on those boards is unsupported for these modes. Wii, GameCube, and N64 are not in the combo list — use a dedicated build for those modes (see below).

Changing platforms

By default the OGX-Mini will emulate an OG Xbox controller, you must hold a button combo for 3 seconds to change which platform you want to play on. Your chosen mode will persist after powering off the device.

Start = Plus (Switch) = Options (Dualsense/DS4)

• XInput (Xbox 360)
  • Start + Dpad Up
• Original Xbox
  • Start + Dpad Right
• Original Xbox Steel Battalion
  • Start + Dpad Right + Right Bumper
• Original Xbox DVD Remote
  • Start + Dpad Right + Left Bumper
• Switch (Pro Controller emulation)
  • Start + Dpad Down
• PlayStation 3
  • Start + Dpad Left
• PlayStation 4 (DualShock 4 USB)
  • Start + Left Bumper + D-pad Left
• SteamOS / Bazzite (DualSense USB + touchpad mouse)
  • Start + Left Bumper + D-pad Up
• PlayStation Classic
  • Start + A (Cross for PlayStation and B for Switch gamepads)
• PlayStation 1 / PlayStation 2 (GPIO output)
  • Start + B — Pico W / Pico 2 W + controller cable; Bluetooth input only (USB-A host out of scope)
• Dreamcast (GPIO output)
  • Start + Y — Pico W / Pico 2 W + controller cable; Bluetooth input only (USB-A host out of scope)
• Wii U (GameCube Adapter) - Start + Left Bumper + D-Pad Down
• Web Application Mode
  • Start + Left Bumper + Right Bumper

Wii, GameCube, and N64 are not selectable by combo. Use a dedicated build for those modes:

• Wii (Wiimote): -DOGXM_FIXED_DRIVER=WII. See Wii Mode Guide.
• GameCube (GPIO): -DOGXM_FIXED_DRIVER=GAMECUBE on Pico W or Pico 2 W. Wire the Pico to a GameCube controller cable and plug that into the console; pair a Bluetooth pad for wireless play. USB-A / wired USB host input does not work in these builds and is out of scope. Example:
  cmake -DOGXM_BOARD=PI_PICO2W -DCMAKE_BUILD_TYPE=Debug -DOGXM_FIXED_DRIVER=GAMECUBE .. then ninja. Flash OGX-Mini-*-GAMECUBE.uf2. Use PI_PICOW for Pico W.
• N64 (GPIO): -DOGXM_FIXED_DRIVER=N64 on Pico W or Pico 2 W. Wire the Pico to an N64 controller cable and plug that into the console; pair a Bluetooth pad for wireless play. USB-A / wired USB host input does not work in these builds and is out of scope. Example:
  cmake -DOGXM_BOARD=PI_PICO2W -DCMAKE_BUILD_TYPE=Debug -DOGXM_FIXED_DRIVER=N64 .. then ninja. Flash OGX-Mini-*-N64.uf2. Use PI_PICOW for Pico W.

PS1/PS2 and Dreamcast (GPIO) use the same intended setup: Pico W / Pico 2 W + Bluetooth input + wires to the matching controller cable into the console. Do not expect the board’s USB-A / PIO USB host port to work as controller input in these retro GPIO builds.

GPIO mode input on Pico W / Pico 2 W is Bluetooth only for these modes. No combo switching in fixed Wii / GameCube / N64 builds.

After a new mode is stored, the RP2040 will reset itself so you don't need to unplug it.

Disconnecting Controllers

For most controllers pressing and holding Start+Select (+/-, etc) for the controller will disconnect it and restart pairing mode. For the OUYA controller there is no Start+Select, the disconnection combo has been set to L3+R3.

Supported devices

Maintainer-supported input is first-party controllers (and paths listed below that are regularly tested). Other devices may still work via existing Bluepad32/USB host code; that does not mean new bugs for them will be investigated without hardware or a donation — see Support policy.

Wired controllers (USB input)

See Wired Controllers for a full list by driver type. The following work when the adapter is outputting to any supported platform (Xbox, Switch, XInput, PS3, DInput, SteamOS / Bazzite, PS1/PS2, Dreamcast, GameCube, N64, etc.):

• Original Xbox Duke and S
• Xbox 360, One, Series, and Elite
• Razer Atrox Arcade Stick (Xbox One 1532:0a00, Xbox 360 24c6:5000; wired USB host)
• Dualshock 3 (PS3)
• Dualshock 4 (PS4)
• Dualsense (PS5)
• Nintendo Switch Pro
• Nintendo Switch wired (including Switch 2 family — Pro 2 0x2069, Joy-Con 2 0x2066/0x2067; wired USB or Bluetooth LE on Pico W / Pico 2 W; see Wired Controllers and IMPROVEMENTS — Switch 2 BLE)
• Nintendo 64 Generic USB
• Playstation Classic
• Generic DInput
• Generic HID (mappings may need to be editted in the web app)

Note: Third-party controllers that change VID/PID by mode or batch may not work correctly and are not a focus for new support.

Wireless adapters

• Xbox 360 PC adapter (Microsoft)
• Adapters that present as standard Switch / XInput / PlayStation devices may work; third-party dongles are best-effort only (see Support policy).

Wireless Bluetooth controllers (Pico W & ESP32)

Note: Bluetooth functionality is in early testing; some controllers may have quirks. BT pads work as input in any USB output mode (OG Xbox, XInput, PS3, Switch, etc.) on Pico W / Pico 2 W, and also when outputting over GPIO to PS1/PS2, Dreamcast, GameCube, or N64 (same as wired USB in those modes).

DualShock 3 (PS3) — USB pairing to the adapter’s Bluetooth (Pico W / Pico 2 W / RP2354): The DS3 does not pair like a normal Bluetooth device. If you plug a DualShock 3 into the adapter’s USB host port while the firmware is running, it will automatically program the controller with this adapter’s Bluetooth address (HID feature 0xF5, same mechanism as the Bluepad32 sixaxispairer tool — restored in v1.0.0.12a as a sync SET after wired enable). Then unplug the USB cable and press the PS button to connect wirelessly. If the radio was not ready at the moment the pad enumerated, pairing is retried on the next input reports until the address is available.

Pico W / Pico 2 W — important for DualShock 4 (DS4): DS4 uses Classic Bluetooth (BR/EDR). The same CYW43 radio also runs BLE advertising for the phone / web app. Running both at once often drops the DS4 link seconds after connect (blue LED then off). Firmware therefore pauses BLE advertising while a Classic BT gamepad is connected (DS4, DS3 over BT, Xbox 360 wireless adapter style links). DualSense and Xbox Series (BLE) mostly use LE and are unaffected by that pause.

Situation	What to do
Use DS4 / Classic BT pad	Connect and play; web app BLE discovery is off until that pad disconnects.
Use Bluetooth in the web app	Disconnect Classic BT controllers first, or plug the adapter in via USB and use Connect via USB in the app.

Full technical detail: Firmware/RP2040/docs/IMPROVEMENTS.md → Pico W / Pico 2 W — DualShock 4 and Classic Bluetooth stability.

Nintendo Switch 2 (Pico W / Pico 2 W): Switch 2 Pro (PID 0x2069) and Joy-Con 2 Left (0x2067) / Right (0x2066) use a custom BLE GATT protocol (not standard gamepad HID). Put the controller in pairing / SYNC mode; the adapter discovers and connects automatically — do not pair it in your PC or phone Bluetooth settings first. Joy-Con 2: pair Left first, then Right while left stays connected — both merge into player 1 like on a Switch. Home maps to PS / Guide (SYS) on PS3, XInput, OG Xbox, etc. Protocol credits: Nadeflore/switch2-controllers, TommyWabg/switch2-controllers-windows10-gyro, and BlueRetro #1249. Details: IMPROVEMENTS — Switch 2 Bluetooth.

Steam Controller 2026 / Triton (Pico W / Pico 2 W / RP2354 BT): Hold RB + B + Steam for BLE pairing (28de:1303, HID-over-GATT). Remove/disconnect it from PC or phone Bluetooth first — only one host can own the link. Uses LE Secure Connections. View → Start, Menu → Back/Select, Steam → Guide / SYS. Details: IMPROVEMENTS — Steam Controller 2026.

First-party / regularly maintained (Bluetooth):

• Xbox Series, One, and Elite 2
• Dualshock 3
• Dualshock 4
• Dualsense
• Switch Pro
• Switch 2 Pro and Joy-Con 2 (L/R) (BLE on Pico W / Pico 2 W / RP2354; wired USB also supported)
• Wii U Pro
• Wii Remote
  • Supported Extensions:
    • Gamepad
    • Nunchuck
    • GameCube Controller

May work (Bluepad32 / community; not a focus for new maintainer issues without hardware or donation):

• Steam (original SC)
• Steam Controller 2026 (Triton) — BLE on Pico W / Pico 2 W / RP2354
• Stadia
• 8BitDo Ultimate Wireless (Switch layout)
• 8BitDo Pro 2 / SN30 Pro — if used, prefer Switch or Android (D-input) mode (not Windows/X-input). See IMPROVEMENTS — 8BitDo Bluetooth. Out of scope for ongoing guesswork fixes (#86).

Please visit this page for a more comprehensive list of Bluepad32 gamepads and Bluetooth pairing instructions.

Features new to this fork

Version history and release notes are in CHANGELOG.md. For detailed firmware improvements — PS3, XInput / XSM3, OG Xbox, PS2/OPL, latency, SteamOS / Bazzite (STEAM mode), PS3 / PS4 motion passthrough, Pico W Bluetooth (DS4 Classic BT, BLE coexistence, Xbox Series BLE, Switch 2 Pro + Joy-Con 2 BLE, Steam Controller 2026 / Triton, DualShock 3 USB→BT auto-pair), Pico W / Pico 2 W PIO USB wired unplug detection, etc. — see Firmware/RP2040/docs/IMPROVEMENTS.md.

Highlights:

• Steam Controller 2026 (Triton) over Bluetooth — Pair with RB + B + Steam on Pico W / Pico 2 W / RP2354 (28de:1303). Requires LE Secure Connections; disconnect from any PC/phone first. View → Start, Menu → Back, Steam → Guide. Details: IMPROVEMENTS — Steam Controller 2026.

• DualShock 3 — USB → Bluetooth auto-pair (restored in v1.0.0.12a) — Plug a DS3 into the adapter’s USB host port to program it with this unit’s BD_ADDR (feature 0xF5), then unplug and press PS. Details: Wireless Bluetooth, IMPROVEMENTS — DS3 USB pairing.

• XInput / Xbox 360 — stock stick feel (#38) — In XInput mode, default (non–WebApp-customized) sticks get a milder 360-like deadzone/curve so Series pads are less twitchy. Details: IMPROVEMENTS — stock stick feel.

• Switch mode — HD rumble to input pads — Console HD rumble is decoded and forwarded to Bluetooth/USB input pads (DualSense, Xbox, etc.). Details: IMPROVEMENTS — Switch HD rumble.

• Pico W / Pico 2 W / RP2354 — USB resume restores BT pairing — After console USB standby, scans restart without unplugging the dongle. Details: IMPROVEMENTS — USB resume pairing.

• Two adapters on one console — Not supported yet as two independent players: units share the same USB identity (VID/PID / serial / XSM3 on 360). Use one OGX + a native or other-brand pad, or a multi-port host. See IMPROVEMENTS — Summary.

• PS3 / PS4 motion (tilt / IMU passthrough) — PS3 and PS4 output modes forward accelerometer (and gyro where available) from DualShock 4, DualSense, Switch Pro, and Wii Remote (BT/USB where supported). Switch output does not pass through motion for now. For real PS3/PS4 consoles, use a USB adapter between OGX-Mini and the console — tested with Brook Wingman XE 2 Converter (works on PS3 and PS4). Details: PS3 / PS4 motion controls, IMPROVEMENTS.md — motion passthrough.

• SteamOS / Bazzite (STEAM output mode) — Start + Left Bumper + D-pad Up (~3 s), web app, or -DOGXM_FIXED_DRIVER=STEAM / build-script fixed mode. USB enumerates as Sony DualSense (054c:0ce6) plus a separate HID mouse interface. DualSense emulation: passthrough of the real PS5 report when input is DualSense (BT or wired USB); other controllers get a synthesized DualSense report (Cross/Circle/Square/Triangle, L1/R2, Share/Options, PS). Touchpad → mouse: DualSense touchpad drag moves the desktop cursor; tap = left click. Controllers without a touchpad are gamepad-only. Works with Bluetooth (Pico W / Pico 2 W) or wired USB input. Details: SteamOS / Bazzite output mode, IMPROVEMENTS.md — STEAM mode, Controller_Mappings.md — STEAM.

• Pico W / Pico 2 W — PIO USB wired unplug: When you unplug the gamepad from the adapter’s USB host port, the firmware now detects disconnect reliably even though PIO USB owns D+/D− (GPIO line state often never shows a true “disconnected” idle). Detection uses debounced hints: HCD port connect status, no TinyUSB configured device (all tuh_mounted addresses), and no host input reports for a few seconds — so the TinyUSB/PIO host can tear down, GPIO line IRQ monitoring can resume, and Bluetooth pairing can work again without power-cycling or “shorting” the port. Details: IMPROVEMENTS.md — Pico W PIO USB unplug.

Note: Maintainer testing is on Feather / Pico W / Pico 2 W / Waveshare RP2350-USB-A. Other boards may not have been tested for every change — community PRs welcome.

Planned additions

Roadmap items (original creator + this fork) and researched projects such as the Xbox One/Series wireless dongle: Planned_Additions.md.

Hardware

For Pi Pico, RP2040-Zero, 4 channel, and ESP32 configurations, please see the hardware folder for diagrams.

I've designed a PCB for the RP2040-Zero so you can make a small form-factor adapter yourself. The gerber files, schematic, and BOM are in Hardware folder.

Adding supported controllers

Community guide (VID/PID, report capture, new host drivers, button mapping, Debug UART logging): Adding_Supported_Controllers.md.

Maintainer policy for first-party / donated hardware: Support policy. Wired pad lists: Wired Controllers.

Build

Full walkthrough (required tools, clone, all submodules, Pico SDK, scripts, manual CMake, flash): Building_From_Source.md.

RP2040 (summary)

Prerequisites: git, Python 3, CMake (≥ 3.13), Ninja, arm-none-eabi-gcc, plus Pico SDK 2.1.0 (not a submodule — see the build guide). CMake patches Bluepad32/BTStack and initializes some submodules during configure; you should still run git submodule update --init --recursive yourself.

Board options (OGXM_BOARD)

Maintainer-tested boards: Adafruit Feather USB Host, Pico W, Pico 2 W, Waveshare RP2350-USB-A — see Support policy. Other OGXM_BOARD values remain buildable for community use; please clone, fix, and open a pull request for those targets rather than expecting untested maintainer fixes. Clones and knock-offs are not supported.

Use one of these values for OGXM_BOARD in a manual build, or pick the same board from the build script’s numbered list:

• PI_PICO
• PI_PICO2
• PI_PICOW
• PI_PICO2W
• RP2040_ZERO (Waveshare RP2040-Zero)
• RP2350_USB_A (Waveshare RP2350-USB-A)
• RP2350_ZERO (Waveshare RP2350-Zero)
• RP2040_XIAO (Seeed Studio XIAO RP2040)
• RP2354 (RP2350 + Pi Radio Module 2 / CYW43439 — Bluetooth wireless controllers like Pico 2 W, plus PIO USB host on GP0/GP1, LED GP25)
• ADAFRUIT_FEATHER use the board’s USB Type-A port for the controller; 5V enable is GPIO 18, D+/D− are GPIO 16/17. If the controller is not detected, plug it in after the board has booted and ensure the green 5V LED next to the USB-A port is on.)
• ESP32_BLUEPAD32_I2C
• ESP32_BLUERETRO_I2C
• EXTERNAL_4CH_I2C

You can also set MAX_GAMEPADS (1–4; default 1). Multi-controller use is not supported for most output modes — see Multi-controller builds. Optional: OGXM_FIXED_DRIVER to lock output mode (e.g. XINPUT, PS3, STEAM, PS4); OGXM_FIXED_DRIVER_ALLOW_COMBOS=ON to keep combos when fixed. MAIN_LOOP_DELAY_US (default 0) sets main-loop delay for lower CPU use (e.g. 250).

Multi-controller builds (MAX_GAMEPADS > 1)

CMake option -DMAX_GAMEPADS=2 (or 3 / 4) builds firmware that can expose more than one emulated controller over USB. Do not assume every output mode works correctly with multiple players.

Status	Output mode
Tested and supported	Wii U (GameCube Adapter) — use Start + Left Bumper + D-Pad Down, or a fixed build with Wii U output. This is the only mode maintainer testing has confirmed for multi-controller use.
Not supported	All other output modes (XInput, Original Xbox, Switch Pro, PS3, PS4, SteamOS / Bazzite, DInput, PS Classic, GPIO modes, Web App, etc.)

A multi-pad build may still compile with other modes available in the combo list, but those modes are not tested, not intended for more than one controller at a time, and not supported for multi-player setups. Bugs, missing players, wrong port assignment, or console rejection are expected if you use them that way.

Recommendation: Use -DMAX_GAMEPADS=1 (default) unless you specifically need a Wii U GameCube Adapter multi-player adapter. For local multiplayer on other consoles, use one OGX-Mini per player or a native multi-port solution — see Two adapters on one console under Features new to this fork.

You'll need the tools listed in Building_From_Source.md. CMake scripts patch Bluepad32 and BTStack and initialize selected git submodules; clone with --recursive (or git submodule update --init --recursive) and install Pico SDK 2.1.0 before the first build.

Build scripts (recommended for new users)

We provide interactive build scripts so you can build firmware without memorizing CMake options:

Platform	Command (run from project root)
Linux / macOS	./scripts/build.sh
Windows (PowerShell)	.\scripts\build.ps1

The script will:

1. Check prerequisites — Verifies that git, python3 (or python), cmake, ninja, and arm-none-eabi-gcc are installed. If something is missing, it prints install hints (e.g. apt install on Debian/Ubuntu, brew install on macOS, Chocolatey on Windows).
2. Ask for your board — Choose from a numbered list (Pi Pico, Pi Pico W, Pi Pico 2 W, RP2040-Zero, RP2350-Zero, RP2350-USB-A, XIAO, RP2354, Adafruit Feather, 4CH I2C, ESP32 hybrid, etc.).
3. Ask for build type — Default (all output modes available via button combos) or Fixed output mode (e.g. Wii, GameCube, N64, STEAM, PS4 — one mode only, no combo switching).
4. Ask for configuration — Release (smaller, faster) or Debug (UART logging for troubleshooting).

Build output (.uf2, .elf, etc.) is written to scripts/build/. To flash the board, copy the .uf2 file from that folder to the Pico’s USB drive. If the build fails, the script can save a log to scripts/build_log.txt for debugging.

Manual build (CMake from command line)

If you prefer to run CMake yourself or use an IDE (e.g. VSCode CMake Tools), use the same options the scripts pass. Example (Windows, Pico W, Release):

git clone --recursive https://github.com/MegaCadeDev/OGX-Mini-2026.git
cd OGX-Mini-2026/Firmware/RP2040
cmake -S . -B build -G Ninja -DCMAKE_BUILD_TYPE=Release -DOGXM_BOARD=PI_PICOW -DMAX_GAMEPADS=1
cmake --build build

Outputs (.elf, .uf2, etc.) are in the build directory; flash the .uf2 to the board. Or use the GCC ARM toolchain and CMake Tools extension in VSCode.

Latency: The adapter sends the latest gamepad state whenever the USB endpoint is free (XInput and similar), and the main loop has no added delay by default, so the host gets updates at its poll rate with minimal latency. See Firmware/RP2040/docs/IMPROVEMENTS.md for details.

Documentation is organized by category in Firmware/RP2040/docs/README.md (feature guides, reference, support/contributing, technical notes) and docs/README.md (research / planning).

ESP32

Please see the Hardware directory for a diagram showing how to hookup the ESP32 to your RP2040.

You will need ESP-IDF v5.1, esptool, python3, and git installed. If you use VSCode, you can install the ESP-IDF extension and configure the project for ESP-IDF v5.1, it'll download everything for you and then you just click the build button at the bottom of the window.

When you build with ESP-IDF, Cmake will run a python script that copies the necessary BTStack files into the components directory, this is needed since BTStack isn't configured as an ESP-IDF component when you download it with git.

Credit to the original creator https://wiredopposite.github.io/ for the original base of the project!

Other projects that have helped enhance this fork

• Sakura-Research-Lab/OGX-Mini-2026-Testing — OG Xbox Guide button (tap/hold IGR/shutdown), board support for RP2350_ZERO, RP2040_XIAO, RP2354, and 8BitDo XInput (Xbox 360) LED keepalive fix.
• Joypad OS — Reference for Xbox 360 (XSM3) authentication with retail consoles; XInput mode on 360 follows the same approach. Descriptors and XSM3 flow are aligned with joypad-os; single config, full XSM3 security string, init/verify in main loop; USB is initialized before Core1 so the 360 can enumerate while BT loads.
• Bluepad32 — Bluetooth controller support (Pico W / Pico 2 W / RP2354).
• faithvoid — Xbox 360 controller vibration/rumble fix (host-side rumble handling, including wireless RUMBLE_ENABLE sequence).
• PicoGamepadConverter — Wii (Wiimote) output mode: approach of USB gamepad on PIO USB with Bluetooth reserved for the Wiimote link, and button/stick mappings for No Extension, Nunchuk, and Classic Controller report modes.
• retro-pico-switch — Reference for Nintendo Switch Pro Controller protocol and report layout (N64/GameCube → Raspberry Pi Pico → Switch via USB or Bluetooth). Used to align OGX-Mini’s Switch mode with correct Pro Controller button byte layout and emulation behavior.
• Nadeflore/switch2-controllers — Foundational Switch 2 BLE discovery, pairing, and GATT protocol work used to implement wireless Switch 2 Pro support on Pico W / Pico 2 W.
• TommyWabg/switch2-controllers-windows10-gyro — Extended Switch 2 fork: 63-byte composed input report, button bitfield, init/feature commands, and Pro Controller rumble packet format (fork of Nadeflore’s project).
• BlueRetro #1249 (darthcloud) — Community reverse engineering of Switch 2 63-byte BLE reports and GATT notify handles.
• SDL3 SDL_hidapi_steam_triton / controller_structs.h — Steam Controller 2026 (Triton) BLE report IDs, button bits, lizard mode, and rumble layout used for OGX Bluepad32 support.

Licenses and third-party code

• Xbox 360 console authentication: XInput builds that work on retail Xbox 360 consoles use libxsm3 (Xbox Security Method 3). libxsm3 is licensed under the GNU Lesser General Public License v2.1 or later; see Firmware/external/libxsm3/LICENSE.txt. libxsm3 credits oct0xor, emoose (ExCrypt), and sanjay900; see Firmware/external/libxsm3/README.md.
• Other dependencies: See the root LICENSE file and the Firmware/external directory for Bluepad32, BTStack, TinyUSB, Pico SDK, and other third-party licenses.