Integrated Device Technology, Inc. reserves the right to make changes to its products or specifications at any time, without notice, in order to improve design or performance
and to supply the best possible product. IDT does not assume any responsibility for use of any circuitry described other than the circuitry embodied in an IDT product. The
Company makes no representations that circuitry described herein is free from patent infringement or other rights of third parties which may result from its use. No license is
granted by implication or otherwise under any patent, patent rights or other rights, of Integrated Device Technology, Inc.
GENERAL DISCLAIMER
Code examples provided by IDT are for illustrative purposes only and should not be relied upon for developing applications. Any use of the code examples below is completely
at your own risk. IDT MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND CONCERNING THE NONINFRINGEMENT, QUALITY, SAFETY OR SUITA BIL IT Y
OF THE CODE, EITHER EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. FURTHER, IDT MAKES NO REPRESENTATIONS OR WARRANTIES AS TO THE TRUTH, ACCURACY OR COMPLETENESS
OF ANY STATEMENTS, INFORMATION OR MATERIALS CONCERNING CODE EXAMPLES CONTAINED IN ANY IDT PUBLICATION OR PUBLIC DISCLOSURE OR
THAT IS CONTAINED ON ANY IDT INTERNET SITE. IN NO EVENT WILL IDT BE LIABLE FOR ANY DIRECT, CONSEQUENTIAL, INCIDENTAL, INDIRECT, PUNITIVE OR
SPECIAL DAMAGES, HOWEVER THEY MAY ARISE, AND EVEN IF IDT HAS BEEN PREVIOUSLY ADVISED ABOUT THE POSSIBILITY OF SUCH DAMAGES. The code
examples also may be subject to United States export control laws and may be subject to the export or import laws of other countries and it is your responsibility to comply with
any applicable laws or regulations.
Integrated Device Technology's products are not authorized for use as critical components in life support devices or systems unless a specific written agreement pertaining to
such intended use is executed between the manufacturer and an officer of IDT.
1. Life support devices or systems are devices or systems which (a) are intended for surgical implant into the body or (b) support or sustain life and whose failure to perform,
when properly used in accordance with instructions for use provided in the labeling, can be reasonably expected to result in a significant injury to the user.
2. A critical component is any components of a life support device or system whose failure to perform can be reasonably expected to cause the failure of the life support device
or system, or to affect its safety or effectiveness.
IDT, the IDT logo, and Integrated Device Technology are trademarks or registered trademarks of Integrated Device Technology, Inc.
The Tsi384 PCIe-to-PCI Bridge User Manual discusses the features, capabilities, and configuration
requirements for the Tsi384.
Document Conventions
15
This document uses the following conventions.
Non-differential Signal Notation
Non-differential signals are either active-low or active-high. An active-low signal has an active state of
logic 0 (or the lower voltage level), and is denoted by a lowercase “n”. An active-high signal has an
active state of logic 1 (or the higher voltage level), and is not denoted by a special character. The
following table illustrates the non-differential signal naming convention.
StateSingle-line signalMulti-line signal
Active lowNAMEnNAMEn[3]
Active highNAMENAME[3]
Differential Signal Notation
Differential signals consist of pairs of complement positive and negative signals that are measured at
the same time to determine a signal’s active or inactive state (they are denoted by “_p” and “_n”,
respectively). The following table illustrates the differential signal naming convention.
StateSingle-line signalMulti-line signal
InactiveNAME_p = 0
ActiveNAME_p = 1
Integrated Device Technology
www.idt.com
NAME_n = 1
NAME_n = 0
NAME_p[3] = 0
NAME_n[3] =1
NAME_p[3] is 1
NAME_n[3] is 0
Tsi384 User Manual
May 5, 2014
About this Document16
Tip
Object Size Notation
•A byte is an 8-bit object.
•A word is a 16-bit object.
•A doubleword (Dword) is a 32-bit object.
Numeric Notation
•Hexadecimal numbers are denoted by the prefix 0x (for example, 0x04).
•Binary numbers are denoted by the prefix 0b (for example, 0b010).
•Registers that have multiple iterations are denoted by {x..y} in their names; where x is first register
and address, and y is the last register and address. For example, REG{0..1} indicates there are two
versions of the register at different addresses: REG0 and REG1.
Symbols
This symbol indicates a basic design concept or information considered helpful.
This symbol indicates important configuration information or suggestions.
This symbol indicates procedures or operating levels that may result in misuse or damage to
the device.
Document Status Information
•Advance – Contains information that is subject to change, and is available once prototypes are
released to customers.
•Preliminary – Contains information about a product that is near production-ready , and is revised as
required.
•Formal – Contains information about a final, customer-ready product, and is available once the
product is released to production.
Tsi384 User Manual
May 5, 2014
Integrated Device Technology
www.idt.com
About this Document17
Revision History
May 5, 2014, Formal
•Changed the 00110 setting to 112 from 102 for UPST_PWR_THRES in the “Upstream Post ed
Write Threshold Register”
•Updated step 3 in “Initialization”
•Added footnote H to Table 51: AC Specifications for PCI/X Interface
August 2009, Formal
This version of the document does not include any technical changes.
May 2009, Formal
•Added additional information about the TEST_BCE signal (see Table 5)
•Added missing register offset, 0x010, to the register map (Table 42)
•Revised the description of the CSR_SEL_400 bit in the “PCI Miscellaneous Clock Straps
Register”
•Changed the minimum value of the T
parameter for PCI 66 MHz to 2 ns (see Table 51)
OV1
July 2008, Formal
•Removed reference to PCIE_REXT pin because it is not applicable to the Tsi384
•Changed the Pin Type definition of various signals (see “Signal Descriptions”)
•Added Design Recommendations for Tsi384’s signals (see “Signal Descriptions”). This
information previously resided in the Tsi384 Board Design Guidelines.
•Corrected the description of the JTAG_TDO signal. Previously it indicated that the signal should
be pulled low if unused. The correct description for this signal if unused is to leave it unconnected
(see “JTAG Interface Signals”).
•Updated the “PCIe and SerDes Control and Status Registers”
•Added a new section that discusses “PCIe Programmable Transmit and Receive Equalization”
February 2008, Formal
•Added a note that explains how the EEPROM Controller handles an EEPROM byte count value
that is programmed to a non-multiple of 6 (see “System Diagram”)
•Revised the description of the “Opaque Memory Lower Register”
•Added bits 18–20 to the “PCIe Link Capabilities Register”
Integrated Device Technology
www.idt.com
Tsi384 User Manual
May 5, 2014
About this Document18
October 2007, Formal
•Revised the description of the PWRUP_EN_ARB signal (see “Power-up Signals”)
•Corrected the name of the PCI_PCIXCAP_PU signal that was used in several figures in “PCI/X
Clocking”. This signal was previously incorrectly named S_PCIXCAP_PU.
•Added power and current characteristics (see “Power Characteristics”)
July 2007, Preliminary
•Added error handling tables for PCIe and PCI/X (see “Error Handling Tables”)
•Updated the power supply sequencing information to indicate that the Tsi384 does not have any
specific sequencing constraints (see “Power Supply Sequencing”)
•Redefined two SerDes registers (see “PCIe Debug and Pattern Generator Control Register” and
“PCIe Pattern Matcher Control and Error Register”)
April 2007, Preliminary
•Updated the description of PCI/X bus arbitration (see “PCI/X Arbitration Scheme”)
•Added a cautionary note on how to use an EEPROM with the Tsi384 (see “System Diagram”)
•Updated the description of how JTAG can provide access to the Tsi384’s registers (see “JTAG
Register Access”)
•Added a new bit, PCI_MISC_CLK_STRAPS[CSR_SEL_400], to allow configuration of the PLL
clock (see “PCI Miscellaneous Clock Straps Register”)
•Added electrical and packaging information. This information used to reside in the
Tsi384 Hardware Manual, whic h is now an obsolete document.
December 2006, Preliminary
This version includes numerous minor changes.
October 2006, Advance
This version includes numerous minor changes.
Tsi384 User Manual
May 5, 2014
Integrated Device Technology
www.idt.com
1. Functional Overview
Topics discussed include the following:
•“Overview”
•“Features”
•“Device Architecture”
•“Typical Applications”
1.1Overview
The IDT T s i384 is a high-performance bus bridge that connects the PC I Expr ess (PCIe) protocol to the
PCI and PCI-X bus standards (see Figure 1).
The Tsi384’s PCIe Interface is a superior performance, configurable port that supports 1, 2, or 4 lanes.
This enables the bridge to offer exceptional throughput performance of up to 1 GBps per transmit and
receive direction. The device’s PCI/X Interface can operate up to 133 MHz in PCI-X mode, or up to
66 MHz in PCI mode. This interface offers designers extensive flexibility by supporting three types of
addressing modes: transparent, opaque, and non-transparent.
19
Integrated Device Technology
www.idt.com
Tsi384 User Manual
May 5, 2014
Figure 1: Tsi384 Block Diagram
PCI/X
Arbiter
Error
Handling
Interrupt
Handling
Clocking/
Reset
EEPROM
Controller
Power
Mgmt
JTAG
PCI/X Interface
PCIe Interface (x4)
80E1000_BK001_01 (Tsi384)
Posted
Writer
Buffer
Posted
Queue
Mux Logic
Non-
Posted
Buffer
NonPosted
Queue
DownstreamDownstream
UpstreamUpstream
Posted
Writer
Buffer
Posted
Queue
Mux Logic
Non-
Posted
Buffer
NonPosted
Queue
Config
Registers
1. Functional Overview20
1.2Features
The Tsi384’s key features are listed in the following sub-sections.
1.2.1General Features
Tsi384 User Manual
May 5, 2014
•Forward bridge, PCIe to PCI/X
•Single store and forward for optimal latency performance
•Supports three modes of addressing:
— Transparent: For eff icient, flow-through configurations
— Opaque: For multi-processor configurations and enhanced private device suppo rt
— Non-transparent: For address remapping of the PCIe and the PCI/PCI-X domains
•Compliant to the following specifications:
— PCI Express Base Specification (Revision 1.1)
— PCI Express-to-PCI/PCI-X Bridge Specification (Revision 1.0)
— PCI-to-PCI Bridge Specification (Revision 1.2)
Integrated Device Technology
www.idt.com
1. Functional Overview21
— PCI Local Bus Specification (Revision 3.0)
— PCI-X Addendum to PCI Local Bus Specification (Revision 2.0) (mode 1 only)
— PCI Bus Power Management Interface Specification (Revision 1.2)
•3.3V PCI/X I/Os
•Support for four external PCI/X bus masters through an integrated arbiter
•Support for external PCI/X bus arbiter
•Support for Masquerade mode (can overwrite vendor and device ID from EEPROM)
•JTAG IEEE 1149.1, 1149.6
•Support for D0, D3 hot, D3 cold power management states
•Packaged in 17 x 17 mm, 256-pin PBGA
1.2.2PCIe Features
•1, 2, or 4 lanes
•512-byte maximum payload
•Advanced error reporting capability
•Lane reversal and lane polarity inversion
•End-to-end CRC (ECRC) check and generation
•Up to four outstanding memory reads
•Four, 128-byte read completion buffers
•ASPM L0s link state power management
•Legacy interrupt signaling
•Hot plug support
1.2.3PCI-X Features
•32/64-bit addressing
•32/64-bit data bus
•50-, 66-, 100-, and 133-MHz operation
•Up to eight outstanding memory reads
•4-KB read completion buffer
1.2.4PCI Features
•32/64-bit addressing
•32/64-bit data bus
•25-, 33-, 50-, and 66-MHz operation
•Up to eight outstanding read requests
Integrated Device Technology
www.idt.com
Tsi384 User Manual
May 5, 2014
•4-KB read completion buffer
Rx PHY
SERDES
Configuration Registers
Data Link Layer
2K Repl ay buff ers
PC Ie P ri ma ry In t er f ac e
PCI /X Interface (Secondary Interface)
Tar get int erface
4
K
(
8
e
n
t
r
y
)
u
p
s
t
r
e
a
m
p
o
s
t
e
d
w
r
it
e
b
u
f
f
e
r
s
Mast er i nte rf ac e
T ransac ti on Layer
Tx P H Y
SERDES
Dat a Link Layer
Tr ansac ti on Layer
orderin g
Order ing
A ddres s dec odin g
PC I / X
Arbiter
JTA G
EEPROM
CLK/
Reset
U
p
s
t
r
e
a
m
R
e
a
d
R
e
q
u
e
s
t
q
u
e
u
e
Read
state
c ache
5
1
2
b
y
t
e
(
8
e
n
t
r
y
)
d
o
w
n
s
t
r
e
a
m
p
o
s
t
e
d
w
r
it
e
b
u
f
f
e
r
s
5
1
2
b
y
t
e
(
4
e
n
t
r
y
)
d
o
w
n
s
t
r
e
a
m
r
e
a
d
c
o
m
p
l
e
t
i
o
n
b
u
f
f
e
r
D
o
w
n
s
t
r
e
a
m
R
e
a
d
R
e
q
u
e
s
t
q
u
e
u
e
Read
state
cache
A ddress dec odi ng
F low control
ACK/noACK
Con fig w ri tes & r ead RequestConfig r eads
PC I - X
4
K
(
8
e
n
t
r
y
)
u
p
s
t
r
e
a
m
r
e
a
d
c
o
m
p
l
e
t
i
o
n
b
u
f
f
e
r
•Short-term caching support
1.3Device Architecture
A high-level, architectural diagram of the Tsi384 is displayed in Figure 2. For more information about
data flow through the device, see “Upstream Data Path” and “Downstream Data Path”.
Figure 2: Tsi384 Device Architecture
1. Functional Overview22
Packets received on the PCIe Interface are processed by the data link layer and transaction layer, if
applicable. If a packet is destined for the transaction layer, its address is decoded and forwarded to the
appropriate destination:
•Configuration register
•Downstream posted write buffer
•Downstream read request queue
•Downstream read completion buffer
Tsi384 User Manual
May 5, 2014
Integrated Device Technology
www.idt.com
1. Functional Overview23
PCI/X data that is destined for the PCIe fabric are subject to PCIe ordering rules. Data is pulled from
the appropriate queue:
•Configuration register
•Upstream posted write buffer
•Upstream read request queue
•Upstream read completion buffer
PCI/X transactions that are decoded for the PCIe address space are forwarded to the appropriate queue:
•Upstream read request queue
•Upstream posted write buffer
PCI-X read completion (Tsi384 is target), from a split transaction, are also decoded and sent to the
downstream read completion buffer.
Transactions destined for downstream devices on the PCI/X bus, are subject to PCI/X ordering rules.
Data is pulled form the appropriate queue:
•Downstream posted write buffer
•Downstream read request queue
PCI-X read completion (Tsi384 is master), from a split transaction, are also ordered and pulled from
the upstream read completion buffer.
PCIe is a serialized protocol at the physical layer, and a packetized protocol at the data link layer. Each
PCIe lane operates at 2.5 Gb symbol rate, or at 2.0 Gb data rate; the difference is a result of the 8/10b
coding process. The Tsi384 uses the following processes to ensure the accurate and timely delivery of
data through the data link layer:
•Credit-based flow control – Prevents data loss and congestion
•ACK/noACK protocol and End-to-End CRC (ECRC) – Ensures reliable data delivery if bit errors
occur
•Replay buffer – Replays packets that are not acknowledged by the receiver (NAK)
In contrast, PCI/X is a parallel data interface at the physical layer. PCI is a non-packetized protocol.
When a bus master starts a read or a write transaction, it indicates only the starting transaction address
to the target, and not the size of the read or write. PCI-X is a also a parallel bus at the physical layer , but
is more accommodating to packetized data flow. For example, the length of a read or write transaction
is defined during the attribute phase on the PCI-X bus.
Integrated Device Technology
www.idt.com
Tsi384 User Manual
May 5, 2014
1. Functional Overview24
In the case of a PCI/X write, which is initiated on the PCI/X Interface and is destined for the root
complex, the data is written into an upstream posted write buffer in the Tsi384. The end of the write
transaction is signaled by the master on the PCI/X bus. Once the write is completed the data can be
forwarded to the PCIe Interface. If the posted write buffer is about to overflow, the Tsi384 indicates a
retry/disconnect on the PCI bus. In the case of a PCI-X transaction, the Tsi384 disconnect on an
allowable disconnect boundary (ADB). Once the posted write buffer empties, the Tsi384 can accept
additional write transactions. The Tsi384 will split write transactions as required to meet PCIe
constraints: to prevent a write crossing a 4-KB boundary; if byte enables are used throughout the
transaction; or if the quantity of data exceeds the maximum payload size (see MAX_SIZE in “PCIe
Device Capabilities Register”). The upstream posted write buffer is managed as a simple FIFO.
A read initiated on the PCI bus that is decoded for an upstream target is handled as a delayed
transaction by the Tsi384. The bridge latches the read transaction and attempts to reserve buffer space
in its upstream read completion buffer. If space is successfully reserved in the buffer, the Tsi384
initiates a read on the PCIe Interface. When the read data is returned from the root comple x, it is store d
in the upstream read completion buffer. PCI-initiated reads, however, do not define the amount of data
to read. Once the master on the PCI bus retries the read transaction, the transaction is checked to
determine if the read data is returned. If it has the read data, the Tsi384 responds as the target and
transfers the read data to the PCI bus. Note the upstream read completion buffer is not a simple FIFO,
as the order that masters on the PCI bus retry is not deterministic. If the complet io n buffer becomes
empty prior to the transaction completing, the Tsi384 disconnects from the PCI bus. When the read
transaction is completed, the Tsi384 discards any prefetched data that is not used and frees up the
buffer.
A read initiated on the PCI-X bus that is decoded for an upstream target is handled as a split transaction
by the Tsi384. The bridge latches the read transaction and attempts to reserve buffer space in the
upstream read completion buffer . If space was successfully reserved in the buf fer, the T si384 initiates a
read on the PCIe Interface for the specified amount of data. When the read data is returned from the
root complex, it is stored in the upstream read completion buffer. When the Tsi384 has received
sufficient read data, the Tsi384 transfers the data to the target on the PCI-X bus.
The 512-byte data blocks in the upstream read completion buffer may be destined to different devices
on the PCI-X bus, and therefore, in different streams. A round-robin algorithm determin es which
stream is sent first. If the upstream read completion buffer is empty before the transaction completes,
the Tsi384 disconnects from the PCI-X bus on an ADB. The Tsi384 splits PCI-X read transactions as
required to meet PCIe constraints: to prevent a read crossing a 4-KB boundary; or if the quantity of
data exceeds MAX_RD_SIZE in the “PCIe Device Control and Status Register”.
A write initiated on the PCIe Interface with the target on the downstream PCI/X bus is written into the
downstream posted write buffer. The Tsi384 acts as the master for the transaction and arbitr ate s for the
PCI/X bus and initiates the write transaction. The downstream posted write buffer is managed as a
FIFO. There will always be space available in the buffer to accept packet data because of the flow
control method used by the PCIe data link layer. If the downstream posted write buffer is about to
overflow , the upstream device will be informed of this by its lack of credits and will not send any more
write data to the Tsi384.
Tsi384 User Manual
May 5, 2014
Integrated Device Technology
www.idt.com
1. Functional Overview25
4
A read initiated on the PCIe Interface with the target on the downstream PCI/X bus is written into the
downstream read request queue. The downstream read request queue is managed with flow control
credits to prevent overflowing. The T si384 latches the read transaction and attempts to reserve space in
the downstream read completion buffer. If space is successfully reserved in the buffer, the Tsi384 acts
as the master for the transaction and initiates a read transaction on the PCI/X bus. The read request
queue is managed using a round-robin algorithm. In the case of PCI-X, the target may respond with a
split response, which causes the Tsi384 to become the target for the read completion.
Programmable address decoders instruct the Tsi384 which transactions on the PCI/X bus to forward
upstream, and which transactions on the PCIe link to forward downstream.
1.4Typical Applications
This section illustrates some typical applications for the Tsi384.
Figure 3: Motherboard Application — PC, Server, SBC, Industrial PC
DRAM
PCIe
Endpoints
Processor
Block
x4x4
Tsi384
PCI-X
Tsi384
Tsi38
Device
Tsi384
PCIe
Switch
PCIe
Endpoints
Integrated Device Technology
www.idt.com
Tsi384 User Manual
May 5, 2014
Figure 4: External Storage Application
PCI-X 133 MHz
PCI-X 133 MHz
PCIe x4
Tsi384
GbE/FC
Controller
GbE/FC
Controller
PCI 66 MHz
PCI 66 MHz
PCIe x4
Tsi384
SCSI
Controller
SCSI
Controller
IOP
DRAM
1. Functional Overview26
PCI-X
to SATA
iSCSI
GbE
with
TOE
Integrated
CPU
x4x4
Tsi384
PCI-X
to SATA
Figure 5: Server Add-in Cards for Networking and Storage
Tsi384 User Manual
May 5, 2014
Integrated Device Technology
www.idt.com
2. Signal Descriptions
Topics discussed include the following:
•“Overview”
•“PCIe Interface Signals”
•“PCI/X Interface Signals”
•“EEPROM Interface Signals”
•“JTAG Interface Signals”
•“Power-up Signals”
•“Power Supply Signals”
2.1Overview
27
Signals are classified according to the types defined in the following table.
3.3 In PU3.3V CMOS input with 265K (+/- 45K) pull-up resistor
3.3 Out3.3V CMOS output
PCI/X BidirPCI/X bi-directional
PCI/X Bidir ODPCI/X bi-directional open-drain
PCI/X InPCI/X input
PCI/X OutPCI/X output
PCI/X ODPCI/X output open-drain
Integrated Device Technology
www.idt.com
Tsi384 User Manual
May 5, 2014
Table 1: Pin Types (Continued)
Pin TypeDefinition
PCIE Diff OutPCIe differential output
PCIE Diff InPCIe differential input
2.2PCIe Interface Signals
Table 2: PCIe Interface Signals
NamePin TypeDescriptionDesign Recommendation
2. Signal Descriptions28
PCIE_PERSTn3.3 InMaster reset in:
0 = Tsi384 in reset
1 = Tsi384 in normal mode
PCIE_TXD_n[3:0]
PCIE_TXD_p[3:0]
PCIE_RXD_n[3:0]
PCIE_RXD_p[3:0]
PCIE_REFCLK_n
PCIE_REFCLK_p
PCIE_LANE_VALIDn[3
:0]
PCIE Diff OutTransmit Data. These differential pair
signals send PCIe 8b/10b encoded
symbols and an embedded clock to the
link partner.
PCIE Diff InReceive Data. These differential pair
signals receive PCIe 8b/10b encoded
symbols and an embedded clock from
the link partner.
PCIE Diff InReference Clock. 100-MHz differential
reference clock.
3.3 outPCIe Lane Valid:
0 = Lane valid
1 = Lane invalid
Direct connect to the PERST# signal.
DC blocking capacitors must be placed
in the link between the transmitter and
the receiver. Place a 0603 or 0402
0.075uF to 0.1uF ceramic capacitor on
each TXD_n, TXD_p signal.
DC blocking capacitors must be placed
in the link between the transmitter and
the receiver; however, the DC blocking
capacitors are normally placed near the
transmitter. When designing an add-in
card, capacitors are not required on this
link. When designing a system board,
the DC blocking capacitors should be
placed near the transmitter.
Refer to the Tsi384 Board Design Guidelines.
When connecting to LEDs, connect the
cathode on PCIE_LANE_VALIDn and
the anode to 3.3V.
Tsi384 User Manual
May 5, 2014
Integrated Device Technology
www.idt.com
2. Signal Descriptions29
2.3PCI/X Interface Signals
Table 3: PCI/X Interface Signals
NamePin TypeDescriptionDesign Recommendation
PCI_ACK64nPCI/X BidirAcknowledge 64-bit Transaction. The
bus target asserts this signal to indicate
it wants to participate in a 64-bit
transaction.
PCI_AD[63:0]PCI/X BidirAddress/Data Bus. These multiplexed
signals provide a 32/64-bit address and
64-bit data bus.
PCI_CBEn[7:0]PCI/X BidirCommand/Byte Enables. These
multiplexed signals indicate the current
transaction type.
PCI_CLKPCI/X InPCI Input Clock. This signal provides
timing for the Tsi384, either from an
external clock or from one of the
PCI_CLKO[4:0] signals (see
“Clocking”).
PCI_CLKO[4:0]PCI/X OutPCI Output Clock. PCI_CLKO[3:0] are
for driving four devices, and
PCI_CLKO[4] can feed back to
PCI_CLK to compensate for PCB track
length (see “Clocking”).
PCI_DEVSELnPCI/X BidirDevice Select. A target device asserts
this signal when it decodes its address
on the bus. The master samples the
signal at the beginning of a transaction,
and the target rescinds it at the end of
the transaction.
Pull up (8.2K) to 3.3V.
Pull up (8.2K) to 3.3V on
PCI_AD[63:32].
Pull up (8.2K) to 3.3V on
PCI_CBE[7:4].
None.
Point-to-point connection to PCI/X
device. IDT recommends a 33 Ohm
series termination resistor.
Pull up (8.2K) to 3.3V.
a
a
a
a
PCI_FRAMEnPCI/X BidirFrame. The current initiator drives this
signal to indicate the start and duration
of a transaction, and the bus target
samples it. The bus master rescinds the
signal at the end of the transaction.
Integrated Device Technology
www.idt.com
Pull up (8.2K) to 3.3V.
Tsi384 User Manual
a
May 5, 2014
Table 3: PCI/X Interface Signals (Continued)
NamePin TypeDescriptionDesign Recommendation
2. Signal Descriptions30
PCI_GNTn[3:0]PCI/X Bidir /
PCI/X Out
PCI_INTDnPCI/X InInterrupt D. Pull up (2.4K) to 3.3V.
PCI_INTCnPCI/X InInterrupt C. Pull up (2.4K) to 3.3V.
PCI_INTBnPCI/X InInterrupt B. Pull up (2.4K) to 3.3V.
PCI_INTAnPCI/X InInterrupt A. Pull up (2.4K) to 3.3V.
PCI_IRDYnPCI/X BidirInitiator Ready. The bus master asserts
Bus Grant. The Tsi384 uses these
multifunction signals to grant access to
the PCI/X bus; however, they are used
differently depending on whether or not
the Tsi384 PCI/X arbiter is used. If the
arbiter is used, then PCI_GNTn[3:0] are
outputs used by the Tsi384 to grant
access to the bus (see “PCI/X
Arbitration”).
If an external arbiter is used,
PCI_GNTn[0] is an input that is driven
by the arbiter to grant the Tsi384 access
to the bus. The remaining pins,
PCI_GNTn[3:1], remain as outputs.
The input/output mode is controlled by
the PWRUP_EN_ARB pin (see
“Power-up Signals”).
this signal to indicate it is ready to
complete the current transaction.
PCI_GNTn[3:0] outputs connect directly
to the PCI device’s PCI_GNTn inputs.
Pull ups are not required on unused
outputs.
Pull up (8.2K) to 3.3V.
PCI_M66ENPCI/X In66-MHz Enable. This signal enables the
PCI Interface for 66-MHz operation.
0 = 33-MHz operation
1 = 66-MHz operation
This signal is ignored in PCI-X mode.
PCI_M66EN must be stable and valid
around the rising edge of
PCIE_PERSTn (see “Reset”).
PCI_PARPCI/X BidirParity. This signal carries even parity
across PCI_AD[31:0] and
PCI_CBEn[3:0]. The bus master
asserts this signal for the address and
write data phases. The bus target
asserts it for read data phases.
Tsi384 User Manual
May 5, 2014
Em
bedded designs
Pull down for 33 MHz and slower
operation. Pull up for greater than
33-MHz operation.
Bused designs using PCI/X slots for
add- in cards
Place a pull-up resistor (~5K to 10K) on
M66EN and route the signal from slot to
slot.
No pull-up or pull-down resistor is
required.
b
Integrated Device Technology
www.idt.com
Loading...
+ 251 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.