PI7C7300DNA datasheet(96/107 Pages) PERICOM

96 / 107 page

PI7C7300D

3-PORT PCI-TO-PCI BRIDGE

Page 96 of 107

Pericom Semiconductor

November 2005 - Revision 1.01

DWC (Row 5)

Yes

In Row 1 Column 1, PMW cannot pass the previous PMW and that means they must

complete on the target bus in the order in which they were received in the initiator bus.

In Row 2 Column1,DRR cannot pass the previous PMW and that means the previous

PMW heading to the same direction must be completed before the DRR can be attempted

on the target bus.

In Row 1 Column 2, PMW can pass the previous DRR as long as the DRR reaches the

head of the delayed transaction queue.

15.3

ABNORMAL TERMINATION (INITIATED BY BRIDGE

MASTER)

15.3.1

MASTER ABORT

Master abort indicates that when PI7C7300D acts as a master and receives no response

(i.e., no target asserts DEVSEL# or S1_DEVSEL# or S2_DEVSEL#) from a target, the

bridge deasserts FRAME# and then deasserts IRDY#.

15.3.2

PARITY AND ERROR REPORTING

Parity must be checked for all addresses and write data. Parity is defined on the P_PAR,

S1_PAR, and S2_PAR signals. Parity should be even (i. e. an even number of‘1’s) across

AD, CBE, and PAR. Parity information on PAR is valid the cycle after AD and CBE are

valid. For reads, even parity must be generated using the initiators CBE signals combined

with the read data. Again, the PAR signal corresponds to read data from the previous

data phase cycle.

15.3.3

REPORTING PARITY ERRORS

For all address phases, if a parity error is detected, the error should be reported on the

P_SERR# signal by asserting P_SERR# for one cycle and then 3-stating two cycles after

the bad address. P_SERR# can only be asserted if bit 6 and 8 in the Command Register

are both set to 1. For write data phases, a parity error should be reported by asserting the

P_PERR# signal two cycles after the data phase and should remain asserted for one cycle

when bit 6 in the Command register is set to a 1. The target reports any type of data

parity errors during write cycles, while the master reports data parity errors during read

cycles.

Detection of an address parity error will cause the PCI-to-PCI Bridge target to not claim

the bus (P_DEVSEL# remains inactive) and the cycle will then terminate with a Master

Abort. When the bridge is acting as master, a data parity error during a read cycle results

in the bridge master initiating a Master Abort.

PI7C7300DNA Datasheet(PDF) 96 Page - Pericom Semiconductor Corporation

PI7C7300DNA Datasheet(HTML) 96 Page - Pericom Semiconductor Corporation

Html Pages

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 ...More

Datasheet Download

Link URL