Pokémon Emerald Runs Natively on $6 Pico 2 Chip
08 Aug 2026
A new hobbyist project has ported Pokémon Emerald to run natively on the Raspberry Pi Pico 2 platform, hitting a full 60 frames per second on hardware that costs roughly $6. The port targets a WeAct Studio Core2350B board equipped with an RP2350B microcontroller clocked at 252 MHz and 16 MB of QSPI flash — a striking demonstration of what modern low-cost embedded chips can do with careful optimization.
What was built
The 11.7 MB game image runs across two cores: Core 0 handles game logic in about 0.3 ms per frame, while Core 1 handles picture-processing-unit (PPU) rendering in roughly 12 ms per frame. The display runs at 240×160 resolution in RGB565 color, and total live RAM usage sits at about 378 KB out of the RP2350's 520 KB — leaving headroom but not much.
The standout engineering detail is a PPU optimization that reportedly cut frame render time from 909 ms down to the 60 fps target — a claimed 45x speedup. That said, not every scene hits the mark: the OBJ-window intro cinematic still runs slower, at 20–25 ms per frame, below the full-speed threshold.
The project is released under the MIT License.
What's missing
The port isn't feature-complete. Several gaps are explicitly noted:
- Audio: DPCM and reverse-playback instruments are silent stubs, so some in-game sound is incomplete.
- Connectivity: Link cable and wireless functionality aren't implemented, meaning device-to-device trading and battling — a core feature of the original game — doesn't work.
- Real-time clock: The RTC is stubbed, so the in-game clock reports as stopped, affecting any time-of-day-dependent events.
The report doesn't specify when the port was completed, who built it, how ROM assets are sourced or bundled, or how the 60 fps figure was validated across different in-game scenarios beyond the noted intro-cinematic exception. There's also no information yet on community reception or reproducibility for other users.
The legal shadow
Pokémon and its character names remain trademarks of Nintendo, Creatures Inc., and GAME FREAK Inc. The report flags this as a real risk: distributing or commercially using the port could expose the project — or anyone building on it — to legal challenges, regardless of the MIT License covering the porting code itself. How the underlying game assets are obtained isn't detailed, which leaves an open question mark over the project's legal footing.
Why founders should care
For founders in devtools, embedded systems, or hardware-adjacent products, this project is a useful signal rather than a business model. It's likely (not certain) that the underlying optimization techniques — squeezing a console-era game engine onto a $6 chip at native frame rates — could be reusable for other resource-constrained embedded software or retro-emulation projects. The MIT License also hints at a plausible open-source distribution pattern that founders exploring hobbyist or embedded gaming products might study.
At the same time, the incomplete features (audio, wireless, RTC) are a reminder that impressive technical demos often sit far from production-ready. Founders evaluating similar proof-of-concept ports should probably build in significant additional engineering time before assuming feature parity is close at hand.
The trademark exposure is the sharpest cautionary note. Any founder considering building a product, tool, or business around similar emulation or porting work should independently verify IP rights and licensing terms — the presence of an MIT License on the code does not resolve trademark or copyright risk tied to the original game itself.
What's unresolved
Several open questions remain, including the developer's identity and background, the project's release date, and whether there's a roadmap for finishing audio, wireless, or real-time clock support. Sources also don't clarify how game assets are being distributed, which is the single biggest variable for anyone assessing legal risk here.