PlayStation 2 · Emulators on PS2

Browse native FCEUmm, PicoDrive and PS2ME builds with their storage paths and supported-system notes.

Emulators on PS2

Browse native FCEUmm, PicoDrive and PS2ME builds with their storage paths and supported-system notes.

3 resources

Emulators running on the PS2

These downloads run on a physical PS2. Add your own compatible ROMs, MIDlets or required BIOS files.

FCEUmm-PS2 original illustrative artwork

Emulators · 0.3.3 · USB ELF

FCEUmm-PS2

A native NES/Famicom emulator with a controller-friendly browser, save states, turbo buttons and multitap support. This is the standard USB-oriented ELF, not the separate CD/DVD build.

  • NES
  • Famicom
  • Save states
  • Multitap
Requires
An ELF launcher, PS2 pad and your own NES ROM dumps or compatible homebrew ROMs. Normal NES cartridges need no BIOS. Famicom Disk System software additionally needs your own compatible disk-system BIOS.
Setup & verified files

Copy the ELF and a separate ROM folder to FAT32 USB, launch it and choose a ROM in its browser. Configure a writable save path. Cross is A, Square is B and L1 opens the menu. ROMs and external BIOS files are not included. If upgrading from an old FCEUmm setup, back up the old FCEUltra.cnf and reset that configuration for this release’s controller mapping.

USB:/APPS/FCEU/fceu-packed.v0.3.3.elf + USB:/ROMS/NES/
fceu-packed.v0.3.3.elf603.1 KB · PS2 ELFSHA-256 a41a3c5dfc0b9283046b905a131a1044625acd67c48d9d1d18af65e12ec51f4aOriginal release file
Package layout
  • fceu-packed.v0.3.3.elf
PicoDrive · native PS2 original illustrative artwork

Emulators · 2.05 · 19d4108

PicoDrive · native PS2

The upstream PS2 build of PicoDrive for Sega Mega Drive/Genesis and related systems. Keep its skin and configuration files with the executable.

  • Genesis
  • Mega Drive
  • Mega CD
  • Standalone
Requires
A homebrew PS2 and your own supported game dumps. Cartridge games need no Mega CD BIOS; Mega CD requires a matching region BIOS dumped from your own hardware. See the included readme for supported BIOS filenames.
Setup & verified files

Extract the full PicoDrive folder to FAT32 USB and launch PicoDrive.elf. Select opens its menu. For CD games, keep BIN files with their CUE and load the CUE so track layout is preserved. BIOS files go beside the emulator as described in readme.txt. This standalone release does not use RetroArch BIOS filenames.

USB:/PicoDrive/{PicoDrive.elf,readme.txt,game_def.cfg,skin/}
PicoDrive_ps2_2.05-19d4108.zip1.00 MB · ZIPSHA-256 22f2abdf5a2f8a5f02c130c4722b7b08ddddd705a161c757c1e3917b0daf70e8Original release file
Package layout
  • PicoDrive/PicoDrive.elf
  • PicoDrive/game_def.cfg
PS2ME original illustrative artwork

Emulators · 1.4.0

PS2ME

Run compatible Java ME MIDlets through a native PS2 launcher and the phoneME virtual machine. It supplies the runtime; add your own JAR applications.

  • Java ME
  • J2ME
  • MIDP 2.0
  • FAT32 USB
Requires
A homebrew-capable PS2, FAT32 USB, PS2 controller, memory card for RecordStore saves and compatible CLDC 1.1 / MIDP 2.0 JARs. No phone BIOS is required; compatibility varies by MIDlet.
Setup & verified files

Extract the release, put its ELF in mass:/PS2ME/ and add your own MIDlets to mass:/PS2ME/games/. bgm.adpcm is optional menu audio. Launch the ELF; Cross launches the selected game, Circle goes back and Select opens per-game options.

mass:/PS2ME/{PS2ME-v1.4.0.elf,bgm.adpcm,games/*.jar}
PS2ME-v1.4.0.zip1.95 MB · ZIPSHA-256 973d62fa632d92cf275c677bdbfd8c6ad0b9e6274a64e6d8a43c7dafc5bd0c54Original release file
PS2ME-v1.4.0.elf3.18 MB · PS2 ELF · extracted ready ELFSHA-256 53cacfc3360efeb8bcf9233289874ca402474076771c1528420aaa74d2f8e0c4

Extracted unchanged from PS2ME-v1.4.0.zip: PS2ME/PS2ME-v1.4.0.elf. The original package is also preserved.

Original container
Package layout
  • PS2ME/bgm.adpcm
  • PS2ME/PS2ME-v1.4.0.elf
  • PS2ME-v1.4.0.elf

Storage & dependency checklist

  1. Start with a working ELF boot methodA downloaded ELF does not make an unmodified PS2 boot homebrew. Use the model-specific FMCB/OpenTuna guidance above, then launch apps through wLaunchELF or a configured menu. No region bypass is required by these homebrew downloads; the boot method still depends on your model and ROM.
  2. Use a conservative USB starting pointFAT32 USB is the starting layout for these instructions. PS2ME explicitly requires it. Memory Card Annihilator’s mca_new supports exFAT. Do not assume that an older app gains exFAT, SMB or MX4SIO support because OPL can use a device.
  3. Keep package folders and assetsExtract ZIP or TAR.GZ files on your computer before copying them. SuperTux needs its APPS tree at the USB root. PicoDrive needs its skin/config files. A direct ELF is only convenient where its optional or external dependencies are explained on its card.
  4. Separate USB, SMB and internal HDD supportOPL 1.1.0 offers USB, SMB and internal HDD routes; these are OPL features, not universal app services. Internal-HDD tools need a real internal drive interface. The Quake ports document their own USB/APA-PFS loading paths. SMB requires working Ethernet and share settings.
  5. Bring the right data and savesNES cartridge ROMs, Mega CD BIOS files, Java JARs and Quake PAKs are different requirements. They are not included in these runtime downloads. SuperTux includes its free game data. Keep an original save backup and a memory card available for apps that save there.
  6. Match the display and controllerUse a PS2 pad for the documented controls. Follow each app’s PAL/NTSC options; do not force an unsupported display mode. PadOS normal is 4:3 with Widescreen OFF. A theme changes OPL’s interface and does not patch game rendering.