NAND Processing Sequence

The processing sequence shown here is just one example. The application does not need to follow this exactly. Note that the messages used in the figure after the NANDCheck[Async] functions are based on the Wii Message List. If the Wii Message List has been updated more recently than the Revolution SDK, however, the list in the figure may be out of sync. Please check the latest version of the Wii Message List.

Description (Figure 1)

• When there is insufficient free space and insufficient free inodes at the same time, give priority to messages that send a notification about insufficient free space.

Description (Figure 2)

• The green box in the upper-right corner of Figure 2 shows general NAND function calls. Note that the information is slightly different for the NANDSimpleSafe series API, so please also see the description for Figure 3.
• The NAND_RESULT_CORRUPT error code indicates that all Wii system memory has been corrupted to an irreparable state. If all Wii system memory has been corrupted, you also cannot expect the Wii to restart. Therefore, if this error is encountered, not only must you stop any application program processes, but also disable the reset/shutdown processes (which are normally enabled) that correspond to the RESET/POWER buttons, and as much as possible give first priority to notifying the player of the contents of this error message.
• The appearance of NAND_RESULT_UNKNOWN or an unexpected error code is strongly suspected to be an SDK bug. As you might expect, the system's operation cannot be guaranteed if these errors are encountered, so we recommend that you display the prescribed error message and do not let control return to the original processing routine of the application program.

Description (Figure 3)

• Figure 3 does not give the flow when a call to the NAND API returns error codes such as NAND_RESULT_CORRUPT, NAND_RESULT_BUSY, and NAND_RESULT_ALLOC_FAILED. See the description of Figure 2.
• If NAND_RESULT_ECC_CRIT or NAND_RESULT_AUTHENTICATION is returned from a call to the NANDSimpleSafeOpen[Async] functions, the original file may be corrupted. As a result, after calling the NANDSimpleSafeCancel[Async] functions to deallocate resources, proceed to notify the player that the save file has been corrupted, and ask for confirmation to delete the file (refer to Figure 2).
• If NAND_RESULT_ECC_CRIT or NAND_RESULT_AUTHENTICATION is returned from a call to the NANDRead[Async] or NANDWrite[Async] functions in the center of Figure 3, this indicates that the temporary files created internally by the NANDSimpleSafe-type functions are corrupted (the content of the original file is most likely unchanged). In contrast to the above case, do not proceed directly to the confirmation of deletion of the damaged file; instead, redo the save process from the beginning.

Revision History

2009/11/20 Replaced the messages in Figures 1 and 2 to synchronize with the Message List.
2009/05/22 Replaced text in Figures 1 and 2. Replaced [Save Data screen] in the message with [Data Management screen].
2009/02/03 Replaced text in Figure 2. Deleted flow to NAND_RESULT_MAXBLOCKS and NAND_RESULT_MAXFILES. In line with this change, deleted the descriptions of these errors.
2007/06/xx Replaced text in Figure 2. Added the flow of NAND_RESULT_UNKNOWN and of unexpected result codes.
2007/05/09 Added an explanation for each figure.
2007/05/09 Added a figure for the error processing sequence when NANDSimpleSafe-related functions are in use.
2007/05/09 Moved the explanation for supplementary items.
2007/02/xx Added a supplementary note concerning the case in which both free space and free inodes are insufficient at the same time.
2006/11/30 Added support for the error codes NAND_RESULT_ALLOC_FAILED, NAND_RESULT_MAXBLOCKS and NAND_RESULT_MAXFILES.
2006/09/19 Standardized terminology. Deleted the word "entry."
2006/08/30 Initial version.

CONFIDENTIAL