Repository navigation
Check For Updates
The main menu's Check for Updates entry (just above About) asks GitHub whether the release this build came from has a newer build, and on request replaces the running ELF with it. Nothing happens until you choose the entry: RiptOPL never checks or downloads on its own.
Every standard build that has a rolling release to come from:
| Build | Channel (GitHub release) | File replaced |
|---|---|---|
| Korium | rolling-korium |
RIPTOPL.ELF |
| IncebtIon | rolling-incebtion |
RIPTOPL.ELF |
| RetroAchievements | rolling-ra |
RIPTOPL-RA.ELF |
| RetroAchievements IncebtIon | rolling-ra |
RIPTOPL-RA-IncebtIon.ELF |
| LLVM Korium / LLVM RA | rolling-llvm |
RIPTOPL.ELF / RIPTOPL-RA.ELF
|
RiptOPLite, debug and variant builds do not have it, so a build is never replaced by a different kind
of build. The channel is fixed at build time (tools/build_edition.py update_channel).
- RiptOPL started from a memory card (
mc0:/mc1:) or a USB/exFAT drive (massN:). Other places (HDD, network, MMCE) are refused before anything is downloaded. - A network adapter with internet access. It uses the same network settings as SMB (Settings > Network). While UDPBD or UDPFS owns the network adapter, it refuses and says so.
- The console clock set to the current date (Settings > General & System > Date and Time): the GitHub certificates cannot be checked without it.
- Downloads the channel's
SHA256SUMS.txt. The release's build number comes from its versioned zip names (RIPTOPL-Korium-v1.2.0-Beta-4257.zip), and the ELF's expected SHA-256 from its line. - Compares that build number with the running one (the number in the About screen's version). Equal or older: "already the newest". A build without a number (a local build) is not compared.
- On your OK, downloads the ELF into memory. The first bytes must be a PS2 ELF header; the size is limited to 8 MB.
- Checks the SHA-256 of what was downloaded against
SHA256SUMS.txt. A mismatch changes nothing. - Overwrites the running ELF in place under its own name, as Launchstation does. No second file, rename or backup is made. The old ELF is emptied before the new one is written, so a card too full for the new ELF can leave it damaged. If the write fails part-way the ELF may be damaged: the message gives the step (1 open, 2 write, 3 close) and the error code, and the ELF must be copied to the device again.
The new build starts the next time RiptOPL is opened. Settings, themes and other files are not touched.
HTTPS with certificate, host name and date always verified, against four built-in roots only: Sectigo
E46 and R46 (github.com) and ISRG X1 and X2 (GitHub's release download host). Redirects are followed
only to github.com, release-assets.githubusercontent.com and objects.githubusercontent.com, at
most three times. The RetroAchievements builds use their existing TLS (TLS 1.3 and 1.2); the others carry
a TLS 1.2-only build of the same mbedTLS (third_party/mbedtls/riptopl_mbedtls_slim_config.h).
Host-tested: the TLS download (.github/scripts/test_ratls_host.py) and the parsing
(.github/scripts/test_selfupdate_host.py, against the real SHA256SUMS.txt files). NOT TESTED on
hardware or in PCSX2: the real GitHub certificate chains, the in-place write to a real memory card and the full download.
Start here
- Getting started
- Fresh-start defaults
- Installation and first boot
- Releases and packages
- Launch diagnostics
Storage and networking
- USB, MX4SIO and iLink
- MMCE
- Internal HDD: APA and exFAT
- PSX DESR DVR (experimental)
- PC CARD CompactFlash (experimental)
- SMB (moved to Network)
- Network: SMB, UDPFS and UDPBD
- HTTP
- NBD server
Games and features
- Game image formats: ISO, ZSO, CHD and CSO
- Neutrino core
- PS1: POPStarter and Ember
- Per-game settings
- Virtual memory cards
- File Manager
- GSM video modes
- In-game reset
- Cheats
- PADEMU
- RetroAchievements
- Apps
Interface and customization
- Settings reference
- Controls
- Coverflow
- Favorites
- Game library: All Games, Recent, Hide and Delete
- Theme engine
- Languages
- Japanese / Unicode game titles
Help and reference
- Troubleshooting
- ZSO format
- Backward-compatible PS3
- Credits and sources
- Features in other forks
- Notes for ps2sdk
- Project overview
Detailed references
- Documentation index
- Interface screenshots and capture workflow
- Test builds and diagnostics
- Launch diagnostics by package, core and transport
- Learning across PS2 loader projects
- VMC creation and recovery
- PC CARD CF implementation reference
- DESR DVR implementation reference
- Per-game console i.LINK ID
- Per-game parental lock
- SIO2MAN hook compatibility
- APA hard disk safety and code 402
- Autolaunch and global settings
- Folders, parental lock and audio
- Language maintenance
- HTTP server conformance tools
- APA recovery tool
- Setup questions and reporting launch failures
- Editions and build configurations
- Automatic VMC creation
- Compressed PS2 images: ZSO, CSO and CHD
- Favorites storage, staged saves and recovery
- CFG titles in game lists
- RA watch-list and snapshot budgets
- Maintaining the documentation
- Where every setting lives
- Check for Updates