PI7C8140AMAE Pericom Semiconductor, PI7C8140AMAE Datasheet - Page 29

• Manufacturer Part Number: PI7C8140AMAE
• Description: IC PCI-PCI BRIDGE 2PORT 128-QFP
• Manufacturer: Pericom Semiconductor

Specifications of PI7C8140AMAE

• Applications: *
• Interface: *
• Voltage - Supply: *
• Package / Case: 128-QFP
• Mounting Type: Surface Mount
• Maximum Operating Temperature: + 85 C
• Minimum Operating Temperature: 0 C
• Mounting Style: SMD/SMT
• Operating Supply Voltage: 3 V to 3.6 V
• Supply Current (max): 230 mA
• Lead Free Status / RoHS Status: Lead free / RoHS Compliant

07-0067
2.8.2 MASTER ABORT RECEIVED BY PI7C8140A
2.8.3 TARGET TERMINATION RECEIVED BY PI7C8140A
2.8.3.1 DELAYED WRITE TARGET TERMINATION RESPONSE
If the bridge is pre-fetching read data when it terminates the transaction because the master latency
timer expires, it does not repeat the transaction to obtain more data.
If the initiator initiates a transaction on the target bus and does not detect DEVSEL# returned by the
target within five clock cycles of the assertion of FRAME#, the bridge terminates the transaction with a
master abort. This sets the received-master-abort bit in the status register corresponding to the target
bus.
For delayed read and write transactions, the bridge is able to reflect the master abort condition back to
the initiator. When the bridge detects a master abort in response to a delayed transaction, and when the
initiator repeats the transaction, the bridge does not respond to the transaction with DEVSEL#, which
induces the master abort condition back to the initiator. The transaction is then removed from the
delayed transaction queue. When a master abort is received in response to a posted write transaction,
the bridge discards the posted write data and makes no more attempts to deliver the data. The bridge
sets the received-master-abort bit in the status register when the master abort is received on the primary
bus, or it sets the received master abort bit in the secondary status register when the master abort is
received on the secondary interface. When master abort is detected in posted write transaction with both
master-abort-mode bit (bit 5 of bridge control register) and the SERR# enable bit (bit 8 of command
register for secondary bus) are set, the bridge asserts P_SERR# if the master-abort-on-posted-write is
not set. The master-abort-on-posted-write bit is bit 4 of the P_SERR# event disable register (offset 64h).
Note: When the bridge performs a Type 1 to special cycle conversion, a master abort is the expected
termination for the special cycle on the target bus. In this case, the master abort received bit is not set,
and the Type 1 configuration transaction is disconnected after the first data phase.
When the bridge initiates a transaction on the target bus and the target responds with DEVSEL#, the
target can end the transaction with one of the following types of termination:
The bridge handles these terminations in different ways, depending on the type of transaction being
performed.
When the bridge initiates a delayed write transaction, the type of target termination received from the
target can be passed back to the initiator. Table 2-7 shows the response to each type of target
termination that occurs during a delayed write transaction.
The bridge repeats a delayed write transaction until one of the following conditions is met:
Normal termination (upon de-assertion of FRAME#)
Target retry
Target disconnect
Target abort
Page 29 of 82
2-PORT PCI-TO-PCI BRIDGE
March 20, 2007 – Revision 1.01
PI7C8140A