SaveDataFilerSaveDataFiler tool provides features to view, import, and export the following types of save data.SaveDataFiler binary is in the following location in the CTR-SDK.
$HORIZON_ROOT/tools/TargetTools/CTR-TS/Release/SaveDataFiler.ciaCopy the above binary to an SD Card, and import it from DevMenu to the system's NAND memory. After that, it can be launched from the HOME Menu.（It can also be launched from
DevMenu.）$HORIZON_ROOT/tools/TargetTools/CTR-TS/Release/SaveDataFiler.csuUse the debugger to write the binary above to the CTR card. You can also start it from the HOME or Test Menu. You can also start it from the debugger's emulation memory.
SaveDataFiler into system NAND memory and use this to import or export user save data into/from backup memory.
| Button | Operation |
|---|---|
| ↑↓ | Move the cursor within the list |
| ←→ | Change tab |
| A | Select / Run |
| B | Cancel |
| X | Delete the selected item |
| Y | Write the save data to the SD Card (Note: See Writing to SD Cards) |
| R+Y | Destroy the selected files (Note: See Destroying Files) |
| L+R+START | Initializes shared expanded save data (Note: See Initializing Shared Expanded Save Data) |
SaveDataFiler to write save data and expanded save data to SD Cards.
sdmc:/filer/
+--- UserSaveData/
| +--- <The date and time saved>/
| +--- 00000000/ ←Data is saved below here（※）
| +--- 00000000.dat ←File containing format parameters
+--- ExtData/
+--- <The date and time saved>/
+--- <expanded save data number>/ ←Data is saved below here
+--- <expanded save data number>.dat ←File containing format parameters
Data saved in the above locations can be restored from the SD Tab.nn::fs::ResultVerificationFailed error is returned when they are loaded using functions from the FS library. You can use this to test error processing for files that are damaged when a card is removed during a write or a when a file is illegally spoofed.SaveDataFiler only attempts to reproduce a destroyed state in accordance with the specification: "The nn::fs::ResultVerificationFailed error is sometimes returned if a Read is performed on a region that has never been written to." Consequently, sometimes the file is not destroyed. If destruction is successful, an error is displayed on the file list.（See the User tab)
root:/test.txt --- (1)
Can not be destroyed, please retry.
[ OK (A) ]
| Number | Description |
|---|---|
| (1) | Displays the path to the file you tried to destroy. |
nn::fs::ResultVerificationFailed error will not be returned.）
Revision : 34302 --- (1)
File Type : file --- (2)
| LimitSize | LimitDir | LimitFile | Dup | --- (3)
| --- | 16 | 16 | ON |
Level : -5
Summary: 8
Module : 17
Desc : 392 --- (4)
File Size : 1024 bytes --- (5)
X: delete this file --- (6)
R+Y: destroy this file
:
| Number | Description | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| (1) | Revision number for the SaveDataFiler. | ||||||||
| (2) | Indicates the type of item selected in the lower screen. | ||||||||
| (3) | When the item selected on the lower screen is an archive, the format parameters of that archive are displayed. Their meanings are as follows.
| ||||||||
| (4) | When an error occurs during an archive mount or during an operation on an item selected from the lower screen, its Result value is displayed.To learn more about the content of errors, see the Description List for the fs library. | ||||||||
| (5) | When the item selected in the lower screen is a file, its size is displayed. -1 is displayed if the size could not be obtained. | ||||||||
| (6) | The operations guide is displayed. |
CTR Card F7FFF FFFFF :If an archive is corrupted, the corresponding
Result value appears on the upper screen when it is mounted.
../ Dir1/ Dir2/ File1 File2 : Read Error (0-512) File3 :When an error occurs during file operations, such as a damaged file, the filename is displayed in red. To display the corresponding
Result value on the upper screen, align the cursor with the filename.| Display | Description |
|---|---|
| Open Error | nn::fs::FileStream::TryInitialize returned an error. There was a failure in opening the file. |
| Read Error | nn::fs::FileStream::TryRead returned an error. There was a failure when reading the file.At the same time, the byte at which the read error occurred is also displayed. ( SaveDataFiler reads in units of 1MB, so the actual region where the error occurs may be smaller than this.） |
| Size Error | nn::fs::FileStream::TryGetSize returned an error. There was a failure in getting the file size (metadata).However, if the system fails to get the metadata, it will also fail to open the file. Thus, an Open Error will generally be displayed. |
00000001 00000002 -- broken -- 00000003 :When an archive is corrupt (when the
nn::fs::MountExtSaveData function returns an error), the number is displayed in red. When the cursor is aligned above the filename, the result value is displayed in the upper screen.
user : 20110101000000 : 00000000 user :20110101121530 : 000f7fff ext : 20110101000000 : 00000001 ext : 20110102141516 : 00000002 : : : (1) (2) (3)
| Number | Description | ||||
|---|---|---|---|---|---|
| (1) | Indicates the save data type.
| ||||
| (2) | This is the directory name (the date and time saved) on the SD Card. | ||||
| (3) | The meaning of this item depends on the save data type.
|
SaveDataFiler.CONFIDENTIAL