Project

FAQ

The questions a developer, hardware engineer, or interviewer is most likely to ask when reviewing pogopo for the first time.


What is pogopo?

pogopo is a compact handheld game console and modular pocket platform. It combines a custom ESP32-S3 board, a 400 × 240 Sharp Memory LCD, physical controls, audio, storage, motion sensing, and a purpose-built firmware called PogopoOS.

Why ESP32-S3?

The project uses its two CPU cores, SPI/I²C/I²S/SDMMC peripherals, external-memory support, and ESP-IDF/FreeRTOS environment. Those capabilities are used directly by the display, controls, audio, storage, motion, and emulator task split.

Why a monochrome Sharp Memory LCD?

The panel gives pogopo a crisp, readable 1-bit image and keeps static pixels visible without a continuous full-screen refresh. Unlike a typical e-paper display, it is fast enough for interactive UI and approximately 30 FPS Game Boy presentation.

What is PogopoOS?

PogopoOS is custom ESP-IDF/C++ firmware. It initializes the board, exposes hardware services, renders the interface, runs applications, manages settings and power, and integrates the Game Boy runtime.

Does it run Linux?

No. PogopoOS is an embedded firmware stack running directly on ESP-IDF and FreeRTOS. It does not boot a Linux kernel or use a desktop operating-system environment.

Can it emulate Game Boy?

Yes. The working runtime uses Peanut-GB and MiniGB APU and reads .gb files from /gameboy. The documented baseline advances the Game Boy CPU at 59.7 Hz and presents to the Sharp LCD at approximately 29.9 Hz.

How are apps and games made?

Native software implements the shared application interface and uses PogopoOS services instead of owning peripherals directly. Apps can draw through the graphics layer and receive input, audio, haptics, storage, motion, power, and settings dependencies from the app manager.

What is the modular expansion system?

It is a planned mechanical and electrical attachment area on the right side of the console. The goal is to connect interchangeable hardware such as extra controls, sensors, wireless functions, storage, or experimental electronics. The final connector, power limits, protocol, and verified module list are still work in progress.

Is pogopo open source?

Project-authored PogopoOS source code and documentation are available under Apache-2.0. Third-party components, games, fonts, and artwork keep their own licenses; see the license page and repository notices for the exact boundary.

What did I design and build myself?

I designed the pogopo handheld platform around a custom PCB and enclosure concept and implemented the current PogopoOS firmware: board drivers, services, 1-bit UI, launcher, settings, power behavior, diagnostics, asset pipeline, and Game Boy integration/optimization. Third-party emulator cores are identified in the repository and remain under their own licenses.

What is finished and what is still experimental?

Working parts include board bring-up, the Sharp display path, controls, audio, haptics, microSD, motion and power services, launcher/settings UI, startup/shutdown behavior, and Game Boy runtime. The modular connector specification, verified expansion modules, broader native game library, other runtimes, final portfolio photography, and several formal reliability benchmarks are still experimental or planned.

pogopo documentation ·