Running Applications Overview

A set of Cafe SDK shell scripts control program execution from the host PC. The sequence of scripts varies depending on the boot mode setting for the CAT-DEV.

Differences Between NAND Mode and PCFS Mode

The following is a table summary of the differences between NAND mode and PCFS mode.

Execution Environment Behavior
setbootmode How Launched Application to Run Launched From1 Available for CAT-R
PCFS (Supported in Cafe SDK 2.10 →) caferun PC RPX PC ($CAFE_ROOT) No
cafediscrun CAT-DEV (HDD) / PC wumad PC ($CAFE_ROOT) No
System Config Tool ODD / CAT-DEV (NAND) / CAT-R (NAND) / USB Installed Application PC ($CAFE_ROOT) No
cafediscrun CAT-DEV (HDD) / PC wumad CAT-DEV (NAND) No
System Config Tool CAT-DEV (NAND) / CAT-R (NAND) Installed Application CAT-DEV (NAND) / CAT-R (NAND) Yes

1 OS, Overlay Applications, System Settings, Application Save Data, Mii and Account Database.

Characteristics of the Two Boot Modes

The devkit boot mode is set by the CAFE_BOOT_MODE environment variable. By default, SDK version 2.04 and later devkits boot from NAND but execute applications from the host PC (via PCFS).

The update procedure for a devkit in NAND boot mode is the same update method that is used by retail systems. Before attempting to change directory settings, ensure that the devkit firmware is updated properly. For information about how to update firmware on the devkit, see CAT-DEV System Update.

For information about how to change boot modes, see Change CAT-DEV Boot Modes.

Running Applications in NAND Boot mode

In the NAND boot mode, applications are launched from the native file system on the host PC. However, the firmware, operating system, drivers, and System Config Tool are installed to and executed from the internal NAND flash storage on the CAT-DEV. After the CAT-DEV is powered ON, explicitly boot the system into System Config Tool before running your application.

NAND Boot mode more closely resembles the boot and launch sequences of the retail console system. It is a useful test of applications and their startup and shutdown sequences.

For more information on how to exit applications and return to System Config Tool, see Multicore Processing on the Wii U.

Running Applications in PCFS-Boot Mode

In the PCFS boot mode, applications are written, compiled, and executed directly from the host PC. The CAT-DEV host bridge uses the native file system on the host PC as an emulated storage device.

After the CAT-DEV is powered ON, open a Cafe Cygwin shell, and then:

Using the Wii U Menu to Test Applications

The Wii U Menu enables you to test your applications during development on a CAT-DEV in the retail console environment. For more information about the retail console system features, see Wii U Overview: System Features on your local Nintendo developer support group website.

The following system features are not available when using the Wii U Menu on a CAT-DEV:

The following APIs and features cannot be tested with the SDK alone. Use the Wii U Menu:

To install the Wii U Menu, download the Wii U Menu Changer for the appropriate regions from your local Nintendo developer support group website. Unzip the file to a location on your hard drive, and then follow the instructions in Readme_WiiU_MenuChanger.html.

Under the following conditions, an application installed in NAND is not debugged and only the title ID is updated.
  • The application is concurrently installed in NAND storage and USB storage.
  • The application is debugged with an older version of the Cafe SDK.

See Also

File System Emulation
Application Configuration

Revision History

2015/03/26 Clarify debugging case when an application is in both NAND and USB.
2014/05/22 Updated links to NAND and PCFS modes.
2014/03/24 Re-ordered subsection.
2014/02/21 Added feedback for table.
2014/02/21 Added NAND PCFS table.
2013/05/08 Automated cleanup pass.
2012/01/23 Updates for System Config Tool
2011/02/21 Initial version.