549
edits
Changes
Jump to navigation
Jump to search
Line 1,014:
Line 1,014: − == Filenames and Paths ==+ Line 1,037:
Line 1,037: − === Binary LowPath ===+ − ==== SystemSaveData Archive Path Data Format ====+ − ===== FS =====+ Line 1,055:
Line 1,055: − ===== FSPXI =====+ Line 1,066:
Line 1,066: − ==== UserSaveDataForCheck Archive Path Data Format ====+ Line 1,083:
Line 1,083: − ==== ExtSaveData Archive Path Data Format ====+ Line 1,100:
Line 1,100: − ==== 0x2345678A Archive Path Data Format ====+ Line 1,140:
Line 1,140: − ==== [[RomFS]] ====+
Fixup header levels
The CARDSPI archive allows access to the gamecard CARD1 raw savedata flash(aka "cardspi:/" in [[FIRM|Process9]]), the file lowpath must be WCHAR "/". The "NAND W FS" archive allows access to the raw NAND image(aka "wnand:/" in Process9), the file lowpath must be WCHAR "/".
The CARDSPI archive allows access to the gamecard CARD1 raw savedata flash(aka "cardspi:/" in [[FIRM|Process9]]), the file lowpath must be WCHAR "/". The "NAND W FS" archive allows access to the raw NAND image(aka "wnand:/" in Process9), the file lowpath must be WCHAR "/".
= Filenames and Paths =
PathType:
PathType:
{| class="wikitable" border="1"
{| class="wikitable" border="1"
|}
|}
== Binary LowPath ==
The format of the data that a binary LowPath points to is custom per archive.
The format of the data that a binary LowPath points to is custom per archive.
=== SystemSaveData Archive Path Data Format ===
==== FS ====
{| class="wikitable" border="1"
{| class="wikitable" border="1"
|-
|-
The file/directory lowpath is a text lowpath in the [[Savegames|savegame]] filesystem.
The file/directory lowpath is a text lowpath in the [[Savegames|savegame]] filesystem.
==== FSPXI ====
{| class="wikitable" border="1"
{| class="wikitable" border="1"
|-
|-
The file lowpath is a binary lowpath containing the u64 saveid, however the high word of the saveid is always zero. The mounted file is the cleartext savegame image. Up to 32 SystemSaveData image files can be opened under a single mounted FSPXI archive.
The file lowpath is a binary lowpath containing the u64 saveid, however the high word of the saveid is always zero. The mounted file is the cleartext savegame image. Up to 32 SystemSaveData image files can be opened under a single mounted FSPXI archive.
=== UserSaveDataForCheck Archive Path Data Format ===
{| class="wikitable" border="1"
{| class="wikitable" border="1"
|-
|-
The file/directory lowpath for this FS archive is a text path in the [[Savegames|savegame]] filesystem.
The file/directory lowpath for this FS archive is a text path in the [[Savegames|savegame]] filesystem.
=== ExtSaveData Archive Path Data Format ===
{| class="wikitable" border="1"
{| class="wikitable" border="1"
|-
|-
For FS, the file/directory lowpath is a text path in the [[extdata]] filesystem. For FSPXI, the file lowpath is a text path relative to the "/extdata/<ExtdataIDHigh>/<ExtdataIDLow>" directory on SD/NAND, for the cleartext extdata image to mount.
For FS, the file/directory lowpath is a text path in the [[extdata]] filesystem. For FSPXI, the file lowpath is a text path relative to the "/extdata/<ExtdataIDHigh>/<ExtdataIDLow>" directory on SD/NAND, for the cleartext extdata image to mount.
=== 0x2345678A Archive Path Data Format ===
{| class="wikitable" border="1"
{| class="wikitable" border="1"
|-
|-
The 0x14-byte lowpath is all-zero for accessing the title's main RomFS.
The 0x14-byte lowpath is all-zero for accessing the title's main RomFS.
=== [[RomFS]] ===
The raw FS image for the main CXI RomFS(for the current app this is accessible via archiveid 0x3) can be accessed via an all-zero 0xc-byte binary file-lowpath. The update RomFS for the current app can be accessed with the first u32 in the binary file-lowpath being set to 0x5. This allows access to the raw level-3 IVFC image: the user process must handle parsing the filesystem used in this image itself.
The raw FS image for the main CXI RomFS(for the current app this is accessible via archiveid 0x3) can be accessed via an all-zero 0xc-byte binary file-lowpath. The update RomFS for the current app can be accessed with the first u32 in the binary file-lowpath being set to 0x5. This allows access to the raw level-3 IVFC image: the user process must handle parsing the filesystem used in this image itself.