ov046 — overlay detail

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.

Reading the binary

The overlay ships on the cart at file ID 46 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 + 46 * 0x20, allocates the destination RAM region at 0x02155a00, decompresses the body in-place (if compressed), and resolves any external relocations.

To inspect this overlay outside the running game, decompress overlay/overlay_046.bin with ndspy.codeCompression.decompress() (Python ndspy library) and load the resulting plaintext into Ghidra or IDA at base address 0x02155a00. The raw Ghidra auto-analysis dump used to populate this page lives at notes/overlay_knowledgebase/raw/ov046.json; the per-overlay descriptive markdown is at notes/overlay_knowledgebase/ov046.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.

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.

• expect → data/2d/expect.ofs
• mgcinfo → data/recipe/mgcinfo.lzs
• selmaterial → data/2d/selmaterial.lzs

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.

• 2d/expect.ofs — no matching container found in clean extract
• 2d/selmaterial.lzs — no matching container found in clean extract
• recipe/mgcinfo.lzs — no matching container found in clean extract
• recipe/recipedata.lzs — no matching container found in clean extract
• recipe/recipemsg.lzs — no matching container found in clean extract
• recipepos — no matching container found in clean extract

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.

Open questions & conflicts

Open questions / unknowns

• Auto-analysis identified 62 functions covering 12346 of 15776 overlay bytes.
• Function names are auto-generated `FUN_<addr>`. Manual renaming based on call-graph + string-ref analysis is a follow-up.
• BSS size is 0 bytes; Ghidra-imported overlay does not include BSS so any references into the BSS range appear as unresolved.

Conflicts with the prior shallow pass

• Partial overlap: prior-pass had `['selmaterial']`; Ghidra adds `['2d/expect.ofs', '2d/selmaterial.lzs', 'expect', 'mgcinfo', 'recipe/mgcinfo.lzs', 'recipe/recipedata.lzs', 'recipe/recipemsg.lzs', 'recipepos']`.

Source

• Per-overlay markdown: notes/overlay_knowledgebase/ov046.md
• Raw Ghidra dump: notes/overlay_knowledgebase/raw/ov046.json
• Overlay-system explainer: overlays system
• Plain-English overlay primer: overlay knowledgebase