Filesystem services

Services

Filesystem service "fs:USER"

You can at most have 32 FS archive handles.

Command Header	Available since system version	Description	Required exheader access info bitmask
0x000100C6	?	Dummy1	None
0x040100C4	?	Control	None
0x08010002	?	Initialize	None
0x080201C2	?	OpenFile	None
0x08030204	?	OpenFileDirectly	None
0x08040142	?	DeleteFile	None
0x08050244	?	RenameFile	None
0x08060142	?	DeleteDirectory	None
0x08070142	?	DeleteDirectoryRecursively	None
0x08080202	?	CreateFile	None
0x08090182	?	CreateDirectory	None
0x080A0244	?	RenameDirectory	None
0x080B0102	?	OpenDirectory	None
0x080C00C2	?	OpenArchive	Each archive ID code has separate access info bitmasks, if it has any
0x080D0144	?	ControlArchive	None
0x080E0080	?	CloseArchive	None
0x080F0180	?	Obsoleted_2_0_FormatThisUserSaveData	None
0x08100200	?	Obsoleted_3_0_CreateSystemSaveData	0x4, for when the input saveID doesn't match the exheader saveID
0x08110040	?	Obsoleted_3_0_DeleteSystemSaveData	0x1004, for when the input saveID doesn't match the exheader saveID
0x08120080	?	GetFreeBytes	None
0x08130000	?	GetCardType	0x1017
0x08140000	?	GetSdmcArchiveResource	None
0x08150000	?	GetNandArchiveResource	0x1007
0x08160000	?	GetSdmcFatfsError	0x2
0x08170000	?	IsSdmcDetected	None
0x08180000	?	IsSdmcWritable	None
0x08190042	?	GetSdmcCid	0x2
0x081A0042	?	GetNandCid	0x2
0x081B0000	?	GetSdmcSpeedInfo	0x2
0x081C0000	?	GetNandSpeedInfo	0x2
0x081D0042	?	GetSdmcLog	0x2
0x081E0042	?	GetNandLog	0x2
0x081F0000	?	ClearSdmcLog	0x2
0x08200000	?	ClearNandLog	0x2
0x08210000	?	CardSlotIsInserted	0x1017
0x08220000	?	CardSlotPowerOn	0x2
0x08230000	?	CardSlotPowerOff	0x2
0x08240000	?	CardSlotGetCardIFPowerStatus	0x2
0x08250040	?	CardNorDirectCommand	0x2
0x08260080	?	CardNorDirectCommandWithAddress	0x2
0x08270082	?	CardNorDirectRead	0x2
0x082800C2	?	CardNorDirectReadWithAddress	0x2
0x08290082	?	CardNorDirectWrite	0x2
0x082A00C2	?	CardNorDirectWriteWithAddress	0x2
0x082B00C2	?	CardNorDirectRead_4xIO	0x2
0x082C0082	?	CardNorDirectCpuWriteWithoutVerify	0x2
0x082D0040	?	CardNorDirectSectorEraseWithoutVerify	0x2
0x082E0040	?	GetProductInfo	0x1005
0x082F0040	?	GetProgramLaunchInfo	0x1005
0x08300182	?	Obsoleted_3_0_CreateExtSaveData	0xC, for when the input extdataID doesn't match the exheader extdataID
0x08310180	?	Obsoleted_3_0_CreateSharedExtSaveData	0x1005
0x08320102	?	Obsoleted_3_0_ReadExtSaveDataIcon	0x100D, for when the input extdataID doesn't match the exheader extdataID
0x08330082	?	Obsoleted_3_0_EnumerateExtSaveData	0x1005
0x08340082	?	Obsoleted_3_0_EnumerateSharedExtSaveData	0x1005
0x08350080	?	Obsoleted_3_0_DeleteExtSaveData	0x100D, for when the input extdataID doesn't match the exheader extdataID
0x08360080	?	Obsoleted_3_0_DeleteSharedExtSaveData	0x1005
0x08370040	?	SetCardSpiBaudRate	0x2
0x08380040	?	SetCardSpiBusMode	0x2
0x08390000	?	SendInitializeInfoTo9	None
0x083A0100	?	GetSpecialContentIndex	0x1005
0x083B00C2	?	GetLegacyRomHeader	0x1015
0x083C00C2	?	GetLegacyBannerData	0x1015
0x083D0100	?	CheckAuthorityToAccessExtSaveData	0x44
0x083E00C2	?	QueryTotalQuotaSize	None
0x083F00C0	?	Obsoleted_3_0_GetExtDataBlockSize	None
0x08400040	?	AbnegateAccessRight	?
0x08410000	?	DeleteSdmcRoot	0x1005
0x08420040	?	DeleteAllExtSaveDataOnNand	0x1005
0x08430000	?	InitializeCtrFileSystem	None
0x08440000	?	CreateSeed	0x2
0x084500C2	?	GetFormatInfo	?
0x08460102	?	GetLegacyRomHeader2	0x1015
0x08470180	?	Obsoleted_2_0_FormatCtrCardUserSaveData	0x6
0x08480042	?	GetSdmcCtrRootPath	0x100D
0x08490040	?	GetArchiveResource	?
0x084A0002	?	ExportIntegrityVerificationSeed	0x4000
0x084B0002	?	ImportIntegrityVerificationSeed	0x4000
0x084C0242	?	FormatSaveData	0x6, in some cases this write isn't needed however
0x084D0102	?	GetLegacySubBannerData	0x1015
0x084E0342	?	UpdateSha256Context	0x5
0x084F0102	?	ReadSpecialFile	None
0x08500040	?	GetSpecialFileSize	None
0x08510242	3.0.0-5	CreateExtSaveData	Shared extdata: 0x101005. Regular extdata in certain cases: 0xC
0x08520100	3.0.0-5	DeleteExtSaveData	Shared extdata: 0x101005. Regular extdata in certain cases: 0x10100D
0x08530142	3.0.0-5	ReadExtSaveDataIcon	0x10100D (this doesn't apply in certain cases, however)
0x085400C0	3.0.0-5	GetExtDataBlockSize	0x10100D (this doesn't apply in certain cases, however)
0x08550102	3.0.0-5	EnumerateExtSaveData	0x101005
0x08560240	3.0.0-5	CreateSystemSaveData	0x4 (this doesn't apply in certain cases, however)
0x08570080	3.0.0-5	DeleteSystemSaveData	0x1004 (this doesn't apply in certain cases, however)
0x08580000	3.0.0-5	StartDeviceMoveAsSource	0x2004
0x08590200	3.0.0-5	StartDeviceMoveAsDestination	0x2004
0x085A00C0	3.0.0-5	SetArchivePriority	None
0x085B0080	3.0.0-5	GetArchivePriority	None
0x085C00C0	3.0.0-5	SetCtrCardLatencyParameter	0xE
0x085D01C0	3.0.0-5	SetFsCompatibilityInfo	0x100001
0x085E0040	3.0.0-5	ResetCardCompatibilityParameter	0xE
0x085F0040	3.0.0-5	SwitchCleanupInvalidSaveData	0x12004
0x08600042	3.0.0-5	EnumerateSystemSaveData	0x2004
0x08610042	3.0.0-5	InitializeWithSdkVersion	None
0x08620040	3.0.0-5	SetPriority	None
0x08630000	3.0.0-5	GetPriority	None
0x08640000	3.0.0-5	Obsoleted_4_0_GetNandInfo	Stubbed, this returns an error
0x08650140	4.0.0-7	SetSaveDataSecureValue	0x121004 (in certain cases this doesn't apply, however)
0x086600C0	4.0.0-7	GetSaveDataSecureValue	0x121004 (in certain cases this doesn't apply, however)
0x086700C4	4.0.0-7	ControlSecureSave	0x121004
0x08680000	4.0.0-7	GetMediaType	None
0x08690000	4.0.0-7	Obsoleted_4_0_GetNandEraseCount	Stubbed, this returns an error.
0x086A0082	4.0.0-7	ReadNandReport	None
0x086B00C2	?	SetOtherSaveDataSecureValue	0x121004
0x086C00C2	?	GetOtherSaveDataSecureValue	0x121004
0x086D0080	?	BeginSaveDataMove	0x20004
0x086E00C0	?	SetThisSaveDataSecureValue	None
0x086F0040	?	GetThisSaveDataSecureValue	None
0x087000C2	?	CheckArchive	None
0x08710140	?	TransferSaveDataCMAC	0x20004
0x08720200	?	RegisterTitleContentOverlay	0x80004
0x08730100	?	UnregisterTitleContentOverlay	0x80004
0x08740000	?	UnregisterAllTitleContentOverlays	0x80004
0x08750140	?	SetSaveArchiveSecureValue	None
0x087600C0	?	GetSaveArchiveSecureValue	None
0x08770140	?	RegisterSpecialTitleContent	0x80004
0x08780100	?	UnregisterSpecialTitleContent	0x80004
0x087900C2	?	Same as GetLegacyBannerData, except for the last parameter this internally passes u8 value 0x1 instead of 0x0, for the FSPXI command.	0x101015
0x087A0180	9.6.0-X	AddSeed	0x200000
0x087B0080	9.6.0-X	GetSeed	0x200000
0x087C0080	9.6.0-X	DeleteSeed	0x200000
0x087D0000	9.6.0-X	GetNumSeeds	0x200000
0x087E0042	9.6.0-X	ListSeeds	0x200000
0x087F0100	9.6.0-X	TitleContentHasSeed	0x200000
0x08800880	9.6.0-X	AddTitleTag	0x200000
0x08810080	9.6.0-X	GetTitleTag	0x200000
0x08820080	9.6.0-X	DeleteTitleTag	0x200000
0x08830000	9.6.0-X	GetNumTitleTags	0x200000
0x08840042	9.6.0-X	ListTitleTags	0x200000
0x088500C0	9.6.0-X	CheckTitleSeed	0x200000
0x088600C0	11.1.0-X	CheckUpdatedDat	0x80000

Note: The question marks from Dummy1 to GetSpecialFileSize on the "available since system version" field are mainly there because I think that most of these are necessary for the main system to function, so theoretically that would mean that since the creation of the 3DS these were available, or since launch if that makes more sense. But because of the peculiar nature of some of the functions, they will remain question marks until they can be confirmed 100%.

When access rights are required for a command, at least one of the bits in the process access info specified in the above table for the command must be set. Error 0xD9004676 is returned when a process attempts to use a command which it doesn't have access rights for the command. The exheader access info field is all zero's for most applications. Note that the permissions listed in the above table is for system-version v2.x, therefore permission bit(s) added with newer FIRM may be missing from this.

Each session for fs:USER has separate permissions, initially these are set to all zero's for new fs:USER sessions. The permissions/etc for fs:USER sessions are initialized via FS:Initialize(loaded from the user process exheader).

Filesystem service "fs:LDR"

This service is identical to fs:USER, except FS:OpenArchive archive 0x2345678E can only be accessed with fs:LDR.

ProgramRegistry service "fs:REG"

Command Header	Description
0x000100C6	Dummy1
0x040103C0	Register
0x04020040	Unregister
0x040300C0	GetProgramInfo
0x04040100	LoadProgram
0x04050080	UnloadProgram
0x04060080	CheckHostLoadId

Only two sessions can be opened for this service at a time, hence no other processes can use this due to pm-module and loader using this.

File and directory access

Files

File session handles obtained via FS:OpenFile and FS:OpenFileDirectly can be used to access files through a service-like interface, despite not being an actual service registered using SRV:RegisterService. To use this service-like interface, simply call the SendSyncRequest SVC with a file session handle, using the IPC buffer in thread-local storage for parameters and responses, just like you would with a proper service.

Command Header	Description
0x000100C6	Dummy1
0x040100C4	Control
0x08010100	OpenSubFile
0x080200C2	Read
0x08030102	Write
0x08040000	GetSize
0x08050080	SetSize
0x08060000	GetAttributes
0x08070040	SetAttributes
0x08080000	Close
0x08090000	Flush
0x080A0040	SetPriority
0x080B0000	GetPriority
0x080C0000	OpenLinkFile
0x0C010100	GetAvailable

Directories

Directory session handles obtained via FS:OpenDirectory are usable via a service-like interface, following the exact same procedure described above for file sessions.

Command Header	Available since system version	Description
0x000100C6	1.0.0-0	Dummy1
0x040100C4	1.0.0-0	Control
0x08010042	1.0.0-0	Read
0x08020000	1.0.0-0	Close
0x08030040	?	SetPriority
0x08040000	?	GetPriority

Archives

ArchiveId	Description	Accessible via FS	Accessible via FSPXI	Only accessible by Process9 internally	Requires binary Lowpath	Required exheader FS access info bitmask
0x00000003	SelfNCCH (including RomFS)	Yes	No	No	No	None
0x00000004	SaveData (the saveID/mediatype for this is loaded from data originally from the user process' exheader)	Yes	No	No	No	None
0x00000006	ExtSaveData	Yes	No	No	Yes	0x100D, when the input extdataID isn't listed in the exheader.
0x00000007	Shared ExtSaveData	Yes	No	No	Yes	None
0x00000008	SystemSaveData	Yes	No	No	Yes	0x4, when the input saveID doesn't match the exheader system-saveID.
0x00000009	SDMC	Yes	Yes	No	No	0x8E
0x0000000A	SDMC Write-Only	Yes	No	No	No	0x808E
0x12345678	ExtSaveData for BOSS	Yes	No	No	Yes	0x44
0x12345679	CARD SPI FS	Yes	Yes	No	No	0x16
0x1234567B	ExtSaveData, and ExtSaveData for BOSS	No	Yes	No	Yes
0x1234567C	SystemSaveData	No	Yes	No	Yes
0x1234567D	NAND RW	Yes	Yes	No	No	0x800
0x1234567E	NAND RO	Yes	Yes	No	No	0x200
0x1234567F	NAND RO Write FS	No	Yes	No	No	?
0x12345680	Extdata transfer. Used for transferring NAND Shared Extdata during system tranfers.	Yes	Yes	No	Yes	?
0x12345681	System Savedata transfer. Used for transferring System Save Data during system tranfers.	Yes	Yes	No	Yes	?
0x12345682	Unknown. There's code for this in spider v9.9, but that code isn't actually used.	Yes	No	No	Yes	?
0x2345678A	Title access. With FS, this allows accessing NCCH/NCSD contents (ExeFS, RomFS, checking if a content uses a seed, checking the validity of the installed seed). FSPXI, additionally, allows opening raw NCCH/NCSD NCCH contents and DSiWare contents for reading, along with encrypted save data.	Yes	Yes	No	Yes	0x1005
0x2345678B	Used internally by Process9 as the lowest level title access archive. Allows for opening various sections of a title (TMD, CMD, raw contents, DLC contents, raw save data (including public/private/banner saves for DSiWare), title and/or content import context files and /data directories for save data.	No	No	Yes	Yes
0x2345678C	Used internally to access Title Database (/dbs) files. For SD, title.db and import.db. For NAND, title.db, import.db, tmp_t.db, tmp_i.db, and jumpid.db.	No	No	Yes	Yes
0x2345678D	Used internally to access non-title /dbs files on the NAND: certs.db and ticket.db.	No	No	Yes	No
0x2345678E	FSPXI: Program Access (limited subset of merged main title + update/patch title access). For fs:LDR(used by the "loader" FIRM ARM11-process), only exefs:/.code. Not accessible with fs:USER.	Yes	Yes	No	Yes	None, see description.
0x567890AB	NAND CTR FS	No	Yes	No	No	?
0x567890AC	TWL PHOTO	Yes	Yes	No	No	?
0x567890AD	TWLS (DSi Sound stores recordings here). This is mapped to the FAT12 image stored in the file at Twln/shared2/0000.	No	Yes	No	No	?
0x567890AE	NAND TWL FS	Yes	Yes	No	No	0x100
0x567890AF	NAND W FS	Yes	Yes	No	No	0x100
0x567890B0	Internally creates the same "ID Storage" wrapper over the NAND that is used for SystemSaveData and Shared ExtData, but all operations are stubbed and return 0xE0C046F8.	No	Yes	No	No
0x567890B1	Gamecard SaveData (for check). This is a wrapper for UserSaveDataForCheck: the OpenArchive code for that is called with archive-lowpath TID=0/mediatype=2(gamecard).	Yes	No	No	No	0x6
0x567890B2	UserSaveData (for check). This is the same as the regular SaveData archive, except with this the savedata ID and mediatype is loaded from the input archive lowpath.	Yes	No	No	Yes	0x6
0x567890B3	AGB Save Data	No	No	Yes	No	-
0x567890B4	Similar to 0x567890B2 but can only access Accessible Save specified in exheader?	Yes	No	No	Yes	?

Archives listed as not requiring a binary lowpath, use lowpath type empty.

The above permission bitmasks are from v2.x, see the above Services section for how these are handled.

Archives CTR NAND, NAND RO Write FS, TWL NAND, NAND W FS, and CARD SPI FS require the corresponding process exheader access control mount flag to be set, in the exheader for any of the currently running ARM11 processes, for FSPXI. The access rights checked by FS module for archive mounting with fs:USER, are stored in the process' exheader accessinfo.

The CARDSPI archive allows access to the gamecard CARD1 raw savedata flash(aka "cardspi:/" in 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:

Value	Description
-1	Returned internally by Process9, when errors occur it seems(in particular when no nul-terminator was found in the input path). The data ptr is set to NULL.
0x0	INVALID - Specifies an invalid path
0x1	EMPTY - Specifies an empty path
0x2	BINARY - Non-text based path. Meaning is per-archive
0x3	ASCII - Text-based path with 7-bit ASCII characters padded to 8-bits each (signed char)
0x4	UTF16 - Text-based path with UTF-16 characters

In IPC requests, sizes of ASCII and UTF16 paths must include space for the null-terminator.

Binary LowPath

The format of the data that a binary LowPath points to is custom per archive.

SystemSaveData / Extdata / Shared Extdata Archive Path Data Format

DataAccessPath

Offset	Size	Description
0x0	0x1	u8 Mediatype
0x1	0x1	only for NAND data (System Savedata / Shared Extdata), otherwise left 0: Value Description 0 Accesses from/to nand:/data/<ID0 of current system> 1 Accesses from/to nand:/fixdata 2 Accesses from/to nand:/data/<ID0 from Device Move Context>
0x2	0x2	padding

SystemSaveData

Archive Path

Index word	Description
0	DataAccessPath
1	save ID low (save ID high is 0)

File Path

The file path is a cleartext ASCII or UTF16 file path (<file path>).

The file path would access the file at <base path>/sysdata/<save ID low>/<save ID high>/<file path>. Note that /<file path> refers to the virtual file system inside the <save ID high> file.

Archive Path

Index word	Description
0	DataAccessPath

File Path

Index word	Description
0	save ID low
1	save ID high

The file path would access the file at <base path>/sysdata/<save ID low>/<save ID high>.

Extdata / Shared Extdata

Archive Path

Index word	Description
0	DataAccessPath
1	ext save ID low
2	ext save ID high

This refers to the extdata filesystem structure's base directory at <base path>/extdata/<ext save ID low>/<ext save ID high>.

File Path

The file path is a cleartext ASCII or UTF16 file path (<file path>).

For FS Extdata, this would acccess <base path>/extdata/<save ID low>/<save ID high>/<directory ID>/<file ID>/<file path>, and /<file path> refers to the virtual file system inside the <file ID> file.

For FS / FSPXI Extdata Transfer, this accesses <base path>/extdata/<save ID low>/<save ID high>/<file path>.

UserSaveDataForCheck Archive Path Data Format

Index word	Description
0	Mediatype (must be non-zero)
1	Lower word saveid
2	Upper word saveid

The file/directory lowpath for this FS archive is a text path in the savegame filesystem.

0x567890B4 Archive Path Data Format

Index word	Description
0	Mediatype
1	Lower_word_saveid >> 8 ?
2	Unknown. Game calculate this using formula 0xFFFFFF00 | unknown_b

Title Access Archive Path Data Format

Title Access Type

Value	Description
0	High-level NCCH content access
1	Save data access (high-level, decrypted)
2	Raw content (low-level NCCH/SRL) access
3	Banner save data access (for DSiWare titles)
4	FS only: Save data transfer (internally uses generated data from FS:BeginSaveDataMove as the IV for "Save data access (low-level, encrypted)")
5	Save data access (low-level, encrypted)

NCCH Access Type

Value	Description
0	RomFS
1	exefs:/.code
2	System Menu Data (exefs:/icon, exefs:/banner, exefs:/logo)
3	NCCH Header(s)
4	"is seeded" check
5	Seed verify/validate

NCCH Header Access Type

Value	Description
0	Extheader (0x0-0x400)
1	Extheader AccessDesc (0x400-0x800)
2	Raw NCCH Header

Archive Path

Offset	Size	Description
0x0	0x8	Program ID (Title ID)
0xB	0x1	Media Type
0xC	0x4	padding

File Path

Offset	Size	Description
0x0	0x4	Title Access Type
0x4	0x10	Dynamic data depending on Title Access Type: High Level NCCH Access Save Data Access (high level) Raw Content FS only: Save Data Transfer Offset Size Description 0x0 0x4 Content index from TMD for NAND/SD titles NCSD partition index for gamecards 0x4 0x4 NCCH Access Type 0x8 0x8 Dynamic data depending on NCCH Access Type: For ExeFS, (System Menu Data / exefs:/.code), 8-byte ExeFS file name For Header Access, u64, NCCH Header Access Type For RomFS, u64, Allowed content types flag ((1 << allowed_type_a) | (1 << allowed_type_b)...) Offset Size Description 0x0 0x10 16-byte IV for save data crypto Offset Size Description 0x0 0x4 Content index from TMD for NAND/SD titles NCSD partition index for gamecards 0x4 0xC padding Offset Size Description 0x0 0x4 Save data transfer key from FS:BeginSaveDataMove 0x4 0xC padding
0x14	0x10	16-byte seed for titles that require one, or for validating a seed against the check value in the NCCH Header's check value. If the title does not use a seed, this should not be included and size 0x14 should be used instead of 0x24.

For encrypted save data access and banner save data access, the entire 0x10 portion of the dynamic data is left blank.

The "is seeded check" NCCH access type opens a virtual 1-byte file that reads either 0 or 1; this value is generated on-the-fly and will be 1 if ncchflags[7] has bit5 set (content uses seed), and 0 otherwise.

For NCCH sections that require a seed (e.g. .code, RomFS, etc.), the additional seed portion of the low path must be populated with the correct seed.

The "Seed Verify/Validate" NCCH access type also requires the seed portion of the lowpath. The target NCCH content is opened (with the opened file interface being stubbed, meaning no real reads/writes can be performed on it), and the given seed is used to calculate the seed check hash, and part of it is compared to the check value in the NCCH header. If it matches, opening the "file" succeeds, otherwise 0xD900458C is returned. If attempt is made to use the seed validation type on a content that does not use a seed, error 0xC92044E6 is returned.

FS Limitations

For FS, this archive functions the same, except for the following limitations:

- Only the title access types "High Level NCCH Access" and "High Level Save Data Access", and "Save Data Transfer" are allowed.

- For high level NCCH access, the types "RomFS", "System Menu Data", "Seeded check", and "Seed Check/Verify" are allowed.

- For "Seed Check/Verify", rather than providing the title seed in the file path (as is the case for FSPXI), the seed is retrieved from the seed database (meaning the file lowpath size is always 0x14 for FS).

Program Access / SelfNCCH access

Provides access to a "merged" archive of a base title and, optionally, a separate update (patch) title.

If no patch title exists, the base title is considered to be the patch title, i.e. turning all "patch" accesses into accesses to the base title.

Program Access Type

Value	Description	Accesses
0	RomFS ("unspecified" content type, the default)	Base title
1	exefs:/.code	Patch title
2	System Menu Data (exefs:/icon, exefs:/banner, exefs:/logo)	Base title
3	Save Data (high level, decrypted)	-
4	RomFS (all content types)	Base title
5	RomFS ("unspecified" content type, the default)	Patch title

Archive Path

Offset	Size	Description
0x0	0x8	u64, Program Handle from PXIPM:RegisterProgram

File Path

Offset	Size	Description
0x0	0x4	Program Access Type
0x4	0x8	Dynamic data depending on Program Access Type: ExeFS files (System Menu Data, etc.) RomFS of base title (all content types) 8-character ExeFS filename Offset Size Description 0x0 0x4 u32, content index of target content 0x4 0x4 padding

FS Limitations

- FSPXI allows all access types.

- When used through fs:LDR by loader, FS only provides access to exefs:/.code.

- For SelfNCCH access, the only allowed access types are "RomFS ("unspecified" content type, the default)" of the Base or Patch title, and "System Menu Data". Attempting to access "Save Data" results in error 0xE0E046BE, "RomFS (all content types)" in 0xF9604784, and "exefs:/.code" in 0xD9004676.

RomFS

Archives 0x3 and 0x2345678E both allow for accessing the level-3 IVFC images for RomFS access. The main CXI RomFS is accessible via an all-zero 0xc-byte binary file-lowpath. The update RomFS can be accessed with the first u32 in the binary file-lowpath being set to 0x5. The user must handle parsing the filesystem used in the exposed image itself.

With FSPXI the returned data for RomFS is the entire RomFS section from the NCCH, starting at the IVFC header.

The 0x3 archive is an interface for the 0x2345678E archive with the current process programID+mediatype. The file lowpath is 3-words. These words are written to 0x2345678E-archive file_lowpath+0, with the rest of that lowpath set to all-zero(lowpath is different from archive 0x2345678A). File lowpath:

Index word	Description
0	See above. The only values which FS-module doesn't allow to be used here are: 0x1: Error 0xE0E046BE. 0x3: Error 0xE0E046BE. 0x4: FS-module executes svcBreak when using this.
1-2	See above. Not validated by FS-module.

SEEDDB

With 9.6.0-X new System_SaveData with saveID 0001000F was added, this seems to be handled by FS-module itself, probably via the new service-cmds added to fsuser. Home Menu and NIM module have access to those commands.

The SEEDDB savedata contains the title-unique seed-data used for the new NCCH keyY generation added with FIRM 9.6.0-X.

Common Types

MediaType

Value	Description
0	NAND
1	SD
2	Game Card

SystemMediaType

Value	Description
0	CTR NAND
1	TWL NAND
2	SD
3	TWL Photo

OpenFlags

Bit	Description
0	Read
1	Write
2	Create

Attributes

Offset	Size	Description
0x0	0x1	Is Directory
0x1	0x1	Is Hidden
0x2	0x1	Is Archive
0x3	0x1	Is Read-Only

WriteOption

Offset	Size	Description
0x0	0x1	Flush
0x1	0x1	Update Time Stamp
0x2	0x1	Reserved
0x3	0x1	Reserved

DirectoryEntry

Offset	Size	Description
0x0	0x20C	UTF-16 Entry Name
0x20C	0xA	8.3 short filename name
0x216	0x4	8.3 short filename extension
0x21A	0x1	Always 1
0x21B	0x1	Reserved
0x21C	0x4	Attributes
0x220	0x8	Entry Size

ArchiveResource

Offset	Size	Description
0x0	0x4	Sector byte-size
0x4	0x4	Cluster byte-size
0x8	0x4	Partition capacity in clusters
0xC	0x4	Available free space in clusters

ProgramInfo

Offset	Size	Description
0x0	0x8	Program ID
0x8	0x1	Media Type
0x9	0x7	Padding

ProductInfo

Offset	Size	Description
0x0	0x10	Product Code
0x10	0x2	Company Code
0x12	0x2	Remaster Version

IntegrityVerificationSeed

Offset	Size	Description
0x0	0x10	AES-CBC MAC over a SHA256 hash, which hashes the first 0x110-bytes of the cleartext SEED.
0x10	0x120	The nand/private/movable.sed, encrypted with AES-CBC using the above MAC for the counter.

ExtSaveDataInfo

Offset	Size	Description
0x0	0x4	DataAccessPath
0x4	0x8	Save ID
0xC	0x4	Reserved

SystemSaveDataInfo

Offset	Size	Description
0x0	0x4	DataAccessPath
0x4	0x4	Save ID

SecureValueSlot

Value	Description
0x1000	SD Application

SecureValueEntry

Offset	Size	Description
0x0	0x4	u32, Secure Value Slot
0x4	0x1	When used as an input entry: Value Description 0 This entry should be removed. 1 This entry should be updated with the given value. When returned from a command: Value Description 0 No entry with the given slot and title ID was found, or: this entry is unused. 1 The entry with the given slot and title ID was found, or: this entry is used.
0x5	0x3	padding
0x8	0x8	u64, Secure Value

TitleTag

Offset	Size	Description
0x0	0x4	Magic, PREP (PREPurchase install)
0x4	0x4	s32, Release date year
0x8	0x1	u8, Release date month
0x9	0x1	u8, Release date day
0xA	0x2	u16, Country code
0xC	0x4	u32, Seed status (0: not downloaded yet, 1: last download attempt failed, 2: seed installed successfully)
0x10	0x4	Result code from last seed installation attempt
0x14	0x4	Support error code from last seed installation attempt
0x18	0x68	reserved padding (unused)

CardSpiBaudRate

Value	Description
0x0	512KHz
0x1	1MHz
0x2	2MHz
0x3	4MHz
0x4	8MHz
0x5	16MHz

CardSpiBusMode

Value	Description
0x0	1-bit
0x1	4-bit

SpecialContentType

Value	Description	Found in
0x1	CTR (Old3DS) Update Partition	Gamecards
0x2	Manual	Gamecards, Digital titles
0x3	DLP Child	Gamecards, Digital titles
0x4	KTR (New3DS) Update Partition	Gamecards

DeviceMoveContext

Offset	Size	Description
0x0	0x10	IVs (ID0 of source console)
0x10	0x10	Encrypt Parameter (used to calculate the IV for encryption)

Errors

See Filesystem_services_PXI.