Skip to content

devices

github-actions[bot] edited this page Oct 29, 2026 · 2 revisions

Device Support

The dashboard distinguishes Ready, Not checked, Absent and Busy states instead of collapsing them into one disconnected label.

Storage matrix

Device Browse Demand-load PS2 ISO via Neutrino
Memory card Yes No Useful as Neutrino loader location; not normal ISO storage
USB / MASS Yes Yes Yes
MX4SIO Yes Yes Yes
MMCE Yes Yes Yes
Internal HDD (APA/PFS) Yes Yes File/app workflows; raw game layouts are backend-specific
ATA/exFAT Yes Yes Yes
UDPFS Where configured Network stack Yes

Why Not checked is selectable

A demand-loaded driver cannot know whether hardware is absent until it runs. A Not checked device therefore remains navigable; opening it triggers the existing lazy loader. A confirmed Absent card remains visible with its status and is skipped by focus navigation.

USB units

USB is labeled USB / MASS. The implementation discovers available units and does not treat mass0: as a permanent identity.

MX4SIO and Memory Card Slot 2

MX4SIO owns the second memory-card slot while active. Opening mc1:/ in Files or a file/folder picker first resets the IOP to release MX4SIO, then reads the memory card. The slot stays selectable even if its cached presence was empty. Background card polling and application scans leave MX4SIO running; opening mc0:/ does not require this switch.

Switching between MMCE and MX4SIO

Opening either mmce0:/ or mmce1:/ while MX4SIO is active resets the IOP before loading MMCE and reading the device. Switching from either MMCE slot to MX4SIO follows the same reset gate. A refused reset stops the switch. Both MMCE slots share one driver and can be browsed in the same IOP session.

USB enumeration and intermittent stalls

When the USB stack starts, Launchstation probes at most four times with spaced checks, including late second-drive discovery. Each probe uses a synchronous PS2 IOP filesystem RPC: the number of retries is bounded, but a single blocked driver call cannot be timed out safely by the EE. The controller's analog light going out can indicate a stalled PAD/SIO2 or IOP session; it does not, by itself, prove a software reset. An overloaded USB power rail is also possible with two bus-powered drives. Compare behavior with one drive, a powered hub, and the older launcher baseline. Do not hot-unplug a drive during active writes.

Tools: USB unit diagnostics

Use Tools > USB unit diagnostics to inspect the last cached logical-unit mask without new I/O or explicitly probe USB unit 0 or 1 one at a time. A manual probe is a synchronous IOP filesystem call; a failed driver can block despite bounded retry logic. Logical usb0:/usb1: numbers are not physical port identifiers. Consult the USB stability audit for technical history.

Clone this wiki locally