Filesystem services PXI
(Redirected from FSPXI)
Jump to navigation
Jump to search
Post 3.x[edit]
Pre 3.x[edit]
| Command Header, prior to 3.0.0-5 | Available since system version | Description |
|---|---|---|
| 0x003E.... | ? | This was removed with 3.0.0-5. |
| 0x003F0000 | 1.0.0-0 | DeleteSdmcRoot |
| 0x00400040 | 1.0.0-0 | DeleteAllExtSaveDataOnNand |
| 0x00410000 | 1.0.0-0 | InitializeCtrFilesystem |
| 0x00420000 | 1.0.0-0 | CreateSeed |
| 0x00430042 | 2.0.0-2 | GetSdmcCtrRootPath |
| 0x00440040 | 2.0.0-2 | GetArchiveResource |
| 0x00450002 | 2.0.0-2 | ExportIntegrityVerificationSeed |
| 0x00460002 | 2.0.0-2 | ImportIntegrityVerificationSeed |
| 0x00470082 | 2.0.0-2 | This was removed with 3.0.0-5. |
| 0x00480102 | 2.0.0-2 | GetLegacySubBannerData |
| 0x00490042 | 2.0.0-2 | ? |
| 0x004A00C2 | 2.0.0-2 | GetFileLastModified |
| 0x004B0102 | 2.0.0-2 | ReadSpecialFile |
| 0x004C0040 | 2.0.0-2 | GetSpecialFileSize |
Commands listed in the previous chart marked as available since 1.0.0-0 that are not shown in this chart are the same between both.
Errors[edit]
| Error-code | Description |
|---|---|
| 0xC82044BE | Object does already exist/failed to create object. |
| 0xC86044D2 | Failed to write file. Partition is full. |
| 0xC8804471 | Attempted to open a file under a directory which doesn't exist. |
| 0xC8804478 | Object doesn't exist / failed to open object(file). Or: The specified title does not exist in the database. |
| 0xC880448D | FSPXI: Gamecard not inserted when attempting to use the gamecard. |
| 0xC88044AB | SDMC/NAND bus error, REG_SDSTATUS: TMIO_STAT_CMD_BUSY or TMIO_STAT_TXUNDERRUN |
| 0xC88044AC | SDMC/NAND bus error, REG_SDSTATUS: TMIO_STAT_ILL_FUNC |
| 0xC92044E6 | Operation not allowed with the current file openflags/file already in use (if file was previously opened for writing). |
| 0xC92044E7 | Resource locked. |
| 0xC9204509 | SDMC/NAND bus error, REG_SDSTATUS: TMIO_STAT_CMDTIMEOUT |
| 0xC960454B | SDMC/NAND bus error, when an error-bit in REG_SDSTATUS separate from the above errors is set. This can also indicate that the TWL partition table in the NAND sector0 is invalid, or that the sector signature for sector0 at offset 0x1FE is invalid? |
| 0xC960454C | SDMC/NAND bus error, REG_SDSTATUS: TMIO_STAT_STOPBIT_ERR |
| 0xC960F401 | SDMC/NAND bus error, REG_SDSTATUS: Bit23 (0x00800000) |
| 0xD8604664 | FSUSER: Returned when attempting to create a file in savedata when the current total number of files is already the maximum. |
| 0xD9004587 | FSPXI: Hash verification failure (only for NCCH region hashes?). |
| 0xD9004588 | FSPXI/FSUSER: Verification failure for RSA or hashes. FSUSER: Verification failed for savegame AES-MAC. |
| 0xD900458B | Invalid RomFS / savedata block hash. |
| 0xD9004676 | FSUSER: The specified service-command / archive is not accessible, due to the currently used exheader accessinfo not having the required bit(s) set. (This error can also indicate that the required ARM9 access-control mount flag is not enabled, in the exheader for any of the running ARM11 processes) |
| 0xE0C046F9 | FSPXI: Specified read-size doesn't match the actual filesize, when accessing ExeFS. |
| 0xE0E046BE | Invalid lowpath. This can also indicate that the specified archive-id does not exist, or that the specified archive-id is not accessible over FSPXI. In certain cases this can also be caused by attempting to open a FSUSER archive where none of the required bit(s) for the archive are set in the user-process exheader accessinfo. |
| 0xE0E046C1 | File-reading returns this when the input 64bit file-pos is negative, or when the file-pos is larger than the filesize. |
| 0xE0E046D1 | Failed to write to file because it would exceed the file size limit of the file system. |
| 0xE160F402 | SDMC/NAND bus error, REG_SDSTATUS: TMIO_STAT_RXRDY |
| 0xE160F403 | SDMC/NAND bus error, REG_SDSTATUS: Bit28 (0x10000000) |
| 0xE160F404 | SDMC/NAND bus error, REG_SDSTATUS: Bit27 (0x08000000) |