*Notice: The information in this document is subject to change without notice
Tsi301
Notes
Tsi301 HyperTransport to PCI User Manual
5-36
PCI Control
Offset
63h
Bits
Type
Reset
Description
7:6
R
00b
Reserved.
5
RW
0
Target Receive FIFO - if asserted, new requests from the PCI bus are only
accepted when the PCI interface’s target receive FIFO is completely empty.
When deasserted, writes are accepted as long as there is space in the FIFO
for the write command and the first beat of data. Not persistent through warm
reset.
4
RW
0
Park Master - this bit controls where the arbiter defaults to when there is no
PCI request outstanding. The default can be to grant the PCI bus to
P_GNT0_N (assumed to be connected to the HyperTransport PCI bridge) or
to grant the PCI bus to the most recent master on the bus.
0 = Park PCI bus on most recent master.
1 = Park PCI bus on P_GNT0_N.
Not persistent through warm reset.
3:0
RW
Fh
ID Sel Charge - number of PCI clocks to charge the AD lines on a Type 0 con-
figuration cycle before asserting P_FRAME_N. Not persistent through warm
reset.
Error Control
Offset 67h–64h
Bits
Type
Reset
Description
31
R
0
Reserved.
30
RC
0
PCI Command/Address Parity Error - a parity error was detected on the PCI
bus during the address phase. This is only logged if the Parity Error Response
Enable bit in the Bridge Control register is set. Not persistent through warm
reset.
29
RC
0
Master Posted PCI Command Error - this is set whenever a PCI posted write
intended by the HyperTransport PCI bridge fails to complete. Possible reasons
are:
• Master Abort Received with Master Abort Mode = 1
• Target Abort Received
• TRDY# Timeout
• Retry Timeout
• Write received PERR with Parity Error Response
Enable = 1
Not persistent through warm reset.
28
RW
0
Discard SERR Fatal - if a secondary bus discard timer expiration occurs with
the Discard Timer SERR# enable asserted, this bit controls whether the SERR
gets mapped to a fatal or nonfatal interrupt:
0 = Nonfatal
1 = Fatal
Not persistent through warm reset.
27
RC
0
Response Match Error - this chip received a response packet to its unitID, indi-
cating that it belonged with a request issued from here, but no request with that
srcTag is outstanding. Persistent through warm reset.