Out of date

This is a conversion of an old document. See SDSC Header for a shorter, snappier version.

Version 1.01

August 29, 2001


This document serves as the specification for the SDSC ROM tag. The SDSC ROM tag provides information about a program in addition to any information already included in the standard SMS/GG header. This specification also serves to document what is currently known about the standard SMS/GG header.


ROM Offset 0x7FE0 (4 Bytes)
"SDSC" (ASCII: 0x53, 0x44, 0x53, 0x43)
ROM Offset 0x7FE4 (1 Byte)
Major Program version number (BCD)
ROM Offset 0x7FE5 (1 Byte)
Minor Program version number (BCD)
ROM Offset 0x7FE6 (1 Byte)
Day (BCD)
ROM Offset 0x7FE7 (1 Byte)
Month (BCD)
ROM Offset 0x7FE8 (2 Bytes)
Year (BCD) (Little-endian: 0x01 0x20 for 2001)
ROM Offset 0x7FEA (2 Bytes)
ROM Address of program author, zero-terminated string. (See Notes #1 and #2 below.)
ROM Offset 0x7FEC (2 Bytes)
ROM Address of program name, zero-terminated string. (See Note #2 below.)
ROM Offset 0x7FEE (2 Bytes)
ROM Address of program release notes, zero-terminated string. (See Note #2 below.)
ROM Offset 0x7FF0 (16 Bytes)
Normal SMS/GG header

Standard SMS/GG Header Format (reproduced here for completeness):

ROM Offset 0x7FF0 (8 Bytes)
"TMR SEGA" (ASCII: 0x54, 0x4D 0x52, 0x20, 0x53, 0x45, 0x47, 0x41)
ROM Offset 0x7FF8 (2 Bytes)
Unknown (See Note #3 below.)
ROM Offset 0x7FFA (2 Bytes)
Checksum (Big-Endian, see Note #4 below.)
ROM Offset 0x7FFC (2 Bytes)
Part Number (Big-Endian BCD) (See Note #5 below)
ROM Offset 0x7FFE (1 Byte)
Version (See Note #6 below.)
ROM Offset 0x7FFF (1 Byte)
Checksum range (See Note #7 below.)

It should be noted that many commercial ROMs don't conform to the standard SMS/GG header - many Japanese roms have other data in the header area, since they don't need a checksum; some don't even have the TMR SEGA (Loletta No Shozou has FFs instead). A lot of games don't have the part number, some even have different values there for alternate versions. (Courtesy Maxim)



To maintain compatibility with previous versions of the SDSC ROM Tag, both the value 0x0000 (the reserved setting in previous specifications) and 0xFFFF are used to indicate a NULL (no string present) program author string.


The 16-bit addresses imply that the program author, program name and release notes strings must reside in one of the first four pages of ROM. These pages do not necessarily need to be mapped into addressable space at run-time. Also, an address of 0xFFFF indicates a NULL string (no string present).


The 16-bit word at 0x7FF8 (and 0x7FF9) contains an unknown value. It is often 0x0000, 0x2020 or 0xFFFF, all of which are "nothing" values (0x20 being ASCII space). ROMs with values there seem to be ones without full headers, for example Japanese SMS games. This area should be considered reserved. Recommended data is 0xFFFF. (Courtesy Maxim and Zoop)


The 16-bit word at 0x7FFA (and 0x7FFB) contains the checksum, in big endian format. It is a 16-bit accumulator, you start at 0 and sum the bytes over the checksummed range, dropping the 17th bit whenever it appears (ie. FFFF + 1 = 0000). The range depends on the byte at 0x7FFF, see Note #7 below. (Courtesy Maxim)


The 16-bit word at 0x7FFC (and 0x7FFD) contain the part number - the game number as on the side of the box. It's big-endian BCD. The part number can be used to find what type the cartridge was:

A second digit of 5 indicates a Plus cartridge, ie. one with battery-backed ram. There's a more complete list in my program's readme, and as I mentioned GG games are different. (Courtesy Maxim)


The byte at 0x7FFE is apparently a version byte. The high nibble is nearly always 2 when the game number begins with a 2, ie. for 3rd-party releases. The low nibble can vary, but it is nearly always 0. (Courtesy Maxim and Zoop)


The byte at 0x7FFF is split into two nibbles, where a value of 0xXY has a high nibble of 0xX and a low nibble of 0xY. The high nibble is the country code, again taken from Zoop's checksummer source:

Export, of course, means outside Japan. The low nibble defines the range over which to checksum the file:

The checksum range is always less than or (usually) equal to the rom size. 4-mega and larger roms are never checksummed over 256KB. (Courtesy Maxim and Zoop)

Return to top