ROM map: Difference between revisions

From Data Crystal
Jump to navigation Jump to search
m (→‎See Also: removed leading space from link to EB ROM map)
 
(2 intermediate revisions by one other user not shown)
Line 3: Line 3:
Please place the [[:Template:rommap|<nowiki>{{rommap|game=</nowiki>''name of game''<nowiki>}}</nowiki>]] template, which links to this page, at the top of each ROM map page.
Please place the [[:Template:rommap|<nowiki>{{rommap|game=</nowiki>''name of game''<nowiki>}}</nowiki>]] template, which links to this page, at the top of each ROM map page.


== Notes on the ROM Map ==
== Notes on the ROM map ==


=== Reading the data ===
=== 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 [[Pointer|address]] and the end [[Pointer|address]] of each block are given, plus a total byte size (shown in parentheses).  [[Pointer|Addresses]] could be in raw [[Hexadecimal|hex]] format, that is, within the ROM file, not as the system sees it.  In order to prevent confusion among ROM formats, the addresses should be given in the format the system uses, or, at least, the format of the pointers should be clarified at the top of the ROM map. Following the location and size is a brief description of the data contained within.  The descriptions are linked to separate topics with details on each block.
The ROM map breaks down the entirety of a ROM's raw code into specific block by function and type of data.  The start [[Pointer|address]] and the end [[Pointer|address]] of each block are given, plus a total byte size (shown in parentheses).  [[Pointer|Addresses]] could be in raw [[Hexadecimal|hex]] format, that is, within the ROM file, not as the system sees it.  In order to prevent confusion among ROM formats, the addresses should be given in the format the system uses, or, at least, the format of the pointers should be clarified at the top of the ROM map. 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 ===
=== Categorization of blocks ===
 
Blocks in a ROM map may be categorized strictly as a means of demarcating various areas.  The label given does not necessarily 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.
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 ==
== See Also ==
* The [[EarthBound:ROM Map|ROM map]] for the game [[EarthBound]] is the basis for the ROM Map format described by this document
* [[Help:Rom Map|Rom Map Guidelines]]
* [[:Category: ROM Maps]]
* The [[EarthBound:ROM map|ROM map]] for the game [[EarthBound]] is the basis for the ROM map format described by this document
* [[RAM Map]] - the format of a RAM map will be similar to that of a ROM Map
* [[:Category:ROM maps]]
* [[RAM map]] - Similar maps for the contents of RAM


[[Category: General Terms]]
[[Category:General Terms]]

Latest revision as of 02:20, 7 April 2013

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). Addresses could be in raw hex format, that is, within the ROM file, not as the system sees it. In order to prevent confusion among ROM formats, the addresses should be given in the format the system uses, or, at least, the format of the pointers should be clarified at the top of the ROM map. Following the location and size is a brief description of the data contained within. The descriptions are linked to separate topics with details on each block.

Categorization of blocks

Blocks in a ROM map may be categorized strictly as a means of demarcating various areas. The label given does not necessarily 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