NES 2.0 Mapper 256: Difference between revisions
NewRisingSun (talk | contribs) (Repeat submapper table for convenience.) |
Rainwarrior (talk | contribs) (transcluding submapper table to avoid redundancy) |
||
| Line 12: | Line 12: | ||
Several plug-and-play consoles use a simple protection scheme intended to prevent interchanging the ROM data between different consoles. The protection scheme works by simply swapping the addresses of the bankswitch registers. Some patterns only change the VTxx-native register addresses, others apply to the MMC3 compatibility registers as well. [[NES 2.0 submappers#NES 2.0 Mapper 256|Submappers]] have been allocated to denote the type of register address mangling: | Several plug-and-play consoles use a simple protection scheme intended to prevent interchanging the ROM data between different consoles. The protection scheme works by simply swapping the addresses of the bankswitch registers. Some patterns only change the VTxx-native register addresses, others apply to the MMC3 compatibility registers as well. [[NES 2.0 submappers#NES 2.0 Mapper 256|Submappers]] have been allocated to denote the type of register address mangling: | ||
{ | {{NES 2.0 Mapper 256/Submapper table}} | ||
Revision as of 16:24, 11 March 2018
NES 2.0 Mapper 256 is used for games using the bankswitching behavior of the OneBus Famiclones. The UNIF board names are UNL-OneBus, BMC-OneBus and UNL-DANCE.
Registers
To emulate ROM images using mapper 256, one must support bankswitching, nametable mirroring selection and IRQs using both the VTxx native registers (see the VT02+ PRG-ROM Bankswitching and VT02+ CHR-ROM Bankswitching articles for details) as well as the MMC3 compatible registers.
Single and split PRG/CHR address space
On physical hardware, bankswitching by the VTxx console itself can only be used if the cartridge uses OneBus addressing, signalled by connecting certain pins on the cartridge connector to Vcc/GND, because only in OneBus mode are the CHR address lines repurposed as higher-order address lines for the single address space. Therefore, regular OneBus ROM images will only contain PRG ROM and no CHR ROM, and PRG ROM ($41xx) and CHR ROM ($201x) bankswitch registers apply to the same address space.
However, ROM images converted from Waixing's WXN format will have both PRG and CHR ROM, yet use the VTxx-native bankswitch registers and/or register address mangling. These images cannot be run unchanged on physical hardware, and were intended to be run by Waixing's proprietary VTxx emulator found on several 32-bit plug-and-play consoles. For simplicity, mapper 256 is also used for such ROM images; to emulate them, simply apply the PRG ROM ($41xx) and CHR ROM ($201x) bankswitch registers to the respective separate address space.
Register address mangling
Several plug-and-play consoles use a simple protection scheme intended to prevent interchanging the ROM data between different consoles. The protection scheme works by simply swapping the addresses of the bankswitch registers. Some patterns only change the VTxx-native register addresses, others apply to the MMC3 compatibility registers as well. Submappers have been allocated to denote the type of register address mangling:
