Separate the components of your setup
Analogue OS firmware, an openFPGA core and the files loaded by that core are different components. Record the firmware version shown on the device, then record each core's author and release separately. A firmware update does not identify which third-party core you installed, and installing a new core does not automatically replace Analogue OS.
Analogue defines a core as an FPGA bitstream packaged with JSON files that describe loading and operation. Pocket has a primary FPGA available to developers and a system FPGA used by Analogue OS. Use the official architecture documentation to understand that boundary; a core release should state its own capabilities and requirements.
Update firmware deliberately
Back up the microSD card first. Analogue's Pocket update procedure accepts FAT32 or exFAT, places one firmware file at the card root, and starts installation when a fully powered-off Pocket boots with that card inserted. Obtain the file through Pocket Support, read its release notes and ensure no other firmware files remain at the root. Leave power and the card undisturbed until the update completes.
After restarting, record the installed version and test an original cartridge or a previously working core. Retain the downloaded file and release notes in a dated computer folder. That record is useful when a later core requires a particular OS version or a bug report asks when behavior changed.
Install one documented core first
- Choose a core release from its maintainer and read its included installation notes, firmware requirements and feature limitations.
- Inspect the archive's folder layout before extraction. A packaged core is normally arranged to merge into the card root; avoid adding an accidental extra enclosing folder.
- Retain the original package. Compare any proposed overwrites with the existing card contents and preserve personal saves separately.
- Provide only the assets the core actually requests, using the required format and directory. A filename alone does not verify a BIOS or game image.
- Start the core with a small known working test, then check input, audio, saving and a return to the OS menu.
Understand the microSD layout
The official directory convention uses a Cores folder containing author-and-core subdirectories, with Assets organized by platform and sometimes by core. Preserve that structure when installing packages. Do not rename folders solely to make the card look tidier; the core definitions and loading rules refer to those identities.
Keep an inventory of core versions, required files and tests completed. An automatic manager can help maintain that inventory, but its changes should still be reviewed before replacing the only working setup. Install optional features in small stages so a regression has an identifiable cause.
Feature claims belong to the core
Check the maintainer's documentation for Memories, sleep, real-time clocks, display modes and unusual cartridge hardware. Availability in one core does not establish availability in another. If a feature is undocumented, test it with expendable progress and record the result narrowly. Continue with saves and storage before making broad library changes.
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.