Establish cartridge compatibility
Pocket's built-in cartridge support covers Game Boy, Game Boy Color and Game Boy Advance. Official adapters extend cartridge use to additional named systems. Match the actual adapter to the actual cartridge rather than treating a physically similar connector as evidence of compatibility. Record any flash cartridge firmware separately from Pocket firmware.
Inspect cartridge contacts and the slot before inserting media. The official adapter guide shows inserting the adapter, fitting the original cartridge with its label facing out and selecting Play Cartridge. It also says not to insert or remove cartridges while Pocket is docked. Follow the current manual when handling adapters and move the unit to a safe position first.
For a game that fails, compare another cartridge from the same supported system and record whether the issue occurs in both handheld and Dock use. Keep the game's region and any unusual hardware features in the report. A failure limited to one cartridge deserves a different investigation from a slot that fails with every known working game.
Check Dock as a separate device
Keep Pocket and Dock firmware records together. Analogue's update instructions describe updating Dock through Pocket and the on-screen prompts. Follow those instructions and leave the connection undisturbed during installation. The official Dock Support page provides its manual and controller-related guidance.
For controller testing, record the controller model, its firmware, connection mode and whether the problem affects the OS menu or a particular core. Start with one documented controller and a direct connection. Add multiplayer devices individually and test the game's player assignment. A supported connection does not establish that every core implements every possible player or peripheral.
Start a core-development project
Analogue's development guide specifies Intel Quartus Lite with Cyclone V support and provides a core template. Begin with that template, its JSON definitions and a small working design. Keep the source revision, toolchain and build output together. Validate a simple display and input experiment before adding a complex memory interface or external accessory.
- Create a stable author and core identity, then update the definition files to match the project.
- Compile the design with the documented toolchain and check warnings relevant to the interface and timing.
- Package the bitstream in the Pocket format required by the official packaging guide, together with its definitions and required assets.
- Install onto a test card and verify startup, reset, input and return-to-menu behavior.
- Document implemented features and known limitations so users can assess the release.
Debugging and release care
JTAG debugging is an advanced workflow with specific approved equipment and access instructions in Analogue's guide. Follow that guide's handling requirements rather than guessing connector pinouts or adapting an unrelated programmer. Running a packaged core from microSD and accessing hardware debugging connections are separate activities.
Before release, test the exact archive on a clean card layout. Include core version, release date, minimum OS requirement and asset requirements. Use save preservation before testing changes to persistent data, and core setup to verify the installation experience.
Sources and review
Reviewed October 11, 2026. The linked manufacturer and project documentation establishes supported behavior. The diagnosis checklists and preservation suggestions are original editorial guidance. Menus, services and project support can change; verify the linked instructions before an irreversible change.