Revision as of 01:07, 25 April 2016

NOTE: This Title list is a condensed version, only the System Titles lists are full lists. For a full list of titles on Nintendo's CDN, see here. The reports/title-lists from here are automatically obtained from the system update SOAP.

Regardless of version, the ExeFS:/.code for mset is the same for USA/EUR/JPN. The 4.0.0-7 version of mset(4.1.0-8 for TWN) has the same ExeFS:/.code for all regions(JPN, USA, EUR, CHN, KOR, TWN). The 5.0.0-11 mset ExeFS:/.code is the same for all regions as well, except for CHN. The 7.0.0-13 mset ExeFS:/.code is unique for the following regions: CHN, KOR, and TWN.

dmnt, debugger sysmodule. This use devunit-only HIO for devunit<>pc comms. This only exists for development units(launched by NS during startup depending on certain Configuration_Memory fields' values). This is installed at the factory, then later deleted at the factory on retail units.

Once Home Menu finishes loading, all of the above system modules are running, except for MP, RO, and act which are automatically loaded when a process requires them. When PM-module terminates processes, it will check whether the processes listed as dependencies for this process are listed as dependencies for other processes. Any processes which are no longer listed in any processes dependencies lists are then terminated. On New_3DS, the only New3DS-specific system-module which automatically gets loaded during system boot is qtm.

All of the above system modules use the "BASE" memory-region(specified in the exheader), except when listed otherwise for certain modules.

When handling the exheader dependency list starting with 8.0.0-18, Old3DS FIRM PM-module now skips handling titles in this list which have any bits in programID-low bitmask 0xF0000000 set(with 8.0.0-18 this is hard-coded). The exheader dependency list handling change is for the New 3DS system-module(s), which do not exist on Old3DS. When the New3DS pm-module is launching any title except NS, it first attempts to launch the title with programID-low bitmask 0x20000000 set, then with that bitmask clear if launching fails.

NATIVE_FIRM and SAFE_MODE_FIRM for the initial versions are exactly the same, besides core-version fields. SAFE_MODE_FIRM is used for running SAFE_MODE titles, on retail SAFE_MODE_FIRM seems to be only used for running the System Updater application. When a GBA VC title is launched, AGB_FIRM is launched to handle running this title. GBA VC savegames stored under SD card /title/<TID>/data use a custom format, this is handled by AGB_FIRM.

TitleID Low

Description

USA/EUR/JPN Versions

CHN Versions

KOR Versions

TWN Versions

00000001

Unknown, very similar to SAFE_MODE_FIRM. Exists only on dev units and seems to only be used by SystemUpdaters.

This titleID-high/programID-high is used for the titles sent over Download Play. Only one 00040001 Download Play title is installed to NAND /title at a time. There can be a maximum of 255 Download Play child titles per Unique ID, indexed by Title ID Variation. The legal index range: 0x0 - 0xff.

TWL (DSi) Titles

Content Category

Bit Mask(s)

Category Bit Mask

Application (DSiWare)

TWL|0x4

0x8004

System Application

TWL|0x1|0x4

0x8005

System Archive

TWL|0x1|0x2|0x4|0x8

0x800F

Bitmask 0x1 for TWL titles denotes a system title (determining whether the title will be updated during a System Update). It appears to be sufficient, but not necessary, to make the title invisible on the Home menu.

0004800F - System Data Archives

New system updates only block DS flash-cards when the above whitelist was updated, or when TWL_FIRM was updated. The whitelist contains the data used for detecting flash-cards, this is used by TWL_FIRM.

00048004 - DSiWare

Although these have a titleID high separate from DSi and a titleID is stored in the SRLs, the content of these SRLs are identical to DSi.