2. Types of Applications

You can develop the following types of 3DS applications.

2.1. Card-Based Software

These applications combine ROM and save data and are written to a Nintendo 3DS Game Card. The packaged software sold in stores is one example of card-based software.

The following table shows where an application is saved, how large it is, and how it handles save data, extended save data, and e-manuals.

Table 2-1. Characteristics of Card-Based Software
Item Description
Save location Nintendo 3DS Game Card
Size

Card1: Between 128 MB and 4 GB. (The actual usable size is different.)

Card2: Between 512 MB and 2 GB. (Shared with save data.)

Save location Backup region of a Game Card. (Differs from the ROM region.)
Size

Card1: Between 128 KB and 512 KB. (The actual usable size is different.)

Card2: Specifiable in units of 1 MB (up to half the capacity of the card).

Extended Save Data Yes. (Extended save data can be deleted from the Extra Data Management screen.)
E-manual support Required
Warning:

Contact Nintendo at support@noa.com before using Card2.

2.2. Downloadable Applications

These applications are imported to an SD card. Software that is purchased in Nintendo eShop and software that is downloaded via SpotPass are two examples of downloadable applications.

The following table shows where an application is saved, how large it is, and how it handles save data, extended save data, and e-manuals.

Table 2-2. Characteristics of Downloadable Applications
Item Description
Save location SD card
Size

A card application that supports download sales can be up to 4 GB.

If an application is only available for sale by download, it can generally be up to 512 MB. (Contact Nintendo support at support@noa.com if you require a size greater than 512 MB.)

Save location SD card. (A save data region is allocated when the application is imported. This region is deleted along with the downloadable application. You cannot delete the save data alone.)
Size Between128 KB and 512 KB. (The actual usable size is different.) If a larger size is required, contact Nintendo support at support@noa.com.
Extended Save Data Yes. (Extended save data is not deleted along with the application. However, it can be deleted from the Extra Data Management screen.)
E-manual support Required
Warning:

If you submit a master submission as a downloadable application (CIA file), you will not be able to request sales as a card-based application later. If you are considering dual distribution, submit the master submission as a card-based application (CCI file).

2.2.1. Importing Downloadable Applications

To run a downloadable application, you must first import it to an SD card.

The retail version of the application is imported after it has been completely downloaded from Nintendo eShop or elsewhere.

You can use either the DevMenu or the PARTNER-CTR software debugger to import an application during development.

To import an application with the DevMenu, you must first write its CIA file to an SD card.

To import an application with the PARTNER-CTR software, either load the CIA file (you can even use a drag-and-drop operation) or run the IMPORT command.

To import an application with the PARTNER-CTR software, either load the CIA file (you can even use a drag-and-drop operation) or run the IMPORT command.

Note:

For more information about how to use DevMenu, see the DevMenu page in the CTR Tools section of the CTR-SDK documentation.

For more information about the PARTNER-CTR commands, see the PARTNER-CTR Debugger Manual.

For more information about the IS-CTR-DEBUGGER commands, see the IS-CTR-DEBUGGER Help.

2.2.1.1. Importing and Overwriting Downloadable Applications

After a downloadable application is imported, it is identified by its unique ID. After you have imported a downloadable application, you cannot import another downloadable application with the same unique ID unless it has a newer version, in which case the new application overwrites the existing one.

Save data is normally preserved, even when an imported application overwrites an existing application. To prevent bugs from occurring, you must manage save data versions and other such information carefully. If the save data region for the application being imported is not the same size as the save data region for the application that has already been imported, the entire save data region will be cleared.

Warning:

You are prohibited from resizing save data when you change the retail version.

Use the DevMenu or the Software Management screen under System Settings to delete downloadable applications that have been imported, when the save data region needs to be cleared, or before importing an earlier version of a downloadable application for debugging. Note that extended save data is not deleted along with a downloadable application.

2.2.2. Advance Download

An advance download function is used to enable a downloadable application to be purchased and downloaded from Nintendo eShop before its release date.

See the chapter about Advance Download in the 3DS Overview.

2.2.3. Demos

A demo can be developed as a downloadable application.

The retail and demo versions of a downloadable application are imported as separate applications, even if they have the same unique ID. This means that you cannot transfer the demo's save data itself to the retail application, although you can share extended save data.

Use caution when sharing extended save data, though. If the demo is started after starting the retail version of your application, the demo uses the data that was updated by the retail application.

A demo's save data is deleted along with the demo, but extended save data is not.

Note:

For more information about the demo version, see Nintendo 3DS Demo Version Creation Instructions – Download Format.

2.2.4. Differences From Card-Based Software, WiiWare, and Nintendo DSiWare

See the chapter about downloadable applications in the 3DS Overview.

2.2.5. Importing TWL NAND Applications

You can use the -srl option for ctr_makecia to create a CTR CIA file from an SRL file that was built as a TWL NAND application. This CIA file can be imported to an SD card just like a downloadable application.

For more information, see the reference for the ctr_makecia tool in the CTR-SDK documentation.

 

Sample Usage:

ctr_makecia32.exe -srl MyTwlApp.srl -o MyTwlApp.cia 
Warning:

Use a CIA file created from an SRL file to check the operations of a Nintendo DSiWare title on a 3DS system. After you have imported your application, you can use the PARTNER-CTR software to run it but not to debug it.

2.3. Client Programs

Host devices distribute these applications to client devices via Download Play.

The following table shows where an application is saved, how large it is, and how it handles save data, extended save data, and e-manuals.

Table 2-3. Characteristics of Client Programs
Item Description
Save location System NAND memory. (Only a single program is saved at a time. Whenever a program is received, it overwrites the previous one. The same version of the same program is not re-downloaded.)
Size Up to 32 MB (uncompressed).
Save data No
Extended save data Yes. (Extended save data is not deleted when a client program is overwritten. However, it can be deleted from the Extra Data Management screen.)
E-manual support Not Required
Comments Client programs are not displayed in the HOME Menu. The banner (model and sound) is not required.
Note:

The configtool can be used to force the same version of the same program to be downloaded while debugging Download Play.

Warning:

Although a downloadable application can become a Download Play server, at this time it cannot start a system update on connected client devices. When a downloadable application is running on a host device, it silently rejects connections from any client device that needs a system update. Applications must display a message provided by Nintendo before they start Download Play.

For more information, see the CTR-SDK API Reference for the DLP library.


CONFIDENTIAL