ov114 β€” overlay detail

DS game only γ¨γ‚“γŒγ‚Šγƒœγ‚¦γ‚·γ¨γŠγ—γ‚ƒγ‚Œγͺまほう぀かい The field guide documents the DS game's internals.

containers: coordinate/crdires.lzs, crdires

ov114 coordinate

containers: coordinate/crdires.lzs, crdires

Header

Numeric metadata for this overlay as read from the overlay table at ROM offset 0x8DE00 (per-entry stride 32 bytes). Function counts, data-item counts, and the call-graph fan-out are from a Ghidra 11.3.1 headless auto-analysis pass.

Overlay ID 114
File ID 114
RAM load address 0x0215e4a0
RAM size 5,568 bytes (0x15c0)
BSS size 0 bytes
On-disk compressed size 4,752 bytes
Compression flag 0x1 (BLZ-compressed)
Functions 24
External calls 77
Jump tables 1
Data items 78
Code coverage 67% (3,750 of 5,568 bytes)

Reading the binary

The overlay ships on the cart at file ID 114 under the BLZ code-LZ compression wrapper (the same backward-LZ scheme Nintendo uses for executable ARM9 code). At load time the engine reads the overlay table entry at ROM offset 0x8DE00 + 114 * 0x20, allocates the destination RAM region at 0x0215e4a0, decompresses the body in-place (if compressed), and resolves any external relocations.

To inspect this overlay outside the running game, decompress overlay/overlay_114.bin with ndspy.codeCompression.decompress() (Python ndspy library) and load the resulting plaintext into Ghidra or IDA at base address 0x0215e4a0. The raw Ghidra auto-analysis dump used to populate this page lives at notes/overlay_knowledgebase/raw/ov114.json; the per-overlay descriptive markdown is at notes/overlay_knowledgebase/ov114.md.

Embedded strings

1 UTF-16 LE string live inside this overlay's compiled binary. These addresses are absolute (inside the overlay's RAM image after load). The text is stored as little-endian UTF-16 code units, NUL-terminated.

0x0215e9b4 `九ジ栀妑`

Container references

Distinct container basenames referenced by this overlay. Each is loaded via the content cache by passing the basename string to a lookup that resolves it to a file ID in the ROM's FAT. The path column shows the file's location in the clean extract, where resolved.

Unresolved

These container basenames appeared in the overlay's string table but no file of that name was found in the clean extract. Most are false-positive ASCII matches (function names, register maps, fragments of other strings); a few may be containers that the overlay names but never actually opens. Listed for completeness.

Function list

Functions Ghidra auto-identified inside this overlay's RAM range. Names prefixed FUN_ are auto-generated from the function's entry address; size is in bytes; the "calls" column counts both intra-overlay branches and external ARM9 call targets. The "strings" column counts how many UTF-16 LE strings each function references.

Show all 24 functions
# Address Size Calls Strings Role hint
1 0x0215e534 28 3 0 trampoline / small helper
2 0x0215e550 54 6 0 code
3 0x0215e588 446 15 0 code
4 0x0215e758 12 0 0 trampoline / small helper
5 0x0215e768 1,674 90 1 refs: coordinate/crdires.lzs
6 0x0215ee40 16 1 0 trampoline / small helper
7 0x0215ee50 20 1 0 trampoline / small helper
8 0x0215ee64 4 0 0 trampoline / small helper
9 0x0215ee68 4 0 0 trampoline / small helper
10 0x0215ee6c 4 0 0 trampoline / small helper
11 0x0215ee70 16 0 0 trampoline / small helper
12 0x0215ee80 58 4 0 code
13 0x0215eebc 462 15 0 code
14 0x0215f308 514 27 2 refs: crdires \| crdires
15 0x0215f528 34 0 0 trampoline / small helper
16 0x0215f6fc 56 3 0 code
17 0x0215f770 52 2 0 code
18 0x0215f7a4 10 0 0 trampoline / small helper
19 0x0215f7b0 10 0 0 trampoline / small helper
20 0x0215f7bc 200 12 0 code
21 0x0215f890 24 2 0 trampoline / small helper
22 0x0215f8ac 30 3 0 trampoline / small helper
23 0x0215f8d0 10 0 0 trampoline / small helper
24 0x0215f8dc 12 1 0 trampoline / small helper

Open questions & conflicts

Open questions / unknowns

Conflicts with the prior shallow pass

Source