UNROM 512: Difference between revisions

From NESdev Wiki
Jump to navigationJump to search
No edit summary
(Replaces "wram" with "RAM" to avoid confusion. WRAM often refers to non-persistent PRG-RAM, which this mapper doesn't natively support.)
 
(12 intermediate revisions by 4 users not shown)
Line 1: Line 1:
{{Infobox_iNES_mapper
{{Infobox_iNES_mapper
|name=UNROM 512
|name=UNROM 512
|company=RetroUSB, InfiniteNESLives
|company=RetroUSB, InfiniteNESLives, Broke Studio
|mapper=30
|mapper=30
|complexity=Discrete logic
|complexity=Discrete logic
|boards=UNROM-512-8, UNROM-512-16, UNROM-512-32
|boards=UNROM-512-8, UNROM-512-16, UNROM-512-32, INL-D-RAM, UNROM-512-F
|prgmax=256K or 512K
|prgmax=256K or 512K
|prgpage=16K + 16K fixed
|prgpage=16K + 16K fixed ($C000)
|chrmax=32K
|chrmax=32K
|chrpage=8K
|chrpage=8K
|busconflicts=Yes (in non-flashable config), else No
|busconflicts=Yes (in non-flashable config), else No
|mirroring=H or V (solder pad), 1-screen switchable, 4 fixed
|mirroring=H or V (solder pad), 1-screen (solder pad or switchable), 4-screen fixed
}}
}}
{{nesdbbox
[[Category:Mappers with bus conflicts]][[Category:Discrete logic mappers]][[Category:Mappers with flash save]]
|ines|30|iNES 030
'''UNROM 512''' is a discrete-logic board made by RetroUSB as an extension of [[UNROM]] with up to 512kB of PRG ROM, bankable CHR RAM, an option for mapper-controlled single-screen mirroring, as well as a self-flashable configuration for rewriting PRG. Since its initial creation InfiniteNESLives has replicated its design and also added an optional four-screen mirroring variation.
|unif_wild|UNROM-512-8|UNROM-512-8
|unif_wild|UNROM-512-16|UNROM-512-16
|unif_wild|UNROM-512-32|UNROM-512-32
}}
[[Category:Mappers with bus conflicts]][[Category:Discrete_logic_mappers]]
'''UNROM 512''' is a discrete-logic board made by RetroUSB as an extension of [[UNROM]] with up to 512kB of PRG ROM, bankable CHR RAM, an option for mapper-controlled single-screen mirroring, as well as a self-flashable configuration for rewriting PRG. Since its initial creation InfiniteNesLives has replicated its design and also added an optional four-screen mirroring variation.


The [[iNES]] format assigns '''iNES Mapper 030''' to UNROM 512.
The [[iNES]] format assigns '''iNES Mapper 030''' to UNROM 512.
Line 29: Line 23:
Examples:
Examples:
* ''Study Hall''
* ''Study Hall''
* ''[[Battle Kid 2: Mountain of Torment]]''
* ''[[User:Sivak/Battle Kid 2: Mountain of Torment|Battle Kid 2: Mountain of Torment]]''
* ''Black Box Challenge'' ([http://slydogstudios.org/ ROM download], 4-screen)
* ''Black Box Challenge'' ([http://slydogstudios.org/ ROM download], 4-screen)
* ''Mystic Origins''
* ''Mystic Origins''
* ''NES Maker''
* ''NES Maker''


== Overview ==
== RetroUSB board ==
* PRG ROM size: Up to 512kB (Up to 256kB on 8Bit XMAS)
* PRG ROM bank size: 16kB
* PRG RAM: None
* CHR capacity: Up to 32kB RAM [[Category:Mappers with CHR RAM]]
* CHR bank size: 8kB
* Nametable [[mirroring]]: Solder pads select vertical, horizontal, mapper-controlled one-screen. (InfiniteNesLives variation permits four-screen mirroring)
* Subject to [[bus conflict]]s: Yes, in the non-flashable configuration [[Category:Mappers with bus conflicts]]
 
== Board ==
=== RetroUSB ===
The example board in question is marked as follows: "Sealie Computing", "12/29/2011 revA", "UNROM 512".  The backside of the board was mislabelled with "ReproPak MMC3".
The example board in question is marked as follows: "Sealie Computing", "12/29/2011 revA", "UNROM 512".  The backside of the board was mislabelled with "ReproPak MMC3".


The board includes 4x banks worth of full 8kB CHR-RAM (Configurable by jumpers) and 32x 16kB PRG banks.
The board includes:
 
The board can be wired in a non-flashable or self-flashable configurations. 
 
Mirroring can be selected between Horizontal, Vertical, and Mapper-controlled One Screen.  The InfiniteNesLives variation optionally adds 4-screen mirroring capabilities.


Bus conflicts are only present on the non-flashable configuration of the board.
* 32x 16kB (512kB total) PRG banks.  The 8BIT XMAS board variant only permits 16x 16kB (256kB total); see ''Electrical schematic'' below
* 4x banks worth of full 8kB CHR-RAM (configurable by jumpers)
* Wiring for non-flashable or self-flashable configurations
* Mirroring selection: horizontal, vertical, and mapper-controlled one-screen
* Bus conflicts are only present on the non-flashable configuration of the board.


Some images of the board:  
Some images of the board:  
Line 94: Line 78:
   ---------------------------
   ---------------------------
    
    
   Range,Mask:   $8000-BFFF, $8000
   Mask: $C000
                $C000-FFFF, $C000
    
    
     $8000:  [.... ....]
     $8000:  [.... ....]
       Write a sequence of bytes here for writing to the flash. The sequence is as follows  
       Write a sequence of bytes here for writing to the flash. The sequence is as follows  


(This code must exist in wram):
(This code must exist in RAM):
         Erase 4KB Flash Sector:
         Erase 4KB Flash Sector:
         $C000:$01, $9555:$AA
         $C000:$01, $9555:$AA
Line 117: Line 100:
         Read the written location twice until you get DATA twice.
         Read the written location twice until you get DATA twice.


Additionally, on 8Bit XMAS boards, any writes here controls the LEDs as follows.
Additionally, on 8BIT XMAS boards, any writes here controls the LEDs as follows.


     $8000:  [BYGR bygr]
     $8000:  [BYGR bygr]
Line 150: Line 133:
</pre>
</pre>


Here's a schematic of the board:
=== Electrical schematic ===
<pre>
<pre>
             ____
             ____
Line 227: Line 210:
         '------'
         '------'


With 8Bit Xmas Board, there is a second 377 chip for the LEDs, and 2 jumpers to control whether the 377 is sourcing
With 8BIT Xmas Board, there is a second 377 chip for the LEDs, and 2 jumpers to control whether the 377 is sourcing
current to the LEDs or sinking current from them.  Additionally, the board has no flash control jumpers, and is hard-wired
current to the LEDs or sinking current from them.  Additionally, the board has no flash control jumpers, and is hard-wired
flashable,  and has no CHR ram control jumpers, is hard-wired as 32KB, and it does not have the second 74LS32 chip,
flashable,  and has no CHR ram control jumpers, is hard-wired as 32KB, and it does not have the second 74LS32 chip,
Line 247: Line 230:
VCC---------[]--------------------+
VCC---------[]--------------------+
GND---------[]--------------------+
GND---------[]--------------------+
</pre>
</pre>


The board is wired in one of the following configurations:
=== Board wiring configurations ===


Not Flashable:
Not Flashable:
*All 4 Flash Locked jumpers are soldered.
*All 4 Flash Locked jumpers are soldered.
*Flashable jumper is not soldered.
*Flashable jumper '''is not''' soldered.
*74*139 is not mounted.
*74*139 '''is not''' mounted.
*This configuration '''is''' subject to bus conflicts
*This configuration is subject to bus conflicts.


Flashable:
Flashable:
*All 4 Flash Locked jumpers are not soldered.
*All 4 Flash Locked jumpers '''are not''' soldered.
*Flashable jumper is soldered.
*Flashable jumper is soldered.
*74*139 is mounted.
*74*139 is mounted.
*This configuration is '''not''' subject to bus conflicts
*This configuration '''is not''' subject to bus conflicts.


The Self-flashable configuration should be implemented according to the [http://www.microchip.com/wwwproducts/Devices.aspx?product=SST39SF040 SST39SF040]'s datasheet.  
The Self-flashable configuration should be implemented according to the [http://www.microchip.com/wwwproducts/Devices.aspx?product=SST39SF040 SST39SF040]'s datasheet.  
Line 268: Line 250:
Example flash writing code - [[Media:Flash.asm.txt|Flash.asm]]
Example flash writing code - [[Media:Flash.asm.txt|Flash.asm]]


== InfiniteNESLives 4-screen board ==


=== InfiniteNESLives 4-screen variation ===
* Two of the unused OR gates are used in combination with jumpers to disable NES mainboard VRAM/CIRAM and utilize cartridge CHR RAM for all pattern, name, & attribute tables.
 
* This variation is only well defined with 32 KiB of CHR-RAM, but note that the last bank of CHR-RAM now contains the nametables.
* Two of the unused OR gates are used in combination with jumpers to disable NES mainboard VRAM/CIRAM and utilize cartridge VRAM for all pattern, name, & attribute tables.
:- As such, only the first 3 CHR-RAM banks (24KB) and the second half of the last bank can be used freely for pattern table tile data.
* This variation only allows CHR-RAM size of 32KB, however the last CHR-RAM bank is designated for non-pattern table use.
* The last 8KB CHR-RAM bank is permanently mapped to PPU $2000-3FFF (effectively $2000-3EFF due to palette data.)
:- This restricts the user to only having free use of the first 3 CHR-RAM banks (24KB) for pattern table tile data.
* The last 8KB CHR-RAM bank is mapped to PPU $2000-3FFF (effectively $2000-3EFF due to palette data.)
** The first 4KB of this last CHR-RAM bank is mapped to PPU $2000-2FFF to provide four-screen mirroring.
** The first 4KB of this last CHR-RAM bank is mapped to PPU $2000-2FFF to provide four-screen mirroring.
** PPU $3000-3EFF are no longer mirrors to nametables, and actually have RAM mapped to each byte which aren't used by the PPU for rendering.
** PPU $3000-3EFF are no longer mirrors of the nametables, and actually have independent RAM mapped.
::- This 3.75KB of RAM can be used by the developer as a 'scratch RAM' space only accessible via CPU $2006/2007.
::- If not used for PT1 in bank 3, this 3.75KB of RAM can be used by the developer as a 'scratch RAM' space accessible via CPU $2006/2007.
::- The last 256bytes of the last CHR-RAM bank are not normally accessible due to pallette data being mapped to PPU $3F00-3FFF.
::- The last 256bytes of the last RAM bank are not accessible at $3Fxx due to palette data being mapped there instead.
* Setting of both CHR RAM bank bits ($8000: 0bx11xxxxx) is permissible, but extreme care must be used when the PPU is rendering as it has the effect of mapping the last CHR-RAM bank to both PPU $0000-1FFF (Pattern tables), and PPU $2000-3F00 (Name/Attribute tables) at the same time.
* Setting of both CHR RAM bank bits ($C000: 0bx11xxxxx) is permissible, but the pattern table at $0000 is now the same physical RAM as holds the nametables.
:- Improperly operating in this mode will render NT/AT data as tiles in PT0, and writes to PT0 will corrupt NT/AT data.
:- Improperly operating in this mode will render NT/AT data as tiles in PT0, and writes to PT0 will corrupt NT/AT data.
:- This mode is the only means of gaining access to the last 256bytes of the last CHR-RAM bank which are normally hidden behind PPU pallette address space.
:- PT1 in this mode remains usable at $1000-$1FFF. This is the only means of gaining access to the last 256bytes of the last CHR-RAM bank which are normally hidden behind PPU palette address space.


==== PPU memory map ====
=== PPU memory map ===
{| class="tabular"
{| class="tabular"
! Address range || Size || Description  
! Address range || Size || Description  
Line 306: Line 287:
|}
|}


==== Electrical schematic ====
=== Electrical schematic ===
<pre>
<pre>
             ____
             ____
Line 341: Line 322:


Supplemental mappers exist for flash carts as well:
Supplemental mappers exist for flash carts as well:
* PowerPak: [//forums.nesdev.org/viewtopic.php?p=236715#p236715 forum post] (limited flash save*)
* PowerPak: [//forums.nesdev.org/viewtopic.php?p=236715#p236715 forum post] (limited flash save)
* Everdrive N8: [//forums.nesdev.org/viewtopic.php?p=235457#p235457 forum post] (no flash save)
* Everdrive N8: [//forums.nesdev.org/viewtopic.php?p=235457#p235457 forum post] (no flash save)


The PowerPak flash save capability lacks the sector erase and chip erase capabilities, due to the underlying hardware being RAM at the time of write. As long as the game writes every byte it intends to read back, this is compatible implementation.
The PowerPak flash save capability lacks the sector erase and chip erase capabilities, due to the underlying hardware being RAM at the time of write. As long as the game writes every byte it intends to read back, this is a compatible implementation.


=== Nametable Configuration ===
=== Nametable Configuration ===

Latest revision as of 23:50, 12 November 2023

UNROM 512
Company RetroUSB, InfiniteNESLives, Broke Studio
Complexity Discrete logic
Boards UNROM-512-8, UNROM-512-16, UNROM-512-32, INL-D-RAM, UNROM-512-F
PRG ROM capacity 256K or 512K
PRG ROM window 16K + 16K fixed ($C000)
PRG RAM capacity None
CHR capacity 32K
CHR window 8K
Nametable mirroring H or V (solder pad), 1-screen (solder pad or switchable), 4-screen fixed
Bus conflicts Yes (in non-flashable config), else No
IRQ No
Audio No
iNES mappers 030

UNROM 512 is a discrete-logic board made by RetroUSB as an extension of UNROM with up to 512kB of PRG ROM, bankable CHR RAM, an option for mapper-controlled single-screen mirroring, as well as a self-flashable configuration for rewriting PRG. Since its initial creation InfiniteNESLives has replicated its design and also added an optional four-screen mirroring variation.

The iNES format assigns iNES Mapper 030 to UNROM 512.

The UNIF names for this board are UNROM-512-8, UNROM-512-16 and UNROM-512-32, depending on how much CHR RAM is present.

In GoodNES 3.23b, a few ROMS using the Waixing FS005 board (INES Mapper 176) are also set to Mapper 30. These ROMs were converted from Waixing's proprietary WXN/MFC format, which has a 16 byte header that is somewhat similar but not the same as the INES header, and when interpreting this header's data as if it were an iNES header, the resulting mapper number would be 30.

Examples:

RetroUSB board

The example board in question is marked as follows: "Sealie Computing", "12/29/2011 revA", "UNROM 512". The backside of the board was mislabelled with "ReproPak MMC3".

The board includes:

  • 32x 16kB (512kB total) PRG banks. The 8BIT XMAS board variant only permits 16x 16kB (256kB total); see Electrical schematic below
  • 4x banks worth of full 8kB CHR-RAM (configurable by jumpers)
  • Wiring for non-flashable or self-flashable configurations
  • Mirroring selection: horizontal, vertical, and mapper-controlled one-screen
  • Bus conflicts are only present on the non-flashable configuration of the board.

Some images of the board:

When board is not flashable:

  Registers:
  ---------------------------
  
  Range,Mask:   $8000-FFFF, $8000
  
    $8000:  [MCCP PPPP]
      M = One screen Mirroring select
      C = CHR RAM bank
      P = PRG ROM bank
  
  PRG Setup:
  ---------------------------
       $8000   $A000   $C000   $E000  
      +-------------------------------+
      |     $8000     |     { -1}     |
      +---------------+---------------+
  
  CHR Setup:
  ---------------------------
        $0000   $1000   
      +-------+-------+
      |     $0000     |
      +-------+-------+

When board is self flashable:

  Registers:
  ---------------------------
  
  Mask: $C000
  
    $8000:  [.... ....]
      Write a sequence of bytes here for writing to the flash. The sequence is as follows 

(This code must exist in RAM):
        Erase 4KB Flash Sector:
        $C000:$01, $9555:$AA
        $C000:$00, $AAAA:$55
        $C000:$01, $9555:$80
        $C000:$01, $9555:$AA
        $C000:$00, $AAAA:$55
        $C000:BANK, ADDR:$30 (Where BANK is $00-1F, ADDR is $8000,$9000,$A000,$B000)
        Read the written location twice until you get $FF twice.

        Write a byte:
        $C000:$01, $9555:$AA
        $C000:$00, $AAAA:$55
        $C000:$01, $9555:$A0
        $C000:BANK, ADDR:DATA (Where BANK is $00-1F, ADDR is $8000-$BFFF, DATA is $00-$FF)
        Read the written location twice until you get DATA twice.

Additionally, on 8BIT XMAS boards, any writes here controls the LEDs as follows.

    $8000:  [BYGR bygr]
        B = Blue 3, Blue 4
        Y = Yellow 3, Yellow 4
        G = Green 3, Green 4
        R = Red 3, Red 4
        b = Blue 1, Blue 2
        y = Yellow 1, Yellow 2
        g = Green 1, Green 2
        r = Red 1, Red 2

  
    $C000:  [MCCP PPPP]
      M = One screen Mirroring select
      C = CHR RAM bank
      P = PRG ROM bank
  
  PRG Setup:
  ---------------------------
       $8000   $A000   $C000   $E000  
      +-------------------------------+
      |     $8000     |     { -1}     |
      +---------------+---------------+
  
  CHR Setup:
  ---------------------------
        $0000   $1000   
      +-------+-------+
      |     $8000     |
      +-------+-------+

Electrical schematic

             ____
A14 ---------\    \
              )    >--- ROM A14
377 Q0 ------/____/

             ____
A14 ---------\    \
              )    >--- ROM A15
377 Q1 ------/____/

             ____
A14 ---------\    \
              )    >--- ROM A16
377 Q2 ------/____/

             ____
A14 ---------\    \
              )    >--- ROM A17
377 Q3 ------/____/

             ____
A14 ---------\    \
              )    >--- ROM A18
377 Q4 ------/____/

16/32KB CHRRAM
377 Q5 --[]--+-- CHRRAM A13
             |
VCC -----[]--+
8KB CHRRAM

8/16KB CHRRAM
VCC -----[]--+
             |
377 Q6 --[]--+-- CHRRAM A14
32KB CHRRAM

ONE
377 Q7 --[]--+
             |
VERT         |
PPU A10 -[]--+-- CIRAM_A10
             |
HORIZ        |
PPU A11 -[]--+

FLASHLOCKED3
R/W ------[]-+
             |
FLASHABLE    |
GND ------[]-+-- 377_/CE

FLASHLOCKED1
VCC ------[]-------+
          ½74LS139 |
          .------. |
CPUA14----|A   Y0|-+- PRGROM_/WE
R/W ------|B   Y1|-+- 377_CLK
          |    Y2| |
/ROMSEL-+-|G   Y3| |
        | '------' |
        |          |
        +---[]-----+
       FLASHLOCKED2

FLASHLOCKED4
GND ------[]-----+
        ½74LS139 |
        .------. |
R/W ----|A   Y0| |
GND ----|B   Y1|-+- PRGROM_/OE
        |    Y2|
/ROMSEL-|G   Y3|
        '------'

With 8BIT Xmas Board, there is a second 377 chip for the LEDs, and 2 jumpers to control whether the 377 is sourcing
current to the LEDs or sinking current from them.  Additionally, the board has no flash control jumpers, and is hard-wired
flashable,  and has no CHR ram control jumpers, is hard-wired as 32KB, and it does not have the second 74LS32 chip,
required for a 512KB board, so its max size is 256KB.

Q0-----R1-----RED1-----RED2-------+
Q1--+--R6-----GRN1----------------+
    +--R5-----GRN2----------------+
Q2-----R3-----YEL1-----YEL2-------+
Q3--+--R9-----BLU1----------------+
    +--R10----BLU2----------------+
Q4-----R2-----RED3-----RED4-------+
Q5--+--R7-----GRN3----------------+
    +--R8-----GRN4----------------+
Q6-----R4-----YEL3-----YEL4-------+
Q7--+--R11----BLU3----------------+
    +--R12----BLU4----------------+
                                  |
VCC---------[]--------------------+
GND---------[]--------------------+

Board wiring configurations

Not Flashable:

  • All 4 Flash Locked jumpers are soldered.
  • Flashable jumper is not soldered.
  • 74*139 is not mounted.
  • This configuration is subject to bus conflicts.

Flashable:

  • All 4 Flash Locked jumpers are not soldered.
  • Flashable jumper is soldered.
  • 74*139 is mounted.
  • This configuration is not subject to bus conflicts.

The Self-flashable configuration should be implemented according to the SST39SF040's datasheet.

Example flash writing code - Flash.asm

InfiniteNESLives 4-screen board

  • Two of the unused OR gates are used in combination with jumpers to disable NES mainboard VRAM/CIRAM and utilize cartridge CHR RAM for all pattern, name, & attribute tables.
  • This variation is only well defined with 32 KiB of CHR-RAM, but note that the last bank of CHR-RAM now contains the nametables.
- As such, only the first 3 CHR-RAM banks (24KB) and the second half of the last bank can be used freely for pattern table tile data.
  • The last 8KB CHR-RAM bank is permanently mapped to PPU $2000-3FFF (effectively $2000-3EFF due to palette data.)
    • The first 4KB of this last CHR-RAM bank is mapped to PPU $2000-2FFF to provide four-screen mirroring.
    • PPU $3000-3EFF are no longer mirrors of the nametables, and actually have independent RAM mapped.
- If not used for PT1 in bank 3, this 3.75KB of RAM can be used by the developer as a 'scratch RAM' space accessible via CPU $2006/2007.
- The last 256bytes of the last RAM bank are not accessible at $3Fxx due to palette data being mapped there instead.
  • Setting of both CHR RAM bank bits ($C000: 0bx11xxxxx) is permissible, but the pattern table at $0000 is now the same physical RAM as holds the nametables.
- Improperly operating in this mode will render NT/AT data as tiles in PT0, and writes to PT0 will corrupt NT/AT data.
- PT1 in this mode remains usable at $1000-$1FFF. This is the only means of gaining access to the last 256bytes of the last CHR-RAM bank which are normally hidden behind PPU palette address space.

PPU memory map

Address range Size Description
$0000-$0FFF $1000 Pattern Table 0
$1000-$1FFF $1000 Pattern Table 1
$2000-$23FF $0400 Nametable 0
$2400-$27FF $0400 Nametable 1
$2800-$2BFF $0400 Nametable 2
$2C00-$2FFF $0400 Nametable 3
$3000-$3EFF $0F00 Scratch RAM
$3F00-$3F1F $0020 Palette RAM indexes
$3F20-$3FFF $00E0 Mirrors of $3F00-$3F1F

Electrical schematic

             ____
PPU A13 -----\    \
              )    >--- CHRRAM A13
377 Q5 ------/____/

             ____
PPU A13 -----\    \
              )    >--- CHRRAM A14
377 Q6 ------/____/

NON-4SCREEN
PPU A13 ----[]--+
                |
GND --------[]--+---- CHRRAM /CE (Cartridge VRAM)
4SCREEN MIRROR

NON-4SCREEN
PPU /A13 ---[]--+
                |
VCC --------[]--+---- CIRAM /CE (NES mainboard VRAM)
4SCREEN MIRROR

Mapper

NES 2.0 may specify the CHR-RAM size from 8 to 32 kB, but the default for iNES should to use 32 kB.

If the Battery flag is set to 1, the mapper is flashable. This means no bus conflicts should be emulated. On the other hand, bus conflicts should be emulated if the battery flag is cleared.

Mapper 30 is currently only using sub mapper 0. The other sub mappers are reserved for future use.

Supported in FCEUX as of r3071, Supported in BizHawk as of r6322

Supplemental mappers exist for flash carts as well:

The PowerPak flash save capability lacks the sector erase and chip erase capabilities, due to the underlying hardware being RAM at the time of write. As long as the game writes every byte it intends to read back, this is a compatible implementation.

Nametable Configuration

The nametable mirroring bits in byte 6 of the iNES header select one of four configurations of nametables:

  • %....0..0 - Horizontal mirroring (aka: vertical arrangement)
  • %....0..1 - Vertical mirroring (aka: horizontal arrangement)
  • %....1..0 - 1-Screen, switchable
  • %....1..1 - 4-Screen, cartridge VRAM

See Also

  • GTROM - A very similar homebrew mapper, but with 32k PRG banking.

References