Processor Data Bus at Frequencies up
to 66 MHz (82433LX and 82433NX)
Y
Drives 3.3V Signal Levels on the CPU
Data and Address Buses (82433NX)
Y
Provides a 64-Bit Interface to DRAM
and a 32-Bit Interface to PCI
Y
Five Integrated Write Posting and Read
Prefetch Buffers Increase CPU and PCI
Performance
Ð CPU-to-Memory Posted Write Buffer
4 Qwords Deep
Ð PCI-to-Memory Posted Write Buffer
Two Buffers, 4 Dwords Each
Ð PCI-to-Memory Read Prefetch Buffer
4 Qwords Deep
Ð CPU-to-PCI Posted Write Buffer
4 Dwords Deep
Ð CPU-to-PCI Read Prefetch Buffer
4 Dwords Deep
Y
CPU-to-Memory and CPU-to-PCI Write
Posting Buffers Accelerate Write
Performance
Two 82433LX or 82433NX Local Bus Accelerator (LBX) components provide a 64-bit data path between the
host CPU/Cache and main memory, a 32-bit data path between the host CPU bus and PCI Local Bus, and a
32-bit data path between the PCI Local Bus and main memory. The dual-port architecture allows concurrent
operations on the host and PCI Buses. The LBXs incorporate three write posting buffers and two read prefetch
buffers to increase CPU and PCI performance. The LBX supports byte parity for the host and main memory
buses. The 82433NX is intended to be used with the 82434NX PCI/Cache/Memory Controller (PCMC). The
82433LX is intended to be used with the 82434LX PCMC. During bus operations between the host, main
memory and PCI, the PCMC commands the LBXs to perform functions such as latching address and data,
merging data, and enabling output buffers. Together, these three components form a ‘‘Host Bridge’’ that
provides a full function dual-port data path interface, linking the host CPU and PCI bus to main memory.
This document describes both the 82433LX and 82433NX. Shaded areas, like this one, describe the
82433NX operations that differ from the 82433LX.
Y
Dual-Port Architecture Allows
Concurrent Operations on the Host and
PCI Buses
Y
Operates Synchronously to the CPU
and PCI Clocks
Y
Supports Burst Read and Writes of
Memory from the Host and PCI Buses
Y
Sequential CPU Writes to PCI
Converted to Zero Wait-State PCI
Bursts with Optional TRDY
Ý
Connection
Y
Byte Parity Support for the Host and
Memory Buses
Ð Optional Parity Generation for Host
to Memory Transfers
Ð Optional Parity Checking for the
Secondary Cache
Ð Parity Checking for Host and PCI
Memory Reads
Ð Parity Generation for PCI to Memory
Writes
Y
160-Pin QFP Package
December 1995Order Number: 290478-004
82433LX/82433NX
290478– 1
LBX Simplified Block Diagram
2
82433LX/82433NX
LOCAL BUS ACCELERATOR (LBX)
CONTENTSPAGE
1.0 ARCHITECTURAL OVERVIEW
1.1 Buffers in the LBX АААААААААААААААААААААААААААААААААААААААААААААААААААААААААААААААААААААА 5
1.2 Control Interface Groups ААААААААААААААААААААААААААААААААААААААААААААААААААААААААААААААА 7
1.3 System Bus Interconnect ААААААААААААААААААААААААААААААААААААААААААААААААААААААААААААААА 7
6.1 NAND Tree ААААААААААААААААААААААААААААААААААААААААААААААААААААААААААААААААААААААААААА 51
6.1.1 TEST VECTOR TABLE ААААААААААААААААААААААААААААААААААААААААААААААААААААААААААА 51
6.1.2 NAND TREE TABLE АААААААААААААААААААААААААААААААААААААААААААААААААААААААААААААА 51
6.2 PLL Test Mode АААААААААААААААААААААААААААААААААААААААААААААААААААААААААААААААААААААААА 53
4
82433LX/82433NX
1.0 ARCHITECTURAL OVERVIEW
The 82430 PCIset consists of the 82434LX PCMC
and 82433LX LBX components plus either a PCI/
ISA bridge or a PCI/EISA bridge. The 82430NX PCIset consists of the 82434NX PCMC and 82433NX
LBX components plus either a PCI/ISA bridge or a
PCI/EISA bridge. The PCMC and LBX provide the
core cache and main memory architecture and
serves as the Host/PCI bridge. An overview of the
PCMC follows the system overview section.
The Local Bus Accelerator (LBX) provides a high
performance data and address path for the
82430LX/82430NX PCIset. The LBX incorporates
five integrated buffers to increase the performance
of the Pentium processor and PCI master devices.
Two LBXs in the system support the following areas:
1. 64-bit data and 32-bit address bus of the Pentium
processor.
2. 32-bit multiplexed address/data bus of PCI.
3. 64-bit data bus of the main memory.
In addition, the LBXs provide parity support for the
three areas noted above (discussed further in Section 1.4).
1.1 Buffers in the LBX
The LBX components have five integrated buffers
designed to increase the performance of the Host
and PCI Interfaces of the 82430LX/82430NX
PCIset.
With the exception of the PCI-to-Memory write buffer
and the CPU-to-PCI write buffer, the buffers in the
LBX store data only, addresses are stored in the
PCMC component.
5
82433LX/82433NX
290478– 2
NOTES:
1. CPU-to-Memory Posted Write Buffer: This buffer is 4 Qwords deep, enabling the Pentium processor to write back a
whole cache line in 4-1-1-1 timing, a total of 7 CPU clocks.
2. PCI-to-Memory Posted Write Buffer: A PCI master can post two consecutive sets of 4 Dwords (total of one cache
line) or two single non-consecutive transactions.
3. PCI-to-Memory Read Prefetch Buffer: A PCI master to memory read transaction will cause this prefetch buffer to
read up to 4 Qwords of data from memory, allowing up to 8 Dwords to be read onto PCI in a single burst transaction.
4. CPU-to-PCI Posted Write Buffer: The Pentium processor can post up to 4 Dwords into this buffer. The TRDY
connect option allows zero-wait state burst writes to PCI, making this buffer especially useful for graphic write
operations.
5. CPU-to-PCI Read Prefetch Buffer: This prefetch buffer is 4 Dwords deep, enabling faster sequential Pentium processor reads when targeting PCI.
Figure 1. Simplified Block Diagram of the LBX Data Buffers
6
Ý
82433LX/82433NX
1.2 Control Interface Groups
The LBX is controlled by the PCMC via the control
interface group signals. There are three interface
groups: Host, Memory, and PCI. These control
groups are signal lines that carry binary codes which
the LBX internally decodes in order to implement
specific functions such as latching data and steering
data from PCI to memory. The control interfaces are
described below.
1. Host Interface Group: These control signals are
named HIG[4:0]and define a total of 29 (30 for
the 82433NX) discrete commands. The PCMC
sends HIG commands to direct the LBX to perform functions related to buffering and storing
host data and/or address.
2. Memory Interface Group: These control signals
are named MIG[2:0]and define a total of 7 discrete commands. The PCMC sends MIG commands to direct the LBX to perform functions related to buffering, storing, and retiring data to
memory.
3. PCI Interface Group: These control signals are
named PIG[3:0]and define a total of 15 discrete
commands. The PCMC sends PIG commands to
direct the LBX to perform functions related to
buffering and storing PCI data and/or address.
1.3 System Bus Interconnect
The architecture of the 82430/82430NX PCIset
splits the 64-bit memory and host data buses into
logical halves in order to manufacture LBX devices
with manageable pin counts. The two LBXs interface
to the 32-bit PCI AD[31:0]bus with 16 bits each.
Each LBX connects to 16 bits of the AD[31:0]bus
and 32-bits of both the MD[0:63]bus and the
D[0:63]bus. The lower order LBX (LBXL) connects
to the low word of the AD[31:0]bus, while the high
order LBX (LBXH) connects to the high word of the
AD[31:0]bus.
Since the PCI connection for each LBX falls on
16-bit boundaries, each LBX does not simply connect to either the low Dword or high Dword of the
Qword memory and host buses. Instead, the low order LBX buffers the first and third words of each
64-bit bus while the high order LBX buffers the second and fourth words of the memory and host
buses.
As shown in Figure 2, LBXL connects to the first and
third words of the 64-bit main memory and host data
buses. The same device also drives the first 16 bits
of the host address bus, A[15:0]. The LBXH device
connects to the second and fourth words of the
64-bit main memory and host data buses. Correspondingly, LBXH drives the remaining 16 bits of the
host address bus, A[31:16].
Figure 2. Simplified Interconnect Diagram of LBXs to System Buses
290478– 3
7
82433LX/82433NX
1.4 PCI TRDYÝInterface
The PCI control signals do not interface to the LBXs,
instead these signals connect to the 82434LX
PCMC component. The main function of the LBXs
PCI interface is to drive address and data onto PCI
when the CPU targets PCI and to latch address and
data when a PCI master targets main memory.
The TRDY
Ý
option provides the capability for zerowait state performance on PCI when the Pentium
processor performs sequential writes to PCI. This
option requires that PCI TRDY
Ý
be connected to
each LBX, for a total of two additional connections in
the system. These two TRDY
addition to the single TRDY
Ý
connections are in
Ý
connection that the
PCMC requires.
1.5 Parity Support
The LBXs support byte parity on the host bus (CPU
and second level cache) and main memory buses
(local DRAM). The LBXs support parity during the
address and data phases of PCI transactions to/
from the host bridge.
2.0 SIGNAL DESCRIPTIONS
This section provides a detailed description of each
signal. The signals (Figure 3) are arranged in functional groups according to their associated interface.
Ý
The ‘
’ symbol at the end of a signal name indicates
that the active, or asserted state occurs when the
signal is at a low voltage level. When ‘
ent after the signal name, the signal is asserted
when at the high voltage level.
The terms assertion and negation are used extensively. This is done to avoid confusion when working
with a mixture of ‘active-low’ and ‘active-high’ signals. The term assert,orassertion indicates that a
signal is active, independent of whether that level is
represented by a high or low voltage. The term ne-gate,ornegation indicates that a signal is inactive.
The following notations are used to describe the signal type.
inInput is a standard input-only signal.
out Totem Pole output is a standard active driver.
t/sTri-State is a bi-directional, tri-state input/out-
put pin.
Ý
’ is not pres-
290478– 4
Figure 3. LBX Signals
8
82433LX/82433NX
2.1 Host Interface Signals
SignalTypeDescription
A[15:0]t/sADDRESS BUS: The bi-directional A[15:0]lines are connected to the address lines of the
D[31:0]t/sHOST DATA: The bi-directional D[31:0]lines are connected to the data lines of the host
HP[3:0]t/sHOST DATA PARITY: HP[3:0]are the bi-directional byte parity signals for the host data
host bus. The high order LBX (determined at reset time using the EOL signal) is
connected to A[31:16], and the low order LBX is connected to A[15:0]. The host address
bus is common with the Pentium processor, second level cache, PCMC and the two
LBXs. During CPU cycles A[31:3]are driven by the CPU and A[2:0]are driven by the
PCMC, all are inputs to the LBXs. During inquire cycles the LBX drives the PCI master
address onto the host address lines A[31:0]. This snoop address is driven to the CPU and
the PCMC by the LBXs to snoop L1 and the integrated second level tags, respectively.
During PCI configuration cycles bound for the PCMC, the LBXs will send or receive the
configuration data to/from the PCMC by copying the host data bus to/from the host
address bus. The LBX drives both halves of the Qword host data bus with data from the
32-bit address during PCMC configuration read cycles. The LBX drives the 32-bit address
with either the low Dword or the high Dword during PCMC configuration write cycles.
In the 82433NX, these pins contain weak internal pull-down resistors.
The high order 82433NX LBX samples A11 at the falling edge of reset to configure the
LBX for PLL test mode. When A11 is sampled low, the LBX is in normal operating mode.
When A11 is sampled high, the LBX drives the internal HCLK from the PLL on the EOL
pin. Note that A11 on the high order LBX is connected to the A27 line on the CPU address
bus. This same address line is used to put the PCMC into PLL test mode.
data bus. The high order LBX (determined at reset time using the EOL signal) is
connected to the host data bus D[63:48]and D[31:16]lines, and the low order LBX is
connected to the host data bus D[47:32]and D[15:0]lines. In the 82433LX, these pins
contain weak internal pull-up resistors.
In the 82433NX, these pins contain weak internal pull-down resistors.
bus. The low order parity bit HP[0]corresponds to D[7:0]while the high order parity bit
HP[3]corresponds to D[31:24]. The HP[3:0
cycles and as parity outputs during read cycles. Even parity is supported and the HP[3:0
signals follow the same timings as D[31:0
internal pull-up resistors.
In the 82433NX, these pins contain weak internal pull-down resistors.
]
signals function as parity inputs during write
]
. In the 82433LX, these pins contain weak
]
9
82433LX/82433NX
2.2 Main Memory (Dram) Interface Signals
SignalTypeDescription
MD[31:0]t/sMEMORY DATA BUS: MD[31:0]are the bi-directional data lines for the memory data
MP[3:0]t/sMEMORY PARITY: MP[3:0]are the bi-directional byte enable parity signals for the
bus. The high order LBX (determined at reset time using the EOL signal) is connected to
the memory data bus MD[63:48]and MD[31:16]lines, and the low order LBX is
connected to the memory data bus MD[47:32]and MD[15:0]lines. The MD[31:0
signals drive data destined for either the host data bus or the PCI bus. The MD[31:0
signals input data that originated from either the host data bus or the PCI bus. These
pins contain weak internal pull-up resistors.
memory data bus. The low order parity bit MP[0]corresponds to MD[7:0]while the high
order parity bit MP[3]corresponds to MD[31:24]. The MP[3:0]signals are parity outputs
during write cycles to memory and parity inputs during read cycles from memory. Even
parity is supported and the MP[3:0]signals follow the same timings as MD[31:0]. These
pins contain weak internal pull-up resistors.
2.3 PCI Interface Signals
SignalTypeDescription
AD[15:0]t/sADDRESS AND DATA: AD[15:0]are bi-directional data lines for the PCI bus. The
Ý
TRDY
AD[15:0]signals sample or drive the address and data on the PCI bus. The high order
LBX (determined at reset time using the EOL signal) is connected to the PCI bus
AD[31:16]lines, and the low order LBX is connected to the PCI AD[15:0]lines.
inTARGET READY: TRDYÝindicates the selected (targeted) device’s ability to complete
the current data phase of the bus operation. For normal operation, TRDYÝis tied
asserted low. When the TRDY
burst writes), TRDY
Ý
Ý
should be connected to the PCI bus.
option is enabled in the PCMC (for zero wait-state PCI
]
]
2.4 PCMC Interface Signals
SignalTypeDescription
HIG[4:0]inHOST INTERFACE GROUP: These signals are driven from the PCMC and control the
MIG[2:0]inMEMORY INTERFACE GROUP: These signals are driven from the PCMC and control
PIG[3:0]inPCI INTERFACE GROUP: These signals are driven from the PCMC and control the PCI
MDLEinMEMORY DATA LATCH ENABLE: During CPU reads from DRAM, the LBX uses a
DRVPCIinDRIVE PCI BUS: This signals enables the LBX to drive either address or data
10
host interface of the LBX. The 82433LX decodes the binary pattern of these lines to
perform 29 unique functions (30 for the 83433NX). These signals are synchronous to the
rising edge of HCLK.
the memory interface of the LBX. The LBX decodes the binary pattern of these lines to
perform 7 unique functions. These signals are synchronous to the rising edge of HCLK.
interface of the LBX. The LBX decodes the binary pattern of these lines to perform 15
unique functions. These signals are synchronous to the rising edge of HCLK.
clocked register to transfer data from the MD[31:0]and MP[3:0]lines to the D[31:0]and
HP[3:0]lines. MDLE is the clock enable for this register. Data is clocked into this register
when MDLE is asserted. The register retains its current value when MDLE is negated.
During CPU reads from main memory, the LBX tri-states the D[31:0]and HP[3:0]lines
on the rising edge of MDLE when HIG[4:0
information onto the PCI AD[15:0]lines.
e
]
NOPC.
82433LX/82433NX
2.4 PCMC Interface Signals (Continued)
SignalTypeDescription
EOLt/sEnd Of Line: This signal is asserted when a PCI master read or write transaction is about
PPOUT t/sLBX PARITY: This signal reflects the parity of the 16 AD lines driven from or latched into
to overrun a cache line boundary. The low order LBX will have this pin connected to the
PCMC (internally pulled up in the PCMC). The high order LBX connects this pin to a pulldown resistor. With one LBX EOL line being pulled down and the other LBX EOL pulled
up, the LBX samples the value of this pin on the negation of the RESET signal to
determine if it’s the high or low order LBX.
the LBX, depending on the command driven on PIG[3:0]. The PCMC uses PPOUT from
both LBXs (called PPOUT[1:0]) to calculate the PCI parity signal (PAR) for CPU to PCI
transactions during the address phase of the PCI cycle. The LBX uses PPOUT to check
the PAR signal for PCI master transactions to memory during the address phase of the
PCI cycle. When transmitting data to PCI the PCMC uses PPOUT to calculate the proper
value for PAR. When receiving data from PCI the PCMC uses PPOUT to check the value
received on PAR.
If the L2 cache does not implement parity, the LBX will calculate parity so the PCMC can
drive the correct value on PAR during L2 reads initiated by a PCI master. The LBX
samples the PPOUT signal at the negation of reset and compares that state with the state
of EOL to determine whether the L2 cache implements parity. The PCMC internally pulls
down PPOUT[0]and internally pulls up PPOUT[1]. The L2 supports parity if PPOUT[0]is
connected to the high order LBX and PPOUT[1]is connected to the low order LBX. The
L2 is defined to not support parity if these connections are reversed, and for this case, the
LBX will calculate parity. For normal operations either connection allows proper parity to
be driven to the PCMC.
2.5 Reset and Clock Signals
SignalTypeDescription
HCLKinHOST CLOCK: HCLK is input to the LBX to synchronize command and data from the host
PCLKinPCI CLOCK: All timing on the LBX PCI interface is referenced to the PCLK input. All
RESETinRESET: Assertion of this signal resets the LBX. After RESET has been negated the LBX
LP1outLOOP 1: Phase Lock Loop Filter pin. The filter components required for the LBX are
LP2inLOOP 2: Phase Lock Loop Filter pin. The filter components required for the LBX are
TESTinTEST: The TEST pin must be tied low for normal system operation.
TSCON inTRI-STATE CONTROL: This signal enables the output buffers on the LBX. This pin must
and memory interfaces. This input is derived from a buffered copy of the PCMC HCLKx
output.
output signals on the PCI interface are driven from PCLK rising edges and all input signals
on the PCI interface are sampled on PCLK rising edges. This input is derived from a
buffered copy of the PCMC PCLK output.
configures itself by sampling the EOL and PPOUT pins. RESET is driven by the PCMC
CPURST pin. The RESET signal is synchronous to HCLK and must be driven directly by
the PCMC.
connected to these pins.
connected to these pins.
be held high for normal operation. If TSCON is negated, all LBX outputs will tri-state.
11
82433LX/82433NX
3.0 FUNCTIONAL DESCRIPTION
3.1 LBX Post and Prefetch Buffers
This section describes the five write posting and
read prefetching buffers implemented in the LBX.
The discussion in this section refers to the operation
of both LBXs in the system.
3.1.1 CPU-TO-MEMORY POSTED WRITE
BUFFER
The write buffer is a queue 4 Qwords deep, it loads
Qwords from the CPU and stores Qwords to memory. It is 4 Qwords deep to accommodate write-backs
from the first or second level cache. It is organized
as a simple FIFO. Commands driven on the HIG[4:0
lines store Qwords into the buffer, while commands
on the MIG[2:0]lines retire Qwords from the buffer.
While retiring Qwords to memory, the DRAM controller unit of the PCMC will assert the appropriate MA,
]
CAS[7:0
track of full/empty states, status of the data and
address.
Byte parity for data to be written to memory is either
propagated from the host bus or generated by the
LBX. The LBX generates parity for data from the
second level cache when the second level cache
does not implement parity.
3.1.2 PCI-TO-MEMORY POSTED WRITE BUFFER
The buffer is organized as 2 buffers (4 Dwords
each). There is an address storage register for each
buffer. When an address is stored one of the two
buffers is allocated and subsequent Dwords of data
are stored beginning at the first location in that buffer. Buffers are retired to memory strictly in order,
Qword at a time.
Commands driven on the PIG[3:0]lines post addresses and data into the buffer. Commands driven
on HIG[4:0]result in addresses being driven on the
host address bus. Commands driven on MIG[2:0
result in data being retired to DRAM.
For cases where the address targeted by the first
Dword is odd, i.e. A[2
an even location in the buffer, the LBX correctly
aligns the Dword when retiring the data to DRAM. In
other words the buffer is capable of retiring a Qword
to memory where the data in the buffer is shifted by
Ý
, and WEÝsignals. The PCMC keeps
e
]
1, and the data is stored in
1 Dword (Dword is position 0 shifted to 1, 1 shifted
to 2 etc.). The DRAM controller of the PCMC asserts
the correct CAS[7:0
C/BE[3:0
Dword.
The End Of Line (EOL) signal is used to prevent PCI
master writes from bursting past the cache line
boundary. The device that provides ‘‘warning’’ to the
PCMC is the low order LBX. This device contains the
PCI master write low order address bits necessary to
determine how many Dwords are left to the end of
the line. Consequently, the LBX protocol uses the
EOL signal from the low order LBX to provide this
‘‘end-of-line’’ warning to the PCMC, so that it may
retry a PCI master write when it bursts past the
cache line boundary. This protocol is described fully
in Section 3.3.6.
]
The LBX calculates Dword parity on PCI write data,
sending the proper value to the PCMC on PPOUT.
The LBX generates byte parity on the MP signals for
writing into DRAM.
3.1.3 PCI-TO-MEMORY READ PREFETCH
This buffer is organized as a line buffer (4 Qwords)
for burst transfers to PCI. The data is transferred into
the buffer a Qword at a time and read out a Dword at
a time. The LBX then effectively decouples the
memory read rate from the PCI rate to increase concurrence.
Each new transaction begins by storing the first
Dword in the first location in the buffer. The starting
Dword for reading data out of the buffer onto PCI
must be specified within a Qword boundary; that is
the first requested Dword on PCI could be an even
or odd Dword. If the snoop for a PCI master read
results in a write-back from first or second level
caches, this write back is sent directly to PCI and
main memory. The following two paragraphs describe this process for cache line write-backs.
Since the write-back data from L1 is in linear order,
]
writing into the buffer is straightforward. Only those
Qwords to be transferred into PCI are latched into
the PCI-to-memory read buffer. For example, if the
address targeted by PCI is in the 3rd or 4th Qword in
the line, the first 2 Qwords of write back data are
discarded and not written into the read buffer. The
primary cache write-back must always be written
Ý
]
BUFFER
Ý
]
signals stored in the PCMC for that
signals depending on the PCI
12
82433LX/82433NX
completely to the CPU-to-Memory posted Write
Buffer.
If the PCI master read data is read from the secondary cache, it is not written back to memory. Writebacks from the second level cache, when using
burst SRAMs, are in Pentium processor burst order
(the order depending on which Qword of the line is
targeted by the PCI read). The buffer is directly addressed when latching second level cache writeback data to accommodate this burst order. For example, if the requested Qword is Qword 1, then the
burst order is 1-0-3-2. Qword 1 is latched in buffer
location 0, Qword 0 is discarded, Qword 3 is latched
into buffer location 2 and Qword 2 is latched into
buffer location 1.
Commands driven on MIG[2:0]and HIG[4:0]enter
data into the buffer from the DRAM interface and the
host interface (i.e. the caches), respectively. Commands driven on the PIG[3:0]lines drive data from
the buffer onto the PCI AD[31:0]lines.
Parity driven on the PPOUT signal is calculated from
the byte parity received on the host bus or the memory bus, whichever is the source. If the second level
cache is the source of the data and does not implement parity, the parity driven on PPOUT is generated
by the LBX from the second level cache data. If
main memory is the source of the read data, PCI
parity is calculated from the DRAM byte parity. Main
memory must implement byte parity to guarantee
correct PCI parity generation.
3.1.4 CPU-TO-PCI POSTED WRITE BUFFER
The CPU-to-PCI Posted Write Buffer is 4 Dwords
deep. The buffer is constructed as a simple FIFO,
with some performance enhancements. An address
is stored in the LBX with each Dword of data. The
structure of the buffer accommodates the packetization of writes to be burst on PCI. This is accomplished by effectively discarding addresses of data
Dwords driven within a burst. Thus, while an address
is stored for each Dword, an address is not necessarily driven on PCI for each Dword. The PCMC determines when a burst write may be performed
based on consecutive addresses. The buffer also
enables consecutive bytes to be merged within a
single Dword, accommodating byte, word, and misaligned Dword string store and string move operations. Qword writes on the host bus are stored within
the buffer as two individual Dword writes, with separate addresses.
The storing of an address with each Dword of data
allows burst writes to be retried easily. In order to
retry transactions, the FIFO is effectively ‘‘backed
up’’ by one Dword. This is accomplished by making
the FIFO physically one entry larger than it is logically. Thus, the buffer is physically 5 entries deep (an
entry consists of an address and a Dword of data),
while logically it is considered full when 4 entries
have been posted. This design allows the FIFO to
be backed up one entry when it is logically full.
Commands driven on HIG[4:0]post addresses and
data into the buffer, and commands driven on
PIG[3:0]retire addresses and data from the buffer
and drive them onto the PCI AD[31:0]lines. As discussed previously, when bursting, not all addresses
are driven onto PCI.
Data parity driven on the PPOUT signal is calculated
from the byte parity received on the host bus. Address parity driven on PPOUT is calculated from the
address received on the host bus.
13
82433LX/82433NX
3.1.5 CPU-TO-PCI READ PREFETCH BUFFER
This prefetch buffer is organized as a single buffer
4 Dwords deep. The buffer is organized as a simple
FIFO. reads from the buffer are sequential; the buffer does not support random access of its contents.
To support reads of less than a Dword the FIFO
read pointer can function with or without a pre-increment. The pointer can also be reset to the first entry
before a Dword is driven. When a Dword is read, it is
driven onto both halves of the host data bus.
Commands driven on the HIG[4:0]lines enable read
addresses to be sent onto PCI, the addresses are
driven using PIG[3:0]commands. Read data is
latched into the LBX by commands driven on the
PIG[3:0]lines and the data is driven onto the host
data bus using commands driven on the HIG[4:0
lines.
The LBX calculates Dword parity on PCI read data,
sending the proper value to the PCMC on PPOUT.
The LBX does not generate byte parity on the host
data bus when the CPU reads PCI.
3.2 LBX Interface Command
Descriptions
This section describes the functionality of the HIG,
MIG and PIG commands driven by the PCMC to the
LBXs.
3.2.1 HOST INTERFACE GROUP: HIG[4:0
The Host Interface commands are shown in Table 1.
These commands are issued by the host interface of
the PCMC to the LBXs in order to perform the following functions:
Reads from CPU-to-PCI read prefetch buffer
#
when the CPU reads from PCI.
Stores write-back data to PCI-to-memory read
#
]
prefetch buffer when PCI read address results in
a hit to a modified line in first or second level
caches.
Posts data to CPU-to-memory write buffer in the
#
case of a CPU to memory write.
Posts data to CPU-to-PCI write buffer in the case
#
of a CPU to PCI write.
Drives host address to Data lines and data to ad-
#
dress lines for programming the PCMC configuration registers.
]
14
82433LX/82433NX
Table 1. HIG Commands
CommandCodeDescription
NOPC00000b No Operation on CPU Bus
CMR11100b CPU Memory Read
CPRF00100b CPU Read First Dword from CPU-to-PCI Read Prefetch Buffer
CPRA00101b CPU Read Next Dword from CPU-to-PCI Read Prefetch Buffer, Toggle A
CPRB00110b CPU Read Next Dword from CPU-to-PCI Read Prefetch Buffer, Toggle B
CPRQ00111b CPU Read Qword from CPU-to-PCI Read Prefetch Buffer
SWB001000b Store Write-Back Data Qword 0 to PCI-to-Memory Read Buffer
SWB101001b Store Write-Back Data Qword 1 to PCI-to-Memory Read Buffer
SWB201010b Store Write-Back Data Qword 2 to PCI-to-Memory Read Buffer
SWB301011b Store Write-Back Data Qword 3 to PCI-to-Memory Read Buffer
PCMWQ01100b Post to CPU-to-Memory Write Buffer Qword
PCMWFQ01101b Post to CPU-to-Memory Write and PCI-to-Memory Read Buffer First Qword
PCMWNQ01110b Post to CPU-to-Memory Write and PCI-to-Memory Read Buffer Next Qword
PCPWL10000b Post to CPU-to-PCI Write Low Dword
MCP3L10011b Merge to CPU-to-PCI Write Low Dword 3 Bytes
MCP2L10010b Merge to CPU-to-PCI Write Low Dword 2 Bytes
MCP1L10001b Merge to CPU-to-PCI Write Low Dword 1 Byte
PCPWH10100b Post to CPU-to-PCI Write High Dword
MCP3H10111b Merge to CPU-to-PCI Write High Dword 3 Bytes
MCP2H10110b Merge to CPU-to-PCI Write High Dword 2 Bytes
MCP1H10101b Merge to CPU-to-PCI Write High Dword 1 Byte
LCPRAD00001b Latch CPU-to-PCI Read Address
DPRA11000b Drive Address from PCI A/D Latch to CPU Address Bus
DPWA11001b Drive Address from PCI-to-Memory Write Buffer to CPU Address Bus
ADCPY11101b Address to Data Copy in the LBX
DACPYH11011b Data to Address Copy in the LBX High Dword
DACPYL11010b Data to Address Copy in the LBX Low Dword
PSCD01111b Post Special Cycle Data
DRVFF11110b Drive FF..FF (All 1’s) onto the Host Data Bus
PCPWHC00011b Post to CPU-to-PCI Write High Dword Configuration
NOTE:
All other patterns are reserved.
15
82433LX/82433NX
NOPCNo Operation is performed on the host
bus by the LBX hence it tri-states its
host bus drivers.
CMRThiscommandeffectively drives
DRAM data onto the host data bus.
The LBX acts as a transparent latch in
this mode, depending on MDLE for
latch control. With the MDLE signal
high the CMR command will cause the
LBXs to buffer memory data onto the
host bus. When MDLE is low. The LBX
will drive onto the host bus whatever
memory data that was latched when
MDLE was negated.
CPRFThis command reads the first Dword of
the CPU-to-PCI read prefetch buffer.
The read pointer of the FIFO is set to
point to the first Dword. The Dword is
driven onto the high and low halves of
the host data bus.
CPRAThis command increments the read
pointer of the CPU-to-PCI read prefetch buffer FIFO and drives that
Dword onto the host bus when it is
driven after a CPRF or CPRB command. If driven after another CPRA
command, the LBX drives the current
Dword while the read pointer of the
FIFO is not incremented. The Dword is
driven onto the upper and lower halves
of the host data bus.
CPRBThis command increments the read
pointer of the CPU-to-PCI read prefetch buffer FIFO and drives that
Dword onto the host bus when it is
driven after a CPRA command. If driven after another CPRB command, the
LBX drives the current Dword while the
read pointer of the FIFO is not incremented. The Dword is driven onto the
upper and lower halves of the host
data bus.
CPRQThis command drives the first Dword
stored in the CPU-to-PCI read prefetch
buffer onto the lower half of the host
data bus, and drives the second Dword
onto the upper half of the host data
bus, regardless of the state of the read
pointer. The read pointer is not affected by this command.
SWB0This command stores a Qword from
the host data lines into location 0 of
the PCI-to-Memory Read Buffer. Parity
is either generated for the data or propagated from the host bus based on the
state of the PPOUT signals sampled at
the negation of RESET when the LBXs
were initialized.
SWB1This command, (similar to SWB0),
stores a Qword from the host data
lines into location 1 of the PCI-to-Memory Read Buffer. Parity is either generated from the data or propagated from
the host bus based on the state of the
PPOUT signal sampled at the falling
edge of RESET.
SWB2This command, (similar to SWB0),
stores a Qword written back from the
first or second level cache into location
2 of the PCI-to-memory read buffer.
Parity is either generated from the data
or propagated from the host bus based
on the state of the PPOUT signal sampled at the falling edge of RESET.
SWB3This command stores a Qword from
the host data lines into location 3 of
the PCI-to-Memory Read Buffer. Parity
is either generated for the data or propagated from the host bus based on the
state of the PPOUT signal sampled at
the falling edge of RESET.
PCMWQThis command posts one Qword of
data from the host data lines to CPUto-Memory Write Buffer in case of a
CPU memory write or a write-back from
the second level cache.
PCMWFQIf the PCI Memory read address leads
to a hit on a modified line in the first
level cache, then a write-back is
scheduled and this data has to be written into the CPU-to-Memory Write Buffer and PCI-to-Memory Read Buffer at
the same time. The write-back of the
first Qword is done by this command to
both the buffers.
PCMWNQThis command follows the previous
command to store or post subsequent
write-back Qwords.
16
82433LX/82433NX
PCPWLThis command posts the low Dword of
a CPU-to-PCI write. The CPU-to-PCI
Write Buffer stores a Dword of PCI address for every Dword of data. Hence,
this command also stores the address
of the Low Dword in the address location for the data. Address bit 2 (A2) is
not stored directly. This command assumes a value of 0 for A2 and this is
what is stored.
MCP3LThis command merges the 3 most sig-
nificant bytes of the low Dword of the
host data bus into the last Dword posted to the CPU-to-PCI write buffer. The
address is not modified.
MCP2LThis command merges the 2 most sig-
nificant bytes of the low Dword of the
host data bus into the last Dword posted to the CPU-to-PCI write buffer. The
address is not modified.
MCP1LThis command merges the most signif-
icant byte of the low Dword of the host
data bus into the last Dword posted to
the CPU-to-PCI write buffer. The address is not modified.
PCPWHThis command posts the upper Dword
of a CPU-to-PCI write, with its address,
into the address location. Hence, to do
a Qword write PCPWL has to be followed by a PCPWH. Address bit 2 (A2)
is not stored directly. This command
forces a value of 1 for A2 and this is
what is stored.
MCP3HThis command merges the 3 most sig-
nificant bytes of the high Dword of the
host data bus into the last Dword posted to the CPU-to-PCI Write Buffer. The
address is not modified.
MCP2HThis command merges the 2 most sig-
nificant bytes of the high Dword of the
host data bus into the last Dword posted to the CPU-to-PCI Write Buffer. The
address is not modified.
MCP1HThis command merges the most signif-
icant byte of the high Dword of the host
data bus into the last Dword posted to
the CPU-to-PCI Write Buffer. The address is not modified.
LCPRADThis command latches the host ad-
dress to drive on PCI for a CPU-to-PCI
read. It is necessary to latch the address in order to drive inquire addresses on the host address bus before the
CPU address is driven onto PCI.
DPRAThe PCI memory read address is
latched in the PCI A/D latch by a PIG
command LCPRAD, this address is
driven onto the host address bus by
DPRA. Used in PCI to memory read
transaction.
DPWAThe DPWA command drives the ad-
dress of the current PCI Master Write
Buffer onto the host address bus. This
command is potentially driven for multiple cycles. When it is no longer driven,
the read pointer will increment to point
to the next buffer, and a subsequent
DPWA command will read the address
from that buffer.
ADCPYThis command drives the host data
bus with the host address. The address is copied on the high and low
halves of the Qword data bus; i.e.
A[31:0]is copied onto D[31:0]and
D[63:32]. This command is used when
the CPU writes to the PCMC configuration registers.
DACPYHThis command drives the host address
bus with the high Dword of host data.
This command is used when the CPU
writes to the PCMC configuration registers.
DACPYLThis command drives the host address
bus with the low Dword of host data.
This command is used when the CPU
writes to the PCMC configuration registers.
PSCDThis command is used to post the val-
ue of the Special Cycle code into the
CPU-to-PCI Posted Write Buffer. The
value is driven onto the A[31:0]lines
by the PCMC, after acquiring the address bus by asserting AHOLD. The
value on the A[31:0]lines is posted
into the DATA location in the CPU-toPCI Posted Write Buffer.
DRVFFThis command causes the LBX to drive
all ‘‘1s’’ (i.e. FFFFFFFFh) onto the host
data bus. It is used for CPU reads from
PCI that terminate with master abort.
PCPWHCThis command posts the high half of
the CPU data bus. The LBXs post the
high half of the data bus even if A2
from the PCMC is low. This command
is used during configuration writes
when using PCI configuration access
mechanism
Ý
1.
17
82433LX/82433NX
3.2.2 MEMORY INTERFACE GROUP: MIG[2:0
The Memory Interface commands are shown in Table 2. These commands are issued by the DRAM controller
of the PCMC to perform the following functions:
Retires data from CPU-to-Memory Write Buffer to DRAM.
#
Stores data into PCI-to-Memory Read Buffer when the PCI read address is targeted to DRAM.
#
Retires PCI-to-Memory Write Buffer to DRAM.
#
Command CodeDescription
NOPM000bNo Operation on Memory Bus
PMRFQ001bPlace into PCI-to-Memory Read Buffer First Qword
PMRNQ010bPlace into PCI-to-Memory Read Buffer Next Qword
MEMDRV111bDrive Latched Data Onto Memory Bus for 1 Clock Cycle
NOTE:
All other patterns are reserved.
NOPMNOperation on the memory bus. The LBX
PMRFQThe PCI-to-Memory read address tar-
PMRNQThis command stores subsequent
RCMWQThis command retires one Qword from
RPMWQThis command retires one Qword of
tri-states its drivers driving the memory
bus.
gets memory if there is a miss on first
and second caches. This command
stores the first Qword of data starting at
the first location in the buffer. This buffer is 8 Dwords or 1 cache line deep.
Qwords from memory starting at the
next available location in the PCI-toMemory Read Buffer. It is always used
after PMRFQ.
the CPU-to-Memory Write Buffer to
DRAM. The address is stored in the address queue for this buffer in the
PCMC.
data from one line of the PCI-to-Memory write buffer to DRAM. When all the
valid data in one buffer is retired, the
next RPMWQ (or RPMWQS) will read
data from the next buffer.
]
Table 2. MIG Commands
RPMWQS This command retires one Qword of
MEMDRVFor a memory write operation the data
data from one line of PCI-to-Memory
write buffer to DRAM. For this command the data in the buffer is shifted by
one Dword (Dword in position 0 is shifted to 1, 1 to 2 etc.). This is because the
address targeted by the first Dword of
the write could be an odd Dword (i.e.,
address bit[2
ligned line this command has to be
used for all the data in the buffer. When
all the valid data in one buffer is retired,
the next RPMWQ (or RPMWQS) will
read data from the next buffer.
on the memory bus is required for more
than one clock cycle hence all DRAM
retires are latched and driven to the
memory bus in subsequent cycles by
this command.
]
is a 1). To retire a misa-
18
82433LX/82433NX
3.2.3 PCI INTERFACE GROUP: PIG[3:0
The PCI Interface commands are shown in Table 3.
These commands are issued by the PCI master/
slave interface of the PCMC to perform the following
functions:
Slave posts address and data to PCI-to-Memory
#
Write Buffer.
Slave sends PCI-to-Memory read data on the AD
#
bus.
Slave latches PCI master memory address so
#
that it can be gated to the host address bus.
Master latches CPU-to-PCI read data from the
#
AD bus.
Master retires CPU-to-PCI write buffer.
#
Master sends CPU-to-PCI address to the AD bus.
#
CommandCodePARDescription
PPMWA1000bIPost to PCI-to-Memory Write Buffer Address
PPMWD1001bIPost to PCI-to-Memory Write Buffer Data
SPMRH1101bOSend PCI Master Read Data High Dword
SPMRL1100bOSend PCI Master Read Data Low Dword
SPMRN1110bOSend PCI Master Read Data Next Dword
LCPRF0000bILatch CPU Read from PCI into Read Prefetch Buffer First Dword
LCPRA0001bILatch CPU Read from PCI into Prefetch Buffer Next Dword, A Toggle
LCPRB0010bILatch CPU Read from PCI into Prefetch Buffer Next Dword, B Toggle
DCPWA0100bODrive CPU-to-PCI Write Buffer Address
DCPWD0101bODrive CPU-to-PCI Write Buffer Data
DCPWL0110bODrive CPU-to-PCI Write Buffer Last Data
DCCPD1011bODiscard Current CPU-to-PCI Write Buffer Data
BCPWR1010bOBackup CPU-to-PCI Write Buffer for Retry
SCPA0111bOSend CPU-to-PCI Address
LPMA0011bILatch PCI Master Address
]
Table 3. PIG Commands
The PCI AD[31:0]lines are driven by asserting the
signal DRVPCI. This signal is used for both master
and slave transactions.
Parity is calculated on either the value being driven
onto PCI or the value being received on PCI, depending on the command. In Table 3, the PAR column has been included to indicate the value that the
PPOUT signals are based on. An ‘‘I’’ indicates that
the PPOUT signals reflect the parity of the AD lines
as inputs to the LBX. An ‘‘O’’ indicates that the
PPOUT signals reflect the value being driven on the
PCI AD lines. See Section 3.3.4 for the timing relationship between the PIG[3:0]command, the
AD[31:0]lines, and the PPOUT signals.
NOTE:
All other patterns are reserved.
19
82433LX/82433NX
PPMWAThis command selects a new buffer
and places the PCI master address
latch value into the address register
for that buffer. The next PPMWD
command posts write data in the first
location of this newly selected buffer. This command also causes the
EOL logic to decrement the count of
Dwords remaining in the line.
PPMWDThis command stores the value in
the AD latch into the next data location in the currently selected buffer.
This command also causes the EOL
logic to decrement the count of
Dwords remaining in the line.
SPMRHThis command sends the high order
Dword from the first Qword of the
PCI-to-Memory Read Buffer onto
PCI. This command also causes the
EOL logic to decrement the count of
Dwords remaining in the line.
SPMRLThis command sends the low order
Dword from the first Qword of the
PCI-to-Memory Read Buffer onto
PCI. This command also selects the
Dword alignment for the transaction
and causes the EOL logic to decrement the count of Dwords remaining
in the line.
SPMRNThis command sends the next
Dword from the PCI-to-Memory
Read Buffer onto PCI. This command also causes the EOL logic to
decrement the count of Dwords remaining in the line. This command is
used for the second and all subsequent Dwords of the current transaction.
LCPRFThis command acquires the value of
the AD[31:0]lines into the first location in the CPU-to-PCI Read Prefetch Buffer until a different command is driven.
LCPRAWhen driven after a LCPRF or
LCPRB command, this command
latches the value of the AD[31:0
lines into the next location into the
CPU-to-PCI Read Prefetch Buffer.
When driven after another LCPRA
command, this command latches
the value on AD[31:0]into the same
location in the CPU-to-PCI Read
Prefetch Buffer, overwriting the previous value.
LCPRBWhen driven after a LCPRA com-
mand, this command latches the value of the AD[31:0]lines into the next
location into the CPU-to-PCI Read
Prefetch Buffer. When driven after
another LCPRB command, this command latches the value on AD[31:0
into the same location in the CPU-toPCI Read Prefetch Buffer, overwriting the previous value.
DCPWAThis command drives the next ad-
dress in the CPU-to-PCI Write Buffer
onto PCI. The read pointer of the
FIFO is not incremented.
DCPWDThis command drives the next data
Dword in the CPU-to-PCI Write Buffer onto PCI. The read pointer of the
FIFO is incremented on the next
PCLK if TRDY
Ý
is asserted.
DCPWLThis command drives the previous
data Dword in the CPU-to-PCI Write
Buffer onto PCI. This is the data
which was driven by the last DCPWD
command. The read pointer of the
FIFO is not incremented.
DCCPDThis command discards the current
Dword in the CPU-to-PCI Write Buffer. This is used to clear write data
when the write transaction terminates with master abort, where
Ý
TRDY
is never asserted.
BCPWRFor this command the CPU-to-PCI
Write Buffer is ‘‘backed up’’ one entry such that the address/data pair
last driven with the DCPWA and
DCPWD commands will be driven
again on the AD[31:0]lines when
the commands are driven again.
This command is used when the target has retried the write cycle.
SCPAThis command drives the value on
the host address bus onto PCI.
LPMAThis command stores the previous
AD[31:0]value into the PCI master
]
address latch. If the EOL logic determines that the requested Dword is
the last Dword of a line, then the
EOL signal will be asserted; otherwise the EOL signal will be negated.
]
20
82433LX/82433NX
3.3 LBX Timing Diagrams
This section describes the timing relationship between the LBX control signals and the interface
buses.
3.3.1 HIG[4:0]COMMAND TIMING
The commands driven on HIG[4:0]can cause the
host address bus and/or the host data bus to be
driven and latched. The following timing diagram illustrates the timing relationship between the driven
command and the buses. The ‘‘host bus’’ in Figure 4
could be address and/or data.
Note that the Drive command takes two cycles to
drive the host data bus, but only one to drive the
address. When the NOPC command is sampled, the
LBX takes only one cycle to release the host bus.
Figure 4. HIG[4:0]Command Timing
The Drive commands in Figure 4 are any of the
following:
Figure 5 illustrates the timing relationship between
Ý
]
the HIG[4:0], MIG[2:0], CAS[7:0
, and MDLE signals for DRAM memory reads. The delays shown in
the diagram do not represent the actual AC timings,
but are intended only to show how the delay affects
the sequencing of the signals.
When the CPU is reading from DRAM, the HIG[4:0
lines are driven with the CMR command that causes
the LBX to drive memory data onto the HD bus. Until
the MD bus is valid, the HD bus is driven with invalid
]
data. When CAS[7:0
comes valid after the DRAM CAS[7:0
Ý
assert, the MD bus be-
]
Ý
access
time. The MD and MP lines are directed through a
synchronous register inside the LBX to the HD and
HP lines. MDLE acts as a clock enable for this register. When MDLE is asserted, the LBX samples the
MD and MP lines. When MDLE is negated, the MD
and HD register retains its current value.
The LBX releases the HD bus based on sampling
the NOPC command on the HIG[4:0]lines and
MDLE being asserted. By delaying the release of the
]
HD bus until MDLE is asserted, the LBX provides
hold time for the data with respect to the write en-
]
Ý
able strobes (CWE[7:0
) of the second level
cache.
22
290478– 6
Figure 5. CPU Read from Memory
82433LX/82433NX
3.3.3 MIG[2:0]COMMAND
Figure 6 illustrates the timing of the MIG[2:0]com-
Ý
]
mands with respect to the MD bus, CAS[7:0
Ý
WE
. Figure 6 shows the MD bus transitioning from
, and
a read to a write cycle.
The Latch command in Figure 6 is any of the
following:
PMRFQPMRNQ
The Retire command in Figure 6 is any of the
following:
RCMWQ RPMWQRPMWQS
Figure 6. MIG[2:0]Command Timing
The data on the MD bus is sampled at the end of the
first cycle into the LBX based on sampling the Latch
]
Ý
command. The CAS[7:0
in the next cycle. The WE
signals can be negated
Ý
signal is asserted in the
next cycle. The required delay between the assertion of WE
Ý
and the assertion of CAS[7:0
]
Ý
means
that the MD bus has 2 cycles to turn around; hence
the NOPM command driven in the second clock.
The LBX starts to drive the MD bus based on sampling the Retire command at the end of the third
clock. After the Retire command is driven for 1 cycle, the data is held at the output by the MEMDRV
command. The LBX releases the MD bus based on
sampling the NOPM command at the end of the
sixth clock.
290478– 7
23
82433LX/82433NX
3.3.4 PIG[3:0]COMMAND, DRVPCI, AND PPOUT
TIMING
Figure 7 illustrates the timing of the PIG[3:0]commands, the DRVPCI signal, and the PPOUT[1:0]signal relative to the PCI AD[31:0]lines.
The Drive commands in Figure 7 are any of the following:
SPMRHSPMRLSPMRN
DCPWADCPWD DCPWL
SCPA
The Latch commands in Figure 7 are any of the following:
PPMWAPPMWD LPMA
The following commands do not fit in either category, although they function like Latch type commands
with respect to the PPOUT[1:0]signals. They are
described in Section 3.3.5.
LCPRFLCPRALCPRB
The DRVPCI signal is driven synchronous to the PCI
bus, enabling the LBXs to initiate driving the PCI
AD[31:0]lines one clock after DRVPCI is asserted.
As shown in Figure 7, if DRVPCI is asserted in cycle
N, the PCI AD[31:0]lines are driven in cycle N
a
The negation of the DRVPCI signal causes the LBXs
to asynchronously release the PCI bus, enabling the
LBXs to cease driving the PCI AD[31:0]lines in the
same clock that DRVPCI is negated. As shown in
Figure 7, if DRVPCI is negated in cycle N, the PCI
AD[31:0]lines are released in cycle N.
PCI address and data parity is available at the LBX
interface on the PPOUT lines from the LBX. The parity for data flow from PCI to LBX is valid 1 clock
cycle after data on the AD bus. The parity for data
flow from LBX to PCI is valid in the same cycle as
the data. When the AD[31:0]lines transition from
input to output, there is no conflict on the parity lines
due to the dead cycle for bus turnaround. This is
illustrated in the sixth and seventh clock of Figure 7.
The structure of the CPU-to-PCI read prefetch buffer
requires special considerations due to the partition
of the PCMC and LBX. The PCMC interfaces only to
the PCI control signals, while the LBXs interface only
to the data. Therefore, it is not possible to latch a
Dword of data into the prefetch buffer after it is qualified by TRDY
latched into the same location until TRDY
pled asserted. Only after TRDY
Ý
. Instead, the data is repetitively
Ý
Ý
is sam-
is sampled asserted is data valid in the buffer. A toggling mechanism
is implemented to advance the write pointer to the
next Dword after the current Dword has been qualified by TRDY
Ý
.
Other considerations of the partition are taken into
account on the host side as well. When reading from
the buffer, the command to drive the data onto the
host bus is sent before it is known that the entry is
valid. This method avoids the wait-state that would
be introduced by waiting for an entry’s TRDY
Ý
to be
asserted before sending the command to drive the
entry onto the host bus. The FIFO structure of the
buffer also necessitates a toggling scheme to advance to the next buffer entry after the current entry
has been successfully driven. Also, this method
gives the LBX the ability to drive the same Dword
twice, enabling reads of less than a Dword to be
serviced by the buffer; reads of individual bytes of a
Dword would read the same Dword 4 times.
The HIG[4:0]and PIG[3:0]lines are defined to enable the features described previously. The LCPRF
PIG[3:0]command latches the first PCI read Dword
into the first location in the CPU-to-PCI read prefetch
Ý
buffer. This command is driven until TRDY
is sampled asserted. The valid Dword would then be in the
first location of the buffer. The cycle after TRDY
Ý
sampled asserted, the PCMC drives the LCPRA
command on the PIG[3:0]lines. This action latches
the value on the PCI AD[31:0]lines into the
next
Dword location in the buffer. Again, the LCPRA com-
Ý
mand is driven until TRDY
is sampled asserted.
Each cycle the LCPRA command is driven, data is
latched into the same location in the buffer. When
Ý
TRDY
is sampled asserted, the PCMC drives the
LCPRB command on the PIG[3:0]lines. This latches
the value on the AD[31:0]lines into the next location
in the buffer, the one
after
the location that the previ-
ous LCPRA command latched data into. After
Ý
TRDY
has been sampled asserted again, the command switches back to LCPRA. In this way, the
same location in the buffer can be filled repeatedly
until valid, and when it is known that the location is
valid, the next location can be filled.
The commands for the HIG[4:0], CPRF, CPRA, and
CPRB, work exactly the same way. If the same command is driven, the same data is driven. Driving an
appropriately different command results in the next
data being driven. Figure 8 illustrates the usage of
these commands.
Figure 8 shows an example of how the PIG commands function on the PCI side. The LCPRF command is driven on the PIG[3:0]lines until TRDY
Ý
sampled asserted at the end of the fifth PCI clock.
The LCPRA command is then driven until TRDY
Ý
again sampled asserted at the end of the seventh
PCI clock. TRDY
Ý
is sampled asserted again so
LCPRB is driven only once. Finally, LCPRA is driven
again until the last TRDY
Ý
is asserted at the end of
the tenth PCI clock. In this way, 4 Dwords are
latched in the read CPU-to-PCI prefetch buffer.
Figure 8 also shows an example of how the HIG
commands function on the host side of the LBX.
Two clocks after sampling the CPRF command, the
LBX drives the host data bus. The data takes two
cycles to become stable. The first data driven in this
case is invalid, since the data has not arrived on PCI.
The data driven on the host bus changes in the seventh host clock, since the LCPRF command has
been driven on the PIG[3:0]lines the previous cycle,
latching a new value into the first location of the read
prefetch buffer. At this point the data is not the cor-
is
rect value, since TRDY
Ý
has not yet been asserted
on PCI. The LCPRF command is driven again in the
is
fifth PCI clock while TRDY
Ý
is sampled asserted at
the end of this clock. The requested data for the
read is then latched into the first location of the read
prefetch buffer and driven onto the host data bus,
becoming valid at the end of CPU clock 12. The
Ý
BRDY
signal can therefore be driven asserted in
this clock. The following read transaction (issued in
CPU clock 15) requests the next Dword, and so the
CPRA command is driven on the HIG[4:0]lines, advancing to read the next location in the read prefetch buffer. As the correct data is already there, the
command is driven only once for this transaction.
The next read transaction requests data in the same
Dword as the previous. Therefore, the CPRA command is driven again, the buffer is not advanced,
and the same Dword is driven onto the host bus.
26
82433LX/82433NX
3.3.6 PIG[3:0]: END-OF-LINE
WARNING SIGNALS: EOL
When posting PCI master writes, the PCMC must be
informed when the line boundary is about to be overrun, as it has no way of determining this itself (recall
that the PCMC does not receive any address bits
from PCI). The low order LBX determines this, as it
contains the low order bits of the PCI master write
address and also tracks how many Dwords of write
data have been posted. Therefore, the low order
LBX component sends the ‘‘end-of-line’’ warning to
the PCMC. This is accomplished with the EOL signal
driven from the low order LBX to the PCMC. Figure 9
illustrates the timing of this signal.
1. The FRAME
Ý
signal is sampled asserted in the
first cycle. The LPMA command is driven on the
PIG[3:0]signals to hold the address while it is
being decoded (e.g. in the MEMCS
Ý
decode circuit of the 82378 SIO). The first data (D0) remains
on the bus until TRDY
Ý
to MEMCS
being sampled asserted in the third
Ý
is asserted in response
clock.
2. The PPMWA command is driven in response to
sampling MEMCS
Ý
asserted. TRDYÝis asserted
in this cycle indicating that D0 has been latched at
the end of the fourth clock. The action of the
PPMWA command is to transfer the PCI address
captured in the PCI AD latch at the end of the first
clock to the posting buffer, and open the PCI AD
latch in order to capture the data. This data will be
posted to the write buffer in the following cycle by
the PPMWD command.
3. The EOL signal is first negated when the LPMA
command is driven on the PIG[3:0]signals. However, if the first data Dword accepted is also the
last that should be accepted, the EOL signal will
be asserted in the third clock. This is the ‘‘end-ofline’’ indication. In this case, the EOL signal is asserted as soon as the LPMA command has been
latched. The action by the PCMC in response is to
Ý
negate TRDY
and assert STOPÝin the fifth
clock. Note that the EOL signal is asserted even
before the MEMCS
Ý
signal is sampled asserted
in this case. The EOL signal will remain asserted
until the next time the LPMA command is driven.
4. If the second Dword is the last that should be
accepted, the EOL signal will be asserted in the
fifth clock to negate TRDYÝand assert STOP
on the following clock. The EOL signal is asserted
in response to the PPMWA command being sampled, and relies on the knowledge that TRDY
Ý
for
the first Dword of data will be sampled asserted
by the master in the same cycle (at the end of the
fourth clock). Therefore, to prevent a third assertion of TRDYÝin the sixth clock, the EOL signal
must be asserted in the fifth clock.
Ý
Figure 9. EOL Signal Timing for PCI Master Writes
290478– 10
27
82433LX/82433NX
A similar sequence is defined for PCI master reads.
While it is possible to know when to stop driving read
data due to the fact that the read address is latched
into the PCMC before any read data is driven on PCI,
the use of the EOL signal for PCI master reads simplifies the logic internal to the PCMC. Figure 10 illustrates the timing of EOL with respect to the PIG[3:0
commands to drive out PCI read data.
Note that unlike the PCI master write sequence, the
Ý
STOP
signal is asserted with the last data transfer,
not after.
1. The LPMA command sampled at the end of the
second clock causes the EOL signal to assert if
there is only one Dword left in the line, otherwise
it will be negated. The first TRDY
the last, and the STOP
Ý
]
with TRDY
2. The SPMRH command causes the count of the
.
Ý
signal will be asserted
Ý
number of Dwords left in the line to be decremented. If this count reaches one, the EOL signal
is asserted. The next TRDY
Ý
STOP
is asserted with TRDYÝ.
Ý
will be the last, and
will also be
28
290478– 11
Figure 10. EOL Signal Timing for PCI Master Reads
82433LX/82433NX
3.4 PLL Loop Filter Components
As shown in Figure 11, loop filter components are
required on the LBX components. A 4.7 KX 5% resistor is typically connected between pins LP1 and
LP2. Pin LP2 has a path to the PLLAGND pin
through a 100X 5% series resistor and a 0.01 mF
10% series capacitor. The ground side of capacitor
C1 and the PLLVSS pin should connect to the
ground plane at a common point. All PLL loop filter
traces should be kept to minimal length and should
be wider than signal traces. Inductor L1 is connected to the 5V power supply on both the 82433LX and
82433NX.
Some circuit boards may require filtering the power
circuit to the LBX PLL. The circuit shown in Figure
11 will typically enable the LBX PLL to have higher
noise immunity than without. Pin PLLVDD is connected to the 5V V
The PLLVDD and PLLVSS pins are bypassed with a
0.01 mF 10% series capacitor.
through a 10X 5% resistor.
CC
The high order 82433NX LBX samples A11 at the
falling edge of reset to configure the LBX for PLL
test mode. When A11 is sampled low, the LBX is in
normal operating mode. When A11 is sampled high,
the LBX drives the internal HCLK from the PLL on
the EOL pin. Note that A11 on the high order LBX is
connected to the A27 line on the CPU address bus.
This same address line is used to put the PCMC into
PLL test mode.
MercuryMercury
60 MHz66 MHz
Neptune
R14.7 KX2.2 KX4.7 KX
R2100X100X100X
C20.01 mF0.01 mF0.01 mF
R310X10X10X
C10.47 mF0.47 mF0.47 mF
1
C1
0.01 mF0.01 mF0.01 mF
Figure 11. Loop Filter Circuit
290478– 12
29
82433LX/82433NX
3.5 PCI Clock Considerations
There is a 1.25 ns clock skew specification between
the PCMC and the LBX that must be adhered to for
proper operation of the PCMC/LBX timing. As
shown in Figure 12, the PCMC drives PCLKOUT to
an external clock driver which supplies copies of
PCLK to PCI devices, the LBXs, and back to the
PCMC. The skew specification is defined as the dif-
Figure 12. Clock Considerations
ference in timing between the signal that appears at
the PCMC PCLKIN input pin and the signal that appears at the LBX PCLK input pin. For both the low
order LBX and the high order LBX, the PCLK rising
and falling edges must not be more than 1.25 ns
apart from the rising and falling edge of the PCMC
PCLKIN signal.
290478– 13
30
82433LX/82433NX
4.0 ELECTRICAL CHARACTERISTICS
Maximum Power Dissipation: АААААА1.4W (82433LX)
Maximum Total Power Dissipation À1.4W (82433NX)
4.1 Absolute Maximum Ratings
Table 4 lists stress ratings only. Functional operation
at these maximums is not guaranteed. Functional
operation conditions are given in Sections 4.2
and 4.3.
Extended exposure to the Absolute Maximum Ratings may affect device reliability.
Case Temperature under Bias ААААААА0
Storage Temperature ААААААААААb40§Ctoa125§C
Voltage on Any Pin
with Respect to GroundААААА
b
Supply Voltage
with Respect to V
ААААААААААААb0.3 toa7.0V
SS
0.3 to V
Ctoa85§C
§
a
0.3V
CC
Maximum Power Dissipation, V
The maximum total power dissipation in the
82433NX on the V
pins may draw as much as 430 mW, however,
V
CC3
total power will not exceed 1.4W.
NOTICE: This data sheet contains information on
products in the sampling and initial production phases
of development. The specifications are subject to
change without notice. Verify with your local Intel
Sales office that you have the latest data sheet before finalizing a design.
*
WARNING: Stressing the device beyond the ‘‘Absolute
Maximum Ratings’’ may cause permanent damage.
These are stress ratings only. Operation beyond the
‘‘Operating Conditions’’ is not recommended and extended exposure beyond the ‘‘Operating Conditions’’
may affect device reliability.
CC
and V
АААААААА430 mW
CC3
pins is 1.4W. The
CC3
4.2 Thermal Characteristics
The LBX is designed for operation at case temperatures between 0§C and 85§C. The thermal resistances of
the package are given in the following tables.
apply to the following signals: AD[15:0],A[15:0],D[31:0],HP[3:0],MD[31:0],MP[3:0], TRDYÝ, RESET,
IH1
apply to the following signals: HIG[4:0], PIG[3:0], MIG[2:0], MDLE, DRVPCI
IH2
apply to the following signals: AD[15:0],A[15:0],D[31:0],HP[3:0],MD[31:0],MP[3:0
OH1
apply to the following signals: PPOUT, EOL
OH2
apply to the following signals: PPOUT, EOL
OH1
apply to the following signals: AD[15:0
OH2
apply to the following signals: A[15:0],D[31:0],HP[3:0],MD[31:0],MP[3:0
OH3
]
]
]
4.3.2 82433NX LBX DC CHARACTERISTICS
Functional Operating Range: V
e
4.75V to 5.25V; V
CC
e
3.135 to 3.465V, T
CC3
CASE
e
0§Ctoa85§C
SymbolParameterMinTypicalMaxUnitNotes
V
IL1
V
IH1
V
IL2
V
IH2
V
IL3
V
IH3
V
OL1
V
OH1
V
OL2
V
OH2
I
OL1
I
OH1
I
OL2
I
OH2
Input Low Voltage
Input High Voltage2.0V
Input Low Voltage
Input High Voltage0.7 x V
Input Low Voltage
Input High Voltage2.0V
Output Low Voltage0.4V4
Output High Voltage2.4V4
Output Low Voltage0.5V5
Output High VoltageV
Output Low Current1mA6
Output High Current
Output Low Current3mA7
Output High Current
b
0.30.8V1
a
0.3V1
CC
b
0.30.3 x V
CC
b
0.30.8V3
b
0.5V5
CC
b
1mA6
b
2mA7
CC
a
V
0.3V2
CC
a
0.3V3
CC3
V2
33
82433LX/82433NX
Functional Operating Range: V
e
T
CASE
e
4.75V to 5.25V; V
CC
0§Ctoa85§C (Continued)
e
3.135V to 3.465V,
CC3
SymbolParameterMinTypicalMaxUnitNotes
I
OL3
I
OH3
I
IH
I
IL
C
IN
C
OUT
C
I/O
NOTES:
and V
1. V
IL1
and V
2. V
IL2
and V
3. V
IL3
and V
4. V
OL1
and V
5. V
OL2
and I
6. I
OL1
and I
7. I
OL2
and I
8. I
OL3
9. The output buffers for A[15:0],D[31:0]and HP[3:0]are powered with V
Output Low Current3mA8
Output High Current
Input Leakage Current
Input Leakage Current
b
1mA8
a
10mA
b
10mA
Input Capacitance4.6pF
Output Capacitance4.3pF
I/O Capacitance4.6pF
apply to the following signals: AD[15:0],MD[31:0],MP[3:0], TRDYÝ, RESET, HCLK, PCLK
IH1
apply to the following signals: HIG[4:0], PIG[3:0], MIG[2:0], MDLE, DRVPCI
IH2
apply to the following signals: A[15:0],D[31:0],HP[3:0
IH3
apply to the following signals: AD[15:0],A[15:0],D[31:0],HP[3:0],MD[31:0],MP[3:0
OH1
apply to the following signals: PPOUT, EOL
OH2
apply to the following signals: PPOUT, EOL
OH1
apply to the following signals: AD[15:0
OH2
apply to the following signals: A[15:0],D[31:0],HP[3:0],MD[31:0],MP[3:0
OH3
]
]
and therefore drive 3.3V signal levels.
CC3
]
]
34
82433LX/82433NX
e
4.4 82433LX AC Characteristics
The AC specifications given in this section consist of
propagation delays, valid delays, input setup requirements, input hold requirements, output float delays,
output enable delays, clock high and low times and
clock period specifications. Figure 13 through Figure
In Figure 13 through Figure 21 VT
lowingsignals: MD[31:0],MP[3:0],D[31:0],
HP[3:0],A[15:0],AD[15:0], TRDY
RESET, TEST.
e
VT
2.5V for the following signals: HIG[4:0],
PIG[3:0], MIG[2:0], MDLE, DRVPCI, PPOUT, EOL.
21 define these specifications. Sections 4.3.1
through 4.3.3 list the AC Specifications.
4.4.1 HOST AND PCI CLOCK TIMING, 66 MHZ (82433LX)
Functional Operating Range: V
e
4.9V to 5.25V; T
CC
CASE
e
0§Ctoa70§C
SymbolParameterMinMaxFigureNotes
t1aHCLK Period152018
t1bHCLK High Time518
t1cHCLK Low Time518
t1dHCLK Rise Time1.519
t1eHCLK Fall Time1.519
t1fHCLK Period Stability
g
100ps
t2aPCLK Period3018
t2bPCLK High Time1218
t2cPCLK Low Time1218
t2dPCLK Rise Time319
t2ePCLK Fall Time319
t3HCLK to PCLK Skew
b
7.25.821
1.5V for the fol-
Ý
, HCLK, PCLK,
1
NOTE:
1. Measured on rising edge of adjacent clocks at 1.5 Volts.
t20aAD[15:0]Output Enable Delay from PCLK Rising217
t20bAD[15:0]Valid Delay from PCLK Rising211141
t20cAD[15:0]Setup Time to PCLK Rising715
t20dAD[15:0]Hold Time from PCLK Rising015
t20eAD[15:0]Float Delay from DRVPCI Falling21016
t21aTRDYÝSetup Time to PCLK Rising715
t21bTRDYÝHold Time from PCLK Rising015
t22aD[31:0],HP[3:0]Output Enable Delay from HCLK Rising07.9172
t22bD[31:0],HP[3:0]Float Delay from HCLK Rising3.115.516
t22cD[31:0],HP[3:0]Float Delay from MDLE Rising211.0163
t22dD[31:0],HP[3:0]Valid Delay from HCLK Rising07.8142
t22eD[31:0],HP[3:0]Setup Time to HCLK Rising3.415
t22fD[31:0],HP[3:0]Hold Time from HCLK Rising0.315
t23aHA[15:0]Output Enable Delay from HCLK Rising015.217
t23bHA[15:0]Float Delay from HCLK Rising015.216
t23cHA[15:0]Valid Delay from HCLK Rising018.5147
t23ccHA[15:0]Valid Delay from HCLK Rising015.58
t23dHA[15:0]Setup Time to HCLK Rising15.0154
t23eHA[15:0]Setup Time to HCLK Rising4.1155
]
t23fHA[15:0
Hold Time from HCLK Rising0.315
t24aMD[31:0],MP[3:0]Valid Delay from HCLK Rising012.0146
t24bMD[31:0],MP[3:0]Setup Time to HCLK Rising4.415
t24cMD[31:0],MP[3:0]Hold Time from HCLK Rising1.015
t25EOL, PPOUT Valid Delay from PCLK Rising2.317.2142
t26aAll Outputs Float Delay from TSCON Falling03016
t26bAll Outputs Enable Delay from TSCON Rising03017
CASE
e
0§Ctoa85§C
NOTES:
1. Min: 0 pF, Max: 50 pF
2.0pF
3. When NOPC command sampled on previous rising HCLK on HIG[4:0
4. CPU to PCI Transfers
5. When ADCPY command is sampled on HIG[4:0
6. 50 pF
7. When DACPYL or DACPYH commands are sampled on HIG[4:0
8. Inquire cycle
]
]
]
39
82433LX/82433NX
4.4.7 TEST TIMING (82433LX)
Functional Operating Range: V
e
4.75V to 5.25V; T
CC
CASE
e
0§Ctoa85§C
SymbolParameterMinMaxFigureNotes
t30All Test Signals Setup Time to10.0In PLL Bypass
HCLK/PCLK RisingMode
t31All Test Signals Hold Time to12.0In PLL Bypass
HCLK/PCLK RisingMode
t32Test Setup Time to HCLK/PCLK Rising15.015
t33Test Hold Time to HCLK/PCLK Rising5.015
t34PPOUT Valid Delay from PCLK Rising0.050015In PLL Bypass
Mode
4.5 82433NX AC Characteristics
The AC specifications given in this section consist of propagation delays, valid delays, input setup requirements, input hold requirements, output float delays, output enable delays, clock high and low times and clock
period specifications. Figure 13 through Figure 21 define these specifications. Section 4.5 lists the AC Specifications.
In Figure 13 through Figure 21 VT
Ý
A[15:0],AD[15:0], TRDY
e
VT
2.5V for the following signals: HIG[4:0
, HCLK, PCLK, RESET, TEST.
e
1.5V for the following signals: MD[31:0],MP[3:0],D[31:0],HP[3:0],
]
, PIG[3:0], MIG[2:0], MDLE, DRVPCI, PPOUT, EOL.
4.5.1 HOST AND PCI CLOCK TIMING, (82433NX)
Functional Operating Range: V
e
4.75V to 5.25V; V
CC
e
3.135V to 3.465V, T
CC3
CASE
e
SymbolParameterMinMaxFigureNotes
t1aHCLK Period152018
t1bHCLK High Time518
t1cHCLK Low Time518
t1dHCLK Rise Time1.519
t1eHCLK Fall Time1.519
t1fHCLK Period Stability
g
100ps
t2aPCLK Period3018
t2bPCLK High Time1218
t2cPCLK Low Time1218
t2dPCLK Rise Time319
t2ePCLK Fall Time319
t3HCLK to PCLK Skew
NOTE:
1. Measured on rising edge of adjacent clocks at 1.5 Volts.
t20aAD[15:0]Output Enable Delay from PCLK Rising217
t20bAD[15:0]Valid Delay from PCLK Rising211141
]
t20cAD[15:0
t20dAD[15:0
Setup Time to PCLK Rising715
]
Hold Time from PCLK Rising015
t20eAD[15:0]Float Delay from DRVPCI Falling21016
t21aTRDYÝSetup Time to PCLK Rising715
t21bTRDYÝHold Time from PCLK Rising015
t22aD[31:0],HP[3:0]Output Enable Delay from HCLK Rising07.5172
t22bD[31:0],HP[3:0]Float Delay from HCLK Rising3.115.516
t22cD[31:0],HP[3:0]Float Delay from MDLE Rising29.5163
t22dD[31:0],HP[3:0]Valid Delay from HCLK Rising07.5142
t22eD[31:0],HP[3:0]Setup Time to HCLK Rising3.115
t22fD[31:0],HP[3:0]Hold Time from HCLK Rising0.315
e
3.135V to 3.465V, T
CC3
b
0.315
b
0.515
e
3.135V to 3.465V, T
CC3
CASE
CASE
e
0§Ctoa85§C
e
0§Ctoa85§C
41
82433LX/82433NX
Functional Operating Range: V
e
T
CASE
e
4.75V to 5V; V
CC
0§Ctoa85§C (Continued)
e
3.135V to 3.465V,
CC3
SymbolParameterMinMaxFigureNotes
t23aHA[15:0]Output Enable Delay from HCLK Rising013.517
t23bHA[15:0]Float Delay from HCLK Rising013.516
t23cHA[15:0]Valid Delay from HCLK Rising017.5147
t23ccHA[15:0]Valid Delay from HCLK Rising013.58
t23dHA[15:0]Setup Time to HCLK Rising15154
t23eHA[15:0]Setup Time to HCLK Rising4.2155
t23fHA[15:0]Hold Time from HCLK Rising0.315
t24aMD[31:0],MP[3:0]Valid Delay from HCLK Rising012.0146
t24bMD[31:0],MP[3:0]Setup Time to HCLK Rising4.415
t24cMD[31:0],MP[3:0]Hold Time from HCLK Rising1.015
t25EOL, PPOUT Valid Delay from PCLK Rising2.317.2142
t26aAll Outputs Float Delay from TSCON Falling03016
t26bAll Outputs Enable Delay from TSCON Rising03017
NOTE:
1. Min: 0 pF, Max: 50 pF
2.0pF
3. When NOPC command sampled on previous rising HCLK on HIG[4:0
4. CPU to PCI Transfers
5. When ADCPY command is sampled on HIG[4:0
6. 50 pF
7. When DACPYL or DACPYH commands are sampled on HIG[4:0
8. Inquire cycle
]
]
]
4.5.4 TEST TIMING (82433NX)
Functional Operating Range: V
e
4.75V to 5.25V; V
CC
e
3.135V to 3.465V, T
CC3
CASE
e
0§Ctoa85§C
SymbolParameterMinMaxFigureNotes
t30All Test Signals Setup Time to HCLK/10.0In PLL Bypass Mode
PCLK Rising
t31All Test Signals Hold Time to HCLK/12.0In PLL Bypass Mode
PCLK Rising
t32Test Setup Time to HCLK/PCLK Rising15.015
t33Test Hold Time to HCLK/PCLK Rising5.015
t34PPOUT Valid Delay from PCLK Rising0.050015In PLL Bypass Mode
42
4.5.5 TIMING DIAGRAMS
82433LX/82433NX
290478– 14
Figure 13. Propagation Delay
290478– 15
Figure 14. Valid Delay from Rising Clock Edge
Figure 15. Setup and Hold Times
Figure 16. Float Delay
Figure 17. Output Enable Delay
290478– 16
290478– 17
290478– 18
43
82433LX/82433NX
290478– 19
Figure 18. Clock High and Low Times and Period
290478– 20
Figure 19. Clock Rise and Fall Times
44
290478– 21
Figure 20. Pulse Width
290478– 22
Figure 21. Output to Output Delay
82433LX/82433NX
5.0 PINOUT AND PACKAGE INFORMATION
5.1 Pin Assignment
Pins 1, 22, 41, 61, and 150 are VDD3 pins on the 82433NX. These pins must be connected to the 3.3V power
supply. All other VDD pins on the 82433NX must be connected to the 5V power supply.
Figure 22. 82433LX and 82433NX Pin Assignment
290478– 23
45
82433LX/82433NX
Table 5. 82433LX and 82433NX Numerical Pin Assignment
Pin NamePinÝType
VDD(82433LX)1V
V
(82433NX)
DD3
V
SS
PLLV
DD
PLLV
SS
PLLAGND5V
LP26in
LP17out
HCLK8in
TEST9in
D610t/s
D211t/s
D1412t/s
D1213t/s
D1114t/s
HP115t/s
D416t/s
D017t/s
D1618t/s
TSCON19in
V
SS
V
SS
VDD(82433LX22V
3 (82433NX)
V
DD
D2023t/s
D1824t/s
HP325t/s
2V
3V
4V
20V
21V
Pin NamePinÝType
D2226t/s
HP227t/s
D2528t/s
D1729t/s
D1930t/s
D2331t/s
A1432t/s
A1233t/s
A834t/s
A635t/s
A1036t/s
A337t/s
A438t/s
A939t/s
V
DD
40V
VDD(82433LX)41V
V
3 (82433NX)
DD
V
SS
42V
A243t/s
A144t/s
A045t/s
A546t/s
A1547t/s
A1348t/s
A1149t/s
A750t/s
Pin NamePinÝType
D2151t/s
D2452t/s
D2753t/s
D3154t/s
D3055t/s
D2656t/s
D2957t/s
D2858t/s
V
SS
V
SS
59V
60V
VDD(82433LX)61V
V
(82433NX)
DD3
HIG062in
HIG163in
HIG264in
HIG365in
HIG466in
MIG067in
MIG168in
MIG269in
MD870t/s
MD2471t/s
MD072t/s
MD1673t/s
MD974t/s
MD2575t/s
46
Table 5. 82433LX and 82433NX Numerical Pin Assignment (Continued)
Pin NamePin
Ý
Type
MD176t/s
MD1777t/s
MD1078t/s
V
SS
V
DD
V
DD
TRDY
Ý
79V
80V
81V
82in
RESET83in
MD2684t/s
MD285t/s
MD1886t/s
MD1187t/s
MD2788t/s
MD389t/s
MD1990t/s
MD1291t/s
MD2892t/s
MD493t/s
V
DD
94V
MD2095t/s
V
SS
V
SS
96V
97V
MD1398t/s
MD2999t/s
MD5100t/s
MD21101t/s
MD14102t/s
MD30103t/s
MD6104t/s
Pin NamePin
Ý
Type
MD22105t/s
MD15106t/s
MD31107t/s
MD7108t/s
MD23109t/s
V
DD
V
SS
110V
111V
MP0112t/s
MP2113t/s
MP1114t/s
MP3115t/s
AD0116t/s
AD1117t/s
AD2118t/s
AD3119t/s
V
DD
V
DD
120V
121V
PPOUT122t/s
EOL123t/s
V
SS
124V
AD4125t/s
AD5126t/s
AD6127t/s
AD7128t/s
AD8129t/s
V
DD
130V
AD9131t/s
AD10132t/s
82433LX/82433NX
Pin NamePinÝType
AD11133t/s
AD12134t/s
AD13135t/s
AD14136t/s
AD15137t/s
MDLE138in
V
DD
V
SS
V
SS
PCLK142in
DRVPCI143in
PIG3144in
PIG2145in
PIG1146in
PIG0147in
D7148t/s
V
SS
VDD(82433LX)150V
V
3 (82433NX)
DD
HP0151t/s
D8152t/s
D1153t/s
D5154t/s
D3155t/s
D10156t/s
D15157t/s
D13158t/s
D9159t/s
V
DD
139V
140V
141V
149V
160V
47
82433LX/82433NX
Table 6. 82433LX and 82433NX Alphabetical Pin Assignment List
Pin NamePin
A045t/s
A144t/s
A243t/s
A337t/s
A438t/s
A546t/s
A635t/s
A750t/s
A834t/s
A939t/s
A1036t/s
A1149t/s
A1233t/s
A1348t/s
A1432t/s
A1547t/s
AD0116t/s
AD1117t/s
AD2118t/s
AD3119t/s
AD4125t/s
AD5126t/s
AD6127t/s
AD7128t/s
AD8129t/s
AD9131t/s
AD10132t/s
AD11133t/s
AD12134t/s
Ý
Type
Pin NamePin
Ý
Type
AD13135t/s
AD14136t/s
AD15137t/s
D017t/s
D1153t/s
D211t/s
D3155t/s
D416t/s
D5154t/s
D610t/s
D7148t/s
D8152t/s
D9159t/s
D10156t/s
D1114t/s
D1213t/s
D13158t/s
D1412t/s
D15157t/s
D1618t/s
D1729t/s
D1824t/s
D1930t/s
D2023t/s
D2151t/s
D2226t/s
D2331t/s
D2452t/s
D2528t/s
Pin NamePin
Ý
Type
D2656t/s
D2753t/s
D2858t/s
D2957t/s
D3055t/s
D3154t/s
DRVPCI143in
EOL123t/s
HCLK8in
HIG062in
HIG163in
HIG264in
HIG365in
HIG466in
HP0151t/s
HP115t/s
HP227t/s
HP325t/s
LP17out
LP26in
MD072t/s
MD176t/s
MD285t/s
MD389t/s
MD493t/s
MD5100t/s
MD6104t/s
MD7108t/s
MD870t/s
48
Table 6. 82433LX and 82433NX Alphabetical Pin Assignment List (Continued)
Pin NamePin
Ý
Type
MD974t/s
MD1078t/s
MD1187t/s
MD1291t/s
MD1398t/s
MD14102t/s
MD15106t/s
MD1673t/s
MD1777t/s
MD1886t/s
MD1990t/s
MD2095t/s
MD21101t/s
MD22105t/s
MD23109t/s
MD2471t/s
MD2575t/s
MD2684t/s
MD2788t/s
MD2892t/s
MD2999t/s
MD30103t/s
MD31107t/s
MDLE138in
MIG067in
Pin NamePinÝType
MIG168in
MIG269in
MP0112t/s
MP1114t/s
MP2113t/s
MP3115t/s
PCLK142in
PIG0147in
PIG1146in
PIG2145in
PIG3144in
PLLAGND5V
PLLV
PLLV
DD
SS
3V
4V
PPOUT122t/s
RESET83in
TEST9in
TRDY82in
TSCON19in
VDD(82433LX)1V
3 (82433NX)
V
DD
VDD(82433LX)22V
V
3 (82433NX)
DD
V
DD
40V
VDD(82433LX)41V
VDD3 (82433NX)
VDD(82433LX)61V
V
3 (82433NX)
DD
82433LX/82433NX
Pin NamePinÝType
V
DD
V
DD
V
DD
V
DD
V
DD
V
DD
V
DD
V
DD
VDD(82433LX)150V
VDD3 (82433NX)
V
DD
V
SS
V
SS
V
SS
V
SS
V
SS
V
SS
V
SS
V
SS
V
SS
V
SS
V
SS
V
SS
V
SS
V
SS
80V
81V
94V
110V
120V
121V
130V
139V
160V
2V
20V
21V
42V
59V
60V
79V
96V
97V
111V
124V
140V
141V
149V
49
82433LX/82433NX
5.2 Package Information
Figure 23. 82433LX and 82433NX 160-Pin QFP Package
Symbol
A4.45
A10.250.65
A23.303.80
B0.200.40
D31.0032.40
D127.8028.20
D325.55
Min ValueMax Value
(mm)(mm)
Table 7. 160-Pin QFP Package Values
Symbol
E31.6032.40
E127.8028.20
E325.55
e0.65
L0.601.00
i0
g0.1
290478– 24
Min ValueMax Value
(mm)(mm)
§
10
§
50
82433LX/82433NX
6.0 TESTABILITY
The TSCON pin may be used to help test circuits
surrounding the LBX. During normal operations, the
TSCON pin must be tied to VCC or connected to
VCC through a pull-up resistor. All LBX outputs are
tri-stated when the TSCON pin is held low or
grounded.
6.1 NAND Tree
A NAND tree is provided in the LBX for Automated
Test Equipment (ATE) board level testing. The
NAND tree allows the tester to set the connectivity
of each of the LBX signal pins.
The following steps must be taken to put the LBX
into PLL bypass mode and enable the NAND tree.
First, to enable PLL bypass mode, drive RESET inactive, TEST active, and the DCPWA command
(0100) on the PIG[3:0]lines. Then drive PCLK from
low to high. DRVPCI must be held low on all rising
edges of PCLK during testing in order to ensure that
the LBX does not drive the AD[15:0]lines. The host
and memory buses are tri-stated by driving NOPM
Table 8. Test Vectors to put LBX Into PLL Bypass and Enable NAND Tree Testing
LBX
Pin/Vector
PCLK01001111111
]
PIG[3:0
RESET11100011111
HCLK00000001010
]
MIG[2:0
]
HIG[4:0
TEST11111111111
DRVPCI00000000000
1234567891011
Ý
0h0h0h4h4h4h4h4h4h4h4h
0h0h0h0h0h0h0h0h0h0h0h
0h0h0h0h0h0h0h0h0h0h0h
(000) and NOPC (00000) on the MIG[2:0]and
HIG[4:0]lines and driving two rising edges on
HCLK. A rising edge on PCLK with RESET high will
cause the LBXs to exit PLL bypass mode. TEST
must remain high throughout the use of the NAND
tree. The combination of TEST and DRVPCI high
with a rising edge of PCLK must be avoided. TSCON
must be driven high throughout testing since driving
it low would tri-state the output of the NAND tree. A
10 ns hold time is required on all inputs sampled by
PCLK or HCLK when in PLL bypass mode.
6.1.1 TEST VECTOR TABLE
The following test vectors can be applied to the
82433LX and 82433NX to put it into PLL bypass
mode and to enable NAND tree testing.
6.1.2 NAND TREE TABLE
Table 9 shows the sequence of the NAND tree in
the 82433LX and 82433NX. Non-inverting inputs are
driven directly into the input of a NAND gate in the
tree. Inverting inputs are driven into an inverter be-
fore going into the NAND tree. The output of the
NAND tree is driven on the PPOUT pin.
51
82433LX/82433NX
Order PinÝSignal
110D6Y
211D2Y
312D14Y
413D12Y
514D11Y
615HP1Y
716D4Y
817D0Y
918D16Y
1023D20Y
1124D18Y
1225HP3Y
1326D22Y
1427HP2Y
1528D25Y
1629D17Y
1730D19Y
1831D23Y
1932A14Y
2033A12Y
2134A8Y
2235A6Y
2336A10Y
2437A3Y
2538A4Y
2639A9Y
Non-
Inverting
Table 9. NAND Tree Sequence
Order PinÝSignal
Non-
Inverting
2743A2Y
2844A1Y
2945A0Y
3046A5Y
3147A15Y
3248A13Y
3349A11Y
3450A7Y
3551D21Y
3652D24Y
3753D27Y
3854D31Y
3955D30Y
4056D26Y
4157D29Y
4258D28Y
4362HIG0Y
4463HIG1Y
4564HIG2Y
4665HIG3Y
4766HIG4Y
4867MIG0N
4968MIG1N
5069MIG2N
5170MD8N
5271MD24N
Order PinÝSignal
Non-
Inverting
5372MD0N
5473MD16N
5574MD9N
5675MD25N
5776MD1N
5877MD17N
5978MD10N
6082TRDY
Ý
6183RESETN
6284MD26N
6385MD2N
6486MD18N
6587MD11N
6688MD27N
6789MD3N
6890MD19N
6991MD12N
7092MD28N
7193MD4N
7295MD20N
7398MD13N
7499MD29N
75100MD5N
76101MD21N
77102MD14N
78103MD30N
Y
52
Table 9. NAND Tree Sequence (Continued)
Order PinÝSignal
79104MD6N
80105MD22N
81106MD15N
82107MD31N
83108MD7N
84109MD23N
85112MP0N
86113MP2N
87114MP1N
88115MP3N
89116AD0Y
90117AD1Y
91118AD2Y
82119AD3Y
93123EOLY
Non-
Inverting
Order PinÝSignal
94125AD4Y
95126AD5Y
96127AD6Y
97128AD7Y
98129AD8Y
99131AD9Y
100132AD10Y
101133AD11Y
102134AD12Y
103135AD13Y
104136AD14Y
105137AD15Y
106138MDLEY
107143DRVPCIN
6.2 PLL Test Mode
The high order 82433NX LBX samples A11 at the
falling edge of reset to configure the LBX for PLL
test mode. When A11 is sampled low, the LBX is in
normal operating mode. When A11 is sampled high,
the LBX drives the internal HCLK from the PLL on
the EOL pin.
Non-
Inverting
82433LX/82433NX
Order PinÝSignal
108144PIG3N
109145PIG2N
110146PIG1N
111147PIG0N
112148D7Y
113151HP0Y
114152D8Y
115153D1Y
116154D5Y
117155D3Y
118156D10Y
119157D15Y
120158D13Y
121159D9Y
Non-
Inverting
53
Loading...
+ hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.