Source review: October 11, 2026. Follow the linked DSi Guide and DS-Homebrew documentation for your exact setup. Their supported installers and procedures can change.
Understand the menu and loader
TWiLight Menu++ provides a launch menu and settings for the DS(i) ecosystem. nds-bootstrap is a separate component that loads supported DS(i) cartridge dumps, DSiWare and DS-mode homebrew through documented paths. Seeing a file icon in the menu does not mean every application has the same hardware access or compatibility. Record the menu version, nds-bootstrap version, entry point and storage location when comparing a result with a compatibility report.
Install the correct package
The DS-Homebrew installation page specifies the DSi archive rather than the 3DS or flashcard archive. Its basic root layout includes _nds, BOOT.NDS and the supplied roms directory. Additional files depend on a configuration such as hiyaCFW or ntrboot. Follow the relevant branch and preserve existing saves before refreshing the package. If you do not yet have a way to run homebrew, start with the DSi Guide; copying menu files alone does not make a stock console execute them.
Start with a small homebrew test
Use an original program from its developer and keep its documentation with the file. Confirm the program's expected data-directory layout and whether it requires DS mode, DSi mode or an accompanying loader. Test a simple program before adding themes, optional emulators or per-game settings. This establishes whether the launch path works without making a large collection of files part of the first diagnosis. Return to the same test after an update so you can identify when behavior changed.
Diagnose a single title methodically
For a game-card dump, compare the clean source file and checksum, loader settings and the project's compatibility notes. Make one change at a time and preserve the original save. A white screen can arise at the storage, launch or application layer; it is not enough information to choose a NAND restore. If the menu itself works but one program fails, record that fact and isolate the program's dependencies. If the menu never starts, return to file layout and the boot target first.
Maintain settings and development tools
Archive working configuration before changing several releases together. Keep game saves separate from optional artwork and cache files, and verify where a particular emulator writes its own saves. Do not assume every add-on has identical compatibility to nds-bootstrap. For original development, use the actual toolchain and libraries specified by the program, retain compiler logs and test both an emulator and real DSi when relevant. A useful bug report includes versions, a reproducible input sequence and the smallest failing example. That level of detail helps the project distinguish a new regression from a pre-existing limitation or an incorrect installation.
Sources and project documentation
- DS-Homebrew: installing TWiLight Menu++ on DSi
- DS-Homebrew: nds-bootstrap manual
- DS-Homebrew: menu FAQ and troubleshooting
For a system-wide boot failure, continue with recovery triage.