Jump to content
Setting up an AI agent? ReverseEngineering.wiki skill (works from the command line, no configuration): https://reverseengineering.wiki/skill/rewiki/SKILL.md · setup for every client, including MCP: https://reverseengineering.wiki/llms.txt · REWiki:Connect

Platform:Nintendo DS

From ReverseEngineering.wiki
Platform
Vendor Nintendo
Versions NDS, DS Lite, DSi, DSi XL
On this wiki Facts · Code · Notes · Topics

Nintendo's dual-screen handheld (2004): an ARM946E-S (ARM9) main CPU and an ARM7TDMI sub CPU, 4 MiB main RAM, two 256x192 screens. DSi (2008) adds more RAM and a second set of ARM9i/ARM7i binaries.

Overview

Two processors run separate programs: the ARM9 binary (game logic, graphics) and the ARM7 binary (sound, touch, Wi-Fi, power), both described in the cartridge header (Format:Nintendo DS ROM image (NDS)). They communicate through the IPC FIFO and a shared-memory region. Games are built with the devkitARM toolchain and Library:libnds (homebrew) or Nintendo's official NitroSDK/Nitro System (commercial; NitroFS, NARC and SDAT are its data formats).

File formats

Pitfalls

  • ARM9 and ARM7 have different address spaces; always look at the RAM address in the header to rebase the binaries (commonly ARM9 at 0x02000000 and 0x02000800 entry offsets for homebrew).
  • Overlays are loaded over the main binary at runtime; to analyse them load each at its ram_address.

Code & repositories

Library:libnds, Tool:ndstool.

  • https://github.com/devkitPro/libnds @ 84e6082ce27c87ed218fb369a9944644aa2243a6 · license: Zlib (declared by the contributor; GitHub's detector did not recognize a license file)
    libnds: include/nds/memory.h (tNDSHeader, DSi header, banner), dldi.h, bios.h, ipc.h.
    Tested on: source read, not run: source read · checked 2026-10-18; last activity 2026-02-19