Texas Instruments and its subsidiaries (TI) reserve the right to make changes to their products
or to discontinue any product or service without notice, and advise customers to obtain the latest
version of relevant information to verify , before placing orders, that information being relied on
is current and complete. All products are sold subject to the terms and conditions of sale supplied
at the time of order acknowledgement, including those pertaining to warranty, patent
infringement, and limitation of liability.
TI warrants performance of its semiconductor products to the specifications applicable at the
time of sale in accordance with TI’s standard warranty. Testing and other quality control
techniques are utilized to the extent TI deems necessary to support this warranty . Specific testing
of all parameters of each device is not necessarily performed, except those mandated by
government requirements.
CERTAIN APPLICATIONS USING SEMICONDUCTOR PRODUCTS MAY INVOLVE
POTENTIAL RISKS OF DEATH, PERSONAL INJURY, OR SEVERE PROPERTY OR
ENVIRONMENTAL DAMAGE (“CRITICAL APPLICATIONS”). TI SEMICONDUCTOR
PRODUCTS ARE NOT DESIGNED, AUTHORIZED, OR WARRANTED TO BE SUIT ABLE FOR
USE IN LIFE-SUPPORT DEVICES OR SYSTEMS OR OTHER CRITICAL APPLICATIONS.
INCLUSION OF TI PRODUCTS IN SUCH APPLICATIONS IS UNDERSTOOD TO BE FULLY
AT THE CUSTOMER’S RISK.
In order to minimize risks associated with the customer’s applications, adequate design and
operating safeguards must be provided by the customer to minimize inherent or procedural
hazards.
TI assumes no liability for applications assistance or customer product design. TI does not
warrant or represent that any license, either express or implied, is granted under any patent right,
copyright, mask work right, or other intellectual property right of TI covering or relating to any
combination, machine, or process in which such semiconductor products or services might be
or are used. TI’s publication of information regarding any third party’s products or services does
not constitute TI’s approval, warranty or endorsement thereof.
The Texas Instruments PCI2250 PCI-to-PCI bridge provides a high performance connection path between two
peripheral component interconnect (PCI) buses. Transactions occur between masters on one PCI bus and targets
on another PCI bus, and the PCI2250 allows bridged transactions to occur concurrently on both buses. The bridge
supports burst-mode transfers to maximize data throughput, and the two bus traffic paths through the bridge act
independently.
The PCI2250 bridge is compliant with the
loading limits of 10 devices per PCI bus and one PCI device per expansion slot by creating hierarchical buses. The
PCI2250 provides two-tier internal arbitration for up to four secondary bus masters and may be implemented with
an external secondary PCI bus arbiter.
The PCI2250 provides compact-PCI (CPCI) hot-swap extended capability, which makes it an ideal solution for
multifunction compact-PCI cards and adapting single function cards to hot-swap compliance.
The PCI2250 bridge is compliant with the
or subtractive decoding on the primary interface, and provides several additional decode options that make it an ideal
bridge to custom PCI applications. Two extension windows are included, and the PCI2250 provides decoding of serial
and parallel port addresses.
The PCI2250 is compliant with
PCI2250 offers PCI CLKRUN bridging support for low-power mobile and docking applications. The PCI2250 has been
designed to lead the industry in power conservation. An advanced CMOS process is utilized to achieve low system
power consumption while operating at PCI clock rates up to 33 MHz.
PCI Power Management Interface Specification Revisions 1.0 and 1.1
PCI Local Bus Specification
, and can be used to overcome the electrical
PCI-to-PCI Bridge Specification
. It can be configured for positive decoding
. Also, the
1.2Features
The PCI2250 supports the following features:
•Configurable for
•Compact-PCI friendly silicon as defined in the
•3.3-V core logic with universal PCI interface compatible with 3.3-V and 5-V PCI signaling environments
•Two 32-bit, 33-MHz PCI buses
PCI Power Management Interface Specification Revision 1.0 or 1.1
Compact-PCI Hot Swap Specification
support
•Provides internal two-tier arbitration for up to four secondary bus masters and supports an external
secondary bus arbiter
•Burst data transfers with pipeline architecture to maximize data throughput in both directions
•Provides programmable extension windows and port decode options
•Independent read and write buffers for each direction
•Provides five secondary PCI clock outputs
•Predictable latency per
•Propagates bus locking
•Secondary bus is driven low during reset
•Provides VGA palette memory and I/O, and subtractive decoding options
•Advanced submicron, low-power CMOS technology
PCI Local Bus Specification
1–1
•Fully compliant with
PCI-to-PCI Bridge Architecture Specification
•Packaged in 160-pin QFP (PCM) and 176-pin thin QFP (PGF)
1.3Related Documents
•
Advanced Configuration and Power Interface (ACPI) Revision 1.0
Primary PCI bus clock. P_CLK provides timing for all transactions on the primary PCI bus. All
primary PCI signals are sampled at rising edge of P_CLK.
PCI reset. When the primary PCI bus reset is asserted, P_RST causes the bridge to put all output
buffers in a high-impedance state and reset all internal registers. When asserted, the device is
completely nonfunctional. During P_RST
is driven high if hot-swap is enabled. After P_RST
, the secondary interface is driven low and NO/HSLED
is deasserted, the bridge is in its default state.
Table 2–6. Primary PCI Address and Data
I/ODESCRIPTION
Primary address/data bus. These signals make up the multiplexed PCI address and data
bus on the primary interface. During the address phase of a primary bus PCI cycle,
I/O
P_AD31–P_AD0 contain a 32-bit address or other destination information. During the data
phase, P_AD31–P_AD0 contain data.
P_C/BE3
P_C/BE2
P_C/BE1
P_C/BE0
82
95
107
122
91
105
117
135
Primary bus commands and byte enables. These signals are multiplexed on the same PCI
terminals. During the address phase of a primary bus cycle, P_C/BE3
bus command. During the data phase, this 4-bit bus is used as byte enables. The byte
enables determine which byte paths of the full 32-bit data bus carry meaningful data.
I/O
P_C/BE0
P_C/BE2
(P_AD31–P_AD24).
applies to byte 0 (P_AD7–P_AD0), P_C/BE1 applies to byte 1 (P_AD15–P_AD8),
applies to byte 2 (P_AD23–P_AD16), and P_C/BE3 applies to byte 3
–P_C/BE0 define the
2–7
Table 2–7. Primary PCI Interface Control
TERMINAL
NAME
P_DEVSEL100110I/O
P_FRAME
P_GNT
P_IDSEL8393I
P_IRDY97107I/O
P_PAR106116I/O
P_PERR
P_REQ6975O
P_SERR105115O
P_STOP101111I/O
P_TRDY99109I/O
PCM
NUMBER
96106I/O
6874I
104114I/O
PGF
NUMBER
I/ODESCRIPTION
Primary device select. The bridge asserts P_DEVSEL to claim a PCI cycle as the target
device. As a PCI initiator on the primary bus, the bridge monitors P_DEVSEL
responds. If no target responds before a time-out occurs, then the bridge terminates the cycle
with a master abort.
Primary cycle frame. P_FRAME is driven by the initiator of a primary bus cycle. P_FRAME
is asserted to indicate that a bus transaction is beginning, and data transactions continue
while this signal is asserted. When P_FRAME
in the final data phase.
Primary bus grant to bridge. P_GNT is driven by the primary PCI bus arbiter to grant the bridge
access to the primary PCI bus after the current data transaction has completed. P_GNT
or may not follow a primary bus request, depending on the primary bus parking algorithm.
Primary initialization device select. P_IDSEL selects the bridge during configuration space
accesses. P_IDSEL can be connected to one of the upper 16 PCI address lines on the primary
PCI bus.
Note: There is no IDSEL signal interfacing the secondary PCI bus; thus, the entire
configuration space of the bridge can only be accessed from the primary bus.
Primary initiator ready. P_IRDY indicates the ability of the primary bus initiator to complete the
current data phase of the transaction. A data phase is completed on a rising edge of P_CLK
where both P_IRDY
asserted, wait states are inserted.
Primary parity. In all primary bus read and write cycles, the bridge calculates even parity
across the P_AD and P_C/BE
this parity indicator with a one-P_CLK delay. As a target during PCI read cycles, the calculated
parity is compared to the initiator parity indicator; a miscompare can result in a parity error
assertion (P_PERR
Primary parity error indicator. P_PERR is driven by a primary bus PCI device to indicate that
calculated parity does not match P_PAR when P_PERR
command register (offset 04h, see Section 4.3).
Primary PCI bus request. P_REQ is asserted by the bridge to request access to the primary
PCI bus as an initiator.
Primary system error. Output pulsed from the bridge when enabled through the command
register (offset 04h, see Section 4.3) indicating a system error has occurred. The bridge need
not be the target of the primary PCI cycle to assert this signal. When bit 1 is enabled in the
bridge control register (offset 3Eh, see Section 4.32), this signal will also pulse indicating that
a system error has occurred on one of the subordinate buses downstream from the bridge.
Primary cycle stop signal. This signal is driven by a PCI target to request the initiator to stop
the current primary bus transaction. This signal is used for target disconnects and is
commonly asserted by target devices which do not support burst data transfers.
Primary target ready. P_TRDY indicates the ability of the primary bus target to complete the
current data phase of the transaction. A data phase is completed on the rising edge of P_CLK
where both P_IRDY
asserted, wait states are inserted.
and P_TRDY are asserted. Until P_IRDY and P_TRDY are both sampled
buses. As an initiator during PCI write cycles, the bridge outputs
).
and P_TRDY are asserted. Until P_IRDY and P_TRDY are both sample
is deasserted, the primary bus transaction is
is enabled through bit 6 of the
until a target
may
2–8
TERMINAL
NAME
S_CLKOUT4
S_CLKOUT3
S_CLKOUT2
S_CLKOUT1
S_CLKOUT0
S_CLK
S_CFN4955I
S_RST4854O
PCM
NUMBER
61
59
57
55
53
5157I
PGF
NUMBER
67
65
63
61
59
T able 2–8. Secondary PCI System
I/ODESCRIPTION
Secondary PCI bus clocks. Provide timing for all transactions on the secondary PCI bus.
Each secondary bus device samples all secondary PCI signals at the rising edge of its
O
corresponding S_CLKOUT input.
Secondary PCI bus clock input. This input syncronizes the PCI2250 to the secondary bus
clocks.
Secondary external arbiter enable. When this signal is high, the secondary external arbiter
is enabled. When the external arbiter is enabled, the S_REQ0
secondary bus grant input to the bridge and S_GNT0
master request to the external arbiter on the secondary bus.
Secondary PCI reset. S_RST is a logical OR of P_RST and the state of the secondary bus
reset bit of the bridge control register (offset 3Eh, see Section 4.32). S_RST
with respect to the state of the secondary interface CLK signal.
Secondary address/data bus. These signals make up the multiplexed PCI address and data
bus on the secondary interface. During the address phase of a secondary bus PCI cycle,
I/O
S_AD31–S_AD0 contain a 32-bit address or other destination information. During the data
phase, S_AD31–S_AD0 contain data.
Secondary bus commands and byte enables. These signals are multiplexed on the same PCI
terminals. During the address phase of a secondary bus cycle, S_C/BE3
bus command. During the data phase, this 4-bit bus is used as byte enables. The byte enables
I/O
determine which byte paths of the full 32-bit data bus carry meaningful data. S_C/BE0
to byte 0 (S_AD7–S_AD0), S_C/BE1
to byte 2 (S_AD23–S_AD16), and S_C/BE3
applies to byte 1 (S_AD15–S_AD8), S_C/BE2 applies
applies to byte 3 (S_AD31–S_AD24).
–S_C/BE0 define the
applies
2–10
Table 2–10. Secondary PCI Interface Control
TERMINAL
NAME
S_DEVSEL79I/O
S_FRAME1113I/O
S_GNT3
S_GNT2
S_GNT1
S_GNT0
S_IRDY1012I/O
S_PAR23I/O
S_PERR
S_REQ3
S_REQ2
S_REQ1
S_REQ0
S_SERR
S_STOP68I/O
S_TRDY911I/O
PCM
NUMBER
47
45
44
43
46I/O
42
39
38
37
35I
PGF
NUMBER
53
51
50
49
47
42
40
39
I/ODESCRIPTION
O
Secondary device select. The bridge asserts S_DEVSEL to claim a PCI cycle as the target
device. As a PCI initiator on the secondary bus, the bridge monitors S_DEVSEL
responds. If no target responds before a timeout occurs, then the bridge terminates the cycle
with a master abort.
Secondary cycle frame. S_FRAME is driven by the initiator of a secondary bus cycle.
S_FRAME
continue while S_FRAME
transaction is in the final data phase.
Secondary bus grant to the bridge. The bridge provides internal arbitration and these signals
are used to grant potential secondary PCI masters access to the bus. Five potential initiators
(including the bridge) can be located on the secondary PCI bus.
When the internal arbiter is disabled, S_GNT0
request signal for the bridge.
Secondary initiator ready. S_IRDY indicates the ability of the secondary bus initiator to
complete the current data phase of the transaction. A data phase is completed on a rising
edge of S_CLK where both S_IRDY
are both sample asserted, wait states are inserted.
Secondary parity. In all secondary bus read and write cycles, the bridge calculates even
parity across the S_AD and S_C/BE
outputs this parity indicator with a one-S_CLK delay . As a target during PCI read cycles, the
calculated parity is compared to the initiator parity indicator. A miscompare can result in a
parity error assertion (S_PERR
Secondary parity error indicator. S_PERR is driven by a secondary bus PCI device to
indicate that calculated parity does not match S_PAR when S_PERR
bit 6 of the command register (offset 04h, see Section 4.3).
Secondary PCI bus request signals. The bridge provides internal arbitration, and these
signals are used as inputs from secondary PCI bus initiators requesting the bus. Five
potential initiators (including the bridge) can be located on the secondary PCI bus.
I
When the internal arbiter is disabled, the S_REQ0
secondary bus grant for the bridge.
Secondary system error. S_SERR is passed through the primary interface by the bridge if
enabled through the bridge control register (offset 3Eh, see Section 4.32). S_SERR
asserted by the bridge.
Secondary cycle stop signal. S_STOP is driven by a PCI target to request the initiator to stop
the current secondary bus transaction. S_STOP
commonly asserted by target devices that do not support burst data transfers.
Secondary target ready. S_TRDY indicates the ability of the secondary bus target to
complete the current data phase of the transaction. A data phase is completed on a rising
edge of S_CLK where both S_IRDY
are both sample asserted, wait states are inserted.
is asserted to indicate that a bus transaction is beginning and data transfers
is asserted. When S_FRAME is deasserted, the secondary bus
is reconfigured as an external secondary bus
and S_TRDY are asserted. Until S_IRDY and S_TRDY
buses. As an initiator during PCI write cycles, the bridge
).
is enabled through
signal is reconfigures as an external
is used for target disconnects and is
and S_TRDY are asserted. Until S_IRDY and S_TRDY
until a target
is never
2–11
Table 2–11. Miscellaneous Terminals
TERMINAL
NAME
GOZ6369INAND tree enable pin.
NO/HSLED6268I/ONAND tree out when GOZ is asserted. Hot-swap LED when GOZ is deasserted.
MS0
MS1/BPCC159174I
P_MFUNC102112I/O
S_MFUNC57I/O
PCM
NUMBER
120132IMode select 0
PGF
NUMBER
I/ODESCRIPTION
Mode select 1 when mode select 0 is low, bus power clock control when mode select 0 is
high.
Primary multifunction terminal. This terminal can be configured as P_CLKRUN, P_LOCK,
or HS_ENUM
Secondary multifunction terminal. This terminal can be configured as S_CLKRUN,
S_LOCK
depending on the values of MS0 and MS1.
, or HS_SWITCH depending on the values of MS0 and MS1.
Primary bus-signaling environment supply. P_V
protection circuitry on primary bus I/O signals.
Secondary bus-signaling environment supply. S_V
protection circuitry on secondary bus I/O signals.
DESCRIPTION
CCP
CCP
is used in
is used in
2–12
3 Feature/Protocol Descriptions
The following sections give an overview of the PCI2250 PCI-to-PCI bridge features and functionality. Figure 3–1
shows a simplified block diagram of a typical system implementation using the PCI2250.
CPU
Host Bus
PCI Bus 0
PCI2250
PCI Bus 1
Host
Bridge
Memory
PCI
Device
PCI Bus 2
PCI2250
PCI Option Slot
PCI
Device
PCI
Device
Figure 3–1. System Block Diagram
PCI
Device
PCI Option Card
PCI Option Card
(Option)
3.1Introduction to the PCI2250
The PCI2250 is a bridge between two PCI buses and is compliant with both the
PCI-to-PCI Bridge Specification
. The bridge supports two 32-bit PCI buses operating at a maximum of 33 MHz. The
primary and secondary buses operate independently in either a 3.3-V or 5-V signaling environment. The core logic
of the bridge, however, is powered at 3.3 V to reduce power consumption.
Host software interacts with the bridge through internal registers. These internal registers provide the standard PCI
status and control for both the primary and secondary buses. Many vendor-specific features that exist in the TI
extension register set are included in the bridge. The PCI configuration header of the bridge is only accessible from
the primary PCI interface.
The bridge provides internal arbitration for the four possible secondary bus masters, and provides each with a
dedicated active low request/grant pair (REQ
/GNT). The arbiter features a two-tier rotational scheme with the
PCI2250 bridge defaulting to the highest priority tier. The bus parking scheme is also configurable and can be set
to either park grant (GNT
) on the bridge or on the last mastering device.
Upon system power up, power-on self-test (POST) software configures the bridge according to the devices that exist
on subordinate buses, and enables the performance-enhancing features of the PCI2250. In a typical system, this is
the only communication with the bridge internal register set.
PCI Local Bus Specification
and the
3–1
3.2PCI Commands
The bridge responds to PCI bus cycles as a PCI target device based on the decoding of each address phase and
internal register settings. Table 3–1 lists the valid PCI bus cycles and their encoding on the command/byte enables
(C/BE
The bridge never responds as a PCI target to the interrupt acknowledge, special cycle, dual address cycle, or
reserved commands. The bridge does, however, initiate special cycles on both interfaces when a type 1 configuration
cycle issues the special cycle request. The remaining PCI commands address either memory , I/O, or configuration
space. The bridge accepts PCI cycles by asserting DEVSEL as a medium-speed device, i.e., DEVSEL is asserted
two clock cycles after the address phase.
The PCI2250 converts memory write and invalidate commands to memory write commands when forwarding
transactions from either the primary or secondary side of the bridge.
3.3Configuration Cycles
The
PCI Local Bus Specification
bridge decodes each type differently . T ype 0 configuration cycles are intended for devices on the primary bus, while
type 1 configuration cycles are intended for devices on some hierarchically subordinate bus. The difference between
these two types of cycles is the encoding of the primary PCI (P_AD) bus during the address phase of the cycle.
Figure 3–2 shows the P_AD bus encoding during the address phase of a type 0 configuration cycle. The 6-bit register
number field represents an 8-bit address with the two lower bits masked to 0, indicating a doubleword boundary . This
results in a 256-byte configuration address space per function per device. Individual byte accesses may be selected
within a doubleword by using the P_C/BE
31
defines two types of PCI configuration read and write cycles: type 0 and type 1. The
signals during the data phase of the cycle.
Reserved
11 1078
Function
Number
Register
Number
102
00
3–2
Figure 3–2. PCI AD31–AD0 During Address Phase of a Type 0 Configuration Cycle
Loading...
+ 59 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.