UTTORI ASM · IN DEVELOPMENT

ROM coverage map

Inspect which ROM bytes are code, data, unknown, or supported by evidence.

buildRomCoverageMap() produces a read-only, target-neutral projection of a validated project's ROM-content coverage. It combines file-space annotations, CFG records with explicit fileOffset values, regions, ranged conflicts, runtime execution offsets, and file-space runtime coverage into maximally coalesced half-open segments. Each segment keeps classification, runtime, provenance, region, and conflict ids separate so the presentation layer cannot hide contradictory evidence.

Summary totals distinguish exclusive classified, unknown, and conflicted bytes. Per-classification totals intentionally overlap when a byte has incompatible classifications. CPU and RAM records without an explicit file offset are returned in unprojected. The helper never guesses a mapper translation. Partially out-of-range records are clipped with diagnostics, and wholly invalid or out-of-ROM records remain visible as unprojected input.