Famicom Network System: Difference between revisions

From NESdev Wiki
Jump to navigationJump to search
(→‎CPU2 Known Registers: Confirmed some things for UART Rx, found parity error flag for Rx.)
 
(58 intermediate revisions by 3 users not shown)
Line 1: Line 1:
=System Overview=
=System Overview=
The Famicom Network System is a complicated device with its own memory mapping system and internal CPU.  The RF5C66 chip provides the main mapper functionality, delegating its own registers at $40A0, RF5A18 Famicom registers at $40D0, an internal Kanji ROM at $5000, an internal 8kByte W-RAM at $6000.  It also controls the bank of a built-in 16kByte CHR-RAM.
The Famicom Network System is a complicated device with its own memory mapping system and internal CPU.  The RF5C66 chip provides the main mapper functionality, delegating its own registers at $40A0, RF5A18 Famicom registers at $40D0, an internal Kanji ROM at $5000, an internal 8kByte W-RAM at $6000.  It also controls the bank of a built-in 16 KiB CHR RAM (using two 8 KiB CHR RAM chips).


The RF5A18 contains CPU2, which is a 65'''<u>C</u>'''02 processor with its own independent CPU clock.  It has a built-in 4kByte ROM.  This chip is responsible for controlling the modem communications.  It communicates with the Famicom CPU through four bidirectional registers at $40Dx.
The RF5A18 contains CPU2, which is a 65'''<u>C</u>'''02 processor with its own independent CPU clock.  It has a built-in 4kByte ROM.  This chip is responsible for controlling the modem communications.  It communicates with the Famicom CPU through four bidirectional registers at $40Dx.


The Famicom Network System plugs into the Famicom through its cartridge connector and provides the user a ZIF style slot to insert a "card".  The card is similar to a normal cartridge but does not have access to any PPU signals.  Commercial cards are observed to have their own MMC1 memory mapper, which does not interfere with any of the registers of the Famicom Network System.  The CPU data bus is routed through the RF5C66 chip before making it to the card, possibly acting just as a bidirectional buffer / signal conditioner.  It is unknown what other reason the data bus would be passed through the RF5C66 like that.  Older revisions of Famicom Network System buffered the Famicom address bus with 74HC541 chips, so it is plausible that this function is literally just a bidirectional buffer integrated into the RF5C66.
The Famicom Network System plugs into the Famicom through its cartridge connector and provides the user a ZIF style slot to insert a ''tsuushin card''.  The card is similar to a normal cartridge but does not have access to any PPU signals.  Commercial cards are observed to have their own MMC1 memory mapper, which does not interfere with any of the registers of the Famicom Network System.  CPU R/W and the CPU data bus are routed through the RF5C66 chip before making it to the card and other internal hardware.  It effectively blocks the Famicom Network System from driving the data bus for certain regions of memory, and possibly also is intended to act as a bidirectional buffer / signal conditioner.  It is also used for blocking writes when the lid switch is open or when the CIC fails.  Older revisions of Famicom Network System also buffered the Famicom address bus with 74HC541 chips, so it is plausible that signal conditioning was a concern.


=LH5323M1 Kanji Graphic ROM=
=LH5323M1 Kanji Graphic ROM=
The LH5323M1 is a 256kByte graphics ROM containing primarily Kanji data that is mapped at $5000-5FFF. Each index in this range is a 32-byte space containing 16x16 1bpp graphics, usually for a single character, and each read automatically advances to the next byte in the sequence. There are 2 128kByte banks, and the low bank is default at power-on. Writing 1 to $40B0.0 selects the high bank. Reading from $40B0 resets to the beginning of the 32-byte sequence.  Writing $40B0 does not reset the sequence however.  No values written to $40B0 have been observed to arbitrarily change or reset the position in the sequence.
The LH5323M1 is a 256kByte graphics ROM containing primarily Kanji data that is mapped at $5000-5FFF. Each index in this range is a 32-byte space containing 16x16 1bpp graphics, usually for a single character, and each read automatically advances to the next byte in the sequence. There are 2 128kByte banks, and the low bank is default at power-on. Writing 1 to $40B0.0 selects the high bank. Reading from $40B0 resets to the beginning of the 32-byte sequence.  Writing $40B0 does not reset the sequence however.  No values written to $40B0 have been observed to arbitrarily change or reset the position in the sequence.  Commercial software has been observed to use throwaway reads when accessing data that does not start at the beginning of the 32-byte area.
 
The Kanji ROM chip is connected directly to the non-buffered Famicom CPU data bus.  Writes in the range $5000-5FFF do activate Kanji ROM /CE and are subject to bus conflict.


=Expansion Audio=
=Expansion Audio=
Line 13: Line 15:


=Disk Drive Support=
=Disk Drive Support=
According to a block diagram with potentially dubious origins, the RF5C66 chip contains a disk drive controller.  Similar design in several ways to the Famicom Disk System, it is suspected that a disk drive can be connected to the expansion port and controlled by the RF5C66.  Since this feature was never used, it is unknown how to use or activate it, or even if that feature is fully implemented.  The original FDS has a large DRAM that is not present as a discrete chip in the Famicom Network System.  It is unknown if such a DRAM could be already integrated into the RF5C66, or could be attached externally and simply not populated, or if a special card was to be constructed containing this RAM.  All original FDS registers are notably absent and all discovered registers start immediately after where the FDS registers would normally be.  There is no obvious path to produce FDS expansion audio.  This remains a mystery presently.
According to a block diagram with potentially dubious origins, the RF5C66 chip contains a disk drive controller.  Similar design in several ways to the Famicom Disk System, it is suspected that a disk drive can be connected to the expansion port and controlled by the RF5C66.  Since this feature was never used, it is unknown how to use or activate it, or even if that feature is fully implemented.  The original FDS has a large DRAM that is not present as a discrete chip in the Famicom Network System.  It is unknown if such a DRAM could be already integrated into the RF5C66, or could be attached externally and simply not populated, or if a special tsuushin card was to be constructed containing this RAM.  All original FDS registers are notably absent and all discovered registers start immediately after where the FDS registers would normally be.  There is no obvious path to produce FDS expansion audio.  This remains a mystery presently.


One possibility if the RF5C66 follows a similar pinout to the FDS RP2C33:
One possibility if the RF5C66 follows a similar pinout to the FDS RP2C33:
Line 27: Line 29:


=Memory Map=
=Memory Map=
  +================+ $0000 - NES internal RAM
  +================+ $0000 - Famicom Internam RAM
  | NES internal  |
  | Famicom        |
  | RAM           |
  | Internal RAM   |
  +----------------+ $0800
  +----------------+ $0800
  |  (Mirrors of  |
  |  (Mirrors of  |
  |  $0000-$07FF) |
  |  $0000-$07FF) |
  +================+ $2000 - NES PPU Registers
  +================+ $2000 - Famicom PPU Registers
  | NES PPU       |
  | Famicom PPU   |
  | Registers      |
  | Registers      |
  +----------------+ $2008
  +----------------+ $2008
  |  (Mirrors of  |
  |  (Mirrors of  |
  |  $2000-$2007) |
  |  $2000-$2007) |
  +================+ $4000 - NES APU, IO, and Test Registers
  +================+ $4000 - Famicom APU, IO, and Test Registers
  | NES APU and IO |
  | FC APU and IO |
  | Registers      |
  | Registers      |
  +----------------+ $4018
  +----------------+ $4018
  | NES Test Mode |
  | FC Test Mode   |
  | Registers      |
  | Registers      |
  +----------------+ $4020
  +----------------+ $4020
  |  (Open Bus)  |
  |  (Open Bus)  |
  +================+ $40A0 - Famicom Modem Registers
  +================+ $40A0 - Famicom Network System Internal Registers
  | Famicom Modem  |
  | Famicom Modem  |
  | RF5C66        |
  | RF5C66        |
Line 53: Line 55:
  +----------------+ $40D0
  +----------------+ $40D0
  | Famicom Modem  |
  | Famicom Modem  |
  | RF5A18         |
  | RF5A18 (CPU2)  |
  | Registers      |
  | Registers      |
  +----------------+ $40D8
  +----------------+ $40D8
Line 59: Line 61:
  |  $40D0-$40D7) |
  |  $40D0-$40D7) |
  +----------------+ $40E0
  +----------------+ $40E0
| Unused Device  |
| Registers      |
| (Open Bus)    |
+----------------+ $40F0
  |  (Open Bus)  |
  |  (Open Bus)  |
  +----------------+ $4100
  +----------------+ $4100
Line 68: Line 74:
  |  (Mirrors of  |
  |  (Mirrors of  |
  |  $4100-$41FF) |
  |  $4100-$41FF) |
  +================+ $5000 - Famicom Modem Kanji ROM
  +================+ $5000 - Famicom Network System Internal Kanji ROM
  | Famicom Modem  |
  | FNS            |
  | LH5323M1      |
  | LH5323M1      |
  | Kanji ROM      |
  | Kanji ROM      |
  +================+ $6000 - Famicom Modem Internal RAM
  +================+ $6000 - Famicom Network System Internal RAM and Tsuushin Card RAM
  | Famicom Modem  |
  | FNS            |
  | Internal RAM  |
  | Internal RAM  |
  +================+ $8000 - Famicom Modem Card Space
  +================+ $8000 - Tsuushin Card ROM Space
  |               |
  | Tsuushin Card  |
  | Card Space     |
  | Space         |
  |                |
  |                |
  +================+ $10000
  +================+ $10000
==Data Bus Behavior==
The CPU data bus is buffered in both directions through the RF5C66 chip before making it to the tsuushin card and other internal hardware, with the exception of the Kanji graphics ROM and the RF5C66's own registers, which sit directly on the CPU data bus.  It appears that the buffer goes from CPU Data Bus to Card Data Bus, or Card Data Bus to CPU Data Bus only.  There has not been a high-impedance state observed when testing each possible address in read and write directions on a standalone RF5C66 chip.  The CPU Data Bus and Card Data Bus were always observed to be equal despite attaching opposite pull-up and pull-down resistors.
When RF5C66 pin 29 is driven low by the master CIC chip's pin 11, it forces Card R/W always high, thereby preventing most RAM and register writes in the Famicom Network System.  Potentially, the data bus buffer has an additional behavior in this mode in order to prevent bus conflicts.  The lid switch also imposes such a behavior when the lid is open, but it does not appear that the RF5C66 has a way of knowing when the switch is open, so the bus conflicts do not appear to be prevented in that case.
The propagation delay of the CPU data bus buffer and CPU R/W buffer are measured to be about 16 nsec.
{| class=wikitable
! Address Range !! Buffer Direction When Reading !! Buffer Direction When Writing !! Notes
|-
! $0x00-$4x1F
| {{no|CPU -> Card}}  || {{yes|CPU -> Card}} || Famicom internal RAM and registers
|-
! $4x20-$4x9F
| {{no|CPU -> Card}}  || {{yes|CPU -> Card}} || (unknown; [[FDS]] registers exactly fit here)
|-
! $4xA0-$4xCF
| {{no|CPU -> Card}}  || {{yes|CPU -> Card}} || RF5C66 registers
|-
! $4xD0-$4xDF
| {{yes|CPU <- Card}} || {{yes|CPU -> Card}} || CPU 2 registers, /CE at RF5C66 pin 42
|-
! $4xE0-$4xEF
| {{yes|CPU <- Card}} || {{yes|CPU -> Card}} || Unused device registers{{Sup|1}}, /CE at RF5C66 pin 41
|-
! $4xF0-$4xFF
| {{no|CPU -> Card}}  || {{yes|CPU -> Card}} || (unknown)
|-
! $5x00-$5xFF
| {{no|CPU -> Card}}  || {{yes|CPU -> Card}}{{Sup|2}} || Kanji graphic ROM, /CE at RF5C66 pin 50
|-
! $6x00-$7xFF
| {{yes|CPU <- Card}} || {{yes|CPU -> Card}} || Famicom Network System internal RAM, /CE at RF5C66 pin 40
|-
! $8x00-$FxFF
| {{yes|CPU <- Card}} || {{yes|CPU -> Card}} || Tsuushin card, /CE is /ROMSEL
|-
|}
{{Sup|1}} Address range $4xE0-$4xEF was meant for a second device similar to CPU 2.  Since that device doesn't exist, a tsuushin card could theoretically exploit those 256 addresses for its own purposes; for example, its own read/write registers.
{{Sup|2}} Writes here are subject to bus conflict on the CPU data bus.


=Known Registers=
=Known Registers=
Line 91: Line 140:
!|Function
!|Function
|-
|-
|$40A1
|$40A0
|{{unknown}}
|{{unknown}}
|{{yes}}
|{{no}}
|{{unknown}}
|{{unknown}}
|RF5C66
|RF5C66
|Unknown Function.
|No evidence has been found that this register does or does not exist.  It is possible that it is a write-only register that is not used by any known Famicom Network System card.  No reads or writes to this register were ever observed to have any effect.  However, its apparent absence is suspicious enough to have this placeholder here.
<pre>
<pre>
Write
Write
Line 104: Line 153:
Read
Read
76543210
76543210
++++++++-- Bits exist but function is unknown
++++++++-- (unlikely to exist)
</pre>
</pre>
{|role="presentation" class="wikitable mw-collapsible mw-collapsed"
{|role="presentation" class="wikitable mw-collapsible mw-collapsed"
Line 110: Line 159:
|-
|-
|
|
*Bench test observed value $FF with pull-downs.
*Bench test found open bus when reading this register.
*Test code writing values $01,02,04,08,10,20,40,80 always read back $FF after each write.
|}
|}
|-
|-
|$40A2
|$40A1
|{{yes}}
|{{unknown}}
|{{yes}}
|{{unknown}}
|RF5C66
|Unknown Function.
<pre>
Write
76543210
++++++++-- (unknown)
 
Read
76543210
++++++++-- Bits exist but function is unknown
</pre>
{|role="presentation" class="wikitable mw-collapsible mw-collapsed"
|Reference Data&nbsp;
|-
|
*Bench test observed value $FF with pull-downs.
*Test code writing values $01,02,04,08,10,20,40,80 always read back $FF after each write.
|}
|-
|$40A2
|{{yes}}
|{{yes}}
|{{yes}}
|{{unknown}}
|{{unknown}}
Line 555: Line 626:
|||||        See also $40B1.3.
|||||        See also $40B1.3.
||||+----- Pin 5C66.38 = $40C0.3 (POR value = 0)
||||+----- Pin 5C66.38 = $40C0.3 (POR value = 0)
||||        CHR-RAM Bank Select
||||        CHR RAM Bank Select (selects between two 8 KiB CHR RAM chips)
++++------ (unknown)
++++------ (unknown)


Line 561: Line 632:
76543210
76543210
|||||||+-- Input value of pin 5C66.31:
|||||||+-- Input value of pin 5C66.31:
|||||||      Host CIC /Reset
|||||||      From FNS CIC (Key) pin 10, or jumpered to GND on models without a CIC chip.
||||||+--- Input value of pin 5C66.32:
||||||+--- Input value of pin 5C66.32:
||||||      Host CIC /Fail
||||||      From FNS CIC (Key) pin 15, or jumpered to GND on models without a CIC chip.
|||||+---- Input value of pin 5C66.33:
|||||+---- Input value of pin 5C66.33:
|||||        CPU2 /Reset
|||||        CPU2 /Reset fed back in for all models, regardless which model-specific 5C66 pin is sending it out.
||||+----- Input value of pin 5C66.34:
||||+----- Input value of pin 5C66.34:
||||        Selected CHR RAM Bank
||||        Selected CHR RAM Bank, fed back in from 5C66.38.
|+++------ (unlikely to exist)
|+++------ (unlikely to exist)
+--------- Input value of pin 5C66.29:
+--------- Input value of pin 5C66.29:
             Filtered Host CIC +Start
             /CPU R/W Inhibit, from FNS CIC (Key) pin 11, or floating up to logic high on models without a CIC chip.
            1 = Writes to card, W-RAM, and $40Dx are allowed
            0 = Blocked (CPU R/W is overriden high, i.e. "read" for these writes)
</pre>
</pre>
*RAM +CE always reflects bit 0 of this register regardless of address space.
*RAM +CE always reflects bit 0 of this register regardless of address space.
**Refer also to $40AE.0 for built-in RAM enabling.
**Refer also to $40AE.0 for built-in RAM enabling.
*All examined software waits for D7 = 1 at initialization.
*All examined software waits for D7 = 1 at initialization.
*D7 is normally 1, but becomes and stays 0 if the cartridge is removed or is not present on power-on.
*D7 is controlled by the CIC key chip, if present.  If the CIC fails authentication, it latches to 0 until a power cycle.
*D1 and D0 always observed low in all cases, regardless if the model does not have CIC key chip, or does have the chip and authentication passes or fails.
**It is unknown in what scenario that the CIC chip could generate logic high on these pins.
**Theories:
***These pins may reflect detection of different lock CIC chips in the tsuushin card, for different regions or "disk drive mode" or something like that.
***Transient role at power-on, indicating when the CIC is ready.
***Showing internal error state of the CIC.
{|role="presentation" class="wikitable mw-collapsible mw-collapsed"
{|role="presentation" class="wikitable mw-collapsible mw-collapsed"
|Reference Data&nbsp;
|Reference Data&nbsp;
Line 706: Line 785:
|{{yes}}
|{{yes}}
|RF5A18
|RF5A18
|Unknown Function.
|Tone Rx and Expansion I/O Control
<pre>
<pre>
Write
Write
Line 741: Line 820:
|{{unknown}}
|{{unknown}}
|RF5A18
|RF5A18
|Unknown Function.
|Clocks
<pre>
<pre>
Write
Write
Line 754: Line 833:
*The purpose is unknown but it could potentially serve to generate random numbers.
*The purpose is unknown but it could potentially serve to generate random numbers.
**The Famicom CPU and CPU2 have separate clocks and are asynchronous, making the value read especially random.
**The Famicom CPU and CPU2 have separate clocks and are asynchronous, making the value read especially random.
{|role="presentation" class="wikitable mw-collapsible mw-collapsed"
|Reference Data&nbsp;
|-
|
*$40Dx registers can be monitored in real-time by statically giving the RF5A18 the bus signals for a read from this register.
**M2 = 1, Card R/W (i.e. buffered CPU R/W) = 1, Famicom /CE = 0, CPU A0,A1,A2 = x,x,x
**Unimplemented bits will latch the Famicom data bus's last value when toggling M2.
*Bits 7,6 follow pull-ups and downs on the data bus.
*Bit 5 is a 0.05% duty square wave, measured 1.200kHz (19.6608MHz CPU2 crystal / 16384)
*Bit 5 is a 0.05% duty square wave, measured 1.200kHz (19.6608MHz CPU2 crystal / 16384)
**Negative pulse width measures 406 nsec, the same as period of bit 2.
**Negative pulse width measures 406 nsec, the same as period of bit 2.
Line 772: Line 843:
*Bit 2 is a 50% duty square wave, measured 2.451MHz (19.6608MHz CPU2 crystal / 8)
*Bit 2 is a 50% duty square wave, measured 2.451MHz (19.6608MHz CPU2 crystal / 8)
*Bit 1 is a 50% duty square wave, measured 4.902MHz (19.6608MHz CPU2 crystal / 4)
*Bit 1 is a 50% duty square wave, measured 4.902MHz (19.6608MHz CPU2 crystal / 4)
**This bit toggles at the same rate as RF5A18 pin 42, though there is a 129.9 degree phase difference.
*Bit 0 is a 50% duty square wave, measured 9.804MHz (19.6608MHz CPU2 crystal / 2)
*Bit 0 is a 50% duty square wave, measured 9.804MHz (19.6608MHz CPU2 crystal / 2)
*The phasing of these signals do not line up nicely but they do stay in perfect sync with CPU2 M2.
*The phasing of these signals do not line up nicely but they do stay in perfect sync with CPU2 M2.
|}
{|role="presentation" class="wikitable mw-collapsible mw-collapsed"
|Reference Data&nbsp;
|-
|
*$40Dx registers can be monitored in real-time by statically giving the RF5A18 the bus signals for a read from this register.
**M2 = 1, Card R/W (i.e. buffered CPU R/W) = 1, Famicom /CE = 0, CPU A0,A1,A2 = x,x,x
**Unimplemented bits will latch the Famicom data bus's last value when toggling M2.
*Bits 7,6 follow pull-ups and downs on the data bus.
|}
|-
|-
|$40D6
|$40D6
Line 781: Line 861:
|{{unknown}}
|{{unknown}}
|RF5A18
|RF5A18
|Unknown Function.
|UART Status
<pre>
<pre>
Write
Write
Line 789: Line 869:
Read
Read
76543210
76543210
||||||++-- Bits exist but function is unknown
|||||||+-- Bit exists but function is unknown
|||||+---- $40D6.2 = !($4113.7 AND $4112.1) written by CPU2.
||||||+--- $40D6.1 = !($4112.0) read by CPU2.  (0 = $4110 UART Rx buffer has a byte ready to be read.)
|||||+---- $40D6.2 = !($4112.1) read by CPU2. (0 = $4110 UART Tx buffer can be written.)
||||+----- $40D6.3 = !($4113.1 OR $4113.2) written by CPU2.
||||+----- $40D6.3 = !($4113.1 OR $4113.2) written by CPU2.
|||+------ $40D6.4 = !($4113.7) written by CPU2.
|||+------ $40D6.4 = !($4113.7) written by CPU2. (1 = Transmit repeat.)
||+------- $40D6.5 = !($4113.6) written by CPU2.
||+------- $40D6.5 = !($4113.6) written by CPU2.
++-------- (unlikely to exist)
++-------- (unlikely to exist)
</pre>
</pre>
$40D6.2 previously observed to equal !($4113.7 AND $4112.1) written by CPU2.  It was later discovered that this bit also follows the $4112.1 read value (Tx buffer ready), which makes a lot more sense being beside $40D6.1 (Rx buffer ready).  The previous observation can be explained because writing to those CPU2 bits both likely changed the availability of the Tx buffer.
{|role="presentation" class="wikitable mw-collapsible mw-collapsed"
{|role="presentation" class="wikitable mw-collapsible mw-collapsed"
|Reference Data&nbsp;
|Reference Data&nbsp;
Line 801: Line 883:
|
|
*Bits 7,6 follow pull-ups and downs on the data bus.
*Bits 7,6 follow pull-ups and downs on the data bus.
*Bits 1 and 0 only ever observed with value 1 regardless of various techniques writing to lots of CPU2 registers.
*Bit 0 only ever observed with value 1 regardless of various techniques writing to lots of CPU2 registers.
*Writing a value to this register does not ''seem to'' cause its own read value to change.
*Writing a value to this register does not ''seem to'' cause its own read value to change.
|}
|}
Line 815: Line 897:


==CPU2 Memory Map==
==CPU2 Memory Map==
===RF5A18 Pin 26 Low (default)===
  +================+ $0000
  +================+ $0000
  | CPU2 RAM      |
  | CPU2 RAM      |
Line 828: Line 911:
  |  last fetch)  |
  |  last fetch)  |
  +================+ $C000
  +================+ $C000
  |   (Open Bus)   |
  | External ROM   |
  |               |
  | (not used)    |
  +================+ $E000
  +================+ $E000
  | RF5A18        |
  | RF5A18        |
  | Internal ROM  |
  | Internal ROM  |
+================+ $10000
===RF5A18 Pin 26 High===
+================+ $0000
| CPU2 RAM      |
| (U6)          |
+================+ $2000
|  (Returns    |
|  last fetch)  |
+================+ $4100
| CPU2 Control  |
| Registers      |
+================+ $4140
|  (Returns    |
|  last fetch)  |
+================+ $C000
|                |
|                |
| External ROM  |
|                |
|                |
  +================+ $10000
  +================+ $10000


Line 1,071: Line 1,175:
|-
|-
|$4110
|$4110
|{{unknown}}
|{{yes}}
|{{yes}}
|{{yes}}
|{{yes}}
|{{yes}}
Line 1,084: Line 1,188:
76543210
76543210
++++++++-- UART Rx Data Byte
++++++++-- UART Rx Data Byte
            Bits 7:0 in 8-bit mode, bits 6:0 in 7-bit mode
</pre>
</pre>
*Writing a byte to this register causes the byte to be sent on pin 90 (MSM6827L TXD).
*Writing a byte to this register automatically clears $4112.1 read value and triggers the byte to be sent on UART Tx.
*Reading a byte from this register automatically clears $4112.0 read value, to be triggered high again next byte received on UART Rx.
*This UART is connected to the MSM6827L TXD and RXD pins.
*This UART is connected to the MSM6827L TXD and RXD pins.
*The byte is ready to read here when the IRQ flag $4112.0 is high.
*The byte is ready to read here when the IRQ flag $4112.0 is high.
Line 1,091: Line 1,197:
*Writes to $4110 are specifically prevented by built-in ROM in modes 0 and 5.
*Writes to $4110 are specifically prevented by built-in ROM in modes 0 and 5.
*Bench testing confirmed reads and writes of this register correspond to data read by UART Rx and written to UART Tx.
*Bench testing confirmed reads and writes of this register correspond to data read by UART Rx and written to UART Tx.
**In 7-bit mode, Rx bit 7 (unused in this case) observed to be 0 but not confirmed always to be 0.
{|role="presentation" class="wikitable mw-collapsible mw-collapsed"
{|role="presentation" class="wikitable mw-collapsible mw-collapsed"
|Reference Data&nbsp;
|Reference Data&nbsp;
Line 1,114: Line 1,221:
Write
Write
76543210
76543210
||||||++-- Bits exist but function is unknown.
|||||||+-- $4111.0 = UART Rx Enable (1 = enabled)
||||||+--- $4111.1 = UART Tx Enable (1 = enabled)
|||||+---- $4111.2 = Baudrate Scaler (0 = multiply baudrate x4)
|||||+---- $4111.2 = Baudrate Scaler (0 = multiply baudrate x4)
||||+----- $4111.3 = Data bits (0 = 7 bits, 1 = 8 bits)
||||+----- $4111.3 = Data bits (0 = 7 bits, 1 = 8 bits)
|||+------ $4111.4 = Stop bits (0 = 1 stop bit, 1 = 2 stop bits)
|||+------ $4111.4 = Tx Stop bits (0 = 1 stop bit, 1 = 2 stop bits)
||+------- $4111.5 = Parity bit (0 = don't use, 1 = append parity bit)
||+------- $4111.5 = Parity bit (0 = don't use, 1 = append parity bit)
|+-------- $4111.6 = Parity type (0 = odd parity, 1 = even parity)
|+-------- $4111.6 = Parity type (0 = odd parity, 1 = even parity)
+--------- $4111.7 = Pin 90 (MSM6827L TXD) = !($4111.7)
+--------- $4111.7 = Send Tx Break (1 = force UART Tx low (break), 0 = normal)


Read
Read
76543210
76543210
++++++++-- Bits exist but function is unknown.
++++++++-- Reads back the value written.
</pre>
</pre>
*For data to come out from pin 90 (MSM6827L TXD), these settings are required:
**Bit 0 = 0 (This bit needs to be confirmed that it is required = 0 for Tx.)
**Bit 1 = 1
**Bit 7 = 0
*See register $4114 for baudrate table.
*See register $4114 for baudrate table.
*This register bench tested using pin 90 (UART Tx).
*Confirmed write bits 2,3,5,6 apply to both Rx and Tx.
**Unconfirmed if the settings also apply to UART Rx.
*Write bit $4111.4 confirmed not to enforce 2 stop bits for UART Rx.
*Bit 7 seems to be an active low enable of the UART.
**Consecutive Rx bytes with 1 stop bit separation can still be received when $4111.4 = 1.
**Bit 7 high drives the Tx pin low; it is not a hi-z state.
*Write bit $4111.7 requires manual operation to send a break character and has no effect on Rx operation.
*Bench test showed that $4111.0 had to be 1 for a UART Rx byte to get received into $4110.
**$4111.1 did not affect the ability to receive the byte on UART Rx.
{|role="presentation" class="wikitable mw-collapsible mw-collapsed"
{|role="presentation" class="wikitable mw-collapsible mw-collapsed"
|Reference Data&nbsp;
|Reference Data&nbsp;
Line 1,165: Line 1,267:
|{{yes}}
|{{yes}}
|{{yes}}
|{{yes}}
|UART IRQ Acknowledge
|UART Status
<pre>
<pre>
Write
Write
Line 1,171: Line 1,273:
|||||||+-- Bit exists but function is unknown
|||||||+-- Bit exists but function is unknown
||||||+--- $4112.1: Tx Silence
||||||+--- $4112.1: Tx Silence
||||||      0 = Set pin 90 (UART Tx) directly high (idle state), 1 = Allow sending data.
||||||      0 = Set UART Tx directly high (idle state), 1 = Allow sending data.
||||||      This bit figures into $40D6.2 read by the Famicom. (See register $40D6.)
||||||      This bit figures into $40D6.2 read by the Famicom. (See register $40D6.)
|+++++---- (unknown)
|+++++---- (unknown)
Line 1,178: Line 1,280:
Read
Read
76543210
76543210
|||||||+-- $4112.0 = $4110 UART Rx Data IRQ Flag, 1 = IRQ Pending.
|||||||+-- $4112.0 = $4110 UART Rx Buffer Ready Flag (1 = $4110 buffer has a byte ready to be read.)
||||||+--- $4112.1 = $4110 UART Tx Ready Flag, 1 = byte can be written.
||||||+--- $4112.1 = $4110 UART Tx Buffer Ready Flag (1 = $4110 buffer can be written.)
||||++---- Bits exist but function is unknown
|||||+---- $4112.2 = UART Tx Idle, 1 = Idle, 0 = Active.
||||+----- Bit exists but function is unknown
|||+------ $4112.4 = Rx Parity Error. (1 = error detected)
|||+------ $4112.4 = Rx Parity Error. (1 = error detected)
+++------- Bits exist but function is unknown
||+------- $4112.5 = Rx Framing Error. (1 = error detected)
|+-------- $4112.6 = Rx Break Received. (1 = break detected)
+--------- Bit exists but function is unknown
</pre>
</pre>
*The ROM suggests that when the IRQ flag is set, a new UART Rx data byte is available in $4110.
*Error and Break bits persist through $4110 operations, but can be cleared by writing 1 to $4112.7.
**This was not confirmed with a bench test, no flag has yet been found when receiving a byte.
*Found $4112.4 read became 1 when setting in parity mode ($4111.5 = 1) and injecting a wrong parity bit.
*Found $4112.4 read became 1 when setting in parity mode ($4111.5 = 1) and injecting a wrong parity bit.
**Confirmed this flag not getting set when changing parity even/odd (i.e. inverted $4111.6).
**Confirmed this flag not getting set anymore with the same test when changing parity even/odd (i.e. inverted $4111.6).
*$4112.6 = 1 (break) comes accompanied with $4112.5 = 1 (framing error).
{|role="presentation" class="wikitable mw-collapsible mw-collapsed"
{|role="presentation" class="wikitable mw-collapsible mw-collapsed"
|Reference Data&nbsp;
|Reference Data&nbsp;
Line 1,229: Line 1,334:
|+-------- $4113.6 figures into $40D6.5 read by the Famicom. (See register $40D6.)
|+-------- $4113.6 figures into $40D6.5 read by the Famicom. (See register $40D6.)
+--------- $4113.7: Tx Repeat
+--------- $4113.7: Tx Repeat
             1 = Send once on pin 90 (MSM6827L TXD), 0 = Send repeatedly
             1 = Send once on pin 90 (UART Tx), 0 = Send repeatedly
             This figures into $40D6.2 and $40D6.4 read by the Famicom. (See register $40D6.)
             This figures into $40D6.2 and $40D6.4 read by the Famicom. (See register $40D6.)


Line 1,265: Line 1,370:
Write
Write
76543210
76543210
||||||++-- Baud Rate of pin 90 (MSM6827L TXD)
||||||++-- UART Baud Rate (Rx and Tx)
||||||      This is a clock divider that also affects frequency seen on $40D5.4.
||||||      This is a clock divider that also affects frequency seen on $40D5.4.
++++++---- (unknown)
++++++---- (unknown)
Line 1,747: Line 1,852:
||+------- $412F.5 = Pin 73 (Tone Rx DV) IRQ enable.  1 = Enabled.
||+------- $412F.5 = Pin 73 (Tone Rx DV) IRQ enable.  1 = Enabled.
|+-------- $412F.6 = Timer 2 IRQ enable.  1 = Enabled.
|+-------- $412F.6 = Timer 2 IRQ enable.  1 = Enabled.
+--------- Bit exists but function is unknown (Probably UART Rx IRQ enable.)
+--------- $412F.7 = UART Rx IRQ enable. 1 = Enabled.


Read
Read
Line 1,766: Line 1,871:
*Pin 33 (MSM6827L /INT) low triggers interrupt.
*Pin 33 (MSM6827L /INT) low triggers interrupt.
*Pin 73 (Tone Rx DV) high triggers interrupt.
*Pin 73 (Tone Rx DV) high triggers interrupt.
*Theory: $412F.7 = UART Rx Interrupt enable.  (Always triggers at power-on when Rx pin is high, which crashes my test setup.)
{|role="presentation" class="wikitable mw-collapsible mw-collapsed"
{|role="presentation" class="wikitable mw-collapsible mw-collapsed"
|Reference Data&nbsp;
|Reference Data&nbsp;
Line 1,798: Line 1,902:
Write
Write
76543210
76543210
++++++++-- (unknown)
|||||||+-- Serial bit to be written
+++++++--- (unknown, unlikely to exist)


Read
Read
Line 1,804: Line 1,909:
++++++++-- (unlikely to exist)
++++++++-- (unlikely to exist)
</pre>
</pre>
*The buffer at RAM $0330 is written to this register 1 bit at a time, seemingly using only bit 0 of the register.
*The most significant bit of each byte is sent first.
*40 bytes are sent from $0330, then only the 6 most significant bits of the 41st byte.
**A total of 326 bits are sent to this register.
*Note: CPU2 commands $10 and $11 fill this buffer.
{|role="presentation" class="wikitable mw-collapsible mw-collapsed"
{|role="presentation" class="wikitable mw-collapsible mw-collapsed"
|Reference Data&nbsp;
|Reference Data&nbsp;
|-
|-
|
|
*The buffer at RAM $0330 is written to this register 1 bit at a time, seemingly using only bit 7 of the register.
**Note: CPU2 commands $10 and $11 fill this buffer.
*Read Bit Existence:
*Read Bit Existence:
**Values $41, $40, $26, and $BF from previous fetch observed unaffected.
**Values $41, $40, $26, and $BF from previous fetch observed unaffected.
Line 1,824: Line 1,932:
Write
Write
76543210
76543210
++++++++-- (unknown)
|||||||+-- Serial bit to be written
+++++++--- (unknown, unlikely to exist)


Read
Read
Line 1,830: Line 1,939:
++++++++-- (unlikely to exist)
++++++++-- (unlikely to exist)
</pre>
</pre>
*The buffer at RAM $0360 is written to this register 1 bit at a time, seemingly using only bit 0 of the register.
*The most significant bit of each byte is sent first.
*40 bytes are sent from $0360, then only the 6 most significant bits of the 41st byte.
**A total of 326 bits are sent to this register.
*Note: CPU2 commands $10, $11, and $6A fill this buffer.
{|role="presentation" class="wikitable mw-collapsible mw-collapsed"
{|role="presentation" class="wikitable mw-collapsible mw-collapsed"
|Reference Data&nbsp;
|Reference Data&nbsp;
|-
|-
|
|
*The buffer at RAM $0360 is written to this register 1 bit at a time, seemingly using only bit 7 of the register.
**Note: CPU2 commands $10, $11, and $6A fill this buffer.
*Read Bit Existence:
*Read Bit Existence:
**Values $41, $40, and $BF from previous fetch observed unaffected.
**Values $41, $40, and $BF from previous fetch observed unaffected.
Line 1,850: Line 1,962:
Write
Write
76543210
76543210
++++++++-- (unknown)
|||||||+-- Serial bit to be written
+++++++--- (unknown, unlikely to exist)


Read
Read
Line 1,856: Line 1,969:
++++++++-- (unlikely to exist)
++++++++-- (unlikely to exist)
</pre>
</pre>
*The buffer at RAM $0390 is written to this register 1 bit at a time, seemingly using only bit 0 of the register.
*The most significant bit of each byte is sent first.
*40 bytes are sent from $0390, then only the 6 most significant bits of the 41st byte.
**A total of 326 bits are sent to this register.
*Note: CPU2 commands $10, $11, and $6A fill this buffer.
{|role="presentation" class="wikitable mw-collapsible mw-collapsed"
{|role="presentation" class="wikitable mw-collapsible mw-collapsed"
|Reference Data&nbsp;
|Reference Data&nbsp;
|-
|-
|
|
*The buffer at RAM $0390 is written to this register 1 bit at a time, seemingly using only bit 7 of the register.
**Note: CPU2 commands $10, $11, and $6A fill this buffer.
*Read Bit Existence:
*Read Bit Existence:
**Values $41, $40, and $BF from previous fetch observed unaffected.
**Values $41, $40, and $BF from previous fetch observed unaffected.
Line 1,876: Line 1,992:
Write
Write
76543210
76543210
++++++++-- (unknown)
|||||||+-- Serial bit to be written
+++++++--- (unknown, unlikely to exist)


Read
Read
Line 1,882: Line 1,999:
++++++++-- (unlikely to exist)
++++++++-- (unlikely to exist)
</pre>
</pre>
*The buffer at RAM $0320 is written to this register 1 bit at a time, seemingly using only bit 0 of the register.
*The most significant bit of each byte is sent first.
*4 bytes are sent from $0320, then only the 4 most significant bits of the 5th byte.
**A total of 36 bits are sent to this register.
*Note: CPU2 commands $10 and $11 fill this buffer.
{|role="presentation" class="wikitable mw-collapsible mw-collapsed"
{|role="presentation" class="wikitable mw-collapsible mw-collapsed"
|Reference Data&nbsp;
|Reference Data&nbsp;
|-
|-
|
|
*The buffer at RAM $0320 is written to this register 1 bit at a time, seemingly using only bit 7 of the register.
**Note: CPU2 commands $10 and $11 fill this buffer.
*Read Bit Existence:
*Read Bit Existence:
**Values $41, $40, and $BF from previous fetch observed unaffected.
**Values $41, $40, and $BF from previous fetch observed unaffected.
Line 1,895: Line 2,015:
|-
|-
|$4134
|$4134
|{{unknown}}
|{{yes}}
|{{yes}}
|{{yes}}
|{{unknown}}
|{{unknown}}
Line 1,909: Line 2,029:
+++++++--- (unlikely to exist)
+++++++--- (unlikely to exist)
</pre>
</pre>
*This register has serial data that can be read 1 bit at a time from $4134.0.
**Without any other register reads/writes, the next bit is provided the next time this register is read.
*In each byte read, the most significant bit comes first.
*CPU2 built-in ROM reads 40 bytes this way and stores them starting at RAM $03C0.
**Then 6 additional bits are read and stored as the 41st byte bits 7:2, and 0 for bits 1:0.
{|role="presentation" class="wikitable mw-collapsible mw-collapsed"
{|role="presentation" class="wikitable mw-collapsible mw-collapsed"
|Reference Data&nbsp;
|Reference Data&nbsp;
Line 1,934: Line 2,059:
Read
Read
76543210
76543210
|||||||+-- Bit exists but function is unknown
|||||||+-- $4135.0 = $4134 Serial Data Ready (1 = ready)
+++++++--- (unlikely to exist)
+++++++--- (unlikely to exist)
</pre>
</pre>
*If $4135.0 = 1, Built-in ROM proceeds to read the serial data from $4134.
*Note: Built-in ROM only treats this register as a flag and does not treat it as serial data.
{|role="presentation" class="wikitable mw-collapsible mw-collapsed"
{|role="presentation" class="wikitable mw-collapsible mw-collapsed"
|Reference Data&nbsp;
|Reference Data&nbsp;
Line 1,963: Line 2,090:
++++++++-- (unlikely to exist)
++++++++-- (unlikely to exist)
</pre>
</pre>
*Built-in ROM writes #$00 to $4137, then writes serial data to $4130, $4131, $4132, $4133, then writes #$00 to this register.
*Theory: This is a "start" flag that starts using new data from $4130-4133 when the flag is cleared.
{|role="presentation" class="wikitable mw-collapsible mw-collapsed"
{|role="presentation" class="wikitable mw-collapsible mw-collapsed"
|Reference Data&nbsp;
|Reference Data&nbsp;
Line 1,986: Line 2,115:
++++++++-- (unlikely to exist)
++++++++-- (unlikely to exist)
</pre>
</pre>
*Built-in ROM writes #$00 to this register, then writes serial data to $4130, $4131, $4132, $4133, then writes #$00 to $4136.
*Theory: This is a "clear" flag that resets write bit counters and/or clears old data from $4130-4133 when the flag is cleared.
{|role="presentation" class="wikitable mw-collapsible mw-collapsed"
{|role="presentation" class="wikitable mw-collapsible mw-collapsed"
|Reference Data&nbsp;
|Reference Data&nbsp;
Line 2,037: Line 2,168:
|$83
|$83
|This command is received by the Famicom in response to writing to command $03.  (See next section for details.)
|This command is received by the Famicom in response to writing to command $03.  (See next section for details.)
|-
|$90
|This command is received by the Famicom in response to writing to command $10.  (See next section for details.)
|-
|$91
|This command is received by the Famicom in response to writing to command $11.  (See next section for details.)
|-
|-
|$92
|$92
Line 2,042: Line 2,179:
|-
|-
|$C0
|$C0
|Unknown function.
|UART Rx Packet
There are 2 different parts of the CPU2 code that can send this message:
There are 2 different parts of the CPU2 code that can send this message:
<pre>[$C0] [count=N] [parameter] [...N bytes...]</pre>
<pre>[$C0] [count=N] [parameter] [...N bytes...]</pre>
Line 2,049: Line 2,186:
*[...N bytes...] are read from register $4110, most recent reads first, 1 byte read from $4110 per IRQ.
*[...N bytes...] are read from register $4110, most recent reads first, 1 byte read from $4110 per IRQ.
*Count N does not include the parameter byte.
*Count N does not include the parameter byte.
*Theory: This is serial data received from the Oki MSM6827L integrated modem chip.
*This is serial data received from the Oki MSM6827L integrated modem chip.
*This response can only happen in mode 2 via IRQ.
*This response can only happen in mode 2 via IRQ.
<br/>
<br/>
Line 2,266: Line 2,403:
|40
|40
|0,2,5
|0,2,5
|Unknown Function.
|Unknown $413x Function.
<pre>Message Bytes:
<pre>Message Bytes:
[$10] [count=$28] [parameter] [...40 bytes...]</pre>
[$10] [count=$28] [parameter] [...40 bytes...]
 
Response:
[$90] [count=$28] [response parameter] [...40 bytes...]</pre>
*This command is similar to command $11, except using pre-defined data from ROM instead of the additional chunks in command $11.
*This command is similar to command $11, except using pre-defined data from ROM instead of the additional chunks in command $11.
*[parameter] is used but does not count towards the byte count.
*[parameter] is used but does not count towards the byte count.
Line 2,291: Line 2,431:
*Writes the 4 data chunks shifting 1 bit at a time to $4130, $4131, $4132, $4133
*Writes the 4 data chunks shifting 1 bit at a time to $4130, $4131, $4132, $4133
*Writes #$00 to $4136
*Writes #$00 to $4136
*For the response, the count has not been confirmed to include [response parameter] or not.
*The response comes from RAM starting at $03C0.  (See register $4134.)
{|role="presentation" class="wikitable mw-collapsible mw-collapsed"
|ROM Data&nbsp;
|-
|-
|$11
|
|$F75C
Data Loaded to $0330 (which later gets written to register $4130):
|127
 
|0,2,5
(These are the 40 bytes supplied by the Famicom to this command, with 1st byte and 41st byte set to $00.)
|Unknown Function.
|-
<pre>Message Bytes:
|
[$11] [count=$7F] [...5 byte chunk...] [...41 byte chunk 0...]
Data Loaded to $0360 (which later gets written to register $4131):
                  [...41 byte chunk 1...] [...41 byte chunk 2...]</pre>
{|class="wikitable"
*Note that the first byte of the 5 byte chunk is not ignored in this command like it is in most others, though it still does not count towards the byte count.
!|Parameter Bits
*The 5 byte chunk gets written to RAM starting at $0320 with lots of bit shifting and byte swapping.  (See Register $4133.)
!|Data
*The 41 byte chunk 0 gets copied to RAM starting at $0330.  (See Register $4130.)
|-
*The 41 byte chunk 1 gets copied to RAM starting at $0360.  (See Register $4131.)
|xxxxx000
*The 41 byte chunk 2 gets copied to RAM starting at $0390.  (See Register $4132.)
|00000c6bbc41351b1e0fa372963f7af704415090ee9a139ff87c60ca610dec66f74bd5b992c8868300
*Shares the remaining code in common with command $10.
|-
|xxxxx001
|0000027473468ebd1f161331ad0e5512ba56487f7b30037dac78ed9c51b308b6d8c597ca8b59cc1300
|-
|-
|$12
|xxxxx010
|$F773
|000001c89b4630b518cbc342a45282fa0908773df56830150ec1955c9ec1abbd1100d4d878604afd00
|>= 3<br/><= 252
|0,2,5
|CRC Calculator
<pre>Message Bytes:
[$12] [count=N] [initial] [polynomial 1] [polynomial 2] [...N-2 bytes...]
 
Response:
[$92] [count=$02] [$00] [CRC 2] [CRC 1]</pre>
*The [initial] byte does not count towards the byte count.
*See next section for information about CRC keys.
*Doesn't seem to write to any registers.
|-
|-
|$40
|xxxxx011
|$F7AF
|00000939c25f1859304000e9fdab927959a49d1acdd136da4ddb2b551b2bc942a36077d1d09dbc3500
|>= 1<br/><= 252
|2
|Unknown Function.
<pre>Message Bytes:
[$40] [count=N] [xx] [...N-1 bytes...]</pre>
*[xx] byte is ignored, but ''does'' count towards the byte count.
*Copies the N-1 bytes data directly into memory starting at the location +2 pointed to by $0000:0001.
*Copies the byte count to the location +1 pointed to by $0000:0001.
*Writes value $FF directly to the location pointed to by $0000:0001.
**Not known what sets up that pointer.
*This command is tricky to disassemble because it actually does copy the [xx] byte, then writes over it with the byte count, ultimately not using it.
|-
|-
|$41
|xxxxx100
|$F7D0
|3cfed7ad4cd7435c3544144572d1d0e83d1859864bf8c7412cac015ced49a1cabce13fbd6262af0b00
|>= 1<br/><= 100
|5
|Unknown Function.
<pre>Message Bytes:
[$41] [count=N] [xx] [...N bytes...]</pre>
*[xx] byte is ignored and does not count towards the byte count.
*Writes ((Byte count + 2) * 2) to the location +1 pointed to by $0000:0001.
*Writes value $00 to the location +2 pointed to by $0000:0001.
*Writes value $0F to the location +3 pointed to by $0000:0001.
*For each of N bytes:
**Writes upper nybble of the byte (>> 4) to the next byte pointed to by $0000:0001.
**Writes the lower nybble of the byte (& $0F) to the next byte pointed to by $0000:0001.
*Appends the value of $007C similarly as 2 nybbles at the end.
*Writes value $FF directly to the location pointed to by $0000:0001.
**Not known what sets up that pointer.
|-
|-
|$60
|xxxxx101
|$F829
|8aac02df739c8c0a2572493bd95755450b06ea0d77f1f08bc665636ed3cf317cb89f6f301ef03a2f00
|6
|0
|Unknown Function.
<pre>Message Bytes:
[$60] [count=$06] [...6 data bytes...]</pre>
*Note that the first data byte is not ignored in this command, and it ''does'' count towards the byte count.
*The 6 data bytes written by this command get copied to CPU2 RAM starting at address $84.
*PiT Motorboat Race uses this command when opening a connection.
*Observed Messages (unused bytes in parentheses):
**PiT Motorboat Race rev 02:
***60 06 00 01 80 00 00 00 (00)
|-
|-
|$61
|xxxxx110
|$F839
|39b07c4f12614dadb4eb214af3a6a0dc046b47d10c184b04d16c91d9eeb5e0c21a052529738c6f0100
|0
|1,3,4
|Disconnect
<pre>Message Bytes:
[$61] [count=$00]</pre>
*This command abruptly disconnects the modem.
*Writes #$00 to register $4102.  (Stops NMI timer 1.)
*Changes mode to 0 when complete.
|-
|-
|$62
|xxxxx111
|$F849
|36a6a31fa79ba49a9f1d1985c640ad9a6c79a4195d06ece8726fc006e1d347efa5d129cdb79017b900
|1
|0,2,5
|Unknown Function.
<pre>Message Bytes:
[$62] [count=$01] [xx] [parameter]</pre>
*[xx] byte is ignored.
*Disables interrupts while executing this command.
*Valid values of the [parameter] byte are $00 and $01.
**Other values abort the command.
*Appears to write to $4120
|-
|-
|$63
|}
|$F887
|-
|0
|
|0,1,2,3,<br/>4,5
Data Loaded to $0390 (which later gets written to register $4132):
|NOP Command
{|class="wikitable"
<pre>Message Bytes:
!|Parameter Bits
[$63] [count=$00]</pre>
!|Data
*This command only validates the byte count = #$00 and is then complete.
|-
|xxxxxx00
|882a14099f3f32b2419d0b09237a252ece6534274700628043a6df86657a84c0c4463fa72b49ad4900
|-
|xxxxxx01
|bbb57552f19d8a71d6ed68fd037188b700eab270071acedc624ff4c64b53ed1c4e1046ed89e775fd00
|-
|xxxxxx10
|cfb8e78ec54b81a1100f02f524acf0e05a45cc36a98f161c115a41082abb587ecabad5453511877100
|-
|xxxxxx11
|aa189432166db82500fffbb1107ced2469b12f0959b263c63a0332bb4a8e6ea378a0a47150cb296100
|-
|}
|-
|
Data Loaded to $0320 (which later gets written to register $4133):
{|class="wikitable"
!|Parameter Bits
!|Data
|-
|xxxxxxxx
|0140500060
|-
|}
|}
|-
|-
|$64
|$11
|$F88D
|$F75C
|1
|127
|0,2,5
|0,2,5
|Modem Off Hook Control
|Unknown $413x Function.
<pre>Message Bytes:
<pre>Message Bytes:
[$64] [count=$01] [xx] [Modem Off Hook mode]</pre>
[$11] [count=$7F] [...5 byte chunk...] [...41 byte chunk 0...]
*[xx] byte is ignored.
                  [...41 byte chunk 1...] [...41 byte chunk 2...]
*[Modem Off Hook mode] Values:
 
**$00 = Don't update but save mode as $00.
Response:
**$01 = Set $4127.4 (/Modem Off Hook) = 0 (off hook). (Also stores #$00 to $0049)
[$91] [count=$29] [response parameter] [...41 bytes...]</pre>
**$02-FF = Set $4127.4 (/Modem Off Hook) = 1 (hang up). (Also stores #$00 to $0049)
*Note that the first byte of the 5 byte chunk is not ignored in this command like it is in most others, though it still does not count towards the byte count.
**Value gets saved to $004E.
*The 5 byte chunk gets written to RAM starting at $0320 with lots of bit shifting and byte swapping.  (See Register $4133.)
*PiT Motorboat Race uses this command when closing a connection.
*The 41 byte chunk 0 gets copied to RAM starting at $0330. (See Register $4130.)
*Observed Messages (unused bytes in parentheses):
*The 41 byte chunk 1 gets copied to RAM starting at $0360. (See Register $4131.)
**PiT Motorboat Race rev 02:
*The 41 byte chunk 2 gets copied to RAM starting at $0390.  (See Register $4132.)
***64 01 (00) 02 (A9 31)
*Shares the remaining code in common with command $10.
*Note: This description is fairly complete.
*For the response, the count has not been confirmed to include [response parameter] or not.
*The response comes from RAM starting at $03C0.  (See register $4134.)
|-
|-
|$65
|$12
|$F89D
|$F773
|2
|>= 3<br/><= 252
|0,2,5
|0,2,5
|Modem Audio Enable and P4-19 Control
|CRC Calculator
<pre>Message Bytes:
<pre>Message Bytes:
[$65] [count=$02] [xx] [Modem Audio Enable mode] [P4-19 mode]</pre>
[$12] [count=N] [initial] [polynomial 1] [polynomial 2] [...N-2 bytes...]
*[xx] byte is ignored.
 
*[Modem Audio Enable mode] Values:
Response:
**$00 = Don't update but save mode as $00.
[$92] [count=$02] [$00] [CRC 2] [CRC 1]</pre>
**$01 = Set $4127.6 (/Modem Audio Enable) = 0 (enabled to TV speakers).
*The [initial] byte does not count towards the byte count.
**$02-FF = Set $4127.6 (/Modem Audio Enable) = 1 (disabled).
*See next section for information about CRC keys.
**Value gets saved to $004F.
*Doesn't seem to write to any registers.
*[P4-19 mode] Values:
|-
**$00 = Don't update but save mode as $00.
|$40
**$01 = Set $4127.7 (Modem P4-19) = 0.
|$F7AF
**$02-FF = Set $4127.7 (Modem P4-19) = 1.
|>= 1<br/><= 252
**Value gets saved to $0050.
*Heart no Benrikun Mini rev 01 A uses this command when closing a connection.
*Observed Messages (unused bytes in parentheses):
**Heart no Benrikun Mini rev 01 A:
***65 02 (00) 02 00 (20)
*Note: This description is fairly complete.
|-
|$66
|$F8B7
|2
|2
|0,2,5
|Unknown Function.
|LED Control
<pre>Message Bytes:
<pre>Message Bytes:
[$66] [count=$02] [xx] [red LED mode] [green LED mode]</pre>
[$40] [count=N] [xx] [...N-1 bytes...]</pre>
*[xx] byte is ignored.
*[xx] byte is ignored, but ''does'' count towards the byte count.
*[red LED mode] Values:
*Copies the N-1 bytes data directly into memory starting at the location +2 pointed to by $0000:0001.
**$00 = Don't update but save mode as $00.
*Copies the byte count to the location +1 pointed to by $0000:0001.
**$01 = Set Red LED on.
*Writes value $FF directly to the location pointed to by $0000:0001.
**$02-7F = Set Red LED off.
**Not known what sets up that pointer.
**$80-FF = Set Red LED to be controlled automatically by network status.
*This command is tricky to disassemble because it actually does copy the [xx] byte, then writes over it with the byte count, ultimately not using it.
**Value gets saved to $004C.
*Theory: This command sends a UART Tx Packet to the Oki MSM6827L, and connected with response command $C0.
*[green LED mode] Values:
|-
**$00 = Don't update but save mode as $00.
|$41
**$01 = Set Green LED on.
|$F7D0
**$02-7F = Set Green LED off.
|>= 1<br/><= 100
**$80-FF = Set Green LED to be controlled automatically by network status.
|5
**Value gets saved to $004D.
|Unknown Function.
*PiT Motorboat Race uses this command when closing a connection.
<pre>Message Bytes:
*Observed Messages (unused bytes in parentheses):
[$41] [count=N] [xx] [...N bytes...]</pre>
**PiT Motorboat Race rev 02:
*[xx] byte is ignored and does not count towards the byte count.
***66 02 (00) 02 02 (31)
*Writes ((Byte count + 2) * 2) to the location +1 pointed to by $0000:0001.
*Note: This description is fairly complete.
*Writes value $00 to the location +2 pointed to by $0000:0001.
*Writes value $0F to the location +3 pointed to by $0000:0001.
*For each of N bytes:
**Writes upper nybble of the byte (>> 4) to the next byte pointed to by $0000:0001.
**Writes the lower nybble of the byte (& $0F) to the next byte pointed to by $0000:0001.
*Appends the value of $007C similarly as 2 nybbles at the end.
*Writes value $FF directly to the location pointed to by $0000:0001.
**Not known what sets up that pointer.
*Theory: This command is something to do with the Tone Rx chip, and connected with response command $C1.
|-
|-
|$67
|$60
|$F8D1
|$F829
|2
|6
|0,5
|0
|Unknown Function.
|Unknown Function.
<pre>Message Bytes:
<pre>Message Bytes:
[$67] [count=$02] [xx] [parameter 0] [parameter 1]</pre>
[$60] [count=$06] [...6 data bytes...]</pre>
*[xx] byte is ignored.
*Note that the first data byte is not ignored in this command, and it ''does'' count towards the byte count.
*If [parameter 0] is $00:
*The 6 data bytes written by this command get copied to CPU2 RAM starting at address $84.
**Abruptly disconnects the modem.
*PiT Motorboat Race uses this command when opening a connection.
**Zeroes out RAM $0076 and $0077.
*Observed Messages (unused bytes in parentheses):
**Changes to mode 0 when complete.
**PiT Motorboat Race rev 02:
*Else if [parameter 0] is not $00:
***60 06 00 01 80 00 00 00 (00)
**Writes [parameter 0] to $74.
**Writes [parameter 1] to $75.
**Refreshes Green LED based on its mode.
**Refreshes P4-27 (Phone Off Hook) based on its mode.
**Zeroes out RAM $76,77,37,39,38.
**Refreshes P4-21 (Phone Audio Enable) based on its mode.
**Zeroes out all queued up outgoing modem Tx messages at RAM $1300-1FFF.
***Each message has space $100 and number of queued messages is at RAM $0100.
**Zeroes out Tone Rx incoming data buffer at RAM $0500-05FF.
**Changes to mode 5 when complete.
|-
|-
|$68
|$61
|$F912
|$F839
|1
|0
|0,5
|1,3,4
|Unknown Function.
|Disconnect
<pre>Message Bytes:
<pre>Message Bytes:
[$68] [count=$01] [xx] [parameter]</pre>
[$61] [count=$00]</pre>
*[xx] byte is ignored.
*This command abruptly disconnects the modem.
*The code has 3 different paths depending on parameter.
*Writes #$00 to register $4102.  (Stops NMI timer 1.)
**[parameter] < #$10
*Changes mode to 0 when complete.
**[parameter] == #$FF
**All other values of [parameter]
|-
|-
|$69
|$62
|$F951
|$F849
|10
|1
|0
|0,2,5
|Unknown Function.
|Unknown Function.
<pre>Message Bytes:
<pre>Message Bytes:
[$69] [count=$0A] [xx] [...10 data bytes...]</pre>
[$62] [count=$01] [xx] [parameter]</pre>
*[xx] byte is ignored.
*[xx] byte is ignored.
*Observed Messages (unused bytes in parentheses):
*Disables interrupts while executing this command.
**PiT Motorboat Race rev 02 when opening a connection:
*Valid values of the [parameter] byte are $00 and $01.
***69 0A (00) 00 04 14 1D 28 80 00 30 26 21 (00 00)
**Other values abort the command.
**JRA-PAT rev 05 and 06 at power-on:
*Appears to write to $4120
***69 0A (00) 00 04 14 1D 28 30 00 30 26 21 (00 00)
*The 10 data bytes are copied to CPU2 RAM starting at $8A.
*If the 6th data byte (location $8F) is > #$FC, it gets overwritten by #$01.
|-
|-
|$6A
|$63
|$F96F
|$F887
|80
|0
|0,2,5
|0,1,2,3,<br/>4,5
|Unknown Function.
|NOP Command
<pre>Message Bytes:
<pre>Message Bytes:
[$6A] [count=$50] [xx] [...40 byte chunk 0...] [...40 byte chunk 1...]</pre>
[$63] [count=$00]</pre>
*[xx] byte is ignored.
*This command only validates the byte count = #$00 and is then complete.
*Copies the 40 byte chunk 0 to RAM starting at $0360. (See Register $4131.)
|-
*Copies the negative (2's complement) of each byte in 40 byte chunk 1 to RAM starting at $0390.
|$64
*Writes #$00 to $0388 and $03B8. (i.e. 41st byte of each.)
|$F88D
*Writes #$10 to $0055.
|1
|0,2,5
|Modem Off Hook Control
<pre>Message Bytes:
[$64] [count=$01] [xx] [Modem Off Hook mode]</pre>
*[xx] byte is ignored.
*[Modem Off Hook mode] Values:
**$00 = Don't update but save mode as $00.
**$01 = Set $4127.4 (/Modem Off Hook) = 0 (off hook). (Also stores #$00 to $0049)
**$02-FF = Set $4127.4 (/Modem Off Hook) = 1 (hang up). (Also stores #$00 to $0049)
**Value gets saved to $004E.
*PiT Motorboat Race uses this command when closing a connection.
*Observed Messages (unused bytes in parentheses):
**PiT Motorboat Race rev 02:
***64 01 (00) 02 (A9 31)
*Note: This description is fairly complete.
*Note: This description is fairly complete.
|-
|-
|$7B
|$65
|$F994
|$F89D
|No<br/>Check
|2
|0,1,2,3,<br/>4,5
|0,2,5
|Software Reset
|Modem Audio Enable and P4-19 Control
<pre>Message Bytes:
<pre>Message Bytes:
[$7B] [count=xx] [xx]</pre>
[$65] [count=$02] [xx] [Modem Audio Enable mode] [P4-19 mode]</pre>
*Does not care about any bytes beyond the command byte.
*[xx] byte is ignored.
*Refreshes the green LED.
*[Modem Audio Enable mode] Values:
*Disables interrupts.
**$00 = Don't update but save mode as $00.
*Writes #$00 to $412F.
**$01 = Set $4127.6 (/Modem Audio Enable) = 0 (enabled to TV speakers).
*Sorts through some memory comparing values then generates a software reset.
**$02-FF = Set $4127.6 (/Modem Audio Enable) = 1 (disabled).
**Stores #$09 as the reset type code into $00FF.
**Value gets saved to $004F.
*[P4-19 mode] Values:
**$00 = Don't update but save mode as $00.
**$01 = Set $4127.7 (Modem P4-19) = 0.
**$02-FF = Set $4127.7 (Modem P4-19) = 1.
**Value gets saved to $0050.
*Heart no Benrikun Mini rev 01 A uses this command when closing a connection.
*Observed Messages (unused bytes in parentheses):
**Heart no Benrikun Mini rev 01 A:
***65 02 (00) 02 00 (20)
*Note: This description is fairly complete.
|-
|-
|$7C
|$66
|$F9AC
|$F8B7
|5
|2
|0,1,2,3,<br/>4,5
|0,2,5
|Arbitrary Memory Read
|LED Control
<pre>Message Bytes:
<pre>Message Bytes:
[$7C] [count=$05] [xx] [CRC 1] [CRC 2] [address MSB] [address LSB] [read count N]
[$66] [count=$02] [xx] [red LED mode] [green LED mode]</pre>
 
*[xx] byte is ignored.
Response:
*[red LED mode] Values:
[$F0] [read count N] [$00] ...N bytes from memory...</pre>
**$00 = Don't update but save mode as $00.
*[xx] byte does not count towards the byte count.
**$01 = Set Red LED on.
*See next section for information about CRC bytes.
**$02-7F = Set Red LED off.
*If [address MSB] >= #$80, exits early with no response. (Prevent ROM dump?? :) )
**$80-FF = Set Red LED to be controlled automatically by network status.
*If [read count N] >= #$39, exits early with no response.
**Value gets saved to $004C.
*[green LED mode] Values:
**$00 = Don't update but save mode as $00.
**$01 = Set Green LED on.
**$02-7F = Set Green LED off.
**$80-FF = Set Green LED to be controlled automatically by network status.
**Value gets saved to $004D.
*PiT Motorboat Race uses this command when closing a connection.
*Observed Messages (unused bytes in parentheses):
**PiT Motorboat Race rev 02:
***66 02 (00) 02 02 (31)
*Note: This description is fairly complete.
|-
|-
|$7D
|$67
|$F9D9
|$F8D1
|>= 5
|2
|0,1,2,3,<br/>4,5
|0,5
|Arbitrary Memory Write
|Unknown Function.
<pre>Message Bytes:
<pre>Message Bytes:
[$7D] [count=N] [xx] [CRC 1] [CRC 2] [address MSB] [address LSB] [...N-4 bytes...]</pre>
[$67] [count=$02] [xx] [parameter 0] [parameter 1]</pre>
*[xx] byte does not count towards the byte count.
*[xx] byte is ignored.
*See next section for information about CRC bytes.
*If [parameter 0] is $00:
*count - 4 is the number of bytes to write to memory.
**Abruptly disconnects the modem.
*Writes $00 to $006E.
**Zeroes out RAM $0076 and $0077.
*Super Mario Club rev 09 uses this command at the welcome screen.
**Changes to mode 0 when complete.
**7D 1A (00) 07 60 01 04 09 01 06 E0 16 A2 90 A5 29 F0 06 C9 FF D0 04 A2 01 86 29 4C 20 F4 (30)
*Else if [parameter 0] is not $00:
**CRC bytes: 07 60
**Writes [parameter 0] to $74.
**Starting address: $0104 (farthest reaches of the stack)
**Writes [parameter 1] to $75.
{| role="presentation" class="wikitable mw-collapsible mw-collapsed"
**Refreshes Green LED based on its mode.
| <strong>Disassembly</strong>
**Refreshes P4-27 (Phone Off Hook) based on its mode.
**Zeroes out RAM $76,77,37,39,38.
**Refreshes P4-21 (Phone Audio Enable) based on its mode.
**Zeroes out all queued up outgoing modem Tx messages at RAM $1300-1FFF.
***Each message has space $100 and number of queued messages is at RAM $0100.
**Zeroes out Tone Rx incoming data buffer at RAM $0500-05FF.
**Changes to mode 5 when complete.
|-
|-
| <pre>      .org $0104
|$68
      .dd2 T0109  ;Wrote over Main Super-loop Function Pointer, now executes code below.
|$F912
      .dd2 TE006  ;Wrote over IRQ Handler Function Pointer, now immediately exits IRQ.
|1
      .dd1 $16    ;Satisfy periodic checksum of bytes $102-109.
|0,5
     
|Unknown Function.
T0109  ldx  #$90    ;Arbitrary code inserted.
<pre>Message Bytes:
      lda  $29
[$68] [count=$01] [xx] [parameter]</pre>
      beq  L0115
*[xx] byte is ignored.
      cmp  #$ff
*The code has 3 different paths depending on parameter.
      bne  L0117
**[parameter] < #$10
      ldx  #$01
**[parameter] == #$FF
L0115  stx  $29
**All other values of [parameter]
L0117  jmp  $f420  ;Continue to original main super-loop.
 
      ; Code Below Existing In CPU2 ROM:
      .org $e006
TE006  jmp  TE502
     
      .org $e502
TE502  ply          ;Return from IRQ.
      plx
      pla
      rti</pre>
|}
*JRA-PAT rev 05 and 06 use this command at power-on.
**7D 29 (00) EC AD 01 02 1A 01 09 01 06 E0 DB A2 90 A5 29 F0 06 C9 FF D0 04 A2 01 86 29 4C 20 F4 AD 32 00 C9 05 D0 03 EE 32 00 4C 39 E8 (00)
**CRC bytes: EC AD
**Starting address: $0102 (farthest reaches of the stack)
{| role="presentation" class="wikitable mw-collapsible mw-collapsed"
| <strong>Disassembly</strong>
|-
|-
| <pre>      .org $0102
|$69
      .dd2 T011A  ;Wrote over NMI function pointer, now executes code below.
|$F951
      .dd2 T0109  ;Wrote over Main Super-loop Function Pointer, now executes code below.
|10
      .dd2 TE006  ;Wrote over IRQ Handler Function Pointer, now immediately exits IRQ.
|0
      .dd1 $db    ;Satisfy periodic checksum of bytes $102-109.
|Unknown Function.
     
<pre>Message Bytes:
T0109  ldx  #$90    ;Arbitrary code inserted.
[$69] [count=$0A] [xx] [...10 data bytes...]</pre>
      lda  $29
*[xx] byte is ignored.
      beq  L0115
*Observed Messages (unused bytes in parentheses):
      cmp  #$ff
**PiT Motorboat Race rev 02 when opening a connection:
      bne  L0117
***69 0A (00) 00 04 14 1D 28 80 00 30 26 21 (00 00)
      ldx  #$01
**JRA-PAT rev 05 and 06 at power-on:
L0115  stx  $29
***69 0A (00) 00 04 14 1D 28 30 00 30 26 21 (00 00)
L0117  jmp  $f420  ;Continue to original main super-loop.
*The 10 data bytes are copied to CPU2 RAM starting at $8A.
     
*If the 6th data byte (location $8F) is > #$FC, it gets overwritten by #$01.
T011A  lda  $0032  ;Arbitrary NMI handler code inserted.
      cmp  #$05
      bne  L0124
      inc  $0032
L0124  jmp  TE839
     
      ; Code Below Existing In CPU2 ROM:
      .org $e006
TE006  jmp  TE502
     
      .org $e502
TE502  ply          ;Return from IRQ.
      plx
      pla
      rti
     
      .org $e839
TE839  ply          ;Return from NMI.
      plx
      pla
      rti</pre>
|}
|-
|-
|$7E
|$6A
|$F9FE
|$F96F
|5
|80
|0,2,5
|Unknown $413x Function.
<pre>Message Bytes:
[$6A] [count=$50] [xx] [...40 byte chunk 0...] [...40 byte chunk 1...]</pre>
*[xx] byte is ignored.
*Copies the 40 byte chunk 0 to RAM starting at $0360.  (See Register $4131.)
*Copies the negative (2's complement) of each byte in 40 byte chunk 1 to RAM starting at $0390.  (See Register $4132.)
*Writes #$00 to $0388 and $03B8. (i.e. 41st byte of each.)
*Writes #$10 to $0055.
*Observations:
**No updates were made to buffers at $0320, $0330 from this command. (i.e. register $4133, $4130 data)
**The command does not appear to initiate any operations to the $413x registers.
*Note: This description is fairly complete.
|-
|$7B
|$F994
|No<br/>Check
|0,1,2,3,<br/>4,5
|0,1,2,3,<br/>4,5
|Unknown Function.
|Software Reset
<pre>Message Bytes:
<pre>Message Bytes:
[$7E] [count=$05] [xx] [CRC 1] [CRC 2] [parameter 0] [parameter 1] [parameter 2]</pre>
[$7B] [count=xx] [xx]</pre>
*[xx] byte does not count towards the byte count.
*Does not care about any bytes beyond the command byte.
*See next section for information about CRC bytes.
*Refreshes the green LED.
*Writes a lot of stuff to $4120 and $4121
*Disables interrupts.
*Writes to $4127 bit 5 (/DTMF Output Enable)
*Writes #$00 to $412F.
*Sorts through some memory comparing values then generates a software reset.
**Stores #$09 as the reset type code into $00FF.
|-
|-
|$7F
|$7C
|$FA16
|$F9AC
|5
|5
|0,1,2,3,<br/>4,5
|0,1,2,3,<br/>4,5
|Unknown Function.
|Arbitrary Memory Read
<pre>Message Bytes:
<pre>Message Bytes:
[$7F] [count=$05] [parameter 0] [CRC 1] [CRC 2] [parameter 1] [parameter 2] [parameter 3]</pre>
[$7C] [count=$05] [xx] [CRC 1] [CRC 2] [address MSB] [address LSB] [read count N]
*[parameter 0] byte does not count towards the byte count.
 
Response:
[$F0] [read count N] [$00] ...N bytes from memory...</pre>
*[xx] byte does not count towards the byte count.
*See next section for information about CRC bytes.
*See next section for information about CRC bytes.
*If [parameter 0] is $00-7F, write value $0C out the P5 Expansion Port.
*If [address MSB] >= #$80, exits early with no response. (Prevent ROM dump?? :) )
*If [parameter 0] is $80-FF, dump RAM $0240-$0280 out the P5 Expansion Port.
*If [read count N] >= #$39, exits early with no response.
**The P5 Expansion port sequences out 1 nybble at a time.
*[parameter 1] gets written to $00B7.
*[parameter 2] gets written to $00B6.
*[parameter 3] gets written to $00B8.
*[parameter 0] gets written to $00B5.
|-
|-
|}
|$7D
 
|$F9D9
===CPU2 Commands with CRC key bytes===
|>= 5
CPU2 command $12 calculates the CRC-16 of its message using [polynomial 1] and [polynomial 2] as the CRC polynomial, with [initial] placed in both bytes of the initial value, and performs the calculation LSB-first or "reflected". This command requires the polynomial to be specified in reciprocal form. For example, to calculate the standard CRC-16 with polynomial $8005, [polynomial 1] would be set to $40, [polynomial 2] would be set to $03, and [initial] would be set to $00.
|0,1,2,3,<br/>4,5
 
|Arbitrary Memory Write
CPU2 Commands $7C, $7D, $7E, and $7F use CRC key bytes [CRC 1] and [CRC 2] to validate the message. These commands calculate a CRC-16 across the message backwards, starting from the last byte and ending at [CRC 1]. The result must be 0 or the command is ignored. The CRC-16 polynomial is $8385 and the initial value is $35AC. The calculation is done LSB-first, or "reflected".
<pre>Message Bytes:
 
[$7D] [count=N] [xx] [CRC 1] [CRC 2] [address MSB] [address LSB] [...N-4 bytes...]</pre>
===Connection Status Byte===
*[xx] byte does not count towards the byte count.
Response commands $80, $81, and $82 send an enumerated value indicating the result when attempting to make a telephone connection. These enumerations are used clearly in the CPU2 ROM: 00, 01, 02, 03, 04, 05, 06, 07, 08, 0B, 0C, 0D, 0E.  CPU2 ROM keeps track of this value at RAM location $0052.  $00 indicates a successful connection, and all other values indicate a failure.  Super Mario Club shows these failures with error code 40xx, xx directly reflecting this byte.  Super Mario Club's manual gives troubleshooting information for most of these values.  That information was used to create the table below.
*See next section for information about CRC bytes.
 
*count - 4 is the number of bytes to write to memory.
{|class="wikitable"
*Writes $00 to $006E.
!|Status<br/>Byte
*Super Mario Club rev 09 uses this command at the welcome screen.
!|Error<br/>Code
**7D 1A (00) 07 60 01 04 09 01 06 E0 16 A2 90 A5 29 F0 06 C9 FF D0 04 A2 01 86 29 4C 20 F4 (30)
!|Description
**CRC bytes: 07 60
**Starting address: $0104 (farthest reaches of the stack)
{|role="presentation" class="wikitable mw-collapsible mw-collapsed"
|Disassembly&nbsp;
|-
|-
|$00
| <pre>      .org $0104
|(n/a)
      .dd2 T0109  ;Wrote over Main Super-loop Function Pointer, now executes code below.
|Connection was successful.
      .dd2 TE006  ;Wrote over IRQ Handler Function Pointer, now immediately exits IRQ.
|-
      .dd1 $16    ;Satisfy periodic checksum of bytes $102-109.
|$01
     
|4001
T0109  ldx  #$90    ;Arbitrary code inserted.
|No dial tone was detected.
      lda  $29
|-
      beq  L0115
|$02
      cmp  #$ff
|4002
      bne  L0117
|An incoming phone call is being received.
      ldx  #$01
|-
L0115  stx  $29
|$03
L0117  jmp  $f420  ;Continue to original main super-loop.
|4003
 
|Pulse vs. Tone setting is incorrect.
      ; Code Below Existing In CPU2 ROM:
      .org $e006
TE006  jmp  TE502
     
      .org $e502
TE502  ply          ;Return from IRQ.
      plx
      pla
      rti</pre>
|}
*JRA-PAT rev 05 and 06 use this command at power-on.
**7D 29 (00) EC AD 01 02 1A 01 09 01 06 E0 DB A2 90 A5 29 F0 06 C9 FF D0 04 A2 01 86 29 4C 20 F4 AD 32 00 C9 05 D0 03 EE 32 00 4C 39 E8 (00)
**CRC bytes: EC AD
**Starting address: $0102 (farthest reaches of the stack)
{|role="presentation" class="wikitable mw-collapsible mw-collapsed"
|Disassembly&nbsp;
|-
|-
|$04
| <pre>      .org $0102
|4004
      .dd2 T011A  ;Wrote over NMI function pointer, now executes code below.
|"0" Outgoing call setting is incorrect.
      .dd2 T0109  ;Wrote over Main Super-loop Function Pointer, now executes code below.
|-
      .dd2 TE006  ;Wrote over IRQ Handler Function Pointer, now immediately exits IRQ.
|$05
      .dd1 $db    ;Satisfy periodic checksum of bytes $102-109.
|4005
     
|DDX-TP connection completed earlier than expected.
T0109  ldx  #$90    ;Arbitrary code inserted.
|-
      lda  $29
|$06
      beq  L0115
|4006
      cmp  #$ff
|Unknown.
      bne  L0117
|-
      ldx  #$01
|$07
L0115  stx  $29
|4007
L0117  jmp  $f420  ;Continue to original main super-loop.
|Unknown.
     
|-
T011A  lda  $0032  ;Arbitrary NMI handler code inserted.
|$08
      cmp  #$05
|4008
      bne  L0124
|Server was busy, disconnected, or rejected the password.
      inc  $0032
|-
L0124  jmp  TE839
|$09
     
|4009
      ; Code Below Existing In CPU2 ROM:
|Server was busy, disconnected, or rejected the password.
      .org $e006
|-
TE006  jmp  TE502
|$0A
     
|400A
      .org $e502
|DDX-TP registration incorrect or server disconnected.
TE502  ply          ;Return from IRQ.
|-
      plx
|$0B
      pla
|400B
      rti
|DDX-TP registration incorrect or server disconnected.
     
|-
      .org $e839
|$0C
TE839  ply          ;Return from NMI.
|400C
      plx
|DDX-TP registration incorrect or server disconnected.
      pla
|-
      rti</pre>
|$0D
|}
|400D
|-
|Problem with telephone line connection.
|$7E
|-
|$F9FE
|$0E
|5
|400E
|0,1,2,3,<br/>4,5
|Problem with telephone line connection.
|Unknown Function.
|-
<pre>Message Bytes:
|}
[$7E] [count=$05] [xx] [CRC 1] [CRC 2] [parameter 0] [parameter 1] [parameter 2]</pre>
 
*[xx] byte does not count towards the byte count.
=Pinouts=
*See next section for information about CRC bytes.
==RF5C66 Mapper and Disk Drive Controller==
*Writes a lot of stuff to $4120 and $4121
 
*Writes to $4127 bit 5 (/DTMF Output Enable)
 
|-
                                                         _____
|$7F
                                                       /    \
|$FA16
                                             CPU A0 -> / 1 100 \ -- +5Vcc
|5
                                           CPU A1 -> / 2    99 \ -- n/c
|0,1,2,3,<br/>4,5
|Unknown Function.
<pre>Message Bytes:
[$7F] [count=$05] [parameter 0] [CRC 1] [CRC 2] [parameter 1] [parameter 2] [parameter 3]</pre>
*[parameter 0] byte does not count towards the byte count.
*See next section for information about CRC bytes.
*If [parameter 0] is $00-7F, write value $0C out the P5 Expansion Port.
*If [parameter 0] is $80-FF, dump RAM $0240-$0280 out the P5 Expansion Port.
**The P5 Expansion port sequences out 1 nybble at a time.
*[parameter 1] gets written to $00B7.
*[parameter 2] gets written to $00B6.
*[parameter 3] gets written to $00B8.
*[parameter 0] gets written to $00B5.
|-
|}
 
===CPU2 Commands with CRC key bytes===
CPU2 command $12 calculates the CRC-16 of its message using [polynomial 1] and [polynomial 2] as the CRC polynomial, with [initial] placed in both bytes of the initial value, and performs the calculation LSB-first or "reflected". This command requires the polynomial to be specified in reciprocal form. For example, to calculate the standard CRC-16 with polynomial $8005, [polynomial 1] would be set to $40, [polynomial 2] would be set to $03, and [initial] would be set to $00.
 
CPU2 Commands $7C, $7D, $7E, and $7F use CRC key bytes [CRC 1] and [CRC 2] to validate the message. These commands calculate a CRC-16 across the message backwards, starting from the last byte and ending at [CRC 1]. The result must be 0 or the command is ignored. The CRC-16 polynomial is $8385 and the initial value is $35AC. The calculation is done LSB-first, or "reflected".
 
===Connection Status Byte===
Response commands $80, $81, and $82 send an enumerated value indicating the result when attempting to make a telephone connection.  These enumerations are used clearly in the CPU2 ROM: 00, 01, 02, 03, 04, 05, 06, 07, 08, 0B, 0C, 0D, 0E.  CPU2 ROM keeps track of this value at RAM location $0052.  $00 indicates a successful connection, and all other values indicate a failure.  Super Mario Club shows these failures with error code 40xx, xx directly reflecting this byte.  Super Mario Club's manual gives troubleshooting information for most of these values.  That information was used to create the table below.
 
{|class="wikitable"
!|Status<br/>Byte
!|Error<br/>Code
!|Description
|-
|$00
|(n/a)
|Connection was successful.
|-
|$01
|4001
|No dial tone was detected.
 
{|role="presentation" class="wikitable mw-collapsible mw-collapsed"
|Reference Data&nbsp;
|-
|
Super Mario Club Manual:
{| class="wikitable"
|-
! おもな原因 (Main Cause) !! 対処方法 (Workaround)
|- style="vertical-align: top;"
|
電話線がはずれています。<br/>
The telephone line is off.
|
*通信アダプタの電話回線の差し込みへ電話線を接続してください。
*Connect the telephone line to the telephone line plug of the communication adapter.
<br/>
*回線テストのテスト1(29ページ) を行ってください。
*Perform Test 1 (page 29) of the line test.
|- style="vertical-align: top;"
|
既に電話が使われています。<br/>
The phone is already in use.
|
通話が終わるまで待ってください。<br/>
Please wait until the call ends.
|- style="vertical-align: top;"
|
ホー厶テレホン用のモジュラーコンセントなどにテレホンスイッチを取りつけていませんか?<br/>
Is the telephone switch attached to a modular outlet for the Ho 厶 telephone?
|
テレホンスイッチがNTT の局線に直接取りつけられるように工事を行ってください。<br/>
Make sure that the telephone switch can be attached directly to the NTT station line.
|}
 
Kangyou Sumimaru no Famicom Trade Manual:
{| class="wikitable"
|-
! 原 因•対応方法 (Cause • Countermeasure)
|- style="vertical-align: top;"
|
電話線は正常に接続されていますか？<br/>
Is the telephone line connected normally?<br/><br/>
自宅の電話が使用中ではありませんか？<br/>
Is your home phone in use?
|}
|}
 
|-
|$02
|4002
|An incoming phone call is being received.
 
{|role="presentation" class="wikitable mw-collapsible mw-collapsed"
|Reference Data&nbsp;
|-
|
Super Mario Club Manual:
{| class="wikitable"
|-
! おもな原因 (Main Cause) !! 対処方法 (Workaround)
|- style="vertical-align: top;"
|
電話がかかってきました。<br/>
I got a call.
|
受話器をお取りください。<br/>
Please pick up the handset.
|}
 
Kangyou Sumimaru no Famicom Trade Manual:
{| class="wikitable"
|-
! 原 因•対応方法 (Cause • Countermeasure)
|- style="vertical-align: top;"
|
もう一度ご利用ください。<br/>
Please use it again.
|}
|}
 
|-
|$03
|4003
|Pulse vs. Tone setting is incorrect.
 
{|role="presentation" class="wikitable mw-collapsible mw-collapsed"
|Reference Data&nbsp;
|-
|
Super Mario Club Manual:
{| class="wikitable"
|-
! おもな原因 (Main Cause) !! 対処方法 (Workaround)
|- style="vertical-align: top;"
|
プッシュ回線とダイヤル回線の設定を誤っています。<br/>
The push line and dial line settings are incorrect.
|
通信アダプタ裏の切換スイッチを回線に合わせてください。<br/>
Set the changeover switch on the back of the communication adapter to match the line.<br/><br/>
 
(番号をかけた時にプッシュ回線の場合はピ・ポ・パと鳴りますのでPBにセットしてください。それ以外はダイヤル回線ですので、20にセットしてください。
*部の地域では 10 にセットしていただく場合があります。)<br/>
(If you use a push line when you dial a number, you will hear a beep, so set it to PB. Other than that, it is a dial line, so set it to 20.
*Set it to 10 in some areas. You may be asked to do so.)
 
|- style="vertical-align: top;"
|
テレホンスイッチを新電電アダプタ等の後に取りつけていませんか?<br/>
Is the telephone switch installed after the new electric adapter, etc.?
|
テレホンスイッチを新電電アダプタより前(NTTの局線側)に取りつけてください。<br/>
Install the telephone switch in front of the new electric adapter (NTT station line side).
|}
 
Kangyou Sumimaru no Famicom Trade Manual:
{| class="wikitable"
|-
! 原 因•対応方法 (Cause • Countermeasure)
|- style="vertical-align: top;"
|
ご利用電話の種類の設定が誤っています。<br/>
The phone type setting is incorrect.<br/><br/>
通信アダプタ裏の電話回線切換スイッチをセットしください。<br/>
Set the telephone line selector switch on the back of the communication adapter.<br/><br/>
任天堂の通信アダプタセット取扱説明書をご覧下さい。<br/>
Please refer to the Nintendo communication adapter set instruction manual.
|}
|}
 
|-
|$04
|4004
|"0" Outgoing call setting is incorrect.
 
{|role="presentation" class="wikitable mw-collapsible mw-collapsed"
|Reference Data&nbsp;
|-
|
Super Mario Club Manual:
{| class="wikitable"
|-
! おもな原因 (Main Cause) !! 対処方法 (Workaround)
|- style="vertical-align: top;"
|
0発信の設定が誤っています。<br/>
The 0 outgoing call setting is incorrect.<br/><br/>
(0発信電話なのに0発信の設定がなされていません。 又は直通電話なのに0発信の設定がされています。)<br/>
(0 outgoing call is not set even though it is a 0 outgoing call, or 0 outgoing call is set even though it is a direct call.)
|
登録内容を見直してください。(訂正する場合は、28ページをご参照ください。)<br/>
Please review the registered contents. (Refer to page 28 for corrections.)<br/><br/>
|- style="vertical-align: top;"
|
テレホンスイッチの取りつけが誤っています<br/>
Wrong installation of telephone switch
|
通信機器の接続 (7,8ページ) をご確認ください。<br/>
Check the connection of communication devices (pages 7 and 8).
|}
 
Kangyou Sumimaru no Famicom Trade Manual:
{| class="wikitable"
|-
! 原 因•対応方法 (Cause • Countermeasure)
|- style="vertical-align: top;"
|
電話回線は利用可能となっていますか？<br/>
Is the telephone line available?<br/><br/>
ご利用の電話は「ゼロ発信」ではありませんか？<br/>
Isn't your phone "zero call"?
|}
|}
 
|-
|$05
|4005
|DDX-TP connection completed earlier than expected.
 
{|role="presentation" class="wikitable mw-collapsible mw-collapsed"
|Reference Data&nbsp;
|-
|
Super Mario Club Manual:
{| class="wikitable"
|-
! おもな原因 (Main Cause) !! 対処方法 (Workaround)
|- style="vertical-align: top;"
|
DDX-TPの開通 (工事) が完了していないと思われます。<br/>
It seems that the opening (construction) of DDX-TP has not been completed.<br/><br/>
|
*回線テストのテスト2 (29ページ) を行ってください。(DDX-TP網IDの場合)
*Perform Test 2 (page 29) of the line test. (For DDX-TP network ID)
<br/>
*NTTの113番に電話して確認してください。
*Please call NTT 113 to confirm.
|- style="vertical-align: top;"
|
テレホンスイッチの取りつけが誤っています。<br/>
The telephone switch is installed incorrectly.
|
通信機器の接続(7, 8ページ) をご確認ぐださい。<br/>
Check the connection of communication devices (pages 7 and 8).
|}
 
Kangyou Sumimaru no Famicom Trade Manual:
{| class="wikitable"
|-
! 原 因•対応方法 (Cause • Countermeasure)
|- style="vertical-align: top;"
|
*113に電話して、NTTにDDXの工事完了を確認して下さい。
*Call 113 to confirm with NTT that the DDX construction has been completed.
|}
|}
 
|-
|$06
|4006
|Unknown.
|-
|$07
|4007
|Unknown.
|-
|$08
|4008
|Server was busy, disconnected, or rejected the password.
 
{|role="presentation" class="wikitable mw-collapsible mw-collapsed"
|Reference Data&nbsp;
|-
|
Super Mario Club Manual:
{| class="wikitable"
|-
! おもな原因 (Main Cause) !! 対処方法 (Workaround)
|- style="vertical-align: top;"
|
センター側が混雑しています。<br/>
The center side is crowded.
|
しばらく経ってから再度お試しください。<br/>
Please try again after a while.
|- style="vertical-align: top;"
|
センターが停止しています。<br/>
The center is stopped.
|
サービス時間を確認してください。<br/>
Please check the service time.
|- style="vertical-align: top;"
|
DDX-TP の開通 (工事) が完了していないと思われます。<br/>
It seems that the opening (construction) of DDX-TP has not been completed.
|
*回線テストのテスト2(29ページ) を行ってください。(DDX- TP綱IDの場合)
*Perform Test 2 (page 29) of the line test. (For DDX-TP rope ID)
<br/>
*NTTの113番に電話して確認してください。
*Please call NTT 113 to confirm.
|- style="vertical-align: top;"
|
テレホンスイッチの取りつけが誤っています。<br/>
The telephone switch is installed incorrectly.
|
通信機器の接続(7,8ページ) をご確認ください。<br/>
Check the connection of communication devices (pages 7 and 8).
|- style="vertical-align: top;"
|
DDX-TPパスワードで、登録に誤りがあります。<br/>
There is an error in the registration of the DDX-TP password.
|
パスワード番号とパスワード登録電話番号をご確認ください。<br/>
Please check your password number and password registration phone number.
|}
 
Kangyou Sumimaru no Famicom Trade Manual:<br/>
Same as 4005.
|}
 
|-
|$09
|4009
|Server was busy.
 
{|role="presentation" class="wikitable mw-collapsible mw-collapsed"
|Reference Data&nbsp;
|-
|
Super Mario Club Manual:<br/>
Same as 4008.<br/><br/>
 
Kangyou Sumimaru no Famicom Trade Manual:
{| class="wikitable"
|-
! 原 因•対応方法 (Cause • Countermeasure)
|- style="vertical-align: top;"
|
相手方が話中です。しばらくして、再度かけ返して下さい。<br/>
The other party is busy. Please call back again after a while.<br/><br/>
|}
|}
 
|-
|$0A
|400A
|rowspan="3"|DDX-TP registration incorrect or server disconnected.
 
{|role="presentation" class="wikitable mw-collapsible mw-collapsed"
|Reference Data&nbsp;
|-
|
Super Mario Club Manual:
{| class="wikitable"
|-
! おもな原因 (Main Cause) !! 対処方法 (Workaround)
|- style="vertical-align: top;"
|
DDX-TPの登録内容に誤りがあります。<br/>
There is an error in the registered contents of DDX-TP.
|
NTTの113番に電話して登録内容の確認をしてください。<br/>
Please call NTT 113 to confirm your registration details.
|- style="vertical-align: top;"
|
センターが停止しています。<br/>
The center is stopped.
|
サービス時間を確認してください。(15ページ)<br/>
Please check the service time. (Page 15)
|}
 
Kangyou Sumimaru no Famicom Trade Manual:
{| class="wikitable"
|-
! 原 因•対応方法 (Cause • Countermeasure)
|- style="vertical-align: top;"
|
再度、お試し下さい。<br/>
Please try again.<br/><br/>
 
頻繁に発生する場合にはファミコントレード事務局へお電話下さい。<br/>
If it occurs frequently, please call the NES Trade Secretariat.
|}
|}
 
|-
|$0B
|400B
<!-- This cell rowspanned from 400A. -->
|-
|$0C
|400C
<!-- This cell rowspanned from 400A. -->
|-
|$0D
|400D
|Problem with telephone line connection.
 
{|role="presentation" class="wikitable mw-collapsible mw-collapsed"
|Reference Data&nbsp;
|-
|
Super Mario Club Manual:
{| class="wikitable"
|-
! おもな原因 (Main Cause) !! 対処方法 (Workaround)
|- style="vertical-align: top;"
|
通信アダプタから電話線がはずれました。<br/>
The telephone line has been disconnected from the communication adapter.
|
通信アダプタと電話線の接続を確認してください。<br/>
Check the connection between the communication adapter and the telephone line.
|}
|}
 
|-
|$0E
|400E
|Problem with telephone line connection or server.
{|role="presentation" class="wikitable mw-collapsible mw-collapsed"
|Reference Data&nbsp;
|-
|
Super Mario Club Manual:<br/>
Same as 400D.<br/><br/>
 
Kangyou Sumimaru no Famicom Trade Manual:<br/>
Same as 400A.
|}
 
|-
|}
 
=Pinouts=
==RF5C66 Mapper and Disk Drive Controller==
 
 
                                                         _____
                                                       /    \
                                             CPU A0 -> / 1 100 \ -- +5Vcc
                                           CPU A1 -> / 2    99 \ -- n/c
                                           CPU A2 -> / 3      98 \ <> CPU D0
                                           CPU A2 -> / 3      98 \ <> CPU D0
                                         CPU A3 -> / 4        97 \ <> CPU D1
                                         CPU A3 -> / 4        97 \ <> CPU D1
Line 2,792: Line 3,358:
                     n/c -- / 27      Package QFP-100, 0.65mm pitch      76 / -> Exp P3-5
                     n/c -- / 27      Package QFP-100, 0.65mm pitch      76 / -> Exp P3-5
           (n/c) $40AE.0 <- / 28                                          75 / -> Exp P3-6
           (n/c) $40AE.0 <- / 28                                          75 / -> Exp P3-6
Filt'd HostCIC +Start -> / 29                Mapper and                74 / <- Exp P3-7
  CIC /CPU R/W Inhibit -> / 29                Mapper and                74 / <- Exp P3-7
          Host CIC-12 <- / 30          Disk Drive Controller          73 / <- Exp P3-8
      Key CIC-12 (?) <- / 30          Disk Drive Controller          73 / <- Exp P3-8
                         /      O                                    72 / <- Exp P3-9
                         /      O                                    72 / <- Exp P3-9
                         \                                            71 / <- Exp P3-11
                         \                                            71 / <- Exp P3-11
      Host CIC /Reset -> \ 31                                      70 / -- GND
      Key CIC-10 (?) -> \ 31                                      70 / -- GND
         Host CIC /Fail -> \ 32                                    69 / -> 5A18-49
         Key CIC-15 (?) -> \ 32                                    69 / -> 5A18-49
             CPU2 /Reset -> \ 33                                  68 / -> CPU2 /Reset (new rev)
             CPU2 /Reset -> \ 33                                  68 / -> CPU2 /Reset (new rev)
     CHR RAM /CE (input) -> \ 34                                67 / <> Exp P3-12          Orientation:
     CHR RAM /CE (input) -> \ 34                                67 / <> Exp P3-12          Orientation:
Line 2,824: Line 3,390:
  - GND pins 23, 39, 70, 90 are all connected together internally.
  - GND pins 23, 39, 70, 90 are all connected together internally.
  - 43, 44, 45, 46 are GND on the PCB, but have internal protection diodes from GND, suggesting they are logic pins.
  - 43, 44, 45, 46 are GND on the PCB, but have internal protection diodes from GND, suggesting they are logic pins.
  - 24, 28, 36, 37, 41, 63 are n/c on the PCB, but have protection diodes from GND, suggesting they may have a function.
  - Pins 45-46, when pulled high, causes oscillation on pin 56.
  - Pins 41 and 42 ranges shown are duplicated at $Cxxx (i.e. ignores /ROMSEL).
  - 24, 28, 36, 37, 41, 63 are n/c on the PCB, but function as noted.
   - It is unknown how the 5A18 prevents bus conflict at $Cxxx range when it has no known access to /ROMSEL.
  - /CE Pins 40, 41, 42, 50 behaviors:
- Pins 45-46, when pulled high, causes oscillation on pin 56.
  - Pin 40 (Built-in RAM /CE) activates low in range $6000-7FFF, regardless of CPU R/W, but only when M2 is high.
  - Pin 29 (CIC-11) observed only high (with or without card inserted).
  - Pin 41 (Unknown /CE) always activates low in range $4xE0-4xEF, regardless of CPU R/W and M2.
   - Seems to be a /reset because it sets pins 52-57 low when this pin is low, and possibly lots of other things.
   - Pin 42 (RF5A18 CPU2 /CE) always activates low in range $4xD0-4xDF, regardless of CPU R/W and M2.
  - Pin 31 (CIC-10) observed only high (with or without card inserted).
  - Pin 50 (Kanji ROM /CE) activates low in range $5000-5FFF, regardless of CPU R/W.  (It appears to go low only when M2 is high but not specifically proven.)
- Pin 32 (CIC-15) observed high with card inserted and low with no card inserted or when hot-removed.
  - Pin 29:
   - Does not go high when hot-inserted or Famicom reset in low state, only high when card is present at power-on.
  - If the FNS has a CIC chip, CIC-11 drives this pin high after 24.8msec, and remains high as long as the CIC authentication is successful.  There is a low-pass filter in this case.
  - If the FNS does not have a CIC chip, the pin floats high.  There may be a pull-up resistor somewhere.  The delay to go high (if any) has not been measured.
   - When this pin is low, it resets pins 52-57 low and possibly lots of other things.
  - Card R/W is always high when this pin is low.
  - Pin 31 (CIC-10) and Pin 32 (CIC-15):
  - Both are jumpered direct to GND if the FNS does not have a CIC chip.
  - If it does have a CIC chip, these signals are both always low with or without tsuushin card inserted.
   - In no observed case are these signals ever high.
  - Pin 16 Pull-up of 20k to 5V is also required in order to avoid triggering reset.
  - Pin 16 Pull-up of 20k to 5V is also required in order to avoid triggering reset.
  - Pin 16 seems to be related to pin 29.  With pin 29 floating and pin 16 pulled high at power on, the chip runs for 5 seconds, then enters reset.
  - Pin 16 seems to be related to pin 29.  With pin 29 floating and pin 16 pulled high at power on, the chip runs for 5 seconds, then enters reset.
Line 2,865: Line 3,438:
                                   +5Vcc -- / 9                  92 \ <> CPU2 D7         
                                   +5Vcc -- / 9                  92 \ <> CPU2 D7         
                                 CPU2 A8 <- / 10                  91 \ -- +5Vcc
                                 CPU2 A8 <- / 10                  91 \ -- +5Vcc
                               CPU2 A9 <- / 11                    90 \ -> MSM6827L TXD
                               CPU2 A9 <- / 11                    90 \ -> UART Tx (MSM6827L TXD)
                             CPU2 A10 <- / 12                      89 \ <- MSM6827L RXD
                             CPU2 A10 <- / 12                      89 \ <- UART Rx (MSM6827L RXD)
                             CPU2 A11 <- / 13                        88 \ <- CPU A2
                             CPU2 A11 <- / 13                        88 \ <- CPU A2
                           CPU2 A12 <- / 14                          87 \ <- CPU A1
                           CPU2 A12 <- / 14                          87 \ <- CPU A1
Line 2,876: Line 3,449:
                     CPU2 R/W <- / 20                                      81 \ <> Card D6
                     CPU2 R/W <- / 20                                      81 \ <> Card D6
         RAM /CE ($0000-1FFF) <- / 21                                            \
         RAM /CE ($0000-1FFF) <- / 21                                            \
  (n/c) ROM /CE ($C000-DFFF) <- / 22                                    O      /
  (n/c) ROM /CE ($C000-xFFF) <- / 22                                    O      /
       P5 /CE ($4129 Only) <- / 23                                          80 / <> Card D5
       P5 /CE ($4129 Only) <- / 23                                          80 / <> Card D5
         (GND) CPU2 +Reset -> / 24                                          79 / <> Card D4
         (GND) CPU2 +Reset -> / 24                                          79 / <> Card D4
                 (GND) ? -> / 25                                          78 / -- GND
                 (GND) ? -> / 25                                          78 / -- GND
                (GND) ? -> / 26            Nintendo RF5A18              77 / <> Card D3
  /Internal ROM Enable -> / 26            Nintendo RF5A18              77 / <> Card D3
  (5C66-68) CPU2 /Reset -> / 27      Package QFP-100, 0.65mm pitch      76 / <> Card D2
  (5C66-68) CPU2 /Reset -> / 27      Package QFP-100, 0.65mm pitch      76 / <> Card D2
   (10k up) CPU2 /IRQ -> / 28                                          75 / <> Card D1
   (10k up) CPU2 /IRQ -> / 28                                          75 / <> Card D1
Line 2,889: Line 3,462:
               +5Vcc -- \ 31                                      70 / <- Tone Rx D2
               +5Vcc -- \ 31                                      70 / <- Tone Rx D2
       MSM6827L DATA <> \ 32                                    69 / <- Tone Rx D1
       MSM6827L DATA <> \ 32                                    69 / <- Tone Rx D1
         MSM6827L /INT -> \ 33                                  68 / -> Tone Rx GT         Orientation:
         MSM6827L /INT -> \ 33                                  68 / -> Tone Rx GT
           MSM6827L /RD <- \ 34                                67 / -> Exp P3-19           --------------------
           MSM6827L /RD <- \ 34                                67 / -> Exp P3-19
           MSM6827L /WR <- \ 35                              66 / <- Exp P3-18               80        51
           MSM6827L /WR <- \ 35                              66 / <> Exp P3-18
           MSM6827L EXCLK <- \ 36                            65 / <- Exp P3-17                 |        |
           MSM6827L EXCLK <- \ 36                            65 / <> Exp P3-17
             (n/c) $4120.2 <- \ 37                          64 / -- +5Vcc                     .-----------.
             (n/c) $4120.2 <- \ 37                          64 / -- +5Vcc                 Orientation:
               MSM6827L AD1 <- \ 38                        63 / -> Modem P4-19             81-|O  RF5A18  |-50
               MSM6827L AD1 <- \ 38                        63 / -> Modem P4-19             --------------------
               MSM6827L AD0 <- \ 39                      62 / -> /Phone Audio Enable          |  Nintendo |
               MSM6827L AD0 <- \ 39                      62 / -> /Phone Audio Enable          80        51
               (n/c) CPU2 D0 <- \ 40                    61 / -> /DTMF Output Enable       100-| GCD 8C  O|-31
               (n/c) CPU2 D0 <- \ 40                    61 / -> /DTMF Output Enable           |         |
                       (n/c) ? <- \ 41                  60 / -> /Phone Off Hook                \-----------'
                       (n/c) ? <- \ 41                  60 / -> /Phone Off Hook                .-----------.
         (4.9152 MHz) Exp P3-16 <- \ 42                59 / -> $4127.3 (n/c)                   |         |
         (4.9152 MHz) Exp P3-16 <- \ 42                59 / -> $4127.3 (n/c)               81-|O  RF5A18  |-50
                             GND -- \ 43              58 / -> /Green LED                      01        30
                             GND -- \ 43              58 / -> /Green LED                      |  Nintendo |
                 19.6608MHz Xtal -- \ 44            57 / -> /Red LED
                 19.6608MHz Xtal -- \ 44            57 / -> /Red LED                     100-|  GCD 8C  O|-31
                       1k to Xtal -- \ 45          56 / -> MSM6827L +Reset     Legend:
                       1k to Xtal -- \ 45          56 / -> MSM6827L +Reset                   \-----------'
                               GND -- \ 46        55 / <- Audio from phone line ------------------------------
                               GND -- \ 46        55 / <- Audio from phone line               |        |
                     (+5Vcc) $4126.0 -> \ 47      54 / <- Modem P4-28           --[RF5A18]-- Power
                     (+5Vcc) $4126.0 -> \ 47      54 / <- Modem P4-28                         01        30
                   (+5Vcc) !($4126.1) -> \ 48    53 / <- Modem P4-25            ->[RF5A18]<- RF5A18 input
                   (+5Vcc) !($4126.1) -> \ 48    53 / <- Modem P4-25             
                               5C66-69 -> \ 49  52 / <- Switch SW1-4            <-[RF5A18]-> RF5A18 output
                               5C66-69 -> \ 49  52 / <- Switch SW1-4            Legend:
                                   n/c -- \ 50 51 / <- Switch SW1-2              <>[RF5A18]<> Bidirectional
                                   n/c -- \ 50 51 / <- Switch SW1-2              ------------------------------
                                           \    /                              ??[RF5A18]?? Unknown
                                           \    /                              --[RF5A18]-- Power, n/a
                                             \  /                                   f      Famicom connection
                                             \  /                               ->[RF5A18]<- RF5A18 input
                                             \ /                                     r      ROM chip connection
                                             \ /                                 <-[RF5A18]-> RF5A18 output
                                               V                                     R      RAM chip connection
                                               V                                 <>[RF5A18]<> Bidirectional
  Notes:
  Notes:
  - This chip contains its very own 65C02 CPU, with built-in ROM.
  - This chip contains its very own 65C02 CPU, with built-in ROM.
  - +5Vcc pins 9, 31, 64, 91 are all connected together internally.
  - +5Vcc pins 9, 31, 64, 91 are all connected together internally.
  - GND pins 18, 43, 46, 78, 100 are all connected together internally.
  - GND pins 18, 43, 46, 78, 100 are all connected together internally.
  - 24, 25, 26 are GND on the PCB, but have internal protection diodes from GND, suggesting they are logic pins.
  - 24, 26 are GND on the PCB, but function as noted.
  - 47, 48 are +5Vcc on the PCB, but have internal protection diodes to +5Vcc, suggesting they are logic pins.
- 25 is GND on the PCB, but has internal protection diode from GND, suggesting it is a logic pin.
  - 15, 16, 17, 19, 22, 37, 40, 41, 59 are n/c on the PCB, but have protection diodes from GND, suggesting they may have a function.
  - 47, 48 are +5Vcc on the PCB, but function as noted.
  - 15, 16, 17, 19, 22, 37, 40, 59 are n/c on the PCB, but function as noted.
- 41 is n/c on the PCB, but has protection diode from GND, suggesting it may have a function.
  - Pin 42 (Exp 16) puts out a 4.92 MHz square wave, ~50% duty.  This is 19.6608 MHz / 4.
  - Pin 42 (Exp 16) puts out a 4.92 MHz square wave, ~50% duty.  This is 19.6608 MHz / 4.
  - CPU2 /Reset comes from RF5C66 pin 68 on new revisions and selectable with J1, J2 on old revisions:
  - CPU2 /Reset comes from RF5C66 pin 68 on new revisions and selectable with J1, J2 on old revisions:
Line 2,929: Line 3,504:
   - The mentioned data bits all appear to have the same data.
   - The mentioned data bits all appear to have the same data.
   - Held low at power-on will fetch the reset vector later when driven high.
   - Held low at power-on will fetch the reset vector later when driven high.
   - Held high at power-on, driven low later, enters the data bus toggle mode but does not appear to fetch the reset vector when driven high after that.
   - Held high at power-on, driven low later, enters the data bus toggle mode but:
  - When pin 26 is held high at power-on, the data bus sticks to $FF and loops through reading addresses.
    - Does not appear to fetch the reset vector when driven high after that.
   - This includes all 6 vector bytes, which also respond with $FF on the data bus.
    - Does execute code, possibly resuming from where it left off.
   - This seems to suggest that the internal ROM is not enabled and we are seeing a runaway bitwise branch opcode $FF (BBS7).
  - When pin 26 is set low (default case: This pin is tied directly to GND on the PCB):
   - Theory: Pin 26 is internal ROM /enable input.
  - Internal ROM is enabled in CPU2 range $E000-FFFF.
   - Open Bus in CPU2 range $C000-DFFF.
   - Pin 22 (ROM /CE) is enabled low in range $C000-DFFF
  - This mode allows ROM expansion at $C000-DFFF, with internal ROM (and its vector table) in place.
- When pin 26 is set high:
  - Internal ROM is disabled, leaving open bus in CPU2 range $E000-FFFF.
  - Open Bus in CPU2 range $C000-DFFF.
   - Pin 22 (ROM /CE) is enabled low in the entire range $C000-FFFF.
  - This mode allows a totally custom external CPU2 ROM with its own interrupt vector table.


==LH5323M1 Kanji Graphic ROM==
==LH5323M1 Kanji Graphic ROM==
Line 2,980: Line 3,563:
   - The conditions resetting or maintaining the bankswitch pin to 1 are still unknown.
   - The conditions resetting or maintaining the bankswitch pin to 1 are still unknown.


==8633 CIC Host==
==8633 Famicom Network System CIC Key Chip==
                          _______  _______
                          |      \_/      |
  (Guest CIC-2) Data 0 <> | 1          18 | -- +5Vcc
  (Guest CIC-1) Data 1 <> | 2  O      17 | -- n/c
                  n/c -- | 3  8633  16 | -- n/c
                  n/c -- | 4          15 | -> /Fail (5C66-32)
                  n/c -- | 5    CIC  14 | -- n/c
                  n/c -- | 6  Host  13 | -- n/c
      (5C66-26) Clock -> | 7          12 | <- 5C66-30
(Guest CIC-11) /Reset -> | 8    U8    11 | -> +Start (5C66-29)
                  GND -- | 9          10 | -> /Reset (5C66-31)
                          |_______________|


==8634A CIC Guest==
Unlike the NES console, the Famicom Network System appears to have the CIC key.
                          _______  _______
                                  _______  _______
                          |      \_/      |
                                  |      \_/      |
  (Host CIC-2) Data 0 <> | 1          18 | -- +5Vcc
  (To Card CIC Pin 2) Data Out <- | 1          18 | -- +5Vcc
  (Host CIC-1) Data 1 <> | 2  O      17 | -- n/c
(From Card CIC Pin 1) Data In -> | 2  O      17 | -- n/c
                  n/c -- | 3  8634A  16 | ?? GND
                          n/c -- | 3  8633  16 | -- n/c
                  n/c -- | 4          15 | -- n/c
                          n/c -- | 4          15 | -> ? (5C66-32) always observed low
                  n/c -- | 5    CIC  14 | -- n/c
                          n/c -- | 5    CIC  14 | -- n/c
                  n/c -- | 6  Guest  13 | ?? +5V
                          n/c -- | 6   Key   13 | -- n/c
      (5C66-26) Clock -> | 7          12 | ?? Card-33, n/c in Famicom Network System
                        Clock -> | 7          12 | <- ? (5C66-30)
    (Cap to 5V) /Reset -> | 8         11 | -> +Start (Host CIC-8)
(From Card CIC Pin 11) +Reset -> | 8   U8    11 | -> /CPU R/W Inhibit (5C66-29)
                  GND -- | 9          10 | -- n/c
                          GND -- | 9          10 | -> ? (5C66-31) always observed low
                          |_______________|
                                  |_______________|


- Note: Some assumptions made on CIC chips based on similarity to F411A from Super NES.
* When the CIC key drives pin 11 low, this stops operation of the Famicom Network System by means of holding Card R/W high.
* The clock is 3.58 MHz, coming from RF5C66 pin 26.


==8kByte CHR-RAM==
==8634A Tsuushin Card CIC Lock Chip==
 
Unlike the NES cartridge, the tsuushin card appears to have the CIC lock.
                                  _______  _______
                                  |      \_/      |
  (To FNS CIC Pin 2) Data Out <- | 1          18 | -- +5Vcc
  (From FNS CIC Pin 1) Data In -> | 2  O      17 | -- n/c
                          n/c -- | 3  8634A  16 | ?? GND
                          n/c -- | 4          15 | -- n/c
                          n/c -- | 5    CIC  14 | -- n/c
                          n/c -- | 6  Lock  13 | ?? +5V
                        Clock -> | 7          12 | ?? Card-33, n/c in Famicom Network System
            (Cap to 5V) +Reset -> | 8          11 | -> CIC Key +Reset (To FNS CIC Pin 8)
                          GND -- | 9          10 | -- n/c
                                  |_______________|
 
* +Reset is connected with a ceramic capacitor to 5V.  This gives a momentary positive pulse at power-on.
* The clock is 3.58 MHz, coming from RF5C66 pin 26.
* Note: Some assumptions made on CIC chips based on similarity to F411A from Super NES.
 
==8kByte CHR RAM==
                     _______  _______
                     _______  _______
                     |      \_/      |
                     |      \_/      |
Line 3,095: Line 3,687:
  Note: The modem module uses modem chip Oki MSM6827L and Dual Tone Receiver MC14LC5436P.
  Note: The modem module uses modem chip Oki MSM6827L and Dual Tone Receiver MC14LC5436P.


==P2: Game Card Connector==
==P2: Tsuushin Card Connector==
 
Note that the tsuushin card may appear to have a metric 1mm pin pitch, but in fact it has an imperial 0.040" (40 thousandths) pin pitch.
   
   
  Card |  | Famicom Network System
  Card |  | Famicom Network System
Line 3,101: Line 3,695:
   1  |--| +5Vcc
   1  |--| +5Vcc
   2  |--| +5Vcc
   2  |--| +5Vcc
   3  |??| n/c in host
   3  |??| n/c in JRA-PAT card, n/c in FNS
   4  |??| n/c in JRA-PAT, Host has 10k pull-up only.
   4  |??| n/c in JRA-PAT card, FNS has 10k pull-up only.
   5  |<>| Card D0
   5  |<>| Card D0
   6  |<>| Card D1
   6  |<>| Card D1
Line 3,131: Line 3,725:
   29  |<-| CPU A13
   29  |<-| CPU A13
   30  |<-| CPU A14
   30  |<-| CPU A14
   31  |??| n/c in JRA-PAT, Host has 10k pull-up only.
   31  |??| n/c in JRA-PAT card, FNS has 10k pull-up only.
   32  |??| n/c in JRA-PAT, Host has 10k pull-up only.
   32  |??| n/c in JRA-PAT card, FNS has 10k pull-up only.
   33  |??| connected to Guest CIC-12 in JRA-PAT, n/c in host
   33  |??| connected to Card Lock CIC-12 in JRA-PAT, n/c in FNS
   34  |??| n/c in JRA-PAT, n/c in host
   34  |??| n/c in JRA-PAT card, n/c in FNS
   35  |->| Guest CIC-11 -> Host CIC-8
   35  |->| CIC Key Reset (Card Lock CIC-11 -> FNS Key CIC-8)
   36  |<>| Guest CIC-1 <> Host CIC-2
   36  |->| CIC Lock-to-Key Data (Card Lock CIC-1 -> FNS Key CIC-2)
   37  |<>| Guest CIC-2 <> Host CIC-1
   37  |<-| CIC Key-to-Lock Data (Card Lock CIC-2 <- FNS Key CIC-1)
   38  |<-| CIC Clock
   38  |<-| CIC Clock (3.58 MHz, from 5C66.26)
   39  |??| n/c in JRA-PAT, Host has 10k pull-up only.
   39  |??| n/c in JRA-PAT card, FNS has 10k pull-up only.
   40  |<-| RAM +CE (n/c in JRA-PAT)
   40  |<-| RAM +CE (n/c in JRA-PAT card)
   41  |--| GND
   41  |--| GND
   42  |--| GND
   42  |--| GND
Line 3,182: Line 3,776:
=See Also=
=See Also=
*https://forums.nesdev.org/viewtopic.php?f=9&t=18530
*https://forums.nesdev.org/viewtopic.php?f=9&t=18530
*https://niwanetwork.org/wiki/Tsuushin_Cartridge
*https://niwanetwork.org/wiki/List_of_Famicom_Network_System_software


[[Category:Mappers using $4020-$5FFF]][[Category:Mappers_with_IRQs]][[Category:ASIC_mappers]][[Category:Pinouts]][[Category:Expansion audio]]
[[Category:Mappers using $4020-$5FFF]][[Category:Mappers_with_IRQs]][[Category:ASIC_mappers]][[Category:Pinouts]][[Category:Expansion audio]]

Latest revision as of 23:35, 6 June 2024

System Overview

The Famicom Network System is a complicated device with its own memory mapping system and internal CPU. The RF5C66 chip provides the main mapper functionality, delegating its own registers at $40A0, RF5A18 Famicom registers at $40D0, an internal Kanji ROM at $5000, an internal 8kByte W-RAM at $6000. It also controls the bank of a built-in 16 KiB CHR RAM (using two 8 KiB CHR RAM chips).

The RF5A18 contains CPU2, which is a 65C02 processor with its own independent CPU clock. It has a built-in 4kByte ROM. This chip is responsible for controlling the modem communications. It communicates with the Famicom CPU through four bidirectional registers at $40Dx.

The Famicom Network System plugs into the Famicom through its cartridge connector and provides the user a ZIF style slot to insert a tsuushin card. The card is similar to a normal cartridge but does not have access to any PPU signals. Commercial cards are observed to have their own MMC1 memory mapper, which does not interfere with any of the registers of the Famicom Network System. CPU R/W and the CPU data bus are routed through the RF5C66 chip before making it to the card and other internal hardware. It effectively blocks the Famicom Network System from driving the data bus for certain regions of memory, and possibly also is intended to act as a bidirectional buffer / signal conditioner. It is also used for blocking writes when the lid switch is open or when the CIC fails. Older revisions of Famicom Network System also buffered the Famicom address bus with 74HC541 chips, so it is plausible that signal conditioning was a concern.

LH5323M1 Kanji Graphic ROM

The LH5323M1 is a 256kByte graphics ROM containing primarily Kanji data that is mapped at $5000-5FFF. Each index in this range is a 32-byte space containing 16x16 1bpp graphics, usually for a single character, and each read automatically advances to the next byte in the sequence. There are 2 128kByte banks, and the low bank is default at power-on. Writing 1 to $40B0.0 selects the high bank. Reading from $40B0 resets to the beginning of the 32-byte sequence. Writing $40B0 does not reset the sequence however. No values written to $40B0 have been observed to arbitrarily change or reset the position in the sequence. Commercial software has been observed to use throwaway reads when accessing data that does not start at the beginning of the 32-byte area.

The Kanji ROM chip is connected directly to the non-buffered Famicom CPU data bus. Writes in the range $5000-5FFF do activate Kanji ROM /CE and are subject to bus conflict.

Expansion Audio

The Famicom Network System does have expansion audio capabilities. The Famicom audio is routed through the modem module, but nowhere directly to either of the large ASICs. Dial tones have been observed through the television speakers. It is unlikely but unknown if there are other possible sources of sound.

Disk Drive Support

According to a block diagram with potentially dubious origins, the RF5C66 chip contains a disk drive controller. Similar design in several ways to the Famicom Disk System, it is suspected that a disk drive can be connected to the expansion port and controlled by the RF5C66. Since this feature was never used, it is unknown how to use or activate it, or even if that feature is fully implemented. The original FDS has a large DRAM that is not present as a discrete chip in the Famicom Network System. It is unknown if such a DRAM could be already integrated into the RF5C66, or could be attached externally and simply not populated, or if a special tsuushin card was to be constructed containing this RAM. All original FDS registers are notably absent and all discovered registers start immediately after where the FDS registers would normally be. There is no obvious path to produce FDS expansion audio. This remains a mystery presently.

One possibility if the RF5C66 follows a similar pinout to the FDS RP2C33: 

        79 / -> Exp P3-2  (reg unknown) Serial Out (observed 95.95kHz)
       78 / <- Exp P3-3  (reg unknown) Serial In
      77 / -> Exp P3-4  (!$40A4.2)    Read / Write
     76 / -> Exp P3-5  (!$40A4.1)    Reset Transfer Timing
    75 / -> Exp P3-6  ($40A3.0)     Turn on Motor
   74 / <- Exp P3-7  ($40A5.2)     Write Protect
  73 / <- Exp P3-8  ($40A5.1)     Disk Not Ready
 72 / <- Exp P3-9  ($40A5.0)     Disk Missing
71 / <- Exp P3-11 ($40A5.7)     Battery Health

Memory Map

+================+ $0000 - Famicom Internam RAM
| Famicom        |
| Internal RAM   |
+----------------+ $0800
|   (Mirrors of  |
|   $0000-$07FF) |
+================+ $2000 - Famicom PPU Registers
| Famicom PPU    |
| Registers      |
+----------------+ $2008
|   (Mirrors of  |
|   $2000-$2007) |
+================+ $4000 - Famicom APU, IO, and Test Registers
| FC APU and IO  |
| Registers      |
+----------------+ $4018
| FC Test Mode   |
| Registers      |
+----------------+ $4020
|   (Open Bus)   |
+================+ $40A0 - Famicom Network System Internal Registers
| Famicom Modem  |
| RF5C66         |
| Registers      |
+----------------+ $40D0
| Famicom Modem  |
| RF5A18 (CPU2)  |
| Registers      |
+----------------+ $40D8
|   (Mirror of   |
|   $40D0-$40D7) |
+----------------+ $40E0
| Unused Device  |
| Registers      |
| (Open Bus)     |
+----------------+ $40F0
|   (Open Bus)   |
+----------------+ $4100
|   (Open Bus)   |
+----------------+ $41A0
|   (Mirror of   |
|   $40A0-$40FF) |
+----------------+ $4200
|   (Mirrors of  |
|   $4100-$41FF) |
+================+ $5000 - Famicom Network System Internal Kanji ROM
| FNS            |
| LH5323M1       |
| Kanji ROM      |
+================+ $6000 - Famicom Network System Internal RAM and Tsuushin Card RAM
| FNS            |
| Internal RAM   |
+================+ $8000 - Tsuushin Card ROM Space
| Tsuushin Card  |
| Space          |
|                |
+================+ $10000

Data Bus Behavior

The CPU data bus is buffered in both directions through the RF5C66 chip before making it to the tsuushin card and other internal hardware, with the exception of the Kanji graphics ROM and the RF5C66's own registers, which sit directly on the CPU data bus. It appears that the buffer goes from CPU Data Bus to Card Data Bus, or Card Data Bus to CPU Data Bus only. There has not been a high-impedance state observed when testing each possible address in read and write directions on a standalone RF5C66 chip. The CPU Data Bus and Card Data Bus were always observed to be equal despite attaching opposite pull-up and pull-down resistors.

When RF5C66 pin 29 is driven low by the master CIC chip's pin 11, it forces Card R/W always high, thereby preventing most RAM and register writes in the Famicom Network System. Potentially, the data bus buffer has an additional behavior in this mode in order to prevent bus conflicts. The lid switch also imposes such a behavior when the lid is open, but it does not appear that the RF5C66 has a way of knowing when the switch is open, so the bus conflicts do not appear to be prevented in that case.

The propagation delay of the CPU data bus buffer and CPU R/W buffer are measured to be about 16 nsec.

Address Range Buffer Direction When Reading Buffer Direction When Writing Notes
$0x00-$4x1F CPU -> Card CPU -> Card Famicom internal RAM and registers
$4x20-$4x9F CPU -> Card CPU -> Card (unknown; FDS registers exactly fit here)
$4xA0-$4xCF CPU -> Card CPU -> Card RF5C66 registers
$4xD0-$4xDF CPU <- Card CPU -> Card CPU 2 registers, /CE at RF5C66 pin 42
$4xE0-$4xEF CPU <- Card CPU -> Card Unused device registers1, /CE at RF5C66 pin 41
$4xF0-$4xFF CPU -> Card CPU -> Card (unknown)
$5x00-$5xFF CPU -> Card CPU -> Card2 Kanji graphic ROM, /CE at RF5C66 pin 50
$6x00-$7xFF CPU <- Card CPU -> Card Famicom Network System internal RAM, /CE at RF5C66 pin 40
$8x00-$FxFF CPU <- Card CPU -> Card Tsuushin card, /CE is /ROMSEL

1 Address range $4xE0-$4xEF was meant for a second device similar to CPU 2. Since that device doesn't exist, a tsuushin card could theoretically exploit those 256 addresses for its own purposes; for example, its own read/write registers.

2 Writes here are subject to bus conflict on the CPU data bus.

Known Registers

Note: All registers available to the Famicom ignore address bits 8-11 because those bits are not physically connected to the RF5C66. Therefore, register $4xA0 has mirrors that exist at $40A0, $41A0 ... $4FA0. For simplicity, this page shows all registers as the $40xx mirror.

Address Read
Has
Effect 		Read
Has
Data 		Write Owner Function
$40A0 Unknown No Unknown RF5C66 No evidence has been found that this register does or does not exist. It is possible that it is a write-only register that is not used by any known Famicom Network System card. No reads or writes to this register were ever observed to have any effect. However, its apparent absence is suspicious enough to have this placeholder here. 
Write
76543210
++++++++-- (unknown)

Read
76543210
++++++++-- (unlikely to exist)
$40A1 Unknown Yes Unknown RF5C66 Unknown Function. 
Write
76543210
++++++++-- (unknown)

Read
76543210
++++++++-- Bits exist but function is unknown
$40A2 Yes Yes Unknown RF5C66 IRQ Acknowledge, similar to FDS register $4030 
Write
76543210
++++++++-- (unknown)

Read
76543210
|||||||+-- Timer Interrupt (1: an IRQ occurred)
||||||+--- Bit exists but function is unknown
||||++---- (unlikely to exist)
++++------ Bits exist but function is unknown
  • Reading this register acknowledges /IRQ.
    • Observed inconsistent behavior acknowledging, possibly suggesting multiple IRQ sources.
$40A3 Unknown No Yes RF5C66 Unknown Function. 
Write
76543210
|||||||+-- EXP 6 = $40A3.0 (POR value = 0)
+++++++--- (unknown)

Read
76543210
++++++++-- (unlikely to exist)
  • Various values written to this register affect the behavior of pulses on pin 79.
$40A4 Unknown No Yes RF5C66 Expansion Port Control 
Write
76543210
|||||||+-- (unknown)
||||||+--- EXP 5 = !($40A4.1) (POR value = 0)
|||||+---- EXP 4 = !($40A4.2) (POR value = 0)
+++++----- (unknown)

Read
76543210
++++++++-- (unlikely to exist)
  • Note: Reading test should be repeated with pull-ups and pull-downs on expansion pins.
  • This register has not been observed read or written to by any commercial software.
$40A5 Unknown Yes Unknown RF5C66 Expansion Port Input Data 
Write
76543210
++++++++-- (unknown)

Read
76543210
|||||||+-- Input value of EXP 9
||||||+--- Input value of EXP 8
|||||+---- Input value of EXP 7
|++++----- (unlikely to exist)
+--------- Input value of EXP 11
$40A6 Unknown Yes Yes RF5C66 M2 Cycle Counter LSB, similar to FDS register $4020 
Write
76543210
++++++++-- Cycle counter reload value (LSB)

Read
76543210
++++++++-- Cycle counter present value (LSB)
  • Writing to this register writes to the cycle counter reload value.
  • Reading this register gives the present value of the counter.
  • Writing any value to $40A8 resets the counter to the reload value.
  • This value counts down.
  • When the value reaches $0000, the next count rolls over to $FFFF or auto-reloads depending on $40A8.0.
$40A7 Unknown Yes Yes RF5C66 M2 Cycle Counter MSB, similar to FDS register $4021 
Write
76543210
++++++++-- Cycle counter reload value (MSB)

Read
76543210
++++++++-- Cycle counter present value (MSB)
  • Refer to description in $40A6, this register being the MSB portion of the counter.
$40A8 Unknown No Yes RF5C66 IRQ Control, similar to FDS register $4022 
Write
76543210
|||||||+-- IRQ Repeat Flag
||||||+--- IRQ Enable
++++++---- (unknown)

Read
76543210
++++++++-- (unlikely to exist)
  • Writing anything to this register resets the cycle counter to the reload value.
  • Observed writing $02 makes /IRQ go low, $00 makes /IRQ go high.
    • Reading $40A2 with /IRQ low acknowledges it back high.
    • Acknowledging with $40A2 first before writing $02 here prevents IRQ immediately going low.
  • Observed rollover of cycle counter to $FFFF with repeat flag = 0 and auto-reload when flag = 1.
$40A9 Yes Yes Unknown RF5C66 Unknown Function. 
Write
76543210
++++++++-- (unknown)

Read
76543210
++++++++-- Bits exist but function is unknown
  • Bench test observed value $00 with pull-ups.
  • When driving RF5C66 pin 45 high, this 8-bit value changes.
  • Pin 45 high causes the value to change continuously, as if counting cycles.
  • The value does not appear to match $40A7 or $40A6, though further testing is required to say that for sure.
  • Reading this register causes its contents to be loaded into register $40AA.
$40AA No Yes Unknown RF5C66 Unknown Function. 
Write
76543210
++++++++-- (unknown)

Read
76543210
++++++++-- Bits exist but function is unknown
  • This register maintains the most recent value that was read from $40A9.
$40AB Yes No Yes RF5C66 Unknown Function. 
Write
76543210
++++++++-- (unknown)

Read
76543210
++++++++-- (unlikely to exist)
  • Reading this register resets the value of $40A9 back to $00.
$40AC Yes No Unknown RF5C66 Unknown Function. 
Write
76543210
++++++++-- (unknown)

Read
76543210
++++++++-- (unlikely to exist)
  • Reading this register prevents timed toggle on RF5C66-69 (see notes in pinout).
$40AD Unknown Yes Yes RF5C66 Mirroring Control 
Write
76543210
|+++++++-- (unknown)
+--------- Mirroring (POR value = 0)
             0 = Vertical Mirroring (CIRAM A10 = PPU A10)
             1 = Horizontal Mirroring (CIRAM A10 = PPU A11)

Read
76543210
|+++++++-- (unlikely to exist)
+--------- Present value of CIRAM A10
$40AE Unknown No Yes RF5C66 Unknown Function. 
Write
76543210
|||||||+-- Built-in RAM /CE control (POR value = 1)
|||||||      1 = Built-in RAM /CE enabled to go low for reads and writes in the range $6000-7FFF.
|||||||          Pin 5C66.28 = 1 at all address ranges.  (This pin normally n/c.)
|||||||      0 = Built-in RAM /CE is always high, preventing all reads and writes of the built-in RAM.
|||||||          Pin 5C66.28 = 0 at all address ranges.  (This pin normally n/c.)
+++++++--- (unknown)

Read
76543210
++++++++-- (unlikely to exist)
  • Refer also to $40C0.0 for built-in RAM enabling.
$40B0 Yes No Yes RF5C66 Kanji Graphic ROM Control 
Write
76543210
|||||||+-- Kanji ROM Bank Select (POR value = 0)
+++++++--- (unknown)

Read
76543210
++++++++-- (unlikely to exist)
  • All reads reset the Kanji auto-increment counter.
  • D0 is written with 0 or 1 in Kanji graphics-loading code depending on the Kanji character index, changing the Kanji bank.
  • For an unknown reason, RF5C66 registers can't be written on test setups. They only work in a real Famicom so far.
$40B1 Unknown Yes Yes RF5C66 Modem Control 
Write
76543210
|||||||+-- Modem Module pin 29 = $40B1.0, rises slowly, goes low fast (POR value = 1)
||||||+--- Modem Module pin 32 = $40B1.1, rises slowly, goes low fast (POR value = 1)
|||||+---- Modem Module pin 31 = $40B1.2, rises slowly, goes low fast (POR value = 1)
||||+----- Pin 5C66.68: CPU2 Reset on new revision Famicom Network Systems (POR value = 1)
||||         CPU2 /Reset = !($40B1.3)
||||         CPU2 runs when $40B1.3 = 0.
||||         See also $40C0.2.
|||+------ Exp 15 = $40B1.4, rises slowly, goes low fast (POR value = 1)
||+------- Exp 14 = $40B1.5, rises slowly, goes low fast (POR value = 1)
|+-------- Exp 13 = $40B1.6, rises slowly, goes low fast (POR value = 1)
+--------- Exp 12 = $40B1.7, rises slowly, goes low fast (POR value = 1)

Read
76543210
|||||||+-- Input value of Modem Module pin 29
||||||+--- Input value of Modem Module pin 32
|||||+---- Input value of Modem Module pin 31
||||+----- Input value of 5C66 pin 63 (normally n/c)
|||+------ Input value of EXP 15
||+------- Input value of EXP 14
|+-------- Input value of EXP 13
+--------- Input value of EXP 12
$40C0 Unknown Yes Yes RF5C66 CIC Status, CHR Bank, and RAM Control 
Write
76543210
|||||||+-- Pin 5C66.35 = $40C0.0 (POR value = 0)
|||||||      RAM +CE Enable (1 = enabled, 0 = disabled)
||||||+--- Pin 5C66.36 = $40C0.1 (POR value = 0)
||||||       (This pin normally n/c)
|||||+---- Pin 5C66.37 = $40C0.2 (POR value = 0)
|||||        Old Revision Famicom Network System: CPU2 /Reset (This pin n/c on newer revisions)
|||||        CPU2 runs on old revisions when $40C0.2 = 1.
|||||        See also $40B1.3.
||||+----- Pin 5C66.38 = $40C0.3 (POR value = 0)
||||         CHR RAM Bank Select (selects between two 8 KiB CHR RAM chips)
++++------ (unknown)

Read
76543210
|||||||+-- Input value of pin 5C66.31:
|||||||      From FNS CIC (Key) pin 10, or jumpered to GND on models without a CIC chip.
||||||+--- Input value of pin 5C66.32:
||||||       From FNS CIC (Key) pin 15, or jumpered to GND on models without a CIC chip.
|||||+---- Input value of pin 5C66.33:
|||||        CPU2 /Reset fed back in for all models, regardless which model-specific 5C66 pin is sending it out.
||||+----- Input value of pin 5C66.34:
||||         Selected CHR RAM Bank, fed back in from 5C66.38.
|+++------ (unlikely to exist)
+--------- Input value of pin 5C66.29:
             /CPU R/W Inhibit, from FNS CIC (Key) pin 11, or floating up to logic high on models without a CIC chip.
             1 = Writes to card, W-RAM, and $40Dx are allowed
             0 = Blocked (CPU R/W is overriden high, i.e. "read" for these writes)
  • RAM +CE always reflects bit 0 of this register regardless of address space.
    • Refer also to $40AE.0 for built-in RAM enabling.
  • All examined software waits for D7 = 1 at initialization.
  • D7 is controlled by the CIC key chip, if present. If the CIC fails authentication, it latches to 0 until a power cycle.
  • D1 and D0 always observed low in all cases, regardless if the model does not have CIC key chip, or does have the chip and authentication passes or fails.
    • It is unknown in what scenario that the CIC chip could generate logic high on these pins.
    • Theories:
      • These pins may reflect detection of different lock CIC chips in the tsuushin card, for different regions or "disk drive mode" or something like that.
      • Transient role at power-on, indicating when the CIC is ready.
      • Showing internal error state of the CIC.
$40D0 Unknown Yes Yes RF5A18 Famicom CPU <-> CPU2 Interface, Data Byte 0 
Write
76543210
++++++++-- 8-bit value written here can be read by CPU2 from register $4123.

Read
76543210
++++++++-- 8-bit value read here was written by CPU2 to register $4123.
$40D1 Unknown Yes Yes RF5A18 Famicom CPU <-> CPU2 Interface, Data Byte 1 
Write
76543210
++++++++-- 8-bit value written here can be read by CPU2 from register $4124.

Read
76543210
++++++++-- 8-bit value read here was written by CPU2 to register $4124.
$40D2 Unknown Yes Yes RF5A18 Famicom CPU <-> CPU2 Interface, Data Byte 2 
Write
76543210
++++++++-- 8-bit value written here can be read by CPU2 from register $4125.

Read
76543210
++++++++-- 8-bit value read here was written by CPU2 to register $4125.
$40D3 Unknown Yes Yes RF5A18 Famicom CPU <-> CPU2 Interface, Data Acknowledge 
Write
76543210
|||+++++-- (unknown)
+++------- 3-bit value written here can be read by CPU2 from register $4122.

Read
76543210
|||+++++-- (unlikely to exist)
+++------- 3-bit value read here was written by CPU2 to register $4122.
$40D4 Unknown Yes Yes RF5A18 Tone Rx and Expansion I/O Control 
Write
76543210
|||||||+-- RF5A18 Pin 65 (Exp 17) = $40D4.0 (open-drain)
||||||+--- RF5A18 Pin 67 (Exp 19) = $40D4.1 (push-pull)
|||||+---- RF5A18 Pin 66 (Exp 18) = $40D4.2 (open-drain)
+++++----- (unknown)

Read
76543210
|||||||+-- $40D4.0 = I/O value of RF5A18 Pin 65 (Exp 17)
||||||+--- $40D4.1 = output value of RF5A18 Pin 67 (Exp 19)
|||||+---- $40D4.2 = I/O value of RF5A18 Pin 66 (Exp 18)
||||+----- $40D4.3 = input value of RF5A18 Pin 69 (Tone Rx D1)
|||+------ $40D4.4 = input value of RF5A18 Pin 70 (Tone Rx D2)
||+------- $40D4.5 = input value of RF5A18 Pin 71 (Tone Rx D4)
|+-------- $40D4.6 = input value of RF5A18 Pin 72 (Tone Rx D8)
+--------- $40D4.7 = input value of RF5A18 Pin 73 (Tone Rx DV)
$40D5 Unknown Yes Unknown RF5A18 Clocks 
Write
76543210
++++++++-- (unknown)

Read
76543210
||++++++-- Bits exist but function is unknown
++-------- (unlikely to exist)
  • The purpose is unknown but it could potentially serve to generate random numbers.
    • The Famicom CPU and CPU2 have separate clocks and are asynchronous, making the value read especially random.
  • Bit 5 is a 0.05% duty square wave, measured 1.200kHz (19.6608MHz CPU2 crystal / 16384)
    • Negative pulse width measures 406 nsec, the same as period of bit 2.
  • Bit 4 is a 50% duty square wave, depending on $4114.1 and $4114.0:
    • (0,0) measured 19.20kHz (19.6608MHz CPU2 crystal / 1024)
    • (0,1) measured 38.40kHz (19.6608MHz CPU2 crystal / 512)
    • (1,0) measured 76.80kHz (19.6608MHz CPU2 crystal / 256)
    • (1,1) measured 153.6kHz (19.6608MHz CPU2 crystal / 128)
  • Bit 3 is a 50% duty square wave, measured 307.3kHz (19.6608MHz CPU2 crystal / 64)
  • Bit 2 is a 50% duty square wave, measured 2.451MHz (19.6608MHz CPU2 crystal / 8)
  • Bit 1 is a 50% duty square wave, measured 4.902MHz (19.6608MHz CPU2 crystal / 4)
    • This bit toggles at the same rate as RF5A18 pin 42, though there is a 129.9 degree phase difference.
  • Bit 0 is a 50% duty square wave, measured 9.804MHz (19.6608MHz CPU2 crystal / 2)
  • The phasing of these signals do not line up nicely but they do stay in perfect sync with CPU2 M2.
$40D6 Unknown Yes Unknown RF5A18 UART Status 
Write
76543210
++++++++-- (unknown)

Read
76543210
|||||||+-- Bit exists but function is unknown
||||||+--- $40D6.1 = !($4112.0) read by CPU2.  (0 = $4110 UART Rx buffer has a byte ready to be read.)
|||||+---- $40D6.2 = !($4112.1) read by CPU2.  (0 = $4110 UART Tx buffer can be written.)
||||+----- $40D6.3 = !($4113.1 OR $4113.2) written by CPU2.
|||+------ $40D6.4 = !($4113.7) written by CPU2.  (1 = Transmit repeat.)
||+------- $40D6.5 = !($4113.6) written by CPU2.
++-------- (unlikely to exist)

$40D6.2 previously observed to equal !($4113.7 AND $4112.1) written by CPU2. It was later discovered that this bit also follows the $4112.1 read value (Tx buffer ready), which makes a lot more sense being beside $40D6.1 (Rx buffer ready). The previous observation can be explained because writing to those CPU2 bits both likely changed the availability of the Tx buffer.

RF5A18 Internal 65C02 CPU

The RF5A18 contains its own CPU, termed "CPU2" on this page. It is a 65C02 supporting bitwise set/clear/branch instructions. Note that CPU2 has its own parallel execution with its own address and data busses that are not available to the Famicom's CPU. CPU2 also has its own clock source, so it does not execute synchronously with the Famicom CPU. CPU2 clock speed is 2.4576 MHz (19.6608 MHz crystal / 8). This section describes CPU2's own memory mapping and its own internal registers.

CPU2 /Reset is controlled 2 different ways depending on the revision of Famicom Network System. To support all revisions when enabling CPU2, both of these bits should be written:

  • $40B1.3 = 0 (new revisions Famicom Network System, and old revisions with J1 closed)
  • $40C0.2 = 1 (old revisions Famicom Network System with J2 closed)

CPU2 Memory Map

RF5A18 Pin 26 Low (default)

+================+ $0000
| CPU2 RAM       |
| (U6)           |
+================+ $2000
|   (Returns     |
|   last fetch)  |
+================+ $4100
| CPU2 Control   |
| Registers      |
+================+ $4140
|   (Returns     |
|   last fetch)  |
+================+ $C000
| External ROM   |
| (not used)     |
+================+ $E000
| RF5A18         |
| Internal ROM   |
+================+ $10000

RF5A18 Pin 26 High

+================+ $0000
| CPU2 RAM       |
| (U6)           |
+================+ $2000
|   (Returns     |
|   last fetch)  |
+================+ $4100
| CPU2 Control   |
| Registers      |
+================+ $4140
|   (Returns     |
|   last fetch)  |
+================+ $C000
|                |
|                |
| External ROM   |
|                |
|                |
+================+ $10000

CPU2 Known Registers

Address Read
Has
Effect 		Read
Has
Data 		Write Function
$4100 No No Yes NMI Timer 1 Period, low byte. 
Write
76543210
++++++++-- NMI timer 1 period low byte.

Read
76543210
++++++++-- (does not exist)
  • Time (seconds) * 1200 = 16-bit timer 1 register value.
    • 1 count = 2048 CPU cycles.
  • This is the LSB of the 16-bit period. Refer to $4101 for the MSB.
$4101 No No Yes NMI Timer 1 Period, high byte. 
Write
76543210
++++++++-- NMI timer 1 period high byte.

Read
76543210
++++++++-- (does not exist)
  • Time (seconds) * 1200 = 16-bit timer 1 register value.
    • 1 count = 2048 CPU cycles.
  • This is the MSB of the 16-bit period. Refer to $4100 for the LSB.
$4102 No No Yes NMI Timer 1 Restart. 
Write
76543210
|||||||+-- $4102.0 = timer 1 loop.  1 = Loop, 0 = One-Shot
||||||+--- $4102.1 = timer 1 restart.  1 = Restart.
++++++---- (unknown)

Read
76543210
++++++++-- (does not exist)
  • When setting bit 1 = 1, timer 1 restarts with the period specified in $4100, $4101.
  • The values of $4100, $4101 are not affected by running timer 1 and need not be rewritten each time.
  • NMI will be generated when timer 1 expires if $412F.0 = 1.
  • The behavior is untested when setting bits 0 or 1 = 1 while timer 1 is already running.
$4103 Yes Yes Unknown NMI Timer 1 Acknowledge. 
Write
76543210
++++++++-- (unknown)

Read
76543210
|||||||+-- $4103.0 = Timer 1 NMI flag.  1 = Timer 1 NMI triggered.
+++++++--- (does not exist)
  • Reading from this register likely acknowledges timer 1 NMI.
  • The read value of $4103.0 reflects the timer 1 NMI flag, but does not reflect external NMI via pin 29.
$4104 No No Yes IRQ Timer 2 Period, low byte. 
Write
76543210
++++++++-- IRQ timer 2 period low byte.

Read
76543210
++++++++-- (does not exist)
  • Time (seconds) * 2,457,600 = 16-bit timer 2 register value.
    • 1 count = 1 CPU cycle.
  • This is the LSB of the 16-bit period. Refer to $4105 for the MSB
$4105 No No Yes IRQ Timer 2 Period, high byte. 
Write
76543210
++++++++-- IRQ Timer 2 Period, high byte.

Read
76543210
++++++++-- (does not exist)
  • Time (seconds) * 2,457,600 = 16-bit timer 2 register value.
    • 1 count = 1 CPU cycle.
  • This is the MSB of the 16-bit period. Refer to $4104 for the LSB
$4106 No No Yes IRQ Timer 2 Restart. 
Write
76543210
|||||||+-- $4106.0 = timer 2 loop.  1 = Loop, 0 = One-Shot
||||||+--- $4106.1 = timer 2 restart.  1 = Restart.
++++++---- (unknown)

Read
76543210
++++++++-- (does not exist)
  • Theory: When setting bit 1 = 1, timer 2 restarts with the period specified in $4100, $4101.
  • Theory: The values of $4104, $4105 are not affected by running timer 2 and need not be rewritten each time.
  • IRQ will be generated when timer 2 expires if $412F.6 = 1.
  • The behavior is untested when setting bits 0 or 1 = 1 while timer 2 is already running.
$4107 Yes Yes Unknown IRQ Timer 2 Acknowledge. 
Write
76543210
++++++++-- (unknown)

Read
76543210
|||||||+-- (unlikely to exist)
||||||+--- Likely to be the Timer 2 IRQ flag
++++++---- (unlikely to exist)
  • Reading from this register likely acknowledges timer 2 IRQ.
  • $4107.1 is probably the timer 2 IRQ flag.
$4110 Yes Yes Yes UART Rx/Tx Data Buffer 
Write
76543210
++++++++-- UART Tx Data Byte
             Bits 7:0 in 8-bit mode, bits 6:0 in 7-bit mode

Read
76543210
++++++++-- UART Rx Data Byte
             Bits 7:0 in 8-bit mode, bits 6:0 in 7-bit mode
  • Writing a byte to this register automatically clears $4112.1 read value and triggers the byte to be sent on UART Tx.
  • Reading a byte from this register automatically clears $4112.0 read value, to be triggered high again next byte received on UART Rx.
  • This UART is connected to the MSM6827L TXD and RXD pins.
  • The byte is ready to read here when the IRQ flag $4112.0 is high.
  • The byte is ready to be written here when flag $4112.1 is high.
  • Writes to $4110 are specifically prevented by built-in ROM in modes 0 and 5.
  • Bench testing confirmed reads and writes of this register correspond to data read by UART Rx and written to UART Tx.
    • In 7-bit mode, Rx bit 7 (unused in this case) observed to be 0 but not confirmed always to be 0.
$4111 Unknown Yes Yes UART Configuration 
Write
76543210
|||||||+-- $4111.0 = UART Rx Enable (1 = enabled)
||||||+--- $4111.1 = UART Tx Enable (1 = enabled)
|||||+---- $4111.2 = Baudrate Scaler (0 = multiply baudrate x4)
||||+----- $4111.3 = Data bits (0 = 7 bits, 1 = 8 bits)
|||+------ $4111.4 = Tx Stop bits (0 = 1 stop bit, 1 = 2 stop bits)
||+------- $4111.5 = Parity bit (0 = don't use, 1 = append parity bit)
|+-------- $4111.6 = Parity type (0 = odd parity, 1 = even parity)
+--------- $4111.7 = Send Tx Break (1 = force UART Tx low (break), 0 = normal)

Read
76543210
++++++++-- Reads back the value written.
  • See register $4114 for baudrate table.
  • Confirmed write bits 2,3,5,6 apply to both Rx and Tx.
  • Write bit $4111.4 confirmed not to enforce 2 stop bits for UART Rx.
    • Consecutive Rx bytes with 1 stop bit separation can still be received when $4111.4 = 1.
  • Write bit $4111.7 requires manual operation to send a break character and has no effect on Rx operation.
$4112 Unknown Yes Yes UART Status 
Write
76543210
|||||||+-- Bit exists but function is unknown
||||||+--- $4112.1: Tx Silence
||||||       0 = Set UART Tx directly high (idle state), 1 = Allow sending data.
||||||       This bit figures into $40D6.2 read by the Famicom. (See register $40D6.)
|+++++---- (unknown)
+--------- $4112.7 = $4110 UART Rx Data IRQ Acknowledge, 1 = Acknowledge IRQ.

Read
76543210
|||||||+-- $4112.0 = $4110 UART Rx Buffer Ready Flag (1 = $4110 buffer has a byte ready to be read.)
||||||+--- $4112.1 = $4110 UART Tx Buffer Ready Flag (1 = $4110 buffer can be written.)
|||||+---- $4112.2 = UART Tx Idle, 1 = Idle, 0 = Active.
||||+----- Bit exists but function is unknown
|||+------ $4112.4 = Rx Parity Error. (1 = error detected)
||+------- $4112.5 = Rx Framing Error. (1 = error detected)
|+-------- $4112.6 = Rx Break Received. (1 = break detected)
+--------- Bit exists but function is unknown
  • Error and Break bits persist through $4110 operations, but can be cleared by writing 1 to $4112.7.
  • Found $4112.4 read became 1 when setting in parity mode ($4111.5 = 1) and injecting a wrong parity bit.
    • Confirmed this flag not getting set anymore with the same test when changing parity even/odd (i.e. inverted $4111.6).
  • $4112.6 = 1 (break) comes accompanied with $4112.5 = 1 (framing error).
$4113 Unknown Yes Yes UART Configuration 
Write
76543210
|||||||+-- (unknown)
||||||+--- $4113.1 figures into $40D6.3 read by the Famicom. (See register $40D6.)
|||||+---- $4113.2 figures into $40D6.3 read by the Famicom. (See register $40D6.)
||+++----- (unknown)
|+-------- $4113.6 figures into $40D6.5 read by the Famicom. (See register $40D6.)
+--------- $4113.7: Tx Repeat
             1 = Send once on pin 90 (UART Tx), 0 = Send repeatedly
             This figures into $40D6.2 and $40D6.4 read by the Famicom. (See register $40D6.)

Read
76543210
++++++++-- Bits exist but function is unknown
$4114 Unknown No Yes UART Baudrate 
Write
76543210
||||||++-- UART Baud Rate (Rx and Tx)
||||||       This is a clock divider that also affects frequency seen on $40D5.4.
++++++---- (unknown)

Read
76543210
++++++++-- (unlikely to exist)
  • Baud Rate Selection:
$4111.2 $4114.1 $4114.0 Baudrate
0 0 0 1200
0 0 1 2400
0 1 0 4800
0 1 1 9600
1 0 0 300
1 0 1 600
1 1 0 1200
1 1 1 2400
$4120 Unknown Yes Yes Unknown Function. 
Write
76543210
|||||||+-- Pin 39 (MSM6827L AD0) = $4120.0
||||||+--- Pin 38 (MSM6827L AD1) = $4120.1
|||||+---- Pin 37 (n/c) = $4120.2
||||+----- Pin 36 (MSM6827L /RD) = $4120.3
|||+------ Pin 35 (MSM6827L /WR) = $4120.4
||+------- Pin 34 (MSM6827L EXCLK) = $4120.5
|+-------- Pin 32 (MSM6827L Data): Direction = $4120.6: 1 = input, 0 = output (refer to $4121.0)
+--------- (unknown)

Read
76543210
|+++++++-- Bits exist but function is unknown
+--------- $4120.7 = Pin 33 (MSM6827L /INT)
  • When pin 32 is set as input, it is unknown if or how the value can be read.
  • Pin 32 floats in input mode, regardless of the value written to $4121.0.
  • When pin 32 is set as output, it is a push-pull output.
$4121 Unknown Yes Yes Unknown Function. 
Write
76543210
|||||||+-- Pin 32 (MSM6827L Data) = $4121.0 when set as output (refer to $4120.6)
+++++++--- (unknown)

Read
76543210
++++++++-- Bits exist but function is unknown
  • Reading $4121.0 reflects the value written to $4121.0 when $4120.6 is set as output.
  • Surprisingly, reading $4121.0 is always 1 when $4120.6 is set as input regardless of:
    • Driving pin 32 high or low.
    • Writing 1 or 0 to $4121.0.
$4122 Unknown Yes Yes Famicom CPU <-> CPU2 Interface, Data Acknowledge 
Write
76543210
|||+++++-- (unlikely to exist)
+++------- 3-bit value written here can be read by Famicom CPU from register $40D3.

Read
76543210
|||+++++-- (unlikely to exist)
+++------- 3-bit value read here was written by Famicom CPU to register $40D3.
  • Read and write directions are represented by separate physical registers.
  • The read value can only be affected by the Famicom CPU.
$4123 Unknown Yes Yes Famicom CPU <-> CPU2 Interface, Data Byte 0 
Write
76543210
++++++++-- 8-bit value written here can be read by Famicom CPU from register $40D0.

Read
76543210
++++++++-- 8-bit value read here was written by Famicom CPU to register $40D0.
  • Read and write directions are represented by separate physical registers.
  • The read value can only be affected by the Famicom CPU.
$4124 Unknown Yes Yes Famicom CPU <-> CPU2 Interface, Data Byte 1 
Write
76543210
++++++++-- 8-bit value written here can be read by Famicom CPU from register $40D1.

Read
76543210
++++++++-- 8-bit value read here was written by Famicom CPU to register $40D1.
  • Read and write directions are represented by separate physical registers.
  • The read value can only be affected by the Famicom CPU.
$4125 Unknown Yes Yes Famicom CPU <-> CPU2 Interface, Data Byte 2 
Write
76543210
++++++++-- 8-bit value written here can be read by Famicom CPU from register $40D2.

Read
76543210
++++++++-- 8-bit value read here was written by Famicom CPU to register $40D2.
  • Read and write directions are represented by separate physical registers.
  • The read value can only be affected by the Famicom CPU.
$4126 Unknown Yes Unknown Unknown Function. 
Write
76543210
++++++++-- (unknown)

Read
76543210
|||||||+-- $4126.0 = Pin 47 (+5V)
||||||+--- $4126.1 = !(Pin 48) (+5V)
|||||+---- $4126.2 = Pin 49 (from 5C66-69)
||||+----- $4126.3 = Pin 51 (Switch SW1-2)
|||+------ $4126.4 = Pin 52 (Switch SW1-4)
||+------- $4126.5 = Pin 53 (Modem P4-25)
|+-------- $4126.6 = Pin 54 (Modem P4-28)
+--------- $4126.7 = Pin 55 (Modem P4-23)
  • SW1 selects between pulse and DTMF dialing.
$4127 Unknown No Yes Unknown Function. 
Write
76543210
|||||||+-- Pin 56 MSM6827L +Reset = $4127.0
||||||+--- Pin 57 /Red LED = $4127.1
|||||+---- Pin 58 /Green LED = $4127.2
||||+----- Pin 59 (n/c) = $4127.3
|||+------ Pin 60 /Phone Off Hook = $4127.4
||+------- Pin 61 /DTMF Output Enable = $4127.5
|+-------- Pin 62 /Phone Audio Enable = $4127.6
+--------- Pin 63 (Modem P4-19) = $4127.7

Read
76543210
++++++++-- (unlikely to exist)
  • Pin 60 observed low corresponding to off hook and pulse dialing pulses.
  • Pin 61 observed low for the duration of DTMF numbers being dialed, but not in pulse mode.
  • Pin 62 observed low corresponding to modem sounds coming through the TV speakers.
  • Pin 63 observed always high.
$4128 Unknown Yes Yes Unknown Function. 
Write
76543210
|||||||+-- Pin 68 (Tone Rx GT) = $4128.0
+++++++--- (unknown)

Read
76543210
|||||+++-- (unlikely to exist)
||||+----- $4128.3 = Pin 69 (Tone Rx D1)
|||+------ $4128.4 = Pin 70 (Tone Rx D2)
||+------- $4128.5 = Pin 71 (Tone Rx D4)
|+-------- $4128.6 = Pin 72 (Tone Rx D8)
+--------- $4128.7 = Pin 73 (Tone Rx DV)
$4129 Unknown Unknown Yes P5 Expansion Port 
Write
76543210
||||++++-- Data nybble written to device attached to P5 connector.
||++------ Used for sequencing writes to the device.
++-------- (unknown)

Read
76543210
||++++++-- Controlled by device attached to P5 connector, though the ROM code never reads it.
++-------- Not used
  • The data bus floats when reading this register, presumably to be driven by a device connected to P5.
  • Pin 23 is a /CE low when writing to this register (untested for reads).
  • Data bits 6 and 7 are not available in the P5 connector.
$412F Unknown Yes Yes Unknown Function. 
Write
76543210
|||||||+-- $412F.0 = Timer 1 NMI enable.  1 = Enabled.
||||+++--- (unknown)
|||+------ $412F.4 = Pin 33 (MSM6827L /INT) IRQ enable. 1 = Enabled.
||+------- $412F.5 = Pin 73 (Tone Rx DV) IRQ enable.  1 = Enabled.
|+-------- $412F.6 = Timer 2 IRQ enable.  1 = Enabled.
+--------- $412F.7 = UART Rx IRQ enable.  1 = Enabled.

Read
76543210
|||||||+-- Bit exists but function is unknown
|||||++--- (unlikely to exist)
||||+----- Bit exists but function is unknown
|||+------ $412F.4 = !(Pin 33) (MSM6827L /INT)
||+------- $412F.5 is set when IRQ is triggered by writing 1 to $412F.5.
||           This is probably the Tone Rx DV interrupt flag.
|+-------- $412F.6 is an IRQ flag.  1 = IRQ pending.
+--------- Bit exists but function is unknown
  • ROM tends to clear $412F.0 immediately after disabling interrupts with SEI, and sets it right before enabling with CLI.
    • The ROM is apparently disabling/enabling both IRQs and the timer NMI this way.
  • None of the write bits in this register prevent external NMI generated from pin 29 low.
  • None of the write bits prevent exteral IRQ generated from pin 28 low either.
  • Pin 33 (MSM6827L /INT) low triggers interrupt.
  • Pin 73 (Tone Rx DV) high triggers interrupt.
$4130 Unknown No Yes Unknown Function. 
Write
76543210
|||||||+-- Serial bit to be written
+++++++--- (unknown, unlikely to exist)

Read
76543210
++++++++-- (unlikely to exist)
  • The buffer at RAM $0330 is written to this register 1 bit at a time, seemingly using only bit 0 of the register.
  • The most significant bit of each byte is sent first.
  • 40 bytes are sent from $0330, then only the 6 most significant bits of the 41st byte.
    • A total of 326 bits are sent to this register.
  • Note: CPU2 commands $10 and $11 fill this buffer.
$4131 Unknown No Yes Unknown Function. 
Write
76543210
|||||||+-- Serial bit to be written
+++++++--- (unknown, unlikely to exist)

Read
76543210
++++++++-- (unlikely to exist)
  • The buffer at RAM $0360 is written to this register 1 bit at a time, seemingly using only bit 0 of the register.
  • The most significant bit of each byte is sent first.
  • 40 bytes are sent from $0360, then only the 6 most significant bits of the 41st byte.
    • A total of 326 bits are sent to this register.
  • Note: CPU2 commands $10, $11, and $6A fill this buffer.
$4132 Unknown No Yes Unknown Function. 
Write
76543210
|||||||+-- Serial bit to be written
+++++++--- (unknown, unlikely to exist)

Read
76543210
++++++++-- (unlikely to exist)
  • The buffer at RAM $0390 is written to this register 1 bit at a time, seemingly using only bit 0 of the register.
  • The most significant bit of each byte is sent first.
  • 40 bytes are sent from $0390, then only the 6 most significant bits of the 41st byte.
    • A total of 326 bits are sent to this register.
  • Note: CPU2 commands $10, $11, and $6A fill this buffer.
$4133 Unknown No Yes Unknown Function. 
Write
76543210
|||||||+-- Serial bit to be written
+++++++--- (unknown, unlikely to exist)

Read
76543210
++++++++-- (unlikely to exist)
  • The buffer at RAM $0320 is written to this register 1 bit at a time, seemingly using only bit 0 of the register.
  • The most significant bit of each byte is sent first.
  • 4 bytes are sent from $0320, then only the 4 most significant bits of the 5th byte.
    • A total of 36 bits are sent to this register.
  • Note: CPU2 commands $10 and $11 fill this buffer.
$4134 Yes Yes Unknown Unknown Function. 
Write
76543210
++++++++-- (unknown)

Read
76543210
|||||||+-- Bit exists but function is unknown
+++++++--- (unlikely to exist)
  • This register has serial data that can be read 1 bit at a time from $4134.0.
    • Without any other register reads/writes, the next bit is provided the next time this register is read.
  • In each byte read, the most significant bit comes first.
  • CPU2 built-in ROM reads 40 bytes this way and stores them starting at RAM $03C0.
    • Then 6 additional bits are read and stored as the 41st byte bits 7:2, and 0 for bits 1:0.
$4135 Unknown Yes Unknown Unknown Function. 
Write
76543210
++++++++-- (unknown)

Read
76543210
|||||||+-- $4135.0 = $4134 Serial Data Ready (1 = ready)
+++++++--- (unlikely to exist)
  • If $4135.0 = 1, Built-in ROM proceeds to read the serial data from $4134.
  • Note: Built-in ROM only treats this register as a flag and does not treat it as serial data.
$4136 Unknown No Yes Unknown Function. 
Write
76543210
++++++++-- (unknown)

Read
76543210
++++++++-- (unlikely to exist)
  • Built-in ROM writes #$00 to $4137, then writes serial data to $4130, $4131, $4132, $4133, then writes #$00 to this register.
  • Theory: This is a "start" flag that starts using new data from $4130-4133 when the flag is cleared.
$4137 Unknown No Yes Unknown Function. 
Write
76543210
++++++++-- (unknown)

Read
76543210
++++++++-- (unlikely to exist)
  • Built-in ROM writes #$00 to this register, then writes serial data to $4130, $4131, $4132, $4133, then writes #$00 to $4136.
  • Theory: This is a "clear" flag that resets write bit counters and/or clears old data from $4130-4133 when the flag is cleared.

Communication Between Famicom and CPU2

Registers $40D0, $40D1, $40D2, and $40D3 are used for communication between Famicom and CPU2. One would tend to expect the Famicom to receive the same value from any of these four registers if read back right after writing. However, each register is actually a separate register in each direction. The Famicom only controls the value read by CPU2, and CPU2 only controls the value read by the Famicom. It may be that CPU2 echoes the value back in some cases, but don't be fooled.

Data packets are sent in both directions between the Famicom and CPU2 using these registers. The data flow is controlled by status and acknowledge flags in $40D3, and data is sent 3 bytes at a time using registers $40D0, $40D1, and $40D2. When CPU2 receives each 3-byte chunk, it buffers it in its RAM starting at address $0401 until the full message has been received. The maximum message length is at most 255 bytes, possibly less.

Each message starts with a command byte, followed by a byte count. The byte after the byte count is not used and not counted towards the byte count in most commands. There are a total of 25 command bytes, which are stored in a lookup table at CPU2 ROM address $FB52. The index of this lookup table corresponds to the index of a function pointer table at address $FBB2, and a command mode support bitfield table at address $FB6B. This is how CPU2 efficiently directs to a unique message handler function for each command byte. The mode bitfield checks against the mode byte at $0051. It is probably used for enforcing the correct sequence of commands, as the command handlers themselves seem to be a major contributor changing the mode. It seems there are 6 possible modes: 0, 1, 2, 3, 4, and 5, though command $03 is set to support modes 6 and 7 as well. The mode may actually represent a global state machine, such as 0 = disconnected, 1 = dialing, etc.

CPU2 Commands

Commands Read by the Famicom from CPU2

Command
Byte 		Description
$80 This command is received by the Famicom in response to writing to command $00. (See next section for details.)
$81 Unknown function. 
[$81] [count=$01] [$00] [connection status]
  • It is unknown what events trigger this command to be sent to the Famicom.
  • [connection status] comes from RAM $0052, see section below for enumerated values.
  • This response can only happen in mode 3 via NMI.
  • Theory: This command is a response to writing to command $01.
$82 Unknown function. 
[$82] [count=$01] [$00] [connection status]
  • It is unknown what events trigger this command to be sent to the Famicom.
  • [connection status] comes from RAM $0052, see section below for enumerated values.

Response:

  • [parameter] $00 means success, all other values indicate an error.
    • When successful, the mode changes to $02.
    • When unsuccessful, the mode changes to $00.
  • [parameter] comes from RAM $0052
  • This response can only happen in mode 4 via NMI.
  • Theory: This command is a response to writing to command $02.
$83 This command is received by the Famicom in response to writing to command $03. (See next section for details.)
$90 This command is received by the Famicom in response to writing to command $10. (See next section for details.)
$91 This command is received by the Famicom in response to writing to command $11. (See next section for details.)
$92 This command is received by the Famicom in response to writing to command $12. (See next section for details.)
$C0 UART Rx Packet

There are 2 different parts of the CPU2 code that can send this message: 

[$C0] [count=N] [parameter] [...N bytes...]
  • This command can only be sent to the Famicom in mode 2.
  • [parameter] comes from RAM $0024.
  • [...N bytes...] are read from register $4110, most recent reads first, 1 byte read from $4110 per IRQ.
  • Count N does not include the parameter byte.
  • This is serial data received from the Oki MSM6827L integrated modem chip.
  • This response can only happen in mode 2 via IRQ.


[$C0] [count=$01] [$00] [parameter]
  • It is unknown what events trigger this command to be sent to the Famicom.
  • The modem abruptly disconnects when sending this command.
  • [parameter] can be #$00 or #$01.
  • This response can only happen in mode 2 via IRQ.
$C1 Tone Rx Data Packet.

When the packet only contains 1 nybble: 

[$C1] [count=$01] [$80] [tone Rx nybble]
  • [tone Rx nybble] is register ($4128 read value >> 3) & 0x0F.


When there is more than 1 nybble in the packet: 

[$C1] [count=N] [parameter] [tone Rx bytes]
  • [parameter] is either $00 or $01 based on the value of RAM $007A.
    • Theory: [parameter] may indicate an even or odd number of nybbles in the packet.
  • Each Tone Rx byte is packed with 2 nybbles.
  • Count N does not include the parameter byte.
$E1 This command indicates that CPU2 had a failure receiving a command from the Famicom.

Command from Famicom that failed due to invalid command byte, or a command not supported in the present mode: 

Message from Famicom:
[invalid command] [count] [byte 0] [byte 1] ...

Response back to Famicom:
[$E1] [count=$03] [?] [$00] [invalid command] [byte 1]
  • [?] byte appears to be open to sending an artifact from the previous response.
  • Observed JRA-PAT rev 05 read this response after attempting to write to command $01 after a failed connection.
    • E1 03 (00) 00 01 01


Command from Famicom that failed due to invalid byte count: 

Message from Famicom:
[command] [invalid count] [byte 0] [byte 1] ...

Response back to Famicom:
[$E1] [count=$03] [$00] [$01] [command] [byte 1]
$F0 This command is received by the Famicom in response to writing to command $7C. (See next section for details.)

Commands Written by the Famicom to CPU2

Note that most descriptions are incomplete.

Command
Byte 		CPU2
Handler
Address 		Byte
Count
Expected 		Modes
Supported 		Description
$00 $F43A >= 0
<= 60 		0 Hook And Dialing Sequence Configuration 
Message Bytes:
[$00] [count=N] [xx] [...N bytes command string...]

Response:
[$80] [count=$01] [$00] [status byte]
  • [xx] byte is ignored.
  • All observed software uses this command when opening a connection.
  • Changes to Command Mode 1 when the full message has been received from the Famicom.
  • [command string] is a series of one-byte commands executed in Command Mode 1.
    • $00-$1F: ignored
    • $20: wait up to 3 seconds for call progress (dial) tone to stop
      • Fails with status $03 if the tone never stops
    • $21: switch to DTMF dialing
    • $22: switch to normal (10pps) pulse dialing
    • $23: switch to fast (20pps) pulse dialing
    • $24: turn on audio output
    • $25: turn off audio output
    • $26: disconnect phone line (on hook)
    • $27: connect phone line (off hook)
    • $28-$2F: ignored
    • $30: dial 0 (10 pulses)
    • $31-$39: dial 1-9 (1-9 pulses)
    • $3A: dial D (no pulses)
    • $3B: dial * (11 pulses)
    • $3C: dial # (12 pulses)
    • $3D: dial A (13 pulses)
    • $3E: dial B (14 pulses)
    • $3F: dial C (15 pulses)
    • $40-7F: currently unknown, but not ignored
    • $80-FF: delay 0.2-25.6 seconds (in 200ms increments)

Response:

  • [connection status] comes from RAM $0052, see section below for enumerated values.
    • When successful, the mode changes to $02.
    • When unsuccessful, the mode changes to $00.
  • This response can only happen in mode 1 via NMI.
$01 $F46C 1 2 Unknown Function. 
Message Bytes:
[$01] [count=$01] [xx] [parameter]
  • [xx] byte is ignored.
  • [parameter] Values:
    • $00 = Write #$00 to $0031
    • $01-FF = Write #$02 to $0031
  • JRA-PAT and PiT Motorboat Race use this command when closing a connection.
  • Observed Messages (unused bytes in parentheses):
    • JRA-PAT rev 05:
      • 01 01 (00) 01 (30 42)
    • PiT Motorboat Race rev 02:
      • 01 01 (00) 01 (02 31)
  • Checks if the byte received is 00 and if so, acts differently.
  • Starts NMI timer 1 with period $0006 (5 msec), one-shot:
    • Writes #$06 to $4100
    • Writes #$00 to $4101
    • Writes #$02 to $4102
  • Changes to Command Mode 3 when complete.
  • Theory: This command generates response command $81 (see previous section).
$02 $F48A 2 0 Unknown Function. 
Message Bytes:
[$02] [count=$02] [xx] [parameter 0] [parameter 1]
  • [xx] byte is ignored.
  • [parameter 0] gets written to $002E.
  • [parameter 1] gets written to $002B and $002C.
  • 9 zero-page addresses get zeroed out; seems to be initializing something.
  • Starts NMI timer 1 with period $0006 (5 msec), one-shot:
    • Writes #$06 to $4100
    • Writes #$00 to $4101
    • Writes #$02 to $4102
  • Changes to Command Mode 4 when complete.
  • Theory: This command generates response command $82 (see previous section).
$03 $F4BB 0 0,1,2,3,
4,5,6,7 		System Revision and Status Information 
Message Bytes:
[$03] [count=$00]

Response:
[$83] [count=$0A] [$00] [ROM revision] [ROM checksum MSB] [ROM checksum LSB] [byte 4] ... [byte 10]
  • Writes to $4120.
  • Writes $412F shadow register to $412F (update only, no apparent modification).
  • Response:
    • [byte 1] = Comes from ROM address $FFF9, which seems to be a ROM revision byte. Observed value $03.
    • [byte 2], [byte 3] = 16-bit ROM checksum. Computed at bootup with the function located at $FD7D. It adds each byte of ROM.
    • [byte 4] = Value read from register $4121 & #$3F. If RAM $0023 is not equal to #$04, it also sets bit 7.
    • [byte 5] = Value read from register $4126.
    • [byte 6] = Value most recently written to $4127.
    • [byte 7] = Present mode.
    • [byte 8] = Number of 256-byte data blocks presently queued up in RAM range $1300-$1FFF.
    • [byte 9] = Value of RAM $0076.
    • [byte 10] = Value of RAM $0077.
  • Observed Messages (unused bytes in parentheses):
    • Super Mario Club rev 09 at power-on:
      • Write: 03 00 (00)
      • Read: 83 0A 00 03 0C AF A1 FB FE 00 0D 00 00
    • JRA-PAT rev 05 and 06 at power-on:
      • Write: 03 00 (00)
      • Read: 83 0A 00 03 0C AF 81 FB FE 00 0D 00 00
$10 $F71A 40 0,2,5 Unknown $413x Function. 
Message Bytes:
[$10] [count=$28] [parameter] [...40 bytes...]

Response:
[$90] [count=$28] [response parameter] [...40 bytes...]
  • This command is similar to command $11, except using pre-defined data from ROM instead of the additional chunks in command $11.
  • [parameter] is used but does not count towards the byte count.
  • [parameter] value #$00 - #$0F:
    • Pre-defined ROM data gets copied from tables.
    • 40 bytes from ROM are copied starting at RAM address $0360. ROM table index using parameter bits 2,1,0.
      • $0388 (i.e. 41st byte) set to #$00.
      • See Register $4131.
    • 40 bytes from ROM are copied starting at RAM address $0390. ROM table index using parameter bits 1,0.
      • $03B8 (i.e. 41st byte) set to #$00.
      • See Register $4132.
    • 40 bytes from the command are copied starting at RAM address $0330.
      • $0358 (i.e. 41st byte) set to #$00.
      • $0330 (i.e. 1st byte) set to #$00.
      • See Register $4130.
    • 5 static bytes from ROM are copied starting at RAM address $0320: 01 40 50 00 60
      • See Register $4133.
  • [parameter] value #$10:
    • Skips the $0360 and $0390 ROM copy routines if RAM $0055 == #$00.
    • If $0055 is not #$00, it aborts the command.
  • Writes #$00 to $4137
  • Writes the 4 data chunks shifting 1 bit at a time to $4130, $4131, $4132, $4133
  • Writes #$00 to $4136
  • For the response, the count has not been confirmed to include [response parameter] or not.
  • The response comes from RAM starting at $03C0. (See register $4134.)
$11 $F75C 127 0,2,5 Unknown $413x Function. 
Message Bytes:
[$11] [count=$7F] [...5 byte chunk...] [...41 byte chunk 0...]
                  [...41 byte chunk 1...] [...41 byte chunk 2...]

Response:
[$91] [count=$29] [response parameter] [...41 bytes...]
  • Note that the first byte of the 5 byte chunk is not ignored in this command like it is in most others, though it still does not count towards the byte count.
  • The 5 byte chunk gets written to RAM starting at $0320 with lots of bit shifting and byte swapping. (See Register $4133.)
  • The 41 byte chunk 0 gets copied to RAM starting at $0330. (See Register $4130.)
  • The 41 byte chunk 1 gets copied to RAM starting at $0360. (See Register $4131.)
  • The 41 byte chunk 2 gets copied to RAM starting at $0390. (See Register $4132.)
  • Shares the remaining code in common with command $10.
  • For the response, the count has not been confirmed to include [response parameter] or not.
  • The response comes from RAM starting at $03C0. (See register $4134.)
$12 $F773 >= 3
<= 252 		0,2,5 CRC Calculator 
Message Bytes:
[$12] [count=N] [initial] [polynomial 1] [polynomial 2] [...N-2 bytes...]

Response:
[$92] [count=$02] [$00] [CRC 2] [CRC 1]
  • The [initial] byte does not count towards the byte count.
  • See next section for information about CRC keys.
  • Doesn't seem to write to any registers.
$40 $F7AF >= 1
<= 252 		2 Unknown Function. 
Message Bytes:
[$40] [count=N] [xx] [...N-1 bytes...]
  • [xx] byte is ignored, but does count towards the byte count.
  • Copies the N-1 bytes data directly into memory starting at the location +2 pointed to by $0000:0001.
  • Copies the byte count to the location +1 pointed to by $0000:0001.
  • Writes value $FF directly to the location pointed to by $0000:0001.
    • Not known what sets up that pointer.
  • This command is tricky to disassemble because it actually does copy the [xx] byte, then writes over it with the byte count, ultimately not using it.
  • Theory: This command sends a UART Tx Packet to the Oki MSM6827L, and connected with response command $C0.
$41 $F7D0 >= 1
<= 100 		5 Unknown Function. 
Message Bytes:
[$41] [count=N] [xx] [...N bytes...]
  • [xx] byte is ignored and does not count towards the byte count.
  • Writes ((Byte count + 2) * 2) to the location +1 pointed to by $0000:0001.
  • Writes value $00 to the location +2 pointed to by $0000:0001.
  • Writes value $0F to the location +3 pointed to by $0000:0001.
  • For each of N bytes:
    • Writes upper nybble of the byte (>> 4) to the next byte pointed to by $0000:0001.
    • Writes the lower nybble of the byte (& $0F) to the next byte pointed to by $0000:0001.
  • Appends the value of $007C similarly as 2 nybbles at the end.
  • Writes value $FF directly to the location pointed to by $0000:0001.
    • Not known what sets up that pointer.
  • Theory: This command is something to do with the Tone Rx chip, and connected with response command $C1.
$60 $F829 6 0 Unknown Function. 
Message Bytes:
[$60] [count=$06] [...6 data bytes...]
  • Note that the first data byte is not ignored in this command, and it does count towards the byte count.
  • The 6 data bytes written by this command get copied to CPU2 RAM starting at address $84.
  • PiT Motorboat Race uses this command when opening a connection.
  • Observed Messages (unused bytes in parentheses):
    • PiT Motorboat Race rev 02:
      • 60 06 00 01 80 00 00 00 (00)
$61 $F839 0 1,3,4 Disconnect 
Message Bytes:
[$61] [count=$00]
  • This command abruptly disconnects the modem.
  • Writes #$00 to register $4102. (Stops NMI timer 1.)
  • Changes mode to 0 when complete.
$62 $F849 1 0,2,5 Unknown Function. 
Message Bytes:
[$62] [count=$01] [xx] [parameter]
  • [xx] byte is ignored.
  • Disables interrupts while executing this command.
  • Valid values of the [parameter] byte are $00 and $01.
    • Other values abort the command.
  • Appears to write to $4120
$63 $F887 0 0,1,2,3,
4,5 		NOP Command 
Message Bytes:
[$63] [count=$00]
  • This command only validates the byte count = #$00 and is then complete.
$64 $F88D 1 0,2,5 Modem Off Hook Control 
Message Bytes:
[$64] [count=$01] [xx] [Modem Off Hook mode]
  • [xx] byte is ignored.
  • [Modem Off Hook mode] Values:
    • $00 = Don't update but save mode as $00.
    • $01 = Set $4127.4 (/Modem Off Hook) = 0 (off hook). (Also stores #$00 to $0049)
    • $02-FF = Set $4127.4 (/Modem Off Hook) = 1 (hang up). (Also stores #$00 to $0049)
    • Value gets saved to $004E.
  • PiT Motorboat Race uses this command when closing a connection.
  • Observed Messages (unused bytes in parentheses):
    • PiT Motorboat Race rev 02:
      • 64 01 (00) 02 (A9 31)
  • Note: This description is fairly complete.
$65 $F89D 2 0,2,5 Modem Audio Enable and P4-19 Control 
Message Bytes:
[$65] [count=$02] [xx] [Modem Audio Enable mode] [P4-19 mode]
  • [xx] byte is ignored.
  • [Modem Audio Enable mode] Values:
    • $00 = Don't update but save mode as $00.
    • $01 = Set $4127.6 (/Modem Audio Enable) = 0 (enabled to TV speakers).
    • $02-FF = Set $4127.6 (/Modem Audio Enable) = 1 (disabled).
    • Value gets saved to $004F.
  • [P4-19 mode] Values:
    • $00 = Don't update but save mode as $00.
    • $01 = Set $4127.7 (Modem P4-19) = 0.
    • $02-FF = Set $4127.7 (Modem P4-19) = 1.
    • Value gets saved to $0050.
  • Heart no Benrikun Mini rev 01 A uses this command when closing a connection.
  • Observed Messages (unused bytes in parentheses):
    • Heart no Benrikun Mini rev 01 A:
      • 65 02 (00) 02 00 (20)
  • Note: This description is fairly complete.
$66 $F8B7 2 0,2,5 LED Control 
Message Bytes:
[$66] [count=$02] [xx] [red LED mode] [green LED mode]
  • [xx] byte is ignored.
  • [red LED mode] Values:
    • $00 = Don't update but save mode as $00.
    • $01 = Set Red LED on.
    • $02-7F = Set Red LED off.
    • $80-FF = Set Red LED to be controlled automatically by network status.
    • Value gets saved to $004C.
  • [green LED mode] Values:
    • $00 = Don't update but save mode as $00.
    • $01 = Set Green LED on.
    • $02-7F = Set Green LED off.
    • $80-FF = Set Green LED to be controlled automatically by network status.
    • Value gets saved to $004D.
  • PiT Motorboat Race uses this command when closing a connection.
  • Observed Messages (unused bytes in parentheses):
    • PiT Motorboat Race rev 02:
      • 66 02 (00) 02 02 (31)
  • Note: This description is fairly complete.
$67 $F8D1 2 0,5 Unknown Function. 
Message Bytes:
[$67] [count=$02] [xx] [parameter 0] [parameter 1]
  • [xx] byte is ignored.
  • If [parameter 0] is $00:
    • Abruptly disconnects the modem.
    • Zeroes out RAM $0076 and $0077.
    • Changes to mode 0 when complete.
  • Else if [parameter 0] is not $00:
    • Writes [parameter 0] to $74.
    • Writes [parameter 1] to $75.
    • Refreshes Green LED based on its mode.
    • Refreshes P4-27 (Phone Off Hook) based on its mode.
    • Zeroes out RAM $76,77,37,39,38.
    • Refreshes P4-21 (Phone Audio Enable) based on its mode.
    • Zeroes out all queued up outgoing modem Tx messages at RAM $1300-1FFF.
      • Each message has space $100 and number of queued messages is at RAM $0100.
    • Zeroes out Tone Rx incoming data buffer at RAM $0500-05FF.
    • Changes to mode 5 when complete.
$68 $F912 1 0,5 Unknown Function. 
Message Bytes:
[$68] [count=$01] [xx] [parameter]
  • [xx] byte is ignored.
  • The code has 3 different paths depending on parameter.
    • [parameter] < #$10
    • [parameter] == #$FF
    • All other values of [parameter]
$69 $F951 10 0 Unknown Function. 
Message Bytes:
[$69] [count=$0A] [xx] [...10 data bytes...]
  • [xx] byte is ignored.
  • Observed Messages (unused bytes in parentheses):
    • PiT Motorboat Race rev 02 when opening a connection:
      • 69 0A (00) 00 04 14 1D 28 80 00 30 26 21 (00 00)
    • JRA-PAT rev 05 and 06 at power-on:
      • 69 0A (00) 00 04 14 1D 28 30 00 30 26 21 (00 00)
  • The 10 data bytes are copied to CPU2 RAM starting at $8A.
  • If the 6th data byte (location $8F) is > #$FC, it gets overwritten by #$01.
$6A $F96F 80 0,2,5 Unknown $413x Function. 
Message Bytes:
[$6A] [count=$50] [xx] [...40 byte chunk 0...] [...40 byte chunk 1...]
  • [xx] byte is ignored.
  • Copies the 40 byte chunk 0 to RAM starting at $0360. (See Register $4131.)
  • Copies the negative (2's complement) of each byte in 40 byte chunk 1 to RAM starting at $0390. (See Register $4132.)
  • Writes #$00 to $0388 and $03B8. (i.e. 41st byte of each.)
  • Writes #$10 to $0055.
  • Observations:
    • No updates were made to buffers at $0320, $0330 from this command. (i.e. register $4133, $4130 data)
    • The command does not appear to initiate any operations to the $413x registers.
  • Note: This description is fairly complete.
$7B $F994 No
Check 		0,1,2,3,
4,5 		Software Reset 
Message Bytes:
[$7B] [count=xx] [xx]
  • Does not care about any bytes beyond the command byte.
  • Refreshes the green LED.
  • Disables interrupts.
  • Writes #$00 to $412F.
  • Sorts through some memory comparing values then generates a software reset.
    • Stores #$09 as the reset type code into $00FF.
$7C $F9AC 5 0,1,2,3,
4,5 		Arbitrary Memory Read 
Message Bytes:
[$7C] [count=$05] [xx] [CRC 1] [CRC 2] [address MSB] [address LSB] [read count N]

Response:
[$F0] [read count N] [$00] ...N bytes from memory...
  • [xx] byte does not count towards the byte count.
  • See next section for information about CRC bytes.
  • If [address MSB] >= #$80, exits early with no response. (Prevent ROM dump?? :) )
  • If [read count N] >= #$39, exits early with no response.
$7D $F9D9 >= 5 0,1,2,3,
4,5 		Arbitrary Memory Write 
Message Bytes:
[$7D] [count=N] [xx] [CRC 1] [CRC 2] [address MSB] [address LSB] [...N-4 bytes...]
  • [xx] byte does not count towards the byte count.
  • See next section for information about CRC bytes.
  • count - 4 is the number of bytes to write to memory.
  • Writes $00 to $006E.
  • Super Mario Club rev 09 uses this command at the welcome screen.
    • 7D 1A (00) 07 60 01 04 09 01 06 E0 16 A2 90 A5 29 F0 06 C9 FF D0 04 A2 01 86 29 4C 20 F4 (30)
    • CRC bytes: 07 60
    • Starting address: $0104 (farthest reaches of the stack)
  • JRA-PAT rev 05 and 06 use this command at power-on.
    • 7D 29 (00) EC AD 01 02 1A 01 09 01 06 E0 DB A2 90 A5 29 F0 06 C9 FF D0 04 A2 01 86 29 4C 20 F4 AD 32 00 C9 05 D0 03 EE 32 00 4C 39 E8 (00)
    • CRC bytes: EC AD
    • Starting address: $0102 (farthest reaches of the stack)
$7E $F9FE 5 0,1,2,3,
4,5 		Unknown Function. 
Message Bytes:
[$7E] [count=$05] [xx] [CRC 1] [CRC 2] [parameter 0] [parameter 1] [parameter 2]
  • [xx] byte does not count towards the byte count.
  • See next section for information about CRC bytes.
  • Writes a lot of stuff to $4120 and $4121
  • Writes to $4127 bit 5 (/DTMF Output Enable)
$7F $FA16 5 0,1,2,3,
4,5 		Unknown Function. 
Message Bytes:
[$7F] [count=$05] [parameter 0] [CRC 1] [CRC 2] [parameter 1] [parameter 2] [parameter 3]
  • [parameter 0] byte does not count towards the byte count.
  • See next section for information about CRC bytes.
  • If [parameter 0] is $00-7F, write value $0C out the P5 Expansion Port.
  • If [parameter 0] is $80-FF, dump RAM $0240-$0280 out the P5 Expansion Port.
    • The P5 Expansion port sequences out 1 nybble at a time.
  • [parameter 1] gets written to $00B7.
  • [parameter 2] gets written to $00B6.
  • [parameter 3] gets written to $00B8.
  • [parameter 0] gets written to $00B5.

CPU2 Commands with CRC key bytes

CPU2 command $12 calculates the CRC-16 of its message using [polynomial 1] and [polynomial 2] as the CRC polynomial, with [initial] placed in both bytes of the initial value, and performs the calculation LSB-first or "reflected". This command requires the polynomial to be specified in reciprocal form. For example, to calculate the standard CRC-16 with polynomial $8005, [polynomial 1] would be set to $40, [polynomial 2] would be set to $03, and [initial] would be set to $00.

CPU2 Commands $7C, $7D, $7E, and $7F use CRC key bytes [CRC 1] and [CRC 2] to validate the message. These commands calculate a CRC-16 across the message backwards, starting from the last byte and ending at [CRC 1]. The result must be 0 or the command is ignored. The CRC-16 polynomial is $8385 and the initial value is $35AC. The calculation is done LSB-first, or "reflected".

Connection Status Byte

Response commands $80, $81, and $82 send an enumerated value indicating the result when attempting to make a telephone connection. These enumerations are used clearly in the CPU2 ROM: 00, 01, 02, 03, 04, 05, 06, 07, 08, 0B, 0C, 0D, 0E. CPU2 ROM keeps track of this value at RAM location $0052. $00 indicates a successful connection, and all other values indicate a failure. Super Mario Club shows these failures with error code 40xx, xx directly reflecting this byte. Super Mario Club's manual gives troubleshooting information for most of these values. That information was used to create the table below.

Status
Byte 		Error
Code 		Description
$00 (n/a) Connection was successful.
$01 4001 No dial tone was detected.
$02 4002 An incoming phone call is being received.
$03 4003 Pulse vs. Tone setting is incorrect.
$04 4004 "0" Outgoing call setting is incorrect.
$05 4005 DDX-TP connection completed earlier than expected.
$06 4006 Unknown.
$07 4007 Unknown.
$08 4008 Server was busy, disconnected, or rejected the password.
$09 4009 Server was busy.
$0A 400A DDX-TP registration incorrect or server disconnected.
$0B 400B
$0C 400C
$0D 400D Problem with telephone line connection.
$0E 400E Problem with telephone line connection or server.

Pinouts

RF5C66 Mapper and Disk Drive Controller

                                                       _____
                                                      /     \
                                           CPU A0 -> / 1 100 \ -- +5Vcc
                                          CPU A1 -> / 2    99 \ -- n/c
                                         CPU A2 -> / 3      98 \ <> CPU D0
                                        CPU A3 -> / 4        97 \ <> CPU D1
                                       CPU A4 -> / 5          96 \ <> CPU D2
                                      CPU A5 -> / 6            95 \ <> CPU D3
                                     CPU A6 -> / 7              94 \ <> CPU D4
                                    CPU A7 -> / 8                93 \ <> CPU D5
                                  CPU A12 -> / 9                  92 \ <> CPU D6
                                 CPU A13 -> / 10                   91 \ <> CPU D7
                                CPU A14 -> / 11                     90 \ -- GND
                               /ROMSEL -> / 12                       89 \ <> Card D0
                              CPU R/W -> / 13                         88 \ <> Card D1
                                  M2 -> / 14                           87 \ <> Card D2
          P6-1 Lid Switch, Card R/W <- / 15                             86 \ <> Card D3
          (20k resistor to 5Vcc) ? -> / 16                               85 \ <> Card D4
                             /IRQ <- / 17                                 84 \ <> Card D5
                           +5Vcc -- / 18                                   83 \ <> Card D6
                            n/c -- / 19                                     82 \ <> Card D7
              21.47727MHz Xtal -- / 20                                       81 \ -- +5Vcc
                         Xtal -- / 21                                            \
                         n/c -- / 22                                     O       /
                        GND -- / 23                                          80 / -- n/c
        (n/c) Xtal Osc Out <- / 24                                          79 / -> Exp P3-2
                      n/c -- / 25                                          78 / <- Exp P3-3
   ToneRx Xin, CIC Clock <- / 26              Nintendo RF5C66             77 / -> Exp P3-4
                    n/c -- / 27       Package QFP-100, 0.65mm pitch      76 / -> Exp P3-5
         (n/c) $40AE.0 <- / 28                                          75 / -> Exp P3-6
 CIC /CPU R/W Inhibit -> / 29                Mapper and                74 / <- Exp P3-7
      Key CIC-12 (?) <- / 30           Disk Drive Controller          73 / <- Exp P3-8
                       /       O                                     72 / <- Exp P3-9
                       \                                            71 / <- Exp P3-11
      Key CIC-10 (?) -> \ 31                                       70 / -- GND
       Key CIC-15 (?) -> \ 32                                     69 / -> 5A18-49
           CPU2 /Reset -> \ 33                                   68 / -> CPU2 /Reset (new rev)
    CHR RAM /CE (input) -> \ 34                                 67 / <> Exp P3-12           Orientation:
                 RAM +CE <- \ 35                               66 / <> Exp P3-13            --------------------
            (n/c) $40C0.1 <- \ 36                             65 / <> Exp P3-14                 80         51
 CPU2 /Reset (old rev: J2) <- \ 37                           64 / <> Exp P3-15                   |         |
                CHR RAM /CE <- \ 38                         63 / <- $40B1.3 (n/c)               .-----------.
                         GND -- \ 39                       62 / <> Modem P4-31               81-|O Nintendo |-50
Built-in RAM /CE ($6000-7FFF) <- \ 40                     61 / <> Modem P4-32                   |  RF5C66   |
      (n/c) ? /CE ($4xE0-4xEF) <- \ 41                   60 / <> Modem P4-29                100-|  GCD 4R  O|-31
       5A18-85 /CE ($4xD0-4xDF) <- \ 42                 59 / -- +5Vcc                           \-----------'
                         (GND) ? -> \ 43               58 / -- n/c                               |         |
                          (GND) ? -> \ 44             57 / -> Kanji ROM A17                     01         30
                           (GND) ? -> \ 45           56 / -> Kanji ROM A4
                            (GND) ? -> \ 46         55 / -> Kanji ROM A3          Legend:
                           CIRAM A10 <- \ 47       54 / -> Kanji ROM A2           ------------------------------
                              PPU A11 -> \ 48     53 / -> Kanji ROM A1            --[RF5C66]-- Power
                               PPU A10 -> \ 49   52 / -> Kanji ROM A0             ->[RF5C66]<- RF5C66 input
             Kanji ROM /CE ($5000-5FFF) <- \ 50 51 / -- n/c                       <-[RF5C66]-> RF5C66 output
                                            \     /                               <>[RF5C66]<> Bidirectional
                                             \   /                                    f      Famicom connection
                                              \ /                                     r      ROM chip connection
                                               V                                      R      RAM chip connection
Notes:
- +5Vcc pins 18, 59, 81, 100 are all connected together internally.
- GND pins 23, 39, 70, 90 are all connected together internally.
- 43, 44, 45, 46 are GND on the PCB, but have internal protection diodes from GND, suggesting they are logic pins.
  - Pins 45-46, when pulled high, causes oscillation on pin 56.
- 24, 28, 36, 37, 41, 63 are n/c on the PCB, but function as noted.
- /CE Pins 40, 41, 42, 50 behaviors:
  - Pin 40 (Built-in RAM /CE) activates low in range $6000-7FFF, regardless of CPU R/W, but only when M2 is high.
  - Pin 41 (Unknown /CE) always activates low in range $4xE0-4xEF, regardless of CPU R/W and M2.
  - Pin 42 (RF5A18 CPU2 /CE) always activates low in range $4xD0-4xDF, regardless of CPU R/W and M2.
  - Pin 50 (Kanji ROM /CE) activates low in range $5000-5FFF, regardless of CPU R/W.  (It appears to go low only when M2 is high but not specifically proven.)
- Pin 29:
  - If the FNS has a CIC chip, CIC-11 drives this pin high after 24.8msec, and remains high as long as the CIC authentication is successful.  There is a low-pass filter in this case.
  - If the FNS does not have a CIC chip, the pin floats high.  There may be a pull-up resistor somewhere.  The delay to go high (if any) has not been measured.
  - When this pin is low, it resets pins 52-57 low and possibly lots of other things.
  - Card R/W is always high when this pin is low.
- Pin 31 (CIC-10) and Pin 32 (CIC-15):
  - Both are jumpered direct to GND if the FNS does not have a CIC chip.
  - If it does have a CIC chip, these signals are both always low with or without tsuushin card inserted.
  - In no observed case are these signals ever high.
- Pin 16 Pull-up of 20k to 5V is also required in order to avoid triggering reset.
- Pin 16 seems to be related to pin 29.  With pin 29 floating and pin 16 pulled high at power on, the chip runs for 5 seconds, then enters reset.
- Tested 10k instead of 20k (per original PCB) on pin 16, found no difference in time or function.
- Pin 69 has a high pulse of 11.9085 usec at any time that register $4xAC has not been read for 12.4892 seconds.
  - Each additional 12.4892 seconds generates another pulse.
  - It has very repeatable precision, at least 6 figures on each.
  - It is not synchronized to M2 or any other inputs.
  - Note that 12.4892 sec * 21.47727 MHz = 2^28, with an error of 0.075%. (Nominal would be 12.4986 sec.)
  - Note that 11.9085 usec * 21.47727 MHz = 2^8, with an error of 0.093%. (Nominal would be 11.9196 usec.)
- Pins 52-56 drive the address pins of the Kanji ROM.  (See notes below the LH5323M1 pinout.)
- Pin 15 (Card R/W) is a non-inverted buffer of CPU R/W.  This signal connects through the lid switch.
- Pin 26 puts out a 3.58 MHz square wave, ~50% duty.  This corresponds to 21.47727 MHz / 6.
- Pin 79 (Exp 2) puts out a 95.95 kHz square wave, 93.7% duty.  Clock source unknown.
  - Note that this seems similar to FDS serial bitrate.
  - Standalone chip can get into a 341.2 kHz mode when touching pin 80, though pulling 80 high or low doesn't correlate.
  - Either frequency, the negative pulse width is 650 nsec.
- Pins 71-79 appear strikingly similar to an FDS interface.
- CIRAM A10 follows PPU A10 by default.

RF5A18 CPU2 / Modem Controller

                                                     _____
                                                    /     \
                                        CPU2 A0 <- / 1 100 \ -- GND
                                       CPU2 A1 <- / 2    99 \ <> CPU2 D0         
                                      CPU2 A2 <- / 3      98 \ <> CPU2 D1         
                                     CPU2 A3 <- / 4        97 \ <> CPU2 D2         
                                    CPU2 A4 <- / 5          96 \ <> CPU2 D3         
                                   CPU2 A5 <- / 6            95 \ <> CPU2 D4         
                                  CPU2 A6 <- / 7              94 \ <> CPU2 D5         
                                 CPU2 A7 <- / 8                93 \ <> CPU2 D6         
                                  +5Vcc -- / 9                  92 \ <> CPU2 D7         
                               CPU2 A8 <- / 10                   91 \ -- +5Vcc
                              CPU2 A9 <- / 11                     90 \ -> UART Tx (MSM6827L TXD)
                            CPU2 A10 <- / 12                       89 \ <- UART Rx (MSM6827L RXD)
                           CPU2 A11 <- / 13                         88 \ <- CPU A2
                          CPU2 A12 <- / 14                           87 \ <- CPU A1
                   (n/c) CPU2 A13 <- / 15                             86 \ <- CPU A0
                  (n/c) CPU2 A14 <- / 16                               85 \ <- /CE (5C66-42)
                 (n/c) CPU2 A15 <- / 17                                 84 \ <- P6-1 Lid Switch, Card R/W
                           GND -- / 18                                   83 \ <- M2
   (2.4576 MHz) (n/c) CPU2 M2 <- / 19                                     82 \ <> Card D7
                    CPU2 R/W <- / 20                                       81 \ <> Card D6
       RAM /CE ($0000-1FFF) <- / 21                                            \
(n/c) ROM /CE ($C000-xFFF) <- / 22                                     O       /
      P5 /CE ($4129 Only) <- / 23                                          80 / <> Card D5
       (GND) CPU2 +Reset -> / 24                                          79 / <> Card D4
                (GND) ? -> / 25                                          78 / -- GND
  /Internal ROM Enable -> / 26             Nintendo RF5A18              77 / <> Card D3
(5C66-68) CPU2 /Reset -> / 27      Package QFP-100, 0.65mm pitch       76 / <> Card D2
  (10k up) CPU2 /IRQ -> / 28                                          75 / <> Card D1
 (10k up) CPU2 /NMI -> / 29             Modem Controller             74 / <> Card D0
               n/c -- / 30                   CPU2                   73 / <- Tone Rx DV
                     /       O                                     72 / <- Tone Rx D8
                     \                                            71 / <- Tone Rx D4
             +5Vcc -- \ 31                                       70 / <- Tone Rx D2
      MSM6827L DATA <> \ 32                                     69 / <- Tone Rx D1
       MSM6827L /INT -> \ 33                                   68 / -> Tone Rx GT
         MSM6827L /RD <- \ 34                                 67 / -> Exp P3-19
          MSM6827L /WR <- \ 35                               66 / <> Exp P3-18
         MSM6827L EXCLK <- \ 36                             65 / <> Exp P3-17
           (n/c) $4120.2 <- \ 37                           64 / -- +5Vcc                  Orientation:
             MSM6827L AD1 <- \ 38                         63 / -> Modem P4-19             --------------------
              MSM6827L AD0 <- \ 39                       62 / -> /Phone Audio Enable          80         51
              (n/c) CPU2 D0 <- \ 40                     61 / -> /DTMF Output Enable            |         |
                     (n/c) ? <- \ 41                   60 / -> /Phone Off Hook                .-----------.
       (4.9152 MHz) Exp P3-16 <- \ 42                 59 / -> $4127.3 (n/c)                81-|O  RF5A18  |-50
                           GND -- \ 43               58 / -> /Green LED                       |  Nintendo |
                19.6608MHz Xtal -- \ 44             57 / -> /Red LED                      100-|  GCD 8C  O|-31
                      1k to Xtal -- \ 45           56 / -> MSM6827L +Reset                    \-----------'
                              GND -- \ 46         55 / <- Audio from phone line                |         |
                   (+5Vcc) $4126.0 -> \ 47       54 / <- Modem P4-28                          01         30
                 (+5Vcc) !($4126.1) -> \ 48     53 / <- Modem P4-25             
                             5C66-69 -> \ 49   52 / <- Switch SW1-4             Legend:
                                  n/c -- \ 50 51 / <- Switch SW1-2              ------------------------------
                                          \     /                               --[RF5A18]-- Power, n/a
                                           \   /                                ->[RF5A18]<- RF5A18 input
                                            \ /                                 <-[RF5A18]-> RF5A18 output
                                             V                                  <>[RF5A18]<> Bidirectional
Notes:
- This chip contains its very own 65C02 CPU, with built-in ROM.
- +5Vcc pins 9, 31, 64, 91 are all connected together internally.
- GND pins 18, 43, 46, 78, 100 are all connected together internally.
- 24, 26 are GND on the PCB, but function as noted.
- 25 is GND on the PCB, but has internal protection diode from GND, suggesting it is a logic pin.
- 47, 48 are +5Vcc on the PCB, but function as noted.
- 15, 16, 17, 19, 22, 37, 40, 59 are n/c on the PCB, but function as noted.
- 41 is n/c on the PCB, but has protection diode from GND, suggesting it may have a function.
- Pin 42 (Exp 16) puts out a 4.92 MHz square wave, ~50% duty.  This is 19.6608 MHz / 4.
- CPU2 /Reset comes from RF5C66 pin 68 on new revisions and selectable with J1, J2 on old revisions:
  - J2 closed = RF5C66 pin 37 (default)
  - J1 closed = RF5C66 pin 68
- Pin 24 prevents CPU2 functioning when held high at power-on.  If the pin is then driven low, the reset vector is then fetched after that.
  - Pin 24 can be freely used as a +reset at any time this way.
- Pin 25 low at any time causes address bus to go to $FFFF and data bus shows a toggle on bits 2,5,6,7: period 208.7 usec, low for 7.93 usec.
  - Other data bits always low.
  - Shortly after applying power, the toggle has a lot of variations for a period of about 1.5 seconds, including a 225 msec gap where the bits are low.
  - The mentioned data bits all appear to have the same data.
  - Held low at power-on will fetch the reset vector later when driven high.
  - Held high at power-on, driven low later, enters the data bus toggle mode but:
    - Does not appear to fetch the reset vector when driven high after that.
    - Does execute code, possibly resuming from where it left off.
- When pin 26 is set low (default case: This pin is tied directly to GND on the PCB):
  - Internal ROM is enabled in CPU2 range $E000-FFFF.
  - Open Bus in CPU2 range $C000-DFFF.
  - Pin 22 (ROM /CE) is enabled low in range $C000-DFFF
  - This mode allows ROM expansion at $C000-DFFF, with internal ROM (and its vector table) in place.
- When pin 26 is set high:
  - Internal ROM is disabled, leaving open bus in CPU2 range $E000-FFFF.
  - Open Bus in CPU2 range $C000-DFFF.
  - Pin 22 (ROM /CE) is enabled low in the entire range $C000-FFFF.
  - This mode allows a totally custom external CPU2 ROM with its own interrupt vector table.

LH5323M1 Kanji Graphic ROM

                              _____  Note: Flat spot does not correspond to pin 1.
                             /     \
                     n/c -- / 12 11 \ -- n/c
           (5C66-52) A0 -> / 13   10 \ -- n/c
                CPU D0 <> / 14      9 \ <- A1 (5C66-53)
               CPU D1 <> / 15        8 \ <- A2 (5C66-54)
              CPU D2 <> / 16          7 \ <- A3 (5C66-55)
                GND -- / 17            6 \ -- GND
            CPU D3 <> / 18              5 \ <- A5 (CPU A0)
           CPU D4 <> / 19                4 \ -- n/c
          CPU D5 <> / 20                  3 \ <- A6 (CPU A1)
         CPU D6 <> / 21                    2 \ <- A7 (CPU A2)
        CPU D7 <> / 22  Nintendo LH5323M1   1 \ -- n/c
                 /        Package QFP-44       \
                 \         0.8mm pitch         /
           n/c -- \ 23                     44 / <- A8 (CPU A3)
            n/c -- \ 24   Kanji Graphic   43 / <- A13 (CPU A8)
       (GND) /OE -- \ 25       ROM       42 / <- A16 (CPU A11)
     (CPU A6) A11 -> \ 26               41 / <- A4 (5C66-56)         Orientation:
     (5C66-50) /CE -> \ 27             40 / -- n/c                   --------------------
                GND -- \ 28           39 / -- n/c                        33         23
        (CPU A7) A12 -> \ 29         38 / -- +5Vcc                        |         |
         (CPU A5) A10 -> \ 30       37 / <- A17 (5C66-57 Bankswitch)     .-----------.
                   n/c -- \ 31     36 / <- A15 (CPU A10)              34-| Nintendo O|-22
                    n/c -- \ 32   35 / -- n/c                            |  CCR-01   |
             (CPU A4) A9 -> \ 33 34 / <- A14 (CPU A9)                    | LH5323M1  |
                             \     /                                  44-|O 9528 D   |-12
                              \   /                                      '-----------/
                               \ /                                        |         |
                                V                                        01         11
                                
Notes:
- 6 & 28 are connected together internally.
- 17 has no measurable connection to 6 & 28.
- All logic pins have protection diode from pin 17, suggesting this is the true GND.
- Pin 25 also appears as a logic pin with respect to pin 17.
- When pins 25 and 27 are both driven low, the data bus becomes an output.  Otherwise it is hi-z.
- Pins 13, 9, 8, 7, 41, 37 are controlled by the RF5C66.
  - Pins 13, 9, 8, 7, 41 are controlled with auto-increment function.
  - The value of these pins increments each M2 falling edge when the CPU is in range $5000-5FFF.
  - Pin 37 is a bankswitch, controlled by register $40B0.0
  - At reset and when reading from register $40B0, these pins reset to 0.
  - The conditions resetting or maintaining the bankswitch pin to 1 are still unknown.

8633 Famicom Network System CIC Key Chip

Unlike the NES console, the Famicom Network System appears to have the CIC key. 

                                 _______   _______
                                 |      \_/      |
 (To Card CIC Pin 2) Data Out <- | 1          18 | -- +5Vcc
(From Card CIC Pin 1) Data In -> | 2  O       17 | -- n/c
                          n/c -- | 3   8633   16 | -- n/c
                          n/c -- | 4          15 | -> ? (5C66-32) always observed low
                          n/c -- | 5    CIC   14 | -- n/c
                          n/c -- | 6    Key   13 | -- n/c
                        Clock -> | 7          12 | <- ? (5C66-30)
(From Card CIC Pin 11) +Reset -> | 8    U8    11 | -> /CPU R/W Inhibit (5C66-29)
                          GND -- | 9          10 | -> ? (5C66-31) always observed low
                                 |_______________|
  • When the CIC key drives pin 11 low, this stops operation of the Famicom Network System by means of holding Card R/W high.
  • The clock is 3.58 MHz, coming from RF5C66 pin 26.

8634A Tsuushin Card CIC Lock Chip

Unlike the NES cartridge, the tsuushin card appears to have the CIC lock. 

                                 _______   _______
                                 |      \_/      |
  (To FNS CIC Pin 2) Data Out <- | 1          18 | -- +5Vcc
 (From FNS CIC Pin 1) Data In -> | 2  O       17 | -- n/c
                          n/c -- | 3   8634A  16 | ?? GND
                          n/c -- | 4          15 | -- n/c
                          n/c -- | 5    CIC   14 | -- n/c
                          n/c -- | 6   Lock   13 | ?? +5V
                        Clock -> | 7          12 | ?? Card-33, n/c in Famicom Network System
           (Cap to 5V) +Reset -> | 8          11 | -> CIC Key +Reset (To FNS CIC Pin 8)
                          GND -- | 9          10 | -- n/c
                                 |_______________|
  • +Reset is connected with a ceramic capacitor to 5V. This gives a momentary positive pulse at power-on.
  • The clock is 3.58 MHz, coming from RF5C66 pin 26.
  • Note: Some assumptions made on CIC chips based on similarity to F411A from Super NES.

8kByte CHR RAM

                   _______   _______
                   |      \_/      |
           n/c? -- | 1          28 | -- +5Vcc
        PPU A12 -> | 2  O       27 | <- PPU /WR
         PPU A7 -> | 3          26 | <- +CE: U3=RF5C66 34/38, U4=PPU /A13
         PPU A6 -> | 4          25 | <- PPU A8
         PPU A5 -> | 5  LH5268  24 | <- PPU A9
         PPU A4 -> | 6    CHR   23 | <- PPU A11
         PPU A3 -> | 7    RAM   22 | <- /OE: PPU /RD
         PPU A2 -> | 8   U3/U4  21 | <- PPU A10
         PPU A1 -> | 9          20 | <- /CE: U3=PPU A13, U4=RF5C66 34/38
         PPU A0 -> | 10         19 | <> PPU D7
         PPU D0 <> | 11         18 | <> PPU D6
         PPU D1 <> | 12         17 | <> PPU D5
         PPU D2 <> | 13         16 | <> PPU D4
            GND -- | 14         15 | <> PPU D3
                   |_______________|

8kByte W-RAM

                   _______   _______
                   |      \_/      |
           n/c? -- | 1          28 | -- +5Vcc
        CPU A12 -> | 2  O       27 | <- /WR: Card R/W (P6-2 Lid Switch)
         CPU A7 -> | 3          26 | <- +CE: RAM +CE
         CPU A6 -> | 4          25 | <- CPU A8
         CPU A5 -> | 5  LH5268  24 | <- CPU A9
         CPU A4 -> | 6 Built-in 23 | <- CPU A11
         CPU A3 -> | 7  W-RAM   22 | <- /OE: GND
         CPU A2 -> | 8    U5    21 | <- Card A10
         CPU A1 -> | 9          20 | <- /CE: Built-in RAM /CE
         CPU A0 -> | 10         19 | <> Card D7
        Card D0 <> | 11         18 | <> Card D6
        Card D1 <> | 12         17 | <> Card D5
        Card D2 <> | 13         16 | <> Card D4
            GND -- | 14         15 | <> Card D3
                   |_______________|

8kByte CPU2 RAM

                   _______   _______
                   |      \_/      |
           n/c? -- | 1          28 | -- +5Vcc
       CPU2 A12 -> | 2  O       27 | <- /WR: CPU2 R/W
        CPU2 A7 -> | 3          26 | <- +CE: +5Vcc
        CPU2 A6 -> | 4          25 | <- CPU2 A8
        CPU2 A5 -> | 5  LH5268  24 | <- CPU2 A9
        CPU2 A4 -> | 6   CPU2   23 | <- CPU2 A11
        CPU2 A3 -> | 7    RAM   22 | <- /OE: GND
        CPU2 A2 -> | 8    U6    21 | <- CPU2 A10
        CPU2 A1 -> | 9          20 | <- /CE: CPU2 RAM /CE
        CPU2 A0 -> | 10         19 | <> CPU2 D7
        CPU2 D0 <> | 11         18 | <> CPU2 D6
        CPU2 D1 <> | 12         17 | <> CPU2 D5
        CPU2 D2 <> | 13         16 | <> CPU2 D4
            GND -- | 14         15 | <> CPU2 D3
                   |_______________|

P4: Modem Module Edge Connector

       Famicom     | Modem  |    Famicom
    Network System | Module | Network System
                   __________
                   |        |
          +5Vcc -- | 1   19 | <- 5A18-63
MSM6827L +Reset -> | 2   20 | <- Tone Rx GT
   MSM6827L AD0 <> | 3   21 | <- /Phone Audio Enable
            GND -- | 4   22 | -> Tone Rx DV
   MSM6827L AD1 <> | 5   23 | -> 5A18-55, Audio from phone line
   MSM6827L RXD <- | 6   24 | <- Tone Rx Xin, from 5C66-26
  MSM6827L DATA <- | 7   25 | -> 5A18-53
   MSM6827L TXD -> | 8   26 | -- GND
   MSM6827L /WR -> | 9   27 | <- /Phone Off Hook
 MSM6827L EXCLK -> | 10  28 | -> 5A18-54
   MSM6827L /RD -> | 11  29 | <> 5C66-60
          +5Vcc -- | 12  30 | <- /DTMF Output Enable
     Tone Rx D1 <- | 13  31 | <> 5C66-62           __________________________
  MSM6827L /INT <- | 14  32 | <> 5C66-61           | Modem Module           |
          +5Vcc -- | 15  33 | <- Audio from 2A03   | Orientation            |
     Tone Rx D2 <- | 16  34 | -> Audio to RF       |                        |
     Tone Rx D8 <- | 17  35 | -- GND               |    19 _____________ 36 |
     Tone Rx D4 <- | 18  36 | -- GND               |     1 |___________| 18 |
                   |________|                      |________________________|
 
Note: The modem module uses modem chip Oki MSM6827L and Dual Tone Receiver MC14LC5436P.

P2: Tsuushin Card Connector

Note that the tsuushin card may appear to have a metric 1mm pin pitch, but in fact it has an imperial 0.040" (40 thousandths) pin pitch. 

Card |  | Famicom Network System
-----+--+-------------------------
  1  |--| +5Vcc
  2  |--| +5Vcc
  3  |??| n/c in JRA-PAT card, n/c in FNS
  4  |??| n/c in JRA-PAT card, FNS has 10k pull-up only.
  5  |<>| Card D0
  6  |<>| Card D1
  7  |<>| Card D2
  8  |<>| Card D3
  9  |<>| Card D4
 10  |<>| Card D5
 11  |<>| Card D6
 12  |<>| Card D7
 13  |<-| Card R/W (P6-2 Lid Switch)
 14  |<-| M2
 15  |<-| /ROMSEL
 16  |<-| CPU A0
 17  |<-| CPU A1
 18  |<-| CPU A2
 19  |<-| CPU A3
 20  |<-| CPU A4
 21  |<-| CPU A5
     |  |
     |  |
 22  |<-| CPU A6
 23  |<-| CPU A7
 24  |<-| CPU A8
 25  |<-| CPU A9
 26  |<-| CPU A10
 27  |<-| CPU A11
 28  |<-| CPU A12
 29  |<-| CPU A13
 30  |<-| CPU A14
 31  |??| n/c in JRA-PAT card, FNS has 10k pull-up only.
 32  |??| n/c in JRA-PAT card, FNS has 10k pull-up only.
 33  |??| connected to Card Lock CIC-12 in JRA-PAT, n/c in FNS
 34  |??| n/c in JRA-PAT card, n/c in FNS
 35  |->| CIC Key Reset (Card Lock CIC-11 -> FNS Key CIC-8)
 36  |->| CIC Lock-to-Key Data (Card Lock CIC-1 -> FNS Key CIC-2)
 37  |<-| CIC Key-to-Lock Data (Card Lock CIC-2 <- FNS Key CIC-1)
 38  |<-| CIC Clock (3.58 MHz, from 5C66.26)
 39  |??| n/c in JRA-PAT card, FNS has 10k pull-up only.
 40  |<-| RAM +CE (n/c in JRA-PAT card)
 41  |--| GND
 42  |--| GND

P3: Expansion Connector

                 Outside    |  FNS  |    Outside                   _____________________
                            _________                             / Orientation        /|
                            |       |                            /____________________/ |
                    /IRQ -> | 1  20 | -- +5Vcc                   |o|_| ==      |_||_|o|/
(95.94kHz Clock) 5C66-79 <- | 2  19 | -> 5A18-67                 \_  _  _ _||_  _  _ _/|
                 5C66-78 -> | 3  18 | -> 5A18-66                  |-| |    || HVC-050| |
                 5C66-77 <- | 4  17 | -> 5A18-65                  |-|_|    ||        | |
                 5C66-76 <- | 5  16 | -> 5A18-42 (4.92MHz Clock)  |        ||        | |
                 5C66-75 <- | 6  15 | <> 5C66-64                  |  20 __/__\__ 11  | |
                            |       |                             |o  1 |______| 10 o| |
                 5C66-74 -> | 7  14 | <> 5C66-65                  | ________________ | |
                 5C66-73 -> | 8  13 | <> 5C66-66                  |/_______________/|| |
                 5C66-72 -> | 9  12 | <> 5C66-67                  ||______________|/ | |
                     GND -- | 10 11 | <- 5C66-71                  |                  | |
                            |_______|                             |      ______      | |
                                                                  |o    | |    |    o| |
                                                                  \_____|/     |_____|/

P5: Expansion Connector

Note: This connector only exists on old revisions of Famicom Network System. Expansion P5 /CE is activated low specifically at CPU2 address $4129. 

Outside |  | Famicom Network System
--------+--+-------------------------
    9   |--| GND
    8   |<>| CPU2 D5
    7   |<>| CPU2 D4
    6   |<>| CPU2 D3
    5   |<>| CPU2 D2
    4   |<>| CPU2 D1
    3   |<>| CPU2 D0
    2   |<-| Expansion P5 /CE
    1   |--| +5V

See Also

Retrieved from "https://www.nesdev.org/w/index.php?title=Famicom_Network_System&oldid=21863"