-
Notifications
You must be signed in to change notification settings - Fork 2
PS3 Compatibility
RiptOPL runs on a PS3 — but only the specific hardware revisions that contain real PS2 silicon. This page explains which models qualify, which storage modes work, and how to get an entry point to launch PS2 titles.
ℹ Only hardware BC models are supported
Not all PS3s can run PS2 software. Only the first-generation units that ship with actual PS2 hardware on board (the COK-001 and COK-002 / COK-002W mainboard families) are supported. All later PS3 models removed the on-board PS2 hardware and cannot run OPL or any other PS2 homebrew loader.
The following mainboard revisions contain the dedicated PS2 Emotion Engine and Graphics Synthesizer chips and are the only PS3 hardware on which RiptOPL operates:
| Mainboard | Notes | psdevwiki reference |
|---|---|---|
| COK-001 | First-generation 20 GB and 60 GB launch units (North America / Japan / PAL). Full hardware PS2 compatibility — both EE and GS are discrete chips. | psdevwiki: COK-001 |
| COK-002 / COK-002W | Later 60 GB (some regions) and first-wave 80 GB units. Still supported by OPL. | psdevwiki: COK-002 |
All other PS3 SKUs (CECHx serial suffixes from P onward, Slim, Super Slim) removed the PS2 hardware and are not supported. If your PS3 model is not listed above, OPL cannot run on it.
How do I identify my PS3 mainboard?
The mainboard revision is not printed on the outside of the console. The easiest method is to check the serial number suffix on the back of the unit, then cross-reference the psdevwiki PS2 Compatibility table. In practice: if you own a 20 GB, 60 GB, or first-wave 80 GB fat PS3 and it came with a PS2 game bundled or advertised "PS2 backward compatibility," it is almost certainly a COK-001 or COK-002. The 40 GB fat and all Slim/Super Slim units are not backward compatible.
On a qualifying PS3, RiptOPL supports the same three storage backends it does on a real PS2:
- USB — FAT32 or exFAT USB mass storage. Works with any entry point (ODE, Swap Magic, CFW). See USB / MX4SIO / iLink.
- SMB — Games streamed over a network share. Works with any entry point. See SMB (network share).
- HDD — Internal PS3 hard drive (APA partition scheme, same format as a real PS2 HDD). CFW with Cobra is required — ODE and optical-disc entry points do not expose the HDD to the PS2 environment. See Internal HDD.
ℹ MMCE, MX4SIO, iLink, UDPBD, UDPFS on PS3
MMCE (SD2PSX / MemCard PRO2), MX4SIO, iLink, and the network-boot protocols (UDPBD / UDPFS) are not tested or confirmed to work on PS3 BC hardware. Stick to USB, SMB, or HDD (CFW only) for a reliable experience.
The PS3 does not boot PS2 ELFs natively — you need a mechanism to launch a PS2 executable. Your options, in roughly increasing order of capability:
A physical Swap Magic disc can bootstrap a PS2 ELF on a stock (OFW) PS3 BC unit with no firmware modification. It is the lowest-friction option for a console you do not want to modify. USB and SMB modes work; HDD mode does not.
Any method that lets you boot an arbitrary PS2 ELF from optical media or a swap trick will work for USB and SMB. HDD mode is still unavailable without CFW.
CFW with Cobra is the preferred entry point. It gives you the cleanest PS2 launch path, unlocks HDD mode, and requires no disc swapping. Install a current CFW that includes Cobra and make sure the Cobra plugin is active. RiptOPL is then launchable as a PS2 ELF through the CFW/Cobra entry point, with no disc swapping required.
ℹ CFW is the only path to HDD mode
Only CFW supports HDD mode. If you want to run games off the PS3's internal hard drive through OPL's APA/PFS partition scheme, you must be on custom firmware with Cobra. No OFW or disc-swap method exposes the HDD to the PS2 environment.
- MMCE, MX4SIO, and iLink storage have not been verified on PS3 BC hardware.
- Network boot protocols (UDPBD / UDPFS) are untested on PS3 BC.
- HDD mode requires CFW + Cobra; it will not work under OFW or disc-based entry points.
- PS3 BC hardware does not support the Neutrino external core — Neutrino is a PS2 IOP/EE-level loader and its interaction with PS3 BC emulation is untested. Use the built-in OPL core on PS3.
- Some GSM video mode adjustments may behave differently on PS3 BC hardware due to the partial GS integration on COK-002/002W units.
Why are non-BC PS3s not supported?
Post-COK-002 PS3 models removed the discrete PS2 hardware entirely. Sony's "Software Compatibility" mode (found on some 40 GB PAL units) used a partial PS2 software emulator but it was never complete and was removed from later firmware. OPL depends on real PS2 EE/GS/IOP hardware being present and accessible — there is no emulation layer it can target on a non-BC PS3. If you want to run PS2 games on a non-BC PS3 you need a different solution entirely (e.g., PS2 Classics from the PlayStation Store, or RPCS3 on a PC).
Source: ps3-bc.html @ fc2e13154e51. Read on the documentation website.
Start here
Storage and networking
- USB, MX4SIO and iLink
- MMCE
- Internal HDD: APA and exFAT
- SMB shares
- Network boot: UDPFS and UDPBD
- HTTP
- NBD server
Games and features
- Neutrino core
- PS1: POPStarter and Ember
- Per-game settings
- Virtual memory cards
- GSM video modes
- In-game reset
- Cheats
- PADEMU
- RetroAchievements
- Apps
Interface and customization
Help and reference
- Troubleshooting
- ZSO format
- Backward-compatible PS3
- Credits and sources
- Features in other forks
- Project overview
Detailed references
- Complete repository guide
- Rolling release reference
- APA hard disk safety and code 402
- Autolaunch and global settings
- Controls reference
- GSM reference
- HTTP reference
- In-game reset reference
- Folders, parental lock and audio
- Language maintenance
- MX4SIO launch reference
- Neutrino reference
- PADEMU reference
- RetroAchievements reference
- Theme engine: full authoring reference
- PS1/VCD reference
- HTTP server conformance tools
- APA recovery tool