Programming UNROM: Difference between revisions

From NESdev Wiki
Jump to navigationJump to search
m (Encourage NES 2.0 adoption...)
(Undo good faith edit by Lidnariq (talk): NES 2.0 not really needed unless iNES is ambiguous. Will take it to talk.)
Line 1: Line 1:
'''UNROM''' is the common name for a discrete mapper found on the UNROM board as well as the less common '''UOROM''' board. UNROM has 64 KB or 128 KB PRG-ROM (divided into 8 16k banks) and CHR-RAM. The UOROM board works the same way and can take PRG-ROM up to 256 KB (16 banks). It is very easy to use once you know how to load CHR RAM.
'''UNROM''' is the common name for a discrete mapper found on the UNROM board as well as the less common '''UOROM''' board. UNROM has 64 KB or 128 KB PRG-ROM (divided into 8 16k banks) and CHR-RAM. The UOROM board works the same way and can take PRG-ROM up to 256 KB (16 banks). It is very easy to use once you know how to load CHR RAM.


== [[NES 2.0]] Header ==
== iNES header ==


Here are NES 2.0 headers for UNROM-using games:
Here is an iNES header for the UNROM mapper.


UNROM, 64 KB:
UNROM, 64 KB:
Line 10: Line 10:
     .byte $04      ;UNROM has 4 16k banks
     .byte $04      ;UNROM has 4 16k banks
     .byte $00      ;UNROM uses CHR RAM, so no CHR ROM
     .byte $00      ;UNROM uses CHR RAM, so no CHR ROM
     .byte $20       ;UNROM is Mapper 2
     .byte $20, $00  ;UNROM is Mapper 2
    .byte $08,0,0  ;Denotes NES 2.0
     .byte $00      ;UNROM has no PRG RAM, though [[PRG RAM circuit|clone boards might]]
     .byte $00      ;UNROM has no PRG RAM, though [[PRG RAM circuit|clone boards might]]


Line 19: Line 18:
     .byte $08      ;UNROM has 8 16k banks
     .byte $08      ;UNROM has 8 16k banks
     .byte $00      ;UNROM uses CHR RAM, so no CHR ROM
     .byte $00      ;UNROM uses CHR RAM, so no CHR ROM
     .byte $20       ;UNROM is Mapper 2
     .byte $20, $00  ;UNROM is Mapper 2
    .byte $08,0,0  ;Denotes NES 2.0
     .byte $00      ;UNROM has no PRG RAM, though clone boards might
     .byte $00      ;UNROM has no PRG RAM, though clone boards might


Line 28: Line 26:
     .byte $10      ;UOROM has 16 16k banks
     .byte $10      ;UOROM has 16 16k banks
     .byte $00      ;UOROM uses CHR RAM, so no CHR ROM
     .byte $00      ;UOROM uses CHR RAM, so no CHR ROM
     .byte $20       ;UOROM is Mapper 2
     .byte $20, $00  ;UOROM is Mapper 2
    .byte $08,0,0  ;Denotes NES 2.0
     .byte $00      ;UOROM has no PRG RAM, though clone boards might
     .byte $00      ;UOROM has no PRG RAM, though clone boards might



Revision as of 05:07, 27 February 2013

UNROM is the common name for a discrete mapper found on the UNROM board as well as the less common UOROM board. UNROM has 64 KB or 128 KB PRG-ROM (divided into 8 16k banks) and CHR-RAM. The UOROM board works the same way and can take PRG-ROM up to 256 KB (16 banks). It is very easy to use once you know how to load CHR RAM.

iNES header

Here is an iNES header for the UNROM mapper.

UNROM, 64 KB:

 .segment "HEADER"
   .byte "NES", $1A
   .byte $04       ;UNROM has 4 16k banks
   .byte $00       ;UNROM uses CHR RAM, so no CHR ROM
   .byte $20, $00  ;UNROM is Mapper 2
   .byte $00       ;UNROM has no PRG RAM, though clone boards might

UNROM, 128 KB (most common):

 .segment "HEADER"
   .byte "NES", $1A
   .byte $08       ;UNROM has 8 16k banks
   .byte $00       ;UNROM uses CHR RAM, so no CHR ROM
   .byte $20, $00  ;UNROM is Mapper 2
   .byte $00       ;UNROM has no PRG RAM, though clone boards might

UOROM, 256 KB:

 .segment "HEADER"
   .byte "NES", $1A
   .byte $10       ;UOROM has 16 16k banks
   .byte $00       ;UOROM uses CHR RAM, so no CHR ROM
   .byte $20, $00  ;UOROM is Mapper 2
   .byte $00       ;UOROM has no PRG RAM, though clone boards might

Bankswitching

UNROM has four or eight banks 16 KB in size; UOROM has 16 banks. The last of these banks is fixed at $C000-$FFFF. The rest (numbered 0-2, 0-6, or 0-14) are switchable at $8000-$BFFF.

Switching banks requires a write to $8000-$FFFF. In UNROM, bits 0-2 of the byte written to $8000-$FFFF will select the bank; UOROM uses bits 0-3. When writing to $8000-$FFFF, the value you are writing must match the value located at the destination address in ROM (see Bus conflict). One way to ensure this is to have a bankswitch lookup table. You can read from this table and then immediately write that value back to the table.

.segment "RODATA"
banktable:              ; Write to this table to switch banks.
  .byte $00, $01, $02, $03, $04, $05, $06
  .byte $07, $08, $09, $0A, $0B, $0C, $0D, $0E
  ; UNROM needs only the first line of this table (0-6)
  ; but UOROM needs both lines (0-14).

.segment "ZEROPAGE":    ; The mapper is read-only; need to track its state separately
current_bank: .res 1

.segment "CODE"
bankswitch_y:
  sty current_bank      ; save the current bank in RAM so the NMI handler can restore it
bankswitch_nosave:
  lda banktable, y      ; read a byte from the banktable
  sta banktable, y      ; and write it back, switching banks
  rts

The lookup table and the bankswitching subroutine MUST be located in the fixed bank ($C000-$FFFF) so that they are always available. To save 12 cycles per bankswitch at a cost of 5 bytes of ROM, the bankswitch_y subroutine can be made into a macro.

With the lookup table and bankswitching subroutine in place, switching banks is as easy as this:

  ldy #$02
  jsr bankswitch_y     ;switch to bank 2

If you switch banks in the NMI handler, such as to run a sound engine, do not write to current_bank. Instead, do this at the end of the NMI handler just before pulling registers:

  ldy current_bank
  jsr bankswitch_nosave

See also