PI7C8154ANAE Pericom Semiconductor, PI7C8154ANAE Datasheet - Page 37

• Manufacturer Part Number: PI7C8154ANAE
• Description: IC PCI-PCI BRIDGE ASYNC 304-PBGA
• Manufacturer: Pericom Semiconductor

Specifications of PI7C8154ANAE

• Applications: *
• Interface: *
• Voltage - Supply: *
• Package / Case: 304-BGA
• Mounting Type: Surface Mount
• Lead Free Status / RoHS Status: Lead free / RoHS Compliant

2.10
2.11
LOW, the 64-bit signals should be connected to pull-up resistors on the board and PI7C8154A does
not perform any input biasing. PI7C8154A can then treat memory write and prefetchable memory
read transactions as 64-bit transactions on the primary.
PI7C8154A always asserts S_REQ64# LOW during S_RESET# to indicate that the 64-bit
extension is supported on the secondary bus. Individual pull-up resistors must always be supplied
for S_AD[63:32], S_CBE[7:4], and S_PAR64.
TRANSACTION FLOW THROUGH
Transaction flow through refers to data being removed from the read/write buffers concurrently as
data is still being written to the buffer.
For reads, flow through occurs when the initiator repeats the delayed transaction while some read
data is in the buffer, but the transaction is still ongoing on the target bus. For read flow through to
occur, there can be no other reads or writes previously posted in the same direction.
For writes, flow through occurs when PI7C8154A is able to arbitrate for the target bus, initiate the
transaction and receive TRDY# from the target, while receiving data from the same transaction on
the initiator bus. Flow through can only occur if the writes that were previously posted in the same
direction are completed.
TRANSACTION TERMINATION
This section describes how PI7C8154A returns transaction termination conditions back to the
initiator.
The initiator can terminate transactions with one of the following types of termination:
Normal termination occurs when the initiator de-asserts FRAME# at the beginning of the last data
phase, and de-asserts IRDYL at the end of the last data phase in conjunction with either TRDY# or
STOP# assertion from the target.
A master abort occurs when no target response is detected. When the initiator does not detect a
DEVSEL# from the target within five clock cycles after asserting FRAME#, the initiator terminates
the transaction with a master abort. If FRAME# is still asserted, the initiator de-asserts FRAME#
on the next cycle, and then de-asserts IRDY# on the following cycle. IRDY# must be asserted in
the same cycle in which FRAME# deasserts. If FRAME# is already deasserted, IRDY# can be
deasserted on the next clock cycle following detection of the master abort condition.
The target can terminate transactions with one of the following types of termination:
TRDY# and DEVSEL# asserted in conjunction with FRAME# deasserted and IRDY# asserted.
STOP# and DEVSEL# asserted with TRDY# deasserted during the first data phase. No data
transfers occur during the transaction. This transaction must be repeated.
Normal termination
Master abort
Normal termination
Target retry
Page 37 of 112
ASYNCHRONOUS 2-PORT
DEC 2009 REVISION 1.02
PCI-to-PCI BRIDGE
Advance Information
PI7C8154A