Introduction
An .rpk (“rompack”) is a cartridge in one file: “essentially a ZIP file” (ninerpedia) that holds the ROM, GROM and RAM dumps and a layout.xml. The XML names a board type (how the cartridge is wired and bank-switched) and puts each dump in a
socket of that board, so an emulator needs no knowledge of the particular game. MAME defines and reads the format (src/lib/formats/rpk.cpp, fetched 2026-11-18, “our words” because the fetch tool returns summaries); the dumps inside are the plain
C, D and G files.
The explorer opens an .rpk with its ZIP reader: the archive’s entries are listed, layout.xml opens as XML and each dump opens by what it is (a ROM or GROM with a standard header is recognised by its bytes; any other opens as bytes, and the
Read as list offers the headerless TI-99/4A ROM). There is no dedicated RPK viewer: the board type and the sockets are read from the XML by eye, using this page.
Software
layout.xml
<romset>
<resources>
<rom id="gromimage" file="ed-assmg.bin" />
</resources>
<configuration>
<pcb type="standard">
<socket id="grom_socket" uses="gromimage"/>
</pcb>
</configuration>
</romset>
(the example in MAME’s source and ninerpedia: the Editor/Assembler module, one GROM dump in the GROM socket of a standard board.)
| Element | Attributes | Meaning |
|---|---|---|
romset | optional version | The root. It must contain resources and configuration. |
rom | id, file (required); crc, sha1 (optional) | A dump in the archive. When a hash is given the dump is hashed on reading and a mismatch fails the read. |
ram | id, length (required); type volatile (default) or persistent; store internal or external; file (required when persistent) | RAM on the cartridge. The length is a number or has a k or m suffix (64k = 65,536). |
pcb | type (required) | The board type; it must be one MAME knows. Its children are only socket elements. |
socket | id, uses (required) | Puts the resource named by uses in a socket of the board. The ids MAME looks for: rom_socket (the first ROM, required for ROM cartridges), rom2_socket (a second ROM, 8 KB at most), grom_socket, ram_socket (persistent RAM is saved by MAME). |
Errors MAME reports: an XML error, a missing layout.xml, an invalid layout, an unknown board type, a uses that names no resource, a RAM without a length or with a malformed one, RAM on a system that cannot have it; a dump missing from the archive or a failed hash is reported without a message of its own. (The DTD in MAME’s source
lacks a closing > on one declaration.)
Board types
As MAME’s cartridges.cpp describes them (summary):
pcb type | What |
|---|---|
standard | ROM at >6000->7FFF (and GROMs) |
paged12k | 4 KB ROM at >6000->6FFF, 8 KB as two 4 KB banks at >7000->7FFF; writes to >6000, >6004, … select bank 0 and >6002, >6006, … bank 1 |
paged (softlist name paged16k) | 16 KB as two 8 KB pages; even word addresses (>6000) select page 0, odd (>6002) page 1 |
paged7 | Four banks selected by writes to >7000, >7002, >7004, >7006 |
minimem | 4 KB ROM at >6000->6FFF, 4 KB battery-backed RAM at >7000->7FFF |
super | Super Space II: 32 KB RAM at >6000->7FFF in 4 banks, switched through the CRU (>0802, >0806, >080A, >080E) |
mbx | 16 KB ROM in four 4 KB banks, selected by a write to >6FFE; 1,022 bytes of RAM at >6C00->6FFD |
paged379i | 16 to 128 KB EEPROM in 2 to 16 pages of 8 KB, with inverted latch addressing (>601E is bank 0) |
paged378 | Up to 512 KB (64 banks), written at >6000, >6002, … >607E; also called UberGROM |
paged377 | Up to 2 MB (256 banks), written at >6000 to >61FE |
pagedcru | 16, 32 or 64 KB in 2, 4 or 8 pages, selected through the CRU (>0800 bit patterns) |
gromemu | Emulated GROMs of 8 KB each, with bank writes to 011x xxxx xxxx xxx0 and the Super-MiniMemory RAM at >7000->7FFF |
MAME rounds a ROM size up to a power of two starting at 8 KB, mirrors smaller ROMs in the bank space of the paged 378 board, and notes that “TI-99/4A cartridges can only occupy 8 KiB of CPU RAM space”, which is why large cartridges need a bank-switching board.
Not described
Known, not yet covered
- Viewer: a dedicated RPK reader: the board type, the sockets and which dump is which are not summarised; the ZIP reader’s generic entry list is what the explorer shows. A test with a real
.rpkwas not made (none was available on the machine where this was written; only the ZIP reader is exercised by the site’s own ZIP tests). - Reference: the exact addresses and CRU bits of each board are MAME’s comments in summary; the original board schematics and the community’s documents were not read.
Unknown
- Reference: the FinalGROM 99 and other flash cartridge files are plain
.binsets (the FinalGROM page says its images are “raw machine code, loaded verbatim” and that MAME.rpkfiles must be extracted first); no other container for them was found.
Links
Reference
- MAME rpk.cpp – the reader this page follows
- MAME cartridges.cpp – the board types
- Ninerpedia: RPK
- ZIP archive – the container
- TI-99/4A cartridge image – the dumps inside