Welcome to Data Crystal's new home! Data Crystal is now part of the TCRF family (sort of).
The wiki has recently moved; please report any issues in Discord. Pardon the dust.

ROM map: Difference between revisions

From Data Crystal
Jump to navigation Jump to search
(Based on top of Earthbound:ROM map, which was orginally by BlueAntoid)
 
No edit summary
Line 17: Line 17:
* The [[EarthBound:ROM map|ROM map]] for the game [[EarthBound]] is the basis for the ROM map format described by this document
* The [[EarthBound:ROM map|ROM map]] for the game [[EarthBound]] is the basis for the ROM map format described by this document
* [[:Category:ROM maps]]
* [[:Category:ROM maps]]
[[Category:General Terms]]

Revision as of 21:53, 20 November 2005

A ROM map is a linear breakdown of the hard-coded data in a ROM. For the purposes of this database, it serves as a jumping-off point to more specific documents regarding each identified block of code.

Please place the {{rommap|game=name of game}} template, which links to this page, at the top of each ROM map page.

Notes on the ROM Map

Reading the data

The ROM map breaks down the entirety of a ROM's raw code into specific block by function and type of data. The start address and the end address of each block are given, plus a total byte size (shown in parentheses). All addresses are raw hex format, that is, within the ROM file, not as the system sees it. Following the location and size is a brief description of the data contained within. The descriptions are linked to seperate topics with details on each block.

Categorization of blocks

Blocks in a ROM map may be categorized strictly as a means of demarking various areas. The label given does not neccessarily mean that all the data is logically grouped in that category. For example, in the EarthBound ROM, music and sound data are scattered throughout the ROM. Please take any seeming incongruities between actual data and the categories in stride.

See Also