SiS600 Pentium II PCI /A.G.P. Chipset
Preliminary V1.0 Jan. 25, 1999
35
Silicon Integrated Systems Corporation
INITIALIZATION
When ECC is enabled, the whole DRAM modules must be first initialized by doing writes before the DRAM read
operations to establish the correlation between 64-bit data and associated 8-bit ECC code which does not exist
after power-on.
ECC DETECTION AND CORRECTION
During DRAM read operations, the full Qword of data and the associated ECC code are transferred
simultaneously from DRAM to the SiS600. If there is a single-bit error in the 72-bit signals (64-bit data plus 8-bit
code), the ECC mechanism will automatically recover the correct 64-bit data. Note that the recovered data is
transferred to the requesting master (Host, PCI, or AGP interface), but the DRAM controller does not initiate a
DRAM write cycle to fix the single-bit error in DRAM.
If the ECC mechanism detects a two-bit error, SiS600 can report this error by SERR# or record it on the Error
Status Register optionally.
ECC GENERATION
During DRAM write operations, SiS600 automatically generates an 8-bit ECC code for the 64-bit data. If the
requested write operation transfers single or multiple Qword of data, the ECC DRAM write can be completed
without any overhead. If the write request only transfers less than 64 bits of data, the DRAM controller performs
a read-merge-write operation.
5.3.
PCI BRIDGE
The PCI bridge of SiS600 consists of three parts: PCI arbiter, PCI master bridge and PCI target bridge. The PCI
arbiter controls the assignment of PCI bus ownership among all PCI masters. The PCI master bridge forwards the
transactions from host bus. The PCI target bridge claims PCI cycles toward system memory or AGP bus as
required by PCI master devices.
5.3.1.
PCI ARBITER
The main function of PCI arbiter takes charge of the PCI bus ownership assignment. This PCI arbiter supports at
most 4 external PCI masters using standard PCI REQ#/GNT# mechanism and 1 PCI master using
PHOLD#/PHLDA# mechanism. The master that uses PHOLD#/PHLDA mechanism is not pre-emptive. That
means the master can own the bus as long as it wishes after it gains the control of PCI bus. The master that use
PHOLD#/PHLDA# mechanism to access PCI bus is typically SiS5595 chip.
Arbitration Algorithm
PCI Masters (Agent 0~6, SIO) Requests
Figure6.4-1 Arbitration Tree shows the arbitration tree in arbiter design. Whenever a PCI cycle occurs, priority
status will be changed. The initial priority for master 0-7 to own PCI bus is 4 -> 0->SIO->2->5->1->6->3->4...