Mapper: Difference between revisions
| Line 504: | Line 504: | ||
|[[File:Mfr icon JYCompany.png|16px]] [[NES 2.0 Mapper 411|411]] | |[[File:Mfr icon JYCompany.png|16px]] [[NES 2.0 Mapper 411|411]] | ||
|[[File:Mfr icon Generic.png|16px]] [[NES 2.0 Mapper 412|412]] | |[[File:Mfr icon Generic.png|16px]] [[NES 2.0 Mapper 412|412]] | ||
|[[File:Mfr icon | |[[File:Mfr icon homebrew.png|16px]] [[NES 2.0 Mapper 413|413]] | ||
|[[File:Mfr icon Missing.png|16px]] [[NES 2.0 Mapper 414|414]] | |[[File:Mfr icon Missing.png|16px]] [[NES 2.0 Mapper 414|414]] | ||
|[[File:Mfr icon Missing.png|16px]] [[NES 2.0 Mapper 415|415]] | |[[File:Mfr icon Missing.png|16px]] [[NES 2.0 Mapper 415|415]] | ||
Revision as of 22:37, 7 July 2020
NES games come in cartridges, and inside of those cartridges are various circuits and hardware. Different games use different circuits and hardware, and the configuration and capabilities of such cartridges is commonly called their mapper. Mappers are designed to extend the system and bypass its limitations, such as by adding RAM to the cartridge or even extra sound channels. More commonly though, mappers are designed to allow games larger than 40K to be made.
The term "mapper" arises from the concept of memory mapping: translating memory hardware into the CPU's and PPU's address spaces. A memory map describes which addresses correspond to which physical locations of memory.
Common capabilities
Multiple functions can be performed by the hardware and circuitry on a cartridge's printed circuit board:
- Mapping of the CHR and PRG chips into the NES's address space, which may be expanded by…
- (often) Bank switching: dynamically changing the memory mapping of cartridge memory into the NES's address spaces. By doing so, the cartridge may have more data than the address space would allow, allowing larger games to be made.
- (often) Using a battery-backed volatile RAM chip, or rarely an EEPROM, to maintain save data between play sessions
- (always) Nametable Mirroring: controlling which way the nametables are arranged, as the NES only has two nametables' worth of CIRAM but four tables addressed.
- (rarely) Providing cartridge-side CHR-RAM or ROM to supplement or replace the nametable CIRAM (4-Screen mirroring).
- (commonly) Generating interrupts, especially ones timed to occur when the PPU reaches a certain scanlines.
- (rarely) Providing additional sound-generation. The Famicom sent its audio through the cartridge port to allow the cartridge to mix in additional channels; the NES does not without modification.
- (rarely) Altering how the attribute table is mapped to provide finer attribute control.
- (rarely) Other sundry functions like fast multiplication.
Most mappers fall into one of two categories: discrete logic, and ASIC based. Some discrete logic mappers are susceptible to bus conflicts. Nintendo uses the term Memory Management Controller (or MMC for short) for its ASIC mappers ("Why Game Paks Never Forget" article in Nintendo Power) (note: it may have originally stood for "Multi Memory Controller", at least according to Japanese).
Naming scheme
Discrete logic mappers are often referred to by the name of a board that they are commonly used in (e.g. "UNROM"). ASIC mappers are named after the ASIC (e.g. "MMC1" or "FME-7"), except in boards that use an ASIC in an unusual way (such as "TQROM", "TLSROM", or "NES-EVENT"). The emulation community generally refers to mappers by a numbering scheme that originated with the iNES emulator (e.g. "mapper 002").
The notation used in Disch's docs describing mappers is explained here.
To allocate a mapper number, you should have A. a hardware implementation or B. an emulator implementation and a sketch of hardware. You should also have a publicly-available dump of an existing commercial cart or most of a homebrew game written.
iNES 1.0 mapper grid
This is the plane 0 table. These mappers do not require a NES 2.0 header.
Most icons next to mapper numbers refer to publishers. Nintendo-made boards with numerous publishers get the Nintendo icon; Nintendo-made boards dominated by one publisher get that publisher's icon. Other icons refer to status:
Duplicate mappers assigned by mistake.
Mappers reserved for use by tools, such as emulator internal use or private use during development of a new mapper.
Mappers created by the NES homebrew scene for cart releases.
Mappers for MMC3-based bootleg cartridges, both single-game and multicart.
Mappers for non-MMC3-based bootleg cartridges, both single-game and multicart.
Mappers for which we have some information but no identified manufacturer.
Mappers that are not yet documented on this wiki. Do not assume undocumented mappers are currently unassigned; consult the source code for well-used emulators like Nestopia, FCEUX, Mesen, Nintendulator and NintendulatorNRS
Plane 1
Plane 1 (NES 2.0 mappers 256-511)
| Key |
|---|
|
Plane 2
Plane 2 (NES 2.0 mappers 512-767)
| Key |
|---|
|
Common mappers for homebrewers
- NROM: About the simplest mapper there is; 32K PRG and 8K CHR. Most beginners start with this.
- UxROM, BxROM: CHR RAM plus PRG bank switching. These are simple and cheap cartridge boards that hold far more memory than NROM.
- MMC1, MMC3: These mappers provide finely grained bank switching and features such as scanline counters. Their design involves an ASIC, which makes them more complicated and expensive than other mappers.
See also
- Nintendo: MMC1, MMC2, MMC3, MMC4, MMC5 with audio, MMC6
- Konami: VRC1, VRC2, VRC3, VRC4, VRC6 with audio, VRC7 with audio, VRC IRQs
- Others: Color Dreams, Namco 163 with audio, NINA-001, NINA-03/06, SUBOR, Sunsoft FME-7 with audio (Sunsoft 5B)
- List of mappers with board names
- List of mappers by Release Date
- List of discrete logic mappers
- List of iNES mapper numbers
- Comparison of Nintendo mappers
- List of mapper names and corresponding iNES mapper numbers
- Hardware pinout, including mapper pinouts
References
- Nintendulator source code
- Nestopia source code
- FCEUX source code
- Planes proposal
External links
- Disch's detailed list of over 50 mappers at romhacking.net
- Kevtris's mapper checklist as implemented in his FPGA NES
