XIO2001 PCI Express™ to PCI Bus Translation Bridge
Data Manual
PRODUCTION DATA information is current as of publication date.
Products conform to specifications per the terms of the Texas
Instruments standard warranty. Production processing does not
necessarily include testing of all parameters.
Please be aware that an important notice concerning availability, standard warranty, and use in critical applications of Texas
Instruments semiconductor products and disclaimers thereto appears at the end of this data sheet.
2PowerPad, MicroStar are trademarks of Texas Instruments.
3PCI Express is a trademark of PCI-SIG.
4All other trademarks are the property of their respective owners.
PRODUCTION DATA information is current as of publication date.
Products conform to specifications per the terms of the Texas
Instruments standard warranty. Production processing does not
necessarily include testing of all parameters.
The Texas Instruments XIO2001 is a PCI Express to PCI local bus translation bridge that provides full PCI
Express and PCI local bus functionality and performance.
2.1Description
The XIO2001 is a single-function PCI Express to PCI translation bridge that is fully compliant to the PCI
Express to PCI/PCI-X Bridge Specification, Revision 1.0. For downstream traffic, the bridge
simultaneously supports up to eight posted and four non-posted transactions. For upstream traffic, up to
six posted and and four non-posted transactions are simultaneously supported.
The PCI Express interface is fully compliant to the PCI Express Base Specification, Revision 2.0.
The PCI Express interface supports a ×1 link operating at full 250 MB/s packet throughput in each
direction simultaneously. Also, the bridge supports the advanced error reporting including extended CRC
(ECRC) as defined in the PCI Express Base Specification. Supplemental firmware or software is required
to fully utilize both of these features.
Robust pipeline architecture is implemented to minimize system latency across the bridge. If parity errors
are detected, then packet poisoning is supported for both upstream and downstream operations.
The PCI local bus is fully compliant with the PCI Local Bus Specification (Revision 2.3) and associated
programming model. Also, the bridge supports the standard PCI-to-PCI bridge programming model. The
PCI bus interface is 32-bit and can operate at either 25 MHz, 33 MHz, 50 MHz, or 66 MHz. Also, the PCI
interface provides fair arbitration and buffered clock outputs for up to 6 subordinate devices.
www.ti.com
Power management (PM) features include active state link PM, PME mechanisms, the beacon and wake
protocols, and all conventional PCI D-states. If the active state link PM is enabled, then the link
automatically saves power when idle using the L0s and L1 states. PM active state NAK, PM PME, and
PME-to-ACK messages are supported. Standard PCI bus power management features provide several
low power modes, which enable the host system to further reduce power consumption.
The bridge has additional capabilities including, but not limited to, serial IRQ with MSI messages, serial
EEPROM, power override, clock run, PCI Express clock request and PCI bus LOCK. Also, five
general-purpose inputs and outputs (GPIOs) are provided for further system control and customization.
2.2Related Documents
•PCI Express to PCI/PCI-X Bridge Specification, Revision 1.0
Throughout this data manual, several conventions are used to convey information. These conventions are
listed below:
1. To identify a binary number or field, a lower case b follows the numbers. For example: 000b is a 3-bit
binary field.
2. To identify a hexadecimal number or field, a lower case h follows the numbers. For example: 8AFh is a
12-bit hexadecimal field.
3. All other numbers that appear in this document that do not have either a b or h following the number
are assumed to be decimal format.
4. If the signal or terminal name has a bar above the name (for example, GRST), then this indicates the
logical NOT function. When asserted, this signal is a logic low, 0, or 0b.
5. Differential signal names end with P, N, +, or – designators. The P or + designators signify the positive
signal associated with the differential pair. The N or – designators signify the negative signal
associated with the differential pair.
6. RSVD indicates that the referenced item is reserved.
7. In Sections 4 through 6, the configuration space for the bridge is defined. For each register bit, the
software access method is identified in an access column. The legend for this access column includes
the following entries:
– r – read access by software
– u – updates by the bridge internal hardware
– w – write access by software
– c – clear an asserted bit with a write-back of 1b by software. Write of zero to the field has no effect
– s – the field may be set by a write of one. Write of zero to the field has no effect
– na – not accessible or not applicable
1/2010DCorrected PNP pinout, replaced Ordering Information with Package Option Addendum
Added PNP package and ESD ratings
Removed terminal assignment tables for all packages
REVISION COMMENTS
2.5Terminal Assignments
The XIO2001 is available in either a 169-ball ZGU MicroStar BGA or a 144−ball ZAJ MicroStar BGA
package.
Figure 2-1 shows a terminal diagram of the ZGU package.
Figure 2-2 shows a terminal diagram of the ZAJ package.
Figure 2-3 shows a terminal diagram of the PNP package.
The following tables give a description of the terminals. These terminals are grouped in tables by
functionality. Each table includes the terminal name, terminal number, I/O type, and terminal description.
The following list describes the different input/output cell types that appear in the terminal description
tables:
•HS DIFF IN = High speed differential input
•HS DIFF OUT = High speed differential output
•PCI BUS = PCI bus 3-state bidirectional buffer with 3.3-V or 5.0-V clamp rail.
•LV CMOS = 3.3-V low voltage CMOS input or output with 3.3-V clamp rail
•BIAS = Input/output terminals that generate a bias voltage to determine a driver's operating current
•Feed through = these terminals connect directly to macros within the part and not through an input or
output cell.
•PWR = Power terminal
•GND = Ground terminal
Table 2-1. Power Supply Terminals
SIGNALDESCRIPTION
PCIRA01, K03D03, J03I/OResistorPCI Rail. 5.0-V or 3.3-V PCI bus clamp voltage to set
V
DD_15
V
DDA_15
V
DD_33
V
DD_33_AUX
V
DDA_33
ZGUZAJPNPI/OEXTERNAL
BALL #BALL #PIN #TYPEPARTS
maximum I/O voltage tolerance of the secondary PCI
bus signals. Connect this terminal to the secondary
PCI bus I/O clamp rail through a 1kΩ resistor.
G04, K07,J08, H08,21, 53, 113PWRBypass1.5-V digital core power terminals
D07, H10,J07, G08,capacitors
G10, F10N13, K13,
G11, F11
F13, H13E12, H12PWRPi filter1.5-V analog power terminal
E04, H03,E05, G06,7, 19, 33, 46,PWRBypass3.3-V digital I/O power terminal
Pullup or
pulldown0 = 100-MHz differential common reference clock
resistorused.
Submit Documentation Feedback
Product Folder Link(s): XIO2001
Clock request. When asserted low, requests
upstream device start clock in cases where clock
may be removed in L1.
Note: Since CLKREQ is an open-drain output
buffer, a system side pullup resistor is required.
PCI Express reset input. The PERST signal
identifies when the system power is stable and
generates an internal power on reset.
Note: The PERST input buffer has hysteresis.
Reference clock select. This terminal selects the
1 = 125-MHz single-ended, reference clock used.
XIO2001
www.ti.com
SCPS212D–MAY 2009–REVISED JANUARY 2010
Table 2-4. PCI Express Terminals (continued)
SIGNALDESCRIPTION
REFCLK+C13C1393DIHS DIFFV
REFCLK–C12B1394DIHS DIFFV
REF0_PCIEK12M1371I/OBIAS–External reference resistor + and – terminals for
REF1_PCIEK13L1372setting TX driver current. An external resistance
RXPE13E1387DIHS DIFFV
RXNE12D1388IN–the differential receive pair for the single PCI
TXPG13H1380DOHS DIFFV
TXNG12G1381OUTthe differential transmit pair for the single PCI
WAKEM13L1268OLVV
ZGUZAJPNPI/OCELLCLAMPEXTERNAL
BALL #BALL #PIN #TYPETYPERAILPARTS
INcomprise the differential input pair for the
INcomprise the differential input pair for the
CMOS
DD_33
DD_33
SS
DD_15
DD_33_
COMBIO
–100-MHz system reference clock. For a
Capacitor
for VSSfor
single-
ended node
External
resistor
Series
capacitor
–
Reference clock. REFCLK+ and REFCLK–
single-ended, 125-MHz system reference clock,
use the REFCLK+ input.
Reference clock. REFCLK+ and REFCLK–
100-MHz system reference clock. For a
single-ended, 125-MHz system reference clock,
attach a capacitor from REFCLK– to VSS.
of 14,532-Ω is connected between REF0_PCIE
and REF1_PCIE terminals. To eliminate the need
for a custom resistor, two series resistors are
recommended: a 14.3-kΩ, 1% resistor and a
232-Ω, 1% resistor.
High-speed receive pair. RXP and RXN comprise
Express lane supported.
High-speed transmit pair. TXP and TXN comprise
Express lane supported.
Wake is an active low signal that is driven low to
reactivate the PCI Express link hierarchy’s main
power rails and reference clocks.
Note: Since WAKE is an open-drain output
buffer, a system side pullup resistor is required.
CLKF03F0113IPCIPCIRPCI clock input. This is the clock input
CLKOUT0B05B05120OPCIPCIRPCI clock outputs. These clock outputs
CLKOUT1B06B06117Busare used to clock the PCI bus. If the
CLKOUT2A07B07114bridge PCI bus clock outputs are used,
CLKOUT3B07A07112–then CLKOUT6 must be connected to
CLKOUT4A09A08107the CLK input.
CLKOUT5A10A10104
CLKOUT6B11C1099
DEVSELH02H0220I/OPCIPCIRPullupPCI device select
FRAMEJ02J0124I/OPCIPCIRPullupPCI frame
GNT5B10B11101OPCIPCIRPCI grant outputs. These signals are
GNT4A11B10103Busused for arbitration when the PCI bus
GNT3B09B09106is the secondary bus and an external
GNT2B08B08109arbiter is not used. GNT0 is used as
GNT1C06A06115the REQ for the bridge when an
GNT0A05A05118external arbiter is used.
INTAM06N0647IPCIPCIRPCI interrupts A–D. These signals are
INTBN06L0648Businterrupt inputs to the bridge on the
INTCM07M0749secondary PCI bus.
INTDL07N0750
IRDYJ01H0323I/OPCIPCIRPullupPCI initiator ready
LOCKM08N0854I/OPCIPCIRThis terminal functions as PCI LOCK
M66ENL06M0645IPCIPCIR66-MHz mode enable
PARF01G0115I/OPCIPCIRPCI bus parity
PERRG02G0317I/OPCIPCIRPullupPCI parity error
PMEL12M1267ILVV
ZGUZAJPNPI/OCELLCLAMPEXTERNAL
BALL #BALL #PIN #TYPETYPERAILPARTS
–
Busto the PCI bus core.
Busresistor per
Busresistor per
Busresistor per
Buswhen bit 12 (LOCK_EN) is set in the
Bus
Bus
Busresistor per
CMOS
DD_33_
COMBIO
–
PCI spec
PCI spec
–
Pullup
resistor per
PCI spec
PCI spec
Pullup
resistor per
PCI spec
PullupPCLK66_SELislowthenthe
resistor perfrequency will be 25 MHz.
PCI spec
–
PCI spec
Pullup
resistor per
PCI spec
general control register (see
Section 4.65).
Note: In lock mode, an external pullup
resistor is required to prevent the
LOCK signal from floating.
0 = Secondary PCI bus and clock
outputs operate at 33 MHz. If
1 = Secondary PCI bus and clock
outputs operate at 66 MHz. If
PCLK66_SELislowthenthe
frequency will be 50 MHz.
Pullup resistor per PCI spec PCI power
management event. This terminal may
be used to detect PME events from a
PCI device on the secondary bus.
REQ5A12C09102IPCIPCIRPCI request inputs. These signals are
REQ4C09A09105BusIf unused, a used for arbitration on the secondary
REQ3C08C08108weak pullup PCI bus when an external arbiter is not
REQ2A08C07110resistor perused. REQ0 is used as the GNT for
REQ1A06C06116PCI specthe bridge when an external arbiter is
REQ0A04A04119used.
PRSTN07L0751OPCIPCIRPCI reset. This terminal is an output to
SERRG03G0216I/OPCIPCIRPullupPCI system error
STOPG01H0118I/OPCIPCIRPullupPCI stop
TRDYH01J0222I/OPCIPCIRPullupPCI target ready
ZGUZAJPNPI/OCELLCLAMPEXTERNAL
BALL #BALL #PIN #TYPETYPERAILPARTS
Busthe secondary PCI bus.
–
Busresistor per
PCI spec
Busresistor per
PCI spec
Busresistor per
PCI spec
Table 2-6. JTAG Terminals
SIGNALDESCRIPTION
JTAG_TCKM12N1265ILVV
JTAG_TDIN12L1063ILVV
JTAG_TDOM11N1161OLVV
JTAG_TMSL10L1164ILVV
ZGUZAJPNPI/OCELLCLAMPEXTERNAL
BALL #BALL #PIN #TYPETYPERAILPARTS
CMOSprovides the clock for the internal TAP
DD_33
Optional pullup
resistor
CMOSinstructions and data are received on
DD_33
Optional pullup Note: This terminal has an internal
resistoractive pullup resistor. The pullup is
CMOSserial output for test instructions and
DD_33
–
CMOSreceived at JTAG_TMS is decoded by
DD_33
Optional pullup
resistor
JTAG test clock input. This signal
controller.
Note: This terminal has an internal
active pullup resistor. The pullup is
active at all times.
Note: This terminal should be tied to
ground or pulled low if JTAG is not
required.
JTAG test data input. Serial test
this terminal.
active at all times.
Note: This terminalcan be left
unconnected if JTAG is not required.
JTAG test data output. This terminal the
data.
Note: This terminalcan be left
unconnected if JTAG is not required.
JTAG test mode select. The signal
the internal TAP controller to control test
operations.
Note: This terminal has an internal
active pullup resistor. The pullup is
active at all times.
Note: This terminalcan be left
unconnected if JTAG is not required.
JTAG test reset. This terminal provides
of the TAP controller.
Note: This terminal has an internal
active pullup resistor. The pullup is
active at all times.
Note: This terminal should be tied to
ground or pulled low if JTAG is not
required.
Table 2-7. Miscellaneous Terminals
SIGNALDESCRIPTION
CLKRUN_EA13C1196ILVV
NCMOS
EXT_ARB_C10A1297ILVV
ENCMOS
GPIO0 //N09N0955I/OLVV
CLKRUNCMOS
GPIO1 //M09M0956I/OLVV
PWR_OVRCMOS
D
GPIO2N10N1057I/OLVV
ZGUZAJPNPI/OCELLCLAMPEXTERNAL
BALL #BALL #PIN #TYPETYPERAILPARTS
DD_33
Optional
pullup
resistor
DD_33
Optional
pullup
resistor
DD_33
Optional
pullup
resistor
DD_33
–
CMOS
DD_33
–
Clock run enable
0 = Clock run support disabled
1 = Clock run support enabled
Note: The CLKRUN_EN input buffer has an
internal active pulldown. This pulldown is active
at all times.
External arbiter enable
0 = Internal arbiter enabled
1 = External arbiter enabled
Note: The EXT_ARB_EN input buffer has an
internal active pulldown. This pulldown is active
at all times.
General-purpose I/O 0/clock run. This terminal
functions as a GPIO controlled by bit 0
(GPIO0_DIR) in the GPIO control register (see
Section 4.59) or the clock run terminal. This
terminal is used as clock run input when the
bridge is placed in clock run mode.
Note: In clock run mode, an external pullup
resistor is required to prevent the CLKRUN
signal from floating.
Note: This terminal has an internal active pullup
resistor. The pullup is only active when reset is
asserted or when the GPIO is configured as an
input.
General-purpose I/O 1/power override. This
terminal functions as a GPIO controlled by bit 1
(GPIO1_DIR) in the GPIO control register (see
Section 4.59) or the power override output
terminal. GPIO1 becomes PWR_OVRD when
bits 22:20 (POWER_OVRD) in the general
control register are set to 001b or 011b (see
Section 4.65).
Note: This terminal has an internal active pullup
resistor. The pullup is only active when reset is
asserted or when the GPIO is configured as an
input.
General-purpose I/O 2. This terminal functions
as a GPIO controlled by bit 2 (GPIO2_DIR) in
the GPIO control register (see Section 4.59).
Note: This terminal has an internal active pullup
resistor. The pullup is only active when reset is
asserted or when the GPIO is configured as an
input.
pullupRegister (see Section 4.58). If no pullup is
resistordetected then this terminal functions as GPIO3.
DD_33
Optional
pullup
resistor
CMOS
DD_33
_COMBIO
–
DD_33
Optional
pulldown
resistor
Pullup or
pulldown
resistor
DD_33
_COMBIO
Pulldownterminal should always be tied directly to
resistorground or an optional pulldown resistor can be
GPIO3 or serial-bus data. This terminal
functions as serial-bus data if a pullup resistor is
detected on SCL or when the SBDETECT bit is
Note: In serial-bus mode, an external pullup
resistor is required to prevent the SDA signal
from floating.
GPIO4 or serial-bus clock. This terminal
functions as serial-bus clock if a pullup resistor
is detected on SCL or when the SBDETECT bit
is set in the Serial Bus Control and Status
Register (see Section 4.58). If no pullup is
detected then this terminal functions as GPIO4.
Note: In serial-bus mode, an external pullup
resistor is required to prevent the SCL signal
from floating.
Note: This terminal has an internal active pullup
resistor. The pullup is only active when reset is
asserted or when the GPIO is configured as an
input.
Global reset input. Asynchronously resets all
logic in device, including sticky bits and power
management state machines.
Note: The GRST input buffer has both
hysteresis and an internal active pullup. The
pullup is active at all times.
PCI clock select. This terminal determines the
default PCI clock frequency driven out the
CLKOUTx terminals.
0 = 50 MHz PCI Clock
1 = 66 MHz PCI Clock
Note: This terminal has an internal active pullup
resistor. This pullup is active at all times.
Note: M66EN terminal also has an affect of PCI
clock frequency.
Serial IRQ interface. This terminal functions as
a serial IRQ interface if a pullup is detected
when PERST is deasserted. If a pulldown is
detected, then the serial IRQ interface is
disabled.
This chapter provides a high-level overview of all significant device features. Figure 3-1 shows a simplified
block diagram of the basic architecture of the PCI-Express to PCI Bridge. The top of the diagram is the
PCI Express interface and the PCI bus interface is located at the bottom of the diagram.
www.ti.com
Figure 3-1. XIO2001 Block Diagram
3.1Power-Up/-Down Sequencing
The bridge contains both 1.5-V and 3.3-V power terminals. The following power-up and power-down
sequences describe how power is applied to these terminals.
In addition, the bridge has three resets: PERST, GRST and an internal power-on reset. These resets are
fully described in Section 3.2. The following power-up and power-down sequences describe how PERST
is applied to the bridge.
The application of the PCI Express reference clock (REFCLK) is important to the power-up/-down
sequence and is included in the following power-up and power-down descriptions.
See the power-down sequencing diagram in Figure 3-3. If the V
after a system shutdown, then the bridge power-down sequence is exactly the same as shown in
Figure 3-3.
DD_33_AUX
www.ti.com
terminal is to remain powered
Figure 3-3. Power-Down Sequence
3.2Bridge Reset Features
There are five bridge reset options that include internally-generated power-on reset, resets generated by
asserting input terminals, and software-initiated resets that are controlled by sending a PCI Express hot
reset or setting a configuration register bit. Table 3-1 identifies these reset sources and describes how the
bridge responds to each reset.
Table 3-1. XIO2001 Reset Options
RESETXIO2001 FEATURERESET RESPONSE
OPTION
BridgeDuring a power-on cycle, the bridge asserts an internal reset When the internal power-on reset is asserted, all control
internally-and monitors the V
generatedreaches 90% of the nominal input voltage specification,management state machines are initialized to their default
power-on reset power is considered stable. After stable power, the bridgestate.
monitors the PCI Express reference clock (REFCLK) andIn addition, the XIO2001 asserts the internal PCI bus reset.
waits 10 ms after active clocks are detected. Then, internal
power-on reset is deasserted.
Global resetWhen GRST is asserted low, an internal power-on resetWhen GRST is asserted low, all control registers, state
inputoccurs. This reset is asynchronous and functions duringmachines, sticky register bits, and power management
GRSTboth normal power states and V
DD_15_COMB
terminal. When this terminalregisters, state machines, sticky register bits, and power
power states.state machines are initialized to their default state. In
AUX
addition, the bridge asserts PCI bus reset (PRST). When
the rising edge of GRST occurs, the bridge samples the
state of all static control inputs and latches the information
internally. If an external serial EEPROM is detected, then a
download cycle is initiated. Also, the process to configure
and initialize the PCI Express link is started. The bridge
starts link training within 80 ms after GRST is deasserted.
PCI ExpressThis XIO2001 input terminal is used by an upstream PCIWhen PERST is asserted low, all control register bits that
reset inputExpress device to generate a PCI Express reset and toare not sticky are reset. Within the configuration register
PERSTsignal a system power good condition.maps, the sticky bits are indicated by the ┦ symbol. Also,
When PERST is asserted low, the XIO2001 generates an
internal PCI Express reset as defined in the PCI Express
specification.
When PERST transitions from low to high, a system powerIn addition, the XIO2001 asserts the internal PCI bus reset.
good condition is assumed by the XIO2001.
Note: The system must assert PERST before power isWhen the rising edge of PERST occurs, the XIO2001
removed, before REFCLK is removed or before REFCLKsamples the state of all static control inputs and latches
becomes unstable.the information internally. If an external serial EEPROM is
PCI ExpressThe XIO2001 responds to a training control hot resetIn the DL_DOWN state, all remaining configuration register
training control received on the PCI Express interface. After a trainingbits and state machines are reset. All remaining bits
hot resetcontrol hot reset, the PCI Express interface enters theexclude sticky bits and EEPROM loadable bits. All
DL_DOWN state.remaining state machines exclude sticky functionality and
PCI bus resetSystem software has the ability to assert and deassert theWhen bit 6 (SRST) in the bridge control register at offset
PRSTPRST terminal on the secondary PCI bus interface. This3Eh (see Section 4.29) is asserted, the bridge asserts the
terminal is the PCI bus reset.PRST terminal. A 0 in the SRST bit deasserts the PRST
all state machines that are not associated with sticky
functionality are reset.
detected, then a download cycle is initiated. Also, the
process to configure and initialize the PCI Express link is
started. The XIO2001 starts link training within 80 ms after
PERST is deasserted.
EEPROM functionality.
Within the configuration register maps, the sticky bits are
indicated by the ┦ symbol and the EEPROM loadable bits
are indicated by the † symbol.
In addition, the XIO2001 asserts the internal PCI bus reset.
terminal.
3.3PCI Express Interface
3.3.1External Reference Clock
The bridge requires either a differential, 100-MHz common clock reference or a single-ended, 125-MHz
clock reference. The selected clock reference must meet all PCI Express Electrical Specification
requirements for frequency tolerance, spread spectrum clocking, and signal electrical characteristics.
Spread Spectrum is an optional feature of the PCI Express Electrical Specification that is supported by
this bridge.
If the REFCLK125_SEL input is connected to VSS, then a differential, 100-MHz common clock reference is
expected by the XIO2001. If the REFCLK125_SEL terminal is connected to V
125-MHz clock reference is expected by the bridge
When the single-ended, 125-MHz clock reference option is enabled, the single-ended clock signal is
connected to the REFCLK+ terminal. The REFCLK– terminal is connected to one side of an external
capacitor with the other side of the capacitor connected to VSS.
When using a single-ended reference clock, care must be taken to ensure interoperability from a system
jitter standpoint. The PCI Express Base Specification does not ensure interoperability when using a
differential reference clock commonly used in PC applications along with a single-ended clock in a
non-common clock architecture. System jitter budgets will have to be verified to ensure interoperability.
See the PCI Express Jitter and BER White Paper from the PCI-SIG.
The bridge supports the PCI Express in-band beacon feature. Beacon is driven on the upstream PCI
Express link by the bridge to request the reapplication of main power when in the L2 link state. To enable
the beacon feature, bit 10 (BEACON_ENABLE) in the general control register at offset D4h is asserted.
See Section 4.65, General Control Register, for details.
If the bridge is in the L2 link state and beacon is enabled, when a secondary PCI bus device asserts PME,
then the bridge outputs the beacon signal on the upstream PCI Express link. The beacon signal frequency
is approximately 500 kHz ± 50% with a differential peak-to-peak amplitude of 500 mV and no
de-emphasis. Once the beacon is activated, the bridge continues to send the beacon signal until main
power is restored as indicated by PERST going inactive. At this time, the beacon signal is deactivated.
3.3.3Wake
The bridge supports the PCI Express sideband WAKE feature. WAKE is an active low signal driven by the
bridge to request the reapplication of main power when in the L2 link state. Since WAKE is an
open-collector output, a system-side pullup resistor is required to prevent the signal from floating.
When the bridge is in the L2 link state and PME is received from a device on the secondary PCI bus, the
WAKE signal is asserted low as a wakeup mechanism. Once WAKE is asserted, the bridge drives the
signal low until main power is restored as indicated by PERST going inactive. At this time, WAKE is
deasserted.
3.3.4Initial Flow Control Credits
www.ti.com
The bridge flow control credits are initialized using the rules defined in the PCI Express Base
Specification. Table 3-2 identifies the initial flow control credit advertisement for the bridge.
Table 3-2. Initial Flow Control Credit Advertisements
CREDIT TYPEINITIAL ADVERTISEMENT
Posted request headers (PH)8
Posted request data (PD)128
Non-posted header (NPH)4
Non-posted data (NPD)4
Completion header (CPLH)0 (infinite)
Completion data (CPLD)0 (infinite)
3.3.5PCI Express Message Transactions
PCI Express messages are both initiated and received by the bridge. Table 3-3 outlines message support
within the bridge.
Table 3-3. Messages Supported by the Bridge
MESSAGESUPPORTEDBRIDGE ACTION
Assert_INTxYesTransmitted upstream
Deassert_INTxYesTransmitted upstream
PM_Active_State_NakYesReceived and processed
PM_PMEYesTransmitted upstream
PME_Turn_OffYesReceived and processed
PME_TO_AckYesTransmitted upstream
ERR_CORYesTransmitted upstream
ERR_NONFATALYesTransmitted upstream
Table 3-3. Messages Supported by the Bridge (continued)
MESSAGESUPPORTEDBRIDGE ACTION
ERR_FATALYesTransmitted upstream
Set_Slot_Power_LimitYesReceived and processed
UnlockNoDiscarded
Hot plug messagesNoDiscarded
Advanced switching messagesNoDiscarded
Vendor defined type 0NoUnsupported request
Vendor defined type 1NoDiscarded
All supported message transactions are processed per the PCI Express Base Specification.
3.4PCI Bus Interface
3.4.1I/O Characteristics
Figure 3-4 shows a 3-state bi-directional buffer that represents the I/O cell design for the PCI bus.
Section 7.7, Electrical Characteristics over Recommended Operating Conditions, provides the electrical
characteristics of the PCI bus I/O cell.
NOTE
The PCI bus interface on the bridge meets the ac specifications of the PCI Local Bus
Specification. Additionally, PCI bus terminals (input or I/O) must be held high or low to
prevent them from floating.
Figure 3-4. 3-State Bidirectional Buffer
3.4.2Clamping Voltage
In the bridge, the PCI bus I/O drivers are powered from the V
tolerant to input signals with 5-V peak-to-peak amplitudes.
For PCI bus interfaces operating at 50MHz or 66 MHz, all devices are required to output only 3.3-V
peak-to-peak signal amplitudes. For PCI bus interfaces operating at 25-MHz or 33-MHz, devices may
output either 3.3-V or 5-V peak-to-peak signal amplitudes. The bridge accommodates both signal
amplitudes.
Each PCI bus I/O driver cell has a clamping diode connected to the internal V
the cell from excessive input voltage. The internal V
rail is connected to two PCIR terminals. If the PCI
CCP
signaling is 3.3-V, then PCIR terminals are connected to a 3.3-V power supply via a 1kΩ resistor. If the
PCI signaling is 5-V, then the PCIR terminals are connected to a 5-V power supply via a 1kΩ resistor.
The PCI bus signals attached to the V
clamping voltage are identified as follows
CCP
•Table 2-5, PCI System Terminals, all terminal names except for PME
•Table 2-7, Miscellaneous Terminals, the terminal name SERIRQ.
The bridge supports the clock run protocol as specified in the PCI Mobile Design Guide. When the clock
run protocol is enabled, the bridge assumes the role of the central resource master.
To enable the clock run function, terminal CLKRUN_EN is asserted high. Then, terminal GPIO0 is enabled
as the CLKRUN signal. An external pullup resistor must be provided to prevent the CLKRUN signal from
floating To verify the operational status of the PCI bus clocks, bit 0 (SEC_CLK_STATUS) in the clock run
status register at offset DAh (see Section 4.68) is read.
Since the bridge has several unique features associated with the PCI bus interface, the system designer
must consider the following interdependencies between these features and the CLKRUN feature:
1. If the system designer chooses to generate the PCI bus clock externally, then the CLKRUN mode of
the bridge must be disabled. The central resource function within the bridge only operates as a
CLKRUN master and does not support the CLKRUN slave mode.
2. If the central resource function has stopped the PCI bus clocks, then the bridge still detects INTx state
changes and will generate and send PCI Express messages upstream.
3. If the serial IRQ interface is enabled and the central resource function has stopped the PCI bus clocks,
then any PCI bus device that needs to report an IRQ interrupt asserts CLKRUN to start the bus clocks.
4. When a PCI bus device asserts CLKRUN, the central resource function turns on PCI bus clocks for a
minimum of 512 cycles.
5. If the serial IRQ function detects an IRQ interrupt, then the central resource function keeps the PCI bus
clocks running until the IRQ interrupt is cleared by software.
6. If the central resource function has stopped the PCI bus clocks and the bridge receives a downstream
transaction that is forwarded to the PCI bus interface, then the bridge asserts CLKRUN to start the bus
clocks.
7. The central resource function is reset by PCI bus reset (PRST) assuring that clocks are present during
PCI bus resets.
www.ti.com
3.4.4PCI Bus External Arbiter
The bridge supports an external arbiter for the PCI bus. Terminal (EXT_ARB_EN), when asserted high,
enables the use of an external arbiter.
When an external arbiter is enabled, GNT0 is connected to the external arbiter as the REQ for the bridge.
Likewise, REQ0 is connected to the external arbiter as the GNT for the bridge.
3.4.5MSI Messages Generated from the Serial IRQ Interface
When properly configured, the bridge converts PCI bus serial IRQ interrupts into PCI Express message
signaled interrupts (MSI). classic PCI configuration register space is provided to enable this feature. The
following list identifies the involved configuration registers:
1. Command register at offset 04h, bit 2 (MASTER_ENB) is asserted (see Table 4-2).
2. MSI message control register at offset 52h, bits 0 (MSI_EN) and 6:4 (MM_EN) enable single and
multiple MSI messages, respectively (see Section 4.42).
3. MSI message address register at offsets 54h and 58h specifies the message memory address. A
nonzero address value in offset 58h initiates 64-bit addressing (see Section 4.37 and Section 4.44).
4. MSI message data register at offset 5Ch specifies the system interrupt message (see Section 4.45).
5. Serial IRQ mode control register at offset E0h specifies the serial IRQ bus format (see Section 4.72).
6. Serial IRQ edge control register at offset E2h selects either level or edge mode interrupts (see
Section 4.73).
7. Serial IRQ status register at offset E4h reports level mode interrupt status (see Section 4.74).
A PCI Express MSI is generated based on the settings in the serial IRQ edge control register. If the
system is configured for edge mode, then an MSI message is sent when the corresponding serial IRQ
interface sample phase transitions from low to high. If the system is configured for level mode, then an
MSI message is sent when the corresponding IRQ status bit in the serial IRQ status register changes from
low to high.
The bridge has a dedicated SERIRQ terminal for all PCI bus devices that support serialized interrupts.
This SERIRQ interface is synchronous to the PCI bus clock input (CLK) frequency. The bridge always
generates a 17-phase serial IRQ stream. Internally, the bridge detects only 16 IRQ interrupts, IRQ0 frame
through IRQ15 frame. The IOCHCK frame is not monitored by the serial IRQ state machine and never
generates an IRQ interrupt or MSI message.
The multiple message enable (MM_EN) field determines the number of unique MSI messages that are
sent upstream on the PCI Express link. From 1 message to 16 messages, in powers of 2, are selectable.
If fewer than 16 messages are selected, then the mapping from IRQ interrupts to MSI messages is
aliased. Table 3-4 illustrates the IRQ interrupt to MSI message mapping based on the number of enabling
messages.
The MSI message format is compatible with the PCI Express request header format for 32-bit and 64-bit
memory write transactions. The system message and message number fields are included in bytes 0 and
1 of the data payload.
3.4.6PCI Bus Clocks
The bridge has seven PCI bus clock outputs and one PCI bus clock input. Up to six PCI bus devices are
supported by the bridge.
Terminal PCLK66_SEL selects the default operating frequency. This signal works in conjunction with
terminal M66EN to determine the final output frequency. When PCLK66_SEL is asserted high then the
clock frequency will be either 66-MHz or 33-MHz depending on the state of M66EN. When M66EN is
asserted high then the clock frequency will be 66-MHz, when M66EN is de-asserted the clock frequency
will be 33-MHz. When PCLK66_SEL is de-asserted then the clock frequency will be either 50-MHz or
25-MHz. When M66EN is asserted high then the clock frequency will be 50-MHz, when M66EN is
de-asserted the clock frequency will be 25-MHz. The clock control register at offset D8h provides 7 control
bits to individually enable or disable each PCI bus clock output (see Section 4.66). The register default is
enabled for all 7 outputs.
The PCI bus clock (CLK) input provides the clock to the internal PCI bus core and serial IRQ core. When
the internal PCI bus clock source is selected, PCI bus clock output 6 (CLKOUT6) is connected to the PCI
bus clock input (CLK). When an external PCI bus clock source is selected, the external clock source is
connected to the PCI bus clock input (CLK). For external clock mode, all seven CLKOUT6:0 terminals
must be disabled using the clock control register at offset D8h (see Section 4.66).
3.5PCI Port Arbitration
The internal PCI port arbitration logic supports up to six external PCI bus devices plus the bridge. This
bridge supports a classic PCI arbiter.
3.5.1Classic PCI Arbiter
The classic PCI arbiter is configured through the classic PCI configuration space at offset DCh. Table 3-5
identifies and describes the registers associated with classic PCI arbitration mode.
Table 3-5. Classic PCI Arbiter Registers
PCI OFFSETREGISTER NAMEDESCRIPTION
Classic PCI configurationArbiter control
register DCh(see Section 4.69)
Classic PCI configurationArbiter request maskstatus if a PCI device does not respond within 16 PCI bus clocks. Bit 6
register DDh(see Section 4.70)(AUTO_MASK) in the arbiter request mask register automatically masks a PCI bus
Classic PCI configurationArbiter time-out statusWhen bit 7 (ARB_TIMEOUT) in the arbiter request mask register is asserted,
register DEh(see Section 4.71)timeout status for each PCI bus device is reported in this register.
Contains a two-tier priority scheme for the bridge and six PCI bus devices. The
bridge defaults to the high priority tier. The six PCI bus devices default to the low
priority tier. A bus parking control bit (bit 7, PARK) is provided.
Six mask bits provide individual control to block each PCI Bus REQ input. Bit 7
(ARB_TIMEOUT) in the arbiter request mask register enables generating timeout
REQ if the device does not respond after GNT is issued. The AUTO_MASK bit is
cleared to disable any automatically generated mask.
www.ti.com
3.6Configuration Register Translation
PCI Express configuration register transactions received by the bridge are decoded based on the
transaction’s destination ID. These configuration transactions can be broken into three subcategories: type
0 transactions, type 1 transactions that target the secondary bus, and type 1 transactions that target a
downstream bus other than the secondary bus.
PCI Express type 0 configuration register transactions always target the configuration space and are never
passed on to the secondary interface.
Type 1 configuration register transactions that target a device on the secondary bus are converted to type
0 configuration register transactions on the PCI bus. Figure 3-5 shows the address phase of a type 0
configuration transaction on the PCI bus as defined by the PCI specification.
Figure 3-5. Type 0 Configuration Transaction Address Phase Encoding
In addition, the bridge converts the destination ID device number to one of the AD[31:16] lines as the
IDSEL signal. The implemented IDSEL signal mapping is shown in Table 3-6.
Type 1 configuration registers transactions that target a downstream bus other then the secondary bus are
output on the PCI bus as type 1 PCI configuration transactions. Figure 3-6 shows the address phase of a
type 1 configuration transaction on the PCI bus as defined by the PCI specification.
Figure 3-6. Type 1 Configuration Transaction Address Phase Encoding
3.7PCI Interrupt Conversion to PCI Express Messages
The bridge converts interrupts from the PCI bus sideband interrupt signals to PCI Express interrupt
messages.
Table 3-7, Figure 3-7, and Figure 3-8 illustrate the format for both the assert and deassert INTx
messages.
Table 3-7. Interrupt Mapping
In The Code Field
INTERRUPTCODE FIELD
INTA00
INTB01
INTC10
INTD11
www.ti.com
Figure 3-7. PCI Express ASSERT_INTX Message
Figure 3-8. PCI Express DEASSERT_INTX Message
3.8PME Conversion to PCI Express Messages
When the PCI bus PME input transitions low, the bridge generates and sends a PCI Express PME
message upstream. The requester ID portion of the PME message uses the stored value in the secondary
bus number register as the bus number, 0 as the device number, and 0 as the function number. The Tag
field for each PME message is 00h. A PME message is sent periodically until the PME signal transitions
high.
Figure 3-9 illustrates the format for a PCI Express PME message.
The bus-locking protocol defined in the PCI Express Base Specification and PCI Local Bus Specification is
provided on the bridge as an additional compatibility feature. The PCI bus LOCK signal is a dedicated
output that is enabled by setting bit 12 in the general control register at offset D4h. See Section 4.65,
General Control Register, for details.
The use of LOCK is only supported by PCI-Express to PCI Bridges in the downstream
direction (away from the root complex).
SCPS212D–MAY 2009–REVISED JANUARY 2010
NOTE
PCI Express locked-memory read request transactions are treated the same as PCI Express memory read
transactions except that the bridge returns a completion for a locked-memory read. Also, the bridge uses
the PCI LOCK protocol when initiating the memory read transaction on the PCI bus.
When a PCI Express locked-memory read request transaction is received and the bridge is not already
locked, the bridge arbitrates for use of the LOCK terminal by asserting REQ. If the bridge receives GNT
and the LOCK terminal is high, then the bridge drives the LOCK terminal low after the address phase of
the first locked-memory read transaction to take ownership of LOCK. The bridge continues to assert
LOCK except during the address phase of locked transactions. If the bridge receives GNT and the LOCK
terminal is low, then the bridge deasserts its REQ and waits until LOCK is high and the bus is idle before
re-arbitrating for the use of LOCK.
Figure 3-10. Starting a Locked Sequence
Once the bridge has ownership of LOCK, the bridge initiates the lock read as a memory read transaction
on the PCI bus. When the target of the locked-memory read returns data, the bridge is considered locked
and all transactions not associated with the locked sequence are blocked by the bridge.
Because PCI Express does not have a unique locked-memory write request packet, all PCI Express
memory write requests that are received while the bridge is locked are considered part of the locked
sequence and are transmitted to PCI as locked-memory write transactions.
The bridge terminates the locked sequence when an unlock message is received from PCI Express and
all previous locked transactions have been completed.
www.ti.com
Figure 3-12. Terminating a Locked Sequence
In the erroneous case that a normal downstream memory read request is received during a locked
sequence, the bridge responds with an unsupported request completion status. Note that this condition
must never occur, because the PCI Express Specification requires the root complex to block normal
memory read requests at the source. All locked sequences that end successfully or with an error condition
must be immediately followed by an unlock message. This unlock message is required to return the bridge
to a known unlocked state.
3.10 Two-Wire Serial-Bus Interface
The bridge provides a two-wire serial-bus interface to load subsystem identification information and
specific register defaults from an external EEPROM. The serial-bus interface signals (SDA and SCL) are
shared with two of the GPIO terminals (3 and 4). If the serial bus interface is enabled, then the GPIO3 and
GPIO4 terminals are disabled. If the serial bus interface is disabled, then the GPIO terminals operate as
described in Section 3.13.
3.10.1 Serial-Bus Interface Implementation
To enable the serial-bus interface, a pullup resistor must be implemented on the SCL signal. At the rising
edge of PERST or GRST, whichever occurs later in time, the SCL terminal is checked for a pullup resistor.
If one is detected, then bit 3 (SBDETECT) in the serial-bus control and status register (see Section 4.58)
is set. Software may disable the serial-bus interface at any time by writing a 0b to the SBDETECT bit. If
no external EEPROM is required, then the serial-bus interface is permanently disabled by attaching a
pulldown resistor to the SCL signal.
The bridge implements a two-terminal serial interface with one clock signal (SCL) and one data signal
(SDA). The SCL signal is a unidirectional output from the bridge and the SDA signal is bidirectional. Both
are open-drain signals and require pullup resistors. The bridge is a bus master device and drives SCL at
approximately 60 kHz during data transfers and places SCL in a high-impedance state (0 frequency)
during bus idle states. The serial EEPROM is a bus slave device and must acknowledge a slave address
equal to A0h. Figure 3-13 illustrates an example application implementing the two-wire serial bus.
SCPS212D–MAY 2009–REVISED JANUARY 2010
Figure 3-13. Serial EEPROM Application
3.10.2 Serial-Bus Interface Protocol
All data transfers are initiated by the serial-bus master. The beginning of a data transfer is indicated by a
start condition, which is signaled when the SDA line transitions to the low state while SCL is in the high
state, as illustrated in Figure 3-14. The end of a requested data transfer is indicated by a stop condition,
which is signaled by a low-to-high transition of SDA while SCL is in the high state, as shown in
Figure 3-14. Data on SDA must remain stable during the high state of the SCL signal, as changes on the
SDA signal during the high state of SCL are interpreted as control signals, that is, a start or stop condition.
Figure 3-14. Serial-Bus Start/Stop Conditions and Bit Transfers
Data is transferred serially in 8-bit bytes. During a data transfer operation, the exact number of bytes that
are transmitted is unlimited. However, each byte must be followed by an acknowledge bit to continue the
data transfer operation. An acknowledge (ACK) is indicated by the data byte receiver pulling the SDA
signal low, so that it remains low during the high state of the SCL signal. Figure 3-15 illustrates the
acknowledge protocol.
Figure 3-15. Serial-Bus Protocol Acknowledge
The bridge performs three basic serial-bus operations: single byte reads, single byte writes, and multibyte
reads. The single byte operations occur under software control. The multibyte read operations are
performed by the serial EEPROM initialization circuitry immediately after a PCI Express reset. See
Section 3.10.3, Serial-Bus EEPROM Application, for details on how the bridge automatically loads the
subsystem identification and other register defaults from the serial-bus EEPROM.
www.ti.com
Figure 3-16 illustrates a single byte write. The bridge issues a start condition and sends the 7-bit slave
device address and the R/W command bit is equal to 0b. A 0b in the R/W command bit indicates that the
data transfer is a write. The slave device acknowledges if it recognizes the slave address. If no
acknowledgment is received by the bridge, then bit 1 (SB_ERR) is set in the serial-bus control and status
register (PCI offset B3h, see Section 4.58). Next, the EEPROM word address is sent by the bridge, and
another slave acknowledgment is expected. Then the bridge delivers the data byte MSB first and expects
a final acknowledgment before issuing the stop condition.
Figure 3-16. Serial-Bus Protocol – Byte Write
Figure 3-17 illustrates a single byte read. The bridge issues a start condition and sends the 7-bit slave
device address and the R/W command bit is equal to 0b (write). The slave device acknowledges if it
recognizes the slave address. Next, the EEPROM word address is sent by the bridge, and another slave
acknowledgment is expected. Then, the bridge issues a restart condition followed by the 7-bit slave
address and the R/W command bit is equal to 1b (read). Once again, the slave device responds with an
acknowledge. Next, the slave device sends the 8-bit data byte, MSB first. Since this is a 1-byte read, the
bridge responds with no acknowledge (logic high) indicating the last data byte. Finally, the bridge issues a
stop condition.
Figure 3-18 illustrates the serial interface protocol during a multi-byte serial EEPROM download. The
serial-bus protocol starts exactly the same as a 1-byte read. The only difference is that multiple data bytes
are transferred. The number of transferred data bytes is controlled by the bridge master. After each data
byte, the bridge master issues acknowledge (logic low) if more data bytes are requested. The transfer
ends after a bridge master no acknowledge (logic high) followed by a stop condition.
SCPS212D–MAY 2009–REVISED JANUARY 2010
Figure 3-17. Serial-Bus Protocol – Byte Read
Figure 3-18. Serial-Bus Protocol – Multibyte Read
Bit 7 (PROT_SEL) in the serial-bus control and status register changes the serial-bus protocol. Each of
the three previous serial-bus protocol figures illustrates the PROT_SEL bit default (logic low). When this
control bit is asserted, the word address and corresponding acknowledge are removed from the serial-bus
protocol. This feature allows the system designer a second serial-bus protocol option when selecting
external EEPROM devices.
3.10.3 Serial-Bus EEPROM Application
The registers and corresponding bits that are loaded through the EEPROM are provided in Table 3-8.
Table 3-8. EEPROM Register Loading Map
SERIAL EEPROM WORDBYTE DESCRIPTION
ADDRESS
00hPCI-Express to PCI bridge function indicator (00h)
01hNumber of bytes to download (25h)
02hPCI 44h, subsystem vendor ID, byte 0
03hPCI 45h, subsystem vendor ID, byte 1
04hPCI 46h, subsystem ID, byte 0s
05hPCI 47h, subsystem ID, byte 1s
06hPCI D4h, general control, byte 0
07hPCI D5h, general control, byte 1
08hPCI D6h, general control, byte 2
09hPCI D7h, general control, byte 3
0AhPCI D8h, clock control
0BhPCI D9h, clock mask
0ChReserved—no bits loaded
0DhPCI DCh, arbiter control
0EhPCI DDh, arbiter request mask
0FhPCI C0h, control and diagnostic register, byte 0
10hPCI C1h, control and diagnostic register, byte 1
11hPCI C2h, control and diagnostic register, byte 2
12hPCI C3h, control and diagnostic register, byte 3
13hPCI C4h, control and diagnostic register, byte 0
14hPCI C5h, control and diagnostic register, byte 1
15hPCI C6h, control and diagnostic register, byte 2
15hPCI C6h, control and diagnostic register, byte 2
16hPCI C7h, control and diagnostic register, byte 3
17hPCI C8h, control and diagnostic register, byte 0
18hPCI C9h, control and diagnostic register, byte 1
19hPCI CAh, control and diagnostic register, byte 2
1AhPCI CBh, control and diagnostic register, byte 3
1BhReserved—no bits loaded
1ChReserved—no bits loaded
1DhPCI E0h, serial IRQ mode control
1EhPCI E2h, serial IRQ edge control, byte 0
1FhPCI E3h, serial IRQ edge control, byte 1
20hPCI E8h, PFA_REQ_LENGTH_LIMIT
21hPCI E9h, PFA_REQ_CNT_LIMIT
22hPCI EAh, CACHE_TMR_XFR_LIMIT
23hPCI ECh, CACHE_TIMER_LOWER_LIMIT, Byte 0
24hPCI EDh, CACHE_TIMER_LOWER_LIMIT, Byte 1
25hPCI EEh, CACHE_TIMER_UPPER_LIMIT, Byte 0
26hPCI EFh, CACHE_TIMER_UPPER_LIMIT, Byte 1
27hEnd-of-list indicator (80h)
www.ti.com
This format must be explicitly followed for the bridge to correctly load initialization values from a serial
EEPROM. All byte locations must be considered when programming the EEPROM.
The serial EEPROM is addressed by the bridge at slave address 1010 000b. This slave address is
internally hardwired and cannot be changed by the system designer. Therefore, all three hardware
address bits for the EEPROM are tied to VSSto achieve this address. The serial EEPROM in the sample
application circuit (Figure 3-13) assumes the 1010b high-address nibble. The lower three address bits are
terminal inputs to the chip, and the sample application shows these terminal inputs tied to VSS.
During an EEPROM download operation, bit 4 (ROMBUSY) in the serial-bus control and status register is
asserted. After the download is finished, bit 0 (ROM_ERR) in the serial-bus control and status register
may be monitored to verify a successful download.
3.10.4 Accessing Serial-Bus Devices Through Software
The bridge provides a programming mechanism to control serial-bus devices through system software.
The programming is accomplished through a doubleword of PCI configuration space at offset B0h.
Table 3-9 lists the registers that program a serial-bus device through software.
Table 3-9. Registers Used To Program Serial-Bus Devices
PCI OFFSETREGISTER NAMEDESCRIPTION
B0hSerial-bus data (seeContains the data byte to send on write commands or the received data byte on read
B1hSerial-bus word addressThe content of this register is sent as the word address on byte writes or reads. This register is
B2hSerial-bus slave addressWrite transactions to this register initiate a serial-bus transaction. The slave device address and
B3hSerial-bus control andSerial interface enable, busy, and error status are communicated through this register. In
Section 4.55)commands.
(see Section 4.56)not used in the quick command protocol. Bit 7 (PROT_SEL) in the serial-bus control and status
register (offset B3h, see Section 4.58) is set to 1b to enable the slave address to be sent.
(see Section 4.57)the R/W command selector are programmed through this register.
status (see Section 4.58)addition, the protocol-select bit (PROT_SEL) and serial-bus test bit (SBTEST) are programmed
through this register.
To access the serial EEPROM through the software interface, the following steps are performed:
1. The control and status byte is read to verify the EEPROM interface is enabled (SBDETECT asserted)
and not busy (REQBUSY and ROMBUSY deasserted).
2. The serial-bus word address is loaded. If the access is a write, then the data byte is also loaded.
3. The serial-bus slave address and R/W command selector byte is written.
4. REQBUSY is monitored until this bit is deasserted.
5. SB_ERR is checked to verify that the serial-bus operation completed without error. If the operation is a
read, then the serial-bus data byte is now valid.
3.11 Advanced Error Reporting Registers
In the extended PCI Express configuration space, the bridge supports the advanced error reporting
capabilities structure. For the PCI Express interface, both correctable and uncorrectable error statuses are
provided. For the PCI bus interface, secondary uncorrectable error status is provided. All uncorrectable
status bits have corresponding mask and severity control bits. For correctable status bits, only mask bits
are provided.
Both the primary and secondary interfaces include first error pointer and header log registers. When the
first error is detected, the corresponding bit position within the uncorrectable status register is loaded into
the first error pointer register. Likewise, the header information associated with the first failing transaction
is loaded into the header log. To reset this first error control logic, the corresponding status bit in the
uncorrectable status register is cleared by a writeback of 1b.
For systems that require high data reliability, ECRC is fully supported on the PCI Express interface. The
primary side advanced error capabilities and control register has both ECRC generation and checking
enable control bits. When the checking bit is asserted, all received TLPs are checked for a valid ECRC
field. If the generation bit is asserted, then all transmitted TLPs contain a valid ECRC field.
3.12 Data Error Forwarding Capability
The bridge supports the transfer of data errors in both directions.
If a downstream PCI Express transaction with a data payload is received that targets the internal PCI bus
and the EP bit is set indicating poisoned data, then the bridge must ensure that this information is
transferred to the PCI bus. To do this, the bridge forces a parity error on each PCI bus data phase by
inverting the parity bit calculated for each double-word of data.
If the bridge is the target of a PCI transaction that is forwarded to the PCI Express interface and a data
parity error is detected, then this information is passed to the PCI Express interface. To do this, the bridge
sets the EP bit in the upstream PCI Express header.
3.13 General-Purpose I/O Interface
Up to five general-purpose input/output (GPIO) terminals are provided for system customization. These
GPIO terminals are 3.3-V tolerant.
The exact number of GPIO terminals varies based on implementing the clock run, power override, and
serial EEPROM interface features. These features share four of the five GPIO terminals. When any of the
three shared functions are enabled, the associated GPIO terminal is disabled.
All five GPIO terminals are individually configurable as either inputs or outputs by writing the
corresponding bit in the GPIO control register at offset B4h (See Section 4.59). A GPIO data register at
offset B6h exists to either read the logic state of each GPIO input or to set the logic state of each GPIO
output. The power-up default state for the GPIO control register is input mode.
3.14 Set Slot Power Limit Functionality
The PCI Express Specification provides a method for devices to limit internal functionality and save power
based on the value programmed into the captured slot power limit scale (CSPLS) and capture slot power
limit value (CSPLV) fields of the PCI Express device capabilities register at offset 74h. See Section 4.49,
Device Capabilities Register, for details. The bridge writes these fields when a set slot power limit
message is received on the PCI Express interface.
www.ti.com
After the deassertion of PERST, the XIO2001 compares the information within the CSPLS and CSPLV
fields of the device capabilities register to the minimum power scale (MIN_POWER_SCALE) and minimum
power value (MIN_POWER_VALUE) fields in the general control register at offset D4h. See Section 4.65,
General Control Register, for details. If the CSPLS and CSPLV fields are less than the
MIN_POWER_SCALE and MIN_POWER_VALUE fields, respectively, then the bridge takes the
appropriate action that is defined below.
The power usage action is programmable within the bridge. The general control register includes a 3-bit
POWER_OVRD field. This field is programmable to the following options:
1. Ignore slot power limit fields.
2. Assert the PWR_OVRD terminal.
3. Disable secondary clocks as specified by the clock mask register at offset D9h (see Section 4.67).
4. Disable secondary clocks as specified by the clock mask register and assert the PWR_OVRD terminal.
5. Respond with unsupported request to all transactions except type 0/1 configuration transactions and
set slot power limit messages
3.15 PCI Express and PCI Bus Power Management
The bridge supports both software-directed power management and active state power management
through standard PCI configuration space. Software-directed registers are located in the power
management capabilities structure located at offset 48h (see Section 4.31). Active state power
management control registers are located in the PCI Express capabilities structure located at offset 70h
(see Section 4.41).
During software-directed power management state changes, the bridge initiates link state transitions to L1
or L2/L3 after a configuration write transaction places the device in a low power state. The power
management state machine is also responsible for gating internal clocks based on the power state.
Table 3-10 identifies the relationship between the D-states and bridge clock operation.
PCI express reference clock input (REFCLK)OnOnOnOn/Off
Internal PCI bus clock to bridge functionOnOffOffOff
The link power management (LPM) state machine manages active state power by monitoring the PCI
Express transaction activity. If no transactions are pending and the transmitter has been idle for at least
the minimum time required by the PCI Express Specification, then the LPM state machine transitions the
link to either the L0s or L1 state. By reading the bridge’s L0s and L1 exit latency in the link capabilities
register, the system software may make an informed decision relating to system performance versus
power savings. The ASLPMC field in the link control register provides an L0s only option, L1 only option,
or both L0s and L1 option.
3.16 Auto Pre-Fetch Agent
The auto pre-fetch agent is an internal logic module that will generate speculative read requests on behalf
of a PCI master to improve upstream memory read performance.
The auto pre-fetch agent will generate a read thread on the PCI-express bus when it receives an
upstream prefetchable memory read request on the PCI bus. A read thread is a sequence of one or more
read requests with contiguous read addresses. The first read of thread will be started by a master on the
PCI bus requesting a read that is forwarded to the root complex by the bridge. Each subsequent read in
the thread will be initiated by the auto pre-fetch agent. Each subsequent read will use the address that
immediately follows the last address of data in the previous read of the thread. Each read request in the
thread will be assigned to an upstream request processor. The pre-fetch agent can issue reads for two
threads at one time, alternating between the threads.
The programming model of the XIO2001 PCI-Express to PCI bridge is compliant to the classic PCI-to-PCI
bridge programming model. The PCI configuration map uses the type 1 PCI bridge header.
All bits marked with a are sticky bits and are reset by a global reset (GRST) or the internally-generated
power-on reset. All bits marked with a ┦ are reset by a PCI Express reset (PERST), a GRST, or the
internally-generated power-on reset. The remaining register bits are reset by a PCI Express hot reset,
PERST, GRST, or the internally-generated power-on reset.
Table 4-1. Classic PCI Configuration Register Map
REGISTER NAMEOFFSET
Device IDVendor ID000h
StatusCommand004h
Class codeRevision ID008h
BISTHeader typeLatency timerCache line size00Ch
Device control base address010h
Reserved014h
Secondary latency timerSubordinate bus numberSecondary bus numberPrimary bus number018h
INTx disable. This bit enables device specific interrupts. Since the bridge does not
generate any internal interrupts, this bit is read-only 0b.
Fast back-to-back enable. The bridge does not generate fast back-to-back transactions;
therefore, this bit returns 0b when read.
SERR enable bit. When this bit is set, the bridge can signal fatal and nonfatal errors on the
PCI Express interface on behalf of SERR assertions detected on the PCI bus.
0 = Disable the reporting of nonfatal errors and fatal errors (default)
1 = Enable the reporting of nonfatal errors and fatal errors
Address/data stepping control. The bridge does not support address/data stepping, and
this bit is hardwired to 0b.
Controls the setting of bit 8 (DATAPAR) in the status register (offset 06h, see Section 4.4)
in response to a received poisoned TLP from PCI Express. A received poisoned TLP is
forwarded with bad parity to conventional PCI regardless of the setting of this bit.
0 = Disables the setting of the master data parity error bit (default)
1 = Enables the setting of the master data parity error bit
VGA palette snoop enable. The bridge does not support VGA palette snooping; therefore,
this bit returns 0b when read.
Memory write and invalidate enable. When this bit is set, the bridge translates PCI
Express memory write requests into memory write and invalidate transactions on the PCI
interface.
0 = Disable the promotion to memory write and invalidate (default)
1 = Enable the promotion to memory write and invalidate
Special cycle enable. The bridge does not respond to special cycle transactions; therefore,
this bit returns 0b when read.
Bus master enable. When this bit is set, the bridge is enabled to initiate transactions on
the PCI Express interface.
0 = PCI Express interface cannot initiate transactions. The bridge must disable the
response to memory and I/O transactions on the PCI interface (default).
1 = PCI Express interface can initiate transactions. The bridge can forward memory
and I/O transactions from PCI secondary interface to the PCI Express interface.
Memory space enable. Setting this bit enables the bridge to respond to memory
transactions on the PCI Express interface.
0 = PCI Express receiver cannot process downstream memory transactions and must
respond with an unsupported request (default)
1 = PCI Express receiver can process downstream memory transactions. The bridge
can forward memory transactions to the PCI interface.
I/O space enable. Setting this bit enables the bridge to respond to I/O transactions on the
PCI Express interface.
0 = PCI Express receiver cannot process downstream I/O transactions and must
respond with an unsupported request (default)
1 = PCI Express receiver can process downstream I/O transactions. The bridge can
The status register provides information about the PCI Express interface to the system. See Table 4-3 for
a complete description of the register contents.
Detected parity error. This bit is set when the PCI Express interface receives a poisoned
TLP. This bit is set regardless of the state of bit 6 (PERR_ENB) in the command register
15PAR_ERRRCU
14SYS_ERRRCU
13MABORTRCU
12TABORT_RECRCUT
11TABORT_SIGRCUT
10:9PCI_SPEEDRDEVSEL timing. These bits are read-only 00b, because they do not apply to PCI Express.
8DATAPARRCU
7FBB_CAPR
6RSVDRReserved. Returns 0b when read.
566MHZR
Signaled system error. This bit is set when the bridge sends an ERR_FATAL or
ERR_NONFATAL message and bit 8 (SERR_ENB) in the command register (offset 04h,
see Section 4.3) is set.
0 = No error signaled
1 = ERR_FATAL or ERR_NONFATAL signaled
Received master abort. This bit is set when the PCI Express interface of the bridge
receives a completion-with-unsupported-request status.
0 = Unsupported request not received on the PCI Express interface
1 = Unsupported request received on the PCI Express interface
Received target abort. This bit is set when the PCI Express interface of the bridge receives
a completion-with-completer-abort status.
0 = Completer abort not received on the PCI Express interface
1 = Completer abort received on the PCI Express interface
Signaled target abort. This bit is set when the PCI Express interface completes a request
with completer abort status.
0 = Completer abort not signaled on the PCI Express interface
1 = Completer abort signaled on the PCI Express interface
Master data parity error. This bit is set if bit 6 (PERR_ENB) in the command register (offset
04h, see Section 4.3) is set and the bridge receives a completion with data marked as
poisoned on the PCI Express interface or poisons a write request received on the PCI
Express interface.
0 = No uncorrectable data error detected on the primary interface
1 = Uncorrectable data error detected on the primary interface
Fast back-to-back capable. This bit does not have a meaningful context for a PCI Express
device and is hardwired to 0b.
66-MHz capable. This bit does not have a meaningful context for a PCI Express device and
is hardwired to 0b.
Capabilities list. This bit returns 1b when read, indicating that the bridge supports additional
PCI capabilities.
Interrupt status. This bit reflects the interrupt status of the function. This bit is read-only 0b
since the bridge does not generate any interrupts internally.
This read-only register categorizes the base class, subclass, and programming interface of the bridge. The
base class is 06h, identifying the device as a bridge. The subclass is 04h, identifying the function as a
PCI-to-PCI bridge, and the programming interface is 00h. Furthermore, the TI device revision is indicated
in the lower byte (03h). See Table 4-4 for a complete description of the register contents.
Table 4-4. Class Code and Revision ID Register Description
BITFIELD NAMEACCESSDESCRIPTION
31:24BASECLASSRBase class. This field returns 06h when read, which classifies the function as a bridge device.
23:16SUBCLASSRSubclass. This field returns 04h when read, which classifies the function as a PCI-to-PCI bridge.
15:8PGMIFRProgramming interface. This field returns 00h when read.
7:0CHIPREVRSilicon revision. This field returns the silicon revision of the function.
4.6Cache Line Size Register
This register is used to determine when a downstream write is memory write (MW) or memory write
invalidate (MWI).
A posted write TLP will normally be sent as a MW on the PCI bus. It will be sent as a MWI when the
following conditions are met:
•Cacheline size register has a value that is a power of two (1, 2, 4, 8, 16, 32, 64, or 128)
This read-only register has no meaningful context for a PCI Express device and returns 00h when read.
PCI register offset:0Dh
Register type:Read only
Default value:00h
BIT NUMBER76543210
RESET STATE00000000
4.8Header Type Register
This read-only register indicates that this function has a type one PCI header. Bit 7 of this register is 0b
indicating that the bridge is a single-function device.
PCI register offset:0Eh
Register type:Read only
Default value:01h
BIT NUMBER76543210
RESET STATE00000001
SCPS212D–MAY 2009–REVISED JANUARY 2010
4.9BIST Register
Since the bridge does not support a built-in self test (BIST), this read-only register returns the value of 00h
when read.
PCI register offset:0Fh
Register type:Read only
Default value:00h
BIT NUMBER76543210
RESET STATE00000000
4.10 Device Control Base Address Register
This register programs the memory base address that accesses the device control registers. By default,
this register is read only. If bit 5 of the Control and Diagnostic Register 2 (see Section 4.63) is set, then
the bits 31:12 of this register become read/write. See Table 4-5 for a complete description of the register
contents.
Table 4-5. Device Control Base Address Register Description
BITFIELD NAMEACCESSDESCRIPTION
31:12ADDRESSR or RWMemory Address. The memory address field for XIO2001 uses 20 read/write bits indicating
that 4096 bytes of memory space are required. While less than this is actually used, typical
systems will allocate this space on a 4K boundary. If the BAR0_EN bit (bit 5 at C8h) is ‘0’,
then these bits are read-only and return zeros when read. If the BAR0_EN bit is ‘1’, then
these bits are read/write.
11:4RSVDRReserved. These bits are read-only and return 00h when read.
3PRE_FETCHRPrefetchable. This bit is read-only 0b indicating that this memory window is not prefetchable.
2:1MEM_TYPERMemory type. This field is read-only 00b indicating that this window can be located anywhere
in the 32-bit address space.
0MEM_INDRMemory space indicator. This field returns 0b indicating that memory space is used.
4.11 Primary Bus Number Register
This read/write register specifies the bus number of the PCI bus segment that the PCI Express interface is
connected to.
This read/write register specifies the bus number of the PCI bus segment that the PCI interface is
connected to. The bridge uses this register to determine how to respond to a type 1 configuration
transaction.
This read/write register specifies the bus number of the highest number PCI bus segment that is
downstream of the bridge. The bridge uses this register to determine how to respond to a type 1
configuration transaction.
This read/write register specifies the lower limit of the I/O addresses that the bridge forwards downstream.
See Table 4-6 for a complete description of the register contents.
I/O base. Defines the bottom address of the I/O address range that determines when to forward I/O
7:4IOBASERWaddress. The lower 12 bits are assumed to be 000h. The 16 bits corresponding to address bits
3:0IOTYPERI/O type. This field is read-only 1h indicating that the bridge supports 32-bit I/O addressing.
transactions from one interface to the other. These bits correspond to address bits [15:12] in the I/O
[31:16] of the I/O address are defined in the I/O base upper 16 bits register (offset 30h, see
Section 4.24).
4.16 I/O Limit Register
This read/write register specifies the upper limit of the I/O addresses that the bridge forwards downstream.
See Table 4-7 for a complete description of the register contents.
I/O limit. Defines the top address of the I/O address range that determines when to forward I/O
7:4IOLIMITRWaddress. The lower 12 bits are assumed to be FFFh. The 16 bits corresponding to address bits
3:0IOTYPERI/O type. This field is read-only 1h indicating that the bridge supports 32-bit I/O addressing.
transactions from one interface to the other. These bits correspond to address bits [15:12] in the I/O
[31:16] of the I/O address are defined in the I/O limit upper 16 bits register (offset 32h, see
Detected parity error. This bit reports the detection of an uncorrectable address, attribute, or data
error by the bridge on its internal PCI bus secondary interface. This bit must be set when any of the
following three conditions are true:
• The bridge detects an uncorrectable address or attribute error as a potential target.
• The bridge detects an uncorrectable data error when it is the target of a write transaction.
15PAR_ERRRCU• The bridge detects an uncorrectable data error when it is the master of a read transaction
14SYS_ERRRCU
13MABORTRCU
12TABORT_RECRCU
11TABORT_SIGRCU
10:9 PCI_SPEEDRDEVSEL timing. These bits are 01b indicating that this is a medium speed decoding device.
8DATAPARRCU
7FBB_CAPR
6RSVDRReserved. Returns 0b when read.
566MHZR
4:0 RSVDRReserved. Returns 00000b when read.
(immediate read data).
The bit is set irrespective of the state of bit 0 (PERR_EN) in the bridge control register at offset 3Eh
(see Section 4.29).
0 = Uncorrectable address, attribute, or data error not detected on secondary interface
1 = Uncorrectable address, attribute, or data error detected on secondary interface
Received system error. This bit is set when the bridge detects an SERR assertion.
0 = No error asserted on the PCI interface
1 = SERR asserted on the PCI interface
Received master abort. This bit is set when the PCI interface of the bridge reports the detection of a
master abort termination by the bridge when it is the master of a transaction on its secondary
interface.
0 = Master abort not received on the PCI interface
1 = Master abort received on the PCI interface
Received target abort. This bit is set when the PCI interface of the bridge receives a target abort.
0 = Target abort not received on the PCI interface
1 = Target abort received on the PCI interface
Signaled target abort. This bit reports the signaling of a target abort termination by the bridge when it
responds as the target of a transaction on its secondary interface.
0 = Target abort not signaled on the PCI interface
1 = Target abort signaled on the PCI interface
Master data parity error. This bit is set if the bridge is the bus master of the transaction on the PCI
bus, bit 0 (PERR_EN) in the bridge control register (offset 3Eh see Section 4.29) is set, and the
bridge either asserts PERR on a read transaction or detects PERR asserted on a write transaction.
0 = No data parity error detected on the PCI interface
1 = Data parity error detected on the PCI Interface
Fast back-to-back capable. This bit returns a 1b when read indicating that the secondary PCI
interface of bridge supports fast back-to-back transactions.
66-MHz capable. The bridge operates at a PCI bus CLK frequency of 66 MHz; therefore, this bit
always returns a 1b.
This read/write register specifies the lower limit of the memory addresses that the bridge forwards
downstream. See Table 4-9 for a complete description of the register contents.
15:4MEMBASERWforward memory transactions from one interface to the other. These bits correspond to address bits
3:0RSVDRReserved. Returns 0h when read.
Memory base. Defines the lowest address of the memory address range that determines when to
[31:20] in the memory address. The lower 20 bits are assumed to be 00000h.
4.19 Memory Limit Register
This read/write register specifies the upper limit of the memory addresses that the bridge forwards
downstream. See Table 4-10 for a complete description of the register contents.
15:4MEMLIMITRWforward memory transactions from one interface to the other. These bits correspond to address bits
3:0RSVDRReserved. Returns 0h when read.
Memory limit. Defines the highest address of the memory address range that determines when to
[31:20] in the memory address. The lower 20 bits are assumed to be FFFFFh.
4.20 Prefetchable Memory Base Register
This read/write register specifies the lower limit of the prefetchable memory addresses that the bridge
forwards downstream. See Table 4-11 for a complete description of the register contents.
Table 4-11. Prefetchable Memory Base Register Description
BITFIELD NAMEACCESSDESCRIPTION
Prefetchable memory base. Defines the lowest address of the prefetchable memory address range
15:4PREBASERWcorrespond to address bits [31:20] in the memory address. The lower 20 bits are assumed to be
3:064BIT64-bit memory indicator. These read-only bits indicate that 64-bit addressing is supported for this
that determines when to forward memory transactions from one interface to the other. These bits
00000h. The prefetchable base upper 32 bits register (offset 28h, see Section 4.22) specifies the bit
[63:32] of the 64-bit prefetchable memory address.
R
memory window.
4.21 Prefetchable Memory Limit Register
This read/write register specifies the upper limit of the prefetchable memory addresses that the bridge
forwards downstream. See Table 4-12 for a complete description of the register contents.
Prefetchable memory limit. Defines the highest address of the prefetchable memory address range
15:4PRELIMITRWcorrespond to address bits [31:20] in the memory address. The lower 20 bits are assumed to be
3:064BIT64-bit memory indicator. These read-only bits indicate that 64-bit addressing is supported for this
that determines when to forward memory transactions from one interface to the other. These bits
FFFFFh. The prefetchable limit upper 32 bits register (offset 2Ch, see Section 4.23) specifies the bit
[63:32] of the 64-bit prefetchable memory address.
R
memory window.
4.22 Prefetchable Base Upper 32-Bit Register
This read/write register specifies the upper 32 bits of the prefetchable memory base register. See
Table 4-13 for a complete description of the register contents.
Table 4-15. I/O Base Upper 16-Bit Register Description
BITFIELD NAMEACCESSDESCRIPTION
15:0IOBASERWthat determines when to forward I/O transactions downstream. These bits correspond to address
I/O base upper 16 bits. Defines the upper 16 bits of the lowest address of the I/O address range
bits [31:20] in the I/O address. The lower 20 bits are assumed to be 00000h.
4.25 I/O Limit Upper 16-Bit Register
This read/write register specifies the upper 16 bits of the I/O limit register. See Table 4-16 for a complete
description of the register contents.
15:0IOLIMITRWdetermines when to forward I/O transactions downstream. These bits correspond to address bits
I/O limit upper 16 bits. Defines the upper 16 bits of the top address of the I/O address range that
[31:20] in the I/O address. The lower 20 bits are assumed to be FFFFFh.
4.26 Capabilities Pointer Register
This read-only register provides a pointer into the PCI configuration header where the PCI power
management block resides. Since the PCI power management registers begin at 40h, this register is
hardwired to 40h.
This read/write register is programmed by the system and indicates to the software which interrupt line the
bridge has assigned to it. The default value of this register is FFh, indicating that an interrupt line has not
yet been assigned to the function. Since the bridge does not generate interrupts internally, this register is
a scratch pad register.
The interrupt pin register is read-only 00h indicating that the bridge does not generate internal interrupts.
While the bridge does not generate internal interrupts, it does forward interrupts from the secondary
interface to the primary interface.
11DTSERRRWDiscard timer SERR enable. Applies only in conventional PCI mode. This bit enables the
10DTSTATUSRCUDiscard timer status. This bit indicates if a discard timer expires and a delayed transaction
9SEC_DTRWSelects the number of PCI clocks that the bridge waits for a master on the secondary
8PRI_DECRPrimary discard timer. This bit has no meaning in PCI Express and is hardwired to 0b.
7FBB_ENRWFast back-to-back enable. This bit allows software to enable fast back-to-back
6SRSTRWSecondary bus reset. This bit is set when software wishes to reset all devices
bridge to generate either an ERR_NONFATAL (by default) or ERR_FATAL transaction on
the primary interface when the secondary discard timer expires and a delayed transaction
is discarded from a queue in the bridge. The severity is selectable only if advanced error
reporting is supported.
0 = Do not generate ERR_NONFATAL or ERR_FATAL on the primary interface as a
result of the expiration of the secondary discard timer. Note that an error message
can still be sent if advanced error reporting is supported and bit 10
(DISCARD_TIMER_MASK) in the secondary uncorrectable error mask register
(offset 130h, see Section 5.11) is clear (default).
1 = Generate ERR_NONFATAL or ERR_FATAL on the primary interface if the
secondary discard timer expires and a delayed transaction is discarded from a
queue in the bridges.
interface to repeat a delayed transaction request. The counter starts once the delayed
completion (the completion of the delayed transaction on the primary interface) has
reached the head of the downstream queue of the bridge (i.e., all ordering requirements
have been satisfied and the bridge is ready to complete the delayed transaction with the
initiating master on the secondary bus). If the master does not repeat the transaction
before the counter expires, then the bridge deletes the delayed transaction from its queue
and sets the discard timer status bit.
Table 4-17. Bridge Control Register Description (continued)
BITFIELD NAMEACCESSDESCRIPTION
5MAMRWMaster abort mode. This bit controls the behavior of the bridge when it receives a master
abort or an unsupported request.
0 = Do not report master aborts. Returns FFFF FFFFh on reads and discard data on
writes (default)
1 = Respond with an unsupported request on PCI Express when a master abort is
received on PCI. Respond with target abort on PCI when an unsupported request
completion on PCI Express is received. This bit also enables error signaling on
master abort conditions on posted writes.
4VGA16RWVGA 16-bit decode. This bit enables the bridge to provide full 16-bit decoding for VGA I/O
addresses. This bit only has meaning if the VGA enable bit is set.
3VGARWVGA enable. This bit modifies the response by the bridge to VGA compatible addresses.
If this bit is set, then the bridge decodes and forwards the following accesses on the
primary interface to the secondary interface (and, conversely, block the forwarding of
these addresses from the secondary to primary interface):
• Memory accesses in the range 000A 0000h to 000B FFFFh
• I/O addresses in the first 64 KB of the I/O address space (address bits [31:16] are
0000h) and where address bits [9:0] are in the range of 3B0h to 3BBh or 3C0h to
3DFh (inclusive of ISA address aliases – address bits [15:10] may possess any
value and are not used in the decoding)
If this bit is set, then forwarding of VGA addresses is independent of the value of bit 2
(ISA), the I/O address and memory address ranges defined by the I/O base and limit
registers, the memory base and limit registers, and the prefetchable memory base and
limit registers of the bridge. The forwarding of VGA addresses is qualified by bits 0
(IO_ENB) and 1 (MEMORY_ENB) in the command register (offset 04h, see Section 4.3).
0 = Do not forward VGA compatible memory and I/O addresses from the primary to
secondary interface (addresses defined above) unless they are enabled for
forwarding by the defined I/O and memory address ranges (default).
1 = Forward VGA compatible memory and I/O addresses (addresses defined above)
from the primary interface to the secondary interface (if the I/O enable and memory
enable bits are set) independent of the I/O and memory address ranges and
independent of the ISA enable bit.
2ISARWISA enable. This bit modifies the response by the bridge to ISA I/O addresses. This
applies only to I/O addresses that are enabled by the I/O base and I/O limit registers and
are in the first 64 KB of PCI I/O address space (0000 0000h to 0000 FFFFh). If this bit is
set, then the bridge blocks any forwarding from primary to secondary of I/O transactions
addressing the last 768 bytes in each 1-KB block. In the opposite direction (secondary to
primary), I/O transactions are forwarded if they address the last 768 bytes in each 1K
block.
0 = Forward downstream all I/O addresses in the address range defined by the I/O
base and I/O limit registers (default)
1 = Forward upstream ISA I/O addresses in the address range defined by the I/O base
and I/O limit registers that are in the first 64 KB of PCI I/O address space (top 768
bytes of each 1-KB block)
1SERR_ENRWSERR enable. This bit controls forwarding of system error events from the secondary
interface to the primary interface. The bridge forwards system error events when:
• This bit is set
• Bit 8 (SERR_ENB) in the command register (offset 04h, see Section 4.3) is set
• SERR is asserted on the secondary interface
0 = Disable the forwarding of system error events (default)
1 = Enable the forwarding of system error events
Table 4-17. Bridge Control Register Description (continued)
BITFIELD NAMEACCESSDESCRIPTION
0PERR_ENRWParity error response enable. Controls the bridge's response to data, uncorrectable
address, and attribute errors on the secondary interface. Also, the bridge always forwards
data with poisoning, from conventional PCI to PCI Express on an uncorrectable
conventional PCI data error, regardless of the setting of this bit.
0 = Ignore uncorrectable address, attribute, and data errors on the secondary interface
(default)
1 = Enable uncorrectable address, attribute, and data error detection and reporting on
the secondary interface
4.30 Capability ID Register
This read-only register identifies the linked list item as the register for Subsystem ID and Subsystem
Vendor ID capabilities. The register returns 0Dh when read.
The contents of this read-only register indicate the next item in the linked list of capabilities for the bridge.
This register reads 48h pointing to the PCI Power Management Capabilities registers.
This register, used for system and option card identification purposes, may be required for certain
operating systems. This read-only register is initialized through the EEPROM and can be written through
the subsystem alias register. This register is reset by a PCI Express reset (PERST), a GRST, or the
internally-generated power-on reset.
This register, used for system and option card identification purposes, may be required for certain
operating systems. This read-only register is initialized through the EEPROM and can be written through
the subsystem alias register. This register is reset by a PCI Express reset (PERST), a GRST, or the
internally-generated power-on reset.
The contents of this read-only register indicate the next item in the linked list of capabilities for the bridge.
This register reads 50h pointing to the MSI Capabilities registers.
Table 4-18. Power Management Capabilities Register Description
BITFIELD NAMEACCESSDESCRIPTION
15:11PME_SUPPORTRPME support. This 5-bit field indicates the power states from which the bridge may assert
10D2_SUPPORTRThis bit returns a 1b when read, indicating that the function supports the D2 device power
9D1_SUPPORTRThis bit returns a 1b when read, indicating that the function supports the D1 device power
8:6AUX_CURRENTR3.3 V
5DSIRDevice specific initialization. This bit returns 0b when read, indicating that the bridge does
4RSVDRReserved. Returns 0b when read.
3PME_CLKRPME clock. This bit returns 0b indicating that the PCI clock is not needed to generate PME.
2:0PM_VERSIONRPower management version. If bit 26 (PCI_PM_VERSION_CTRL) in the general control
PME. Because the bridge never generates a PME except on a behalf of a secondary
device, this field is read-only and returns 00000b.
state.
state.
auxiliary current requirements. This field returns 000b since the bridge does not
AUX
generate PME from D3
not require special initialization beyond the standard PCI configuration header before a
generic class driver is able to use it.
register (offset D4h, see Section 4.65) is 0b, then this field returns 010b indicating revision
1.1 compatibility. If PCI_PM_VERSION_CTRL is 1b, then this field returns 011b indicating
revision 1.2 compatibility.
cold
.
4.37 Power Management Control/Status Register
This register determines and changes the current power state of the bridge. No internal reset is generated
when transitioning from the D3
register contents.
state to the D0 state. See Table 4-19 for a complete description of the
Table 4-19. Power Management Control/Status Register Description
BITFIELD NAMEACCESSDESCRIPTION
15PME_STATRPME status. This bit is read-only and returns 0b when read.
14:13DATA_SCALERData scale. This 2-bit field returns 00b when read since the bridge does not use the data
12:9DATA_SELRData select. This 4-bit field returns 0h when read since the bridge does not use the data
8PME_ENRWPME enable. This bit has no function and acts as scratchpad space. The default value for
7:4RSVDRReserved. Returns 0h when read.
3NO_SOFT_RESETRNo soft reset. If bit 26 (PCI_PM_VERSION_CTRL) in the general control register (offset
2RSVDRReserved. Returns 0b when read.
1:0PWR_STATERWPower state. This 2-bit field determines the current power state of the function and sets the
register.
register.
this bit is 0b.
D4h, see Section 4.65) is 0b, then this bit returns 0b for compatibility with version 1.1 of the
PCI Power Management Specification. If PCI_PM_VERSION_CTRL is 1b, then this bit
returns 1b indicating that no internal reset is generated and the device retains its
configuration context when transitioning from the D3
function into a new power state. This field is encoded as follows:
4.38 Power Management Bridge Support Extension Register
This read-only register indicates to host software what the state of the secondary bus will be when the
bridge is placed in D3. See Table 4-20 for a complete description of the register contents.
Table 4-20. PM Bridge Support Extension Register Description
BITFIELD NAMEACCESSDESCRIPTION
7BPCCRBus power/clock control enable. This bit indicates to the host software if the bus secondary
clocks are stopped when the bridge is placed in D3. The state of the BPCC bit is
controlled by bit 11 (BPCC_E) in the general control register (offset D4h, see
Section 4.65).
0 = The secondary bus clocks are not stopped in D3
1 = The secondary bus clocks are stopped in D3
6BSTATERB2/B3 support. This bit is read-only 1b indicating that the bus state in D3 is B2.
5:0RSVDRReserved. Returns 00 0000b when read.
www.ti.com
4.39 Power Management Data Register
The read-only register is not applicable to the bridge and returns 00h when read.
This read-only register identifies the linked list item as the register for message signaled interrupts
capabilities. The register returns 05h when read.
The contents of this read-only register indicate the next item in the linked list of capabilities for the bridge.
This register reads 70h pointing to the subsystem ID capabilities registers.
bridge is capable of generating. This field is read-only 100b indicating that the bridge can
signal 1 interrupt for each IRQ supported on the serial IRQ stream up to a maximum of 16
unique interrupts.
software for the bridge to signal that a serial IRQ has been detected.
0 = MSI signaling is prohibited (default)
1 = MSI signaling is enabled
4.43 MSI Message Lower Address Register
This register contains the lower 32 bits of the address that a MSI message writes to when a serial IRQ is
detected. See Table 4-22 for a complete description of the register contents.
This register contains the upper 32 bits of the address that a MSI message writes to when a serial IRQ is
detected. If this register contains 0000 0000h, then 32-bit addressing is used; otherwise, 64-bit addressing
is used.
This register contains the data that software programmed the bridge to send when it send a MSI message.
See Table 4-23 for a complete description of the register contents.
15:4MSGRWSystem specific message. This field contains the portion of the message that the bridge
3:0MSG_NUMRWMessage number. This portion of the message field may be modified to contain the
forwards unmodified.
message number is multiple messages are enable. The number of bits that are modifiable
depends on the number of messages enabled in the message control register.
1 message = No message data bits can be modified (default)
2 messages = Bit 0 can be modified
4 messages = Bits 1:0 can be modified
8 messages = Bits 2:0 can be modified
16 messages = Bits 3:0 can be modified
This read-only register identifies the linked list item as the register for subsystem ID and subsystem
vendor ID capabilities. The register returns 10h when read.
The contents of this read-only register indicate the next item in the linked list of capabilities for the bridge.
This register reads 00h, indicating no additional capabilities are supported.
This read-only register indicates the capabilities of the bridge related to PCI Express. See Table 4-24 for a
complete description of the register contents.
The device capabilities register indicates the device specific capabilities of the bridge. See Table 4-25 for
a complete description of the register contents.
31:28RSVDRReserved. Returns 0h when read.
27:26CSPLSRUCaptured slot power limit scale. The value in this field is programmed by the host by issuing a
25:18CSPLVRUCaptured slot power limit value. The value in this field is programmed by the host by issuing a
17:16RSVDRReserved. Return 00b when read.
15RBERRRole based error reporting. This bit is hardwired to 1 indicating that this bridge supports Role
14PIPRPower indicator present. This bit is hardwired to 0b indicating that a power indicator is not
13AIPRAttention indicator present. This bit is hardwired to 0b indicating that an attention indicator is not
12ABPRAttention button present. This bit is hardwired to 0b indicating that an attention button is not
11:9EP_L1_LATRUEndpoint L1 acceptable latency. This field indicates the maximum acceptable latency for a
8:6EP_L0S_LATRUEndpoint L0s acceptable latency. This field indicates the maximum acceptable latency for a
5ETFSRExtended tag field supported. This field indicates the size of the tag field not supported.
4:3PFSRPhantom functions supported. This field is read-only 00b indicating that function numbers are
2:0MPSSRMaximum payload size supported. This field indicates the maximum payload size that the
Set_Slot_Power_Limit message. When a Set_Slot_Power_Limit message is received, bits 9:8
are written to this field. The value in this field specifies the scale used for the slot power limit.
00 = 1.0x
01 = 0.1x
10 = 0.01x
11 = 0.001x
Set_Slot_Power_Limit message. When a Set_Slot_Power_Limit message is received, bits 7:0
are written to this field. The value in this field in combination with the slot power limit scale value
(bits 27:26) specifies the upper limit of power supplied to the slot. The power limit is calculated
by multiplying the value in this field by the value in the slot power limit scale field.
Based Error Reporting.
implemented.
implemented.
implemented.
transition from L1 to L0 state. This field can be programmed by writing to the L1_LATENCY
field (bits 15:13) in the general control register (offset D4h, see Section 4.65). The default value
for this field is 110b which indicates a range from 32ms to 64ms. This field cannot be
programmed to be less than the latency for the PHY to exit the L1 state.
transition from L0s to L0 state. This field can be programmed by writing to the L0s_LATENCY
field (bits 18:16) in the general control register (offset D4h, see Section 4.65). The default value
for this field is 110b which indicates a range from 2ms to 4ms. This field cannot be programmed
to be less than the latency for the PHY to exit the L0s state.
not used for phantom functions.
device can support for TLPs. This field is encoded as 010b indicating the maximum payload
size for a TLP is 512 bytes.
15CFG_RTRY_ENBRWConfiguration retry status enable. When this read/write bit is set to 1b, the bridge returns a
14:12MRRSRWMaximum read request size. This field is programmed by host software to set the maximum
11ENSREnable no snoop. This bit is hardwired to 0 since this device never sets the No Snoop attribute
10APPERWAuxiliary power PM enable. This bit has no effect in the bridge.
9PFERPhantom function enable. Since the bridge does not support phantom functions, this bit is
8ETFERExtended tag field enable. Since the bridge does not support extended tags, this bit is
7:5MPSRWMaximum payload size. This field is programmed by host software to set the maximum size of
4EROREnable relaxed ordering. Since the bridge does not support relaxed ordering, this bit is
3URRERWUnsupported request reporting enable. If this bit is set, then the bridge sends an
2FERERWFatal error reporting enable. If this bit is set, then the bridge is enabled to send ERR_FATAL
completion with completion retry status on PCI Express if a configuration transaction
forwarded to the secondary interface did not complete within the implementation specific
time-out period. When this bit is set to 0b, the bridge does not generate completions with
completion retry status on behalf of configuration transactions. The default value of this bit is
0b.
size of a read request that the bridge can generate. The bridge uses this field to determine
how much data to fetch on a read request. This field is encoded as:
Table 4-26. Device Control Register Description (continued)
BITFIELD NAMEACCESSDESCRIPTION
1NFERERWNonfatal error reporting enable. If this bit is set, then the bridge is enabled to send
ERR_NONFATAL messages to the root complex when a system error event occurs.
0 = Do not report nonfatal errors to the root complex (default)
1 = Report nonfatal errors to the root complex
0CERERWCorrectable error reporting enable. If this bit is set, then the bridge is enabled to send
ERR_COR messages to the root complex when a system error event occurs.
0 = Do not report correctable errors to the root complex (default)
1 = Report correctable errors to the root complex
4.51 Device Status Register
The device status register provides PCI Express device specific information to the system. See Table 4-27
for a complete description of the register contents.
15:6RSVDRReserved. Returns 00 0000 0000b when read.
5PENDRUTransaction pending. This bit is set when the bridge has issued a non-posted transaction that
4APDRUAUX power detected. This bit indicates that AUX power is present.
3URDRCUUnsupported request detected. This bit is set by the bridge when an unsupported request is
2FEDRCUFatal error detected. This bit is set by the bridge when a fatal error is detected.
1NFEDRCUNonfatal error detected. This bit is set by the bridge when a nonfatal error is detected.
0CEDRCUCorrectable error detected. This bit is set by the bridge when a correctable error is detected.
has not been completed.
0 = No AUX power detected
1 = AUX power detected
received.
4.52 Link Capabilities Register
The link capabilities register indicates the link specific capabilities of the bridge. See Table 4-28 for a
complete description of the register contents.
Table 4-28. Link Capabilities Register Description
BITFIELD NAMEACCESSDESCRIPTION
31:24PORT_NUMRPort number. This field indicates port number for the PCI Express link. This field is read-only
23:22RSVDRReserved. Return 00b when read.
21LBN_CAPRLink bandwidth notification. This bit is hardwired to 0b since this field is not applicable to a
20DLLLAR_CAPRDLL link active reporting capable. This bit is hardwired to 0b since the bridge does not support
19SDER_CAPRSurprise down error reporting capable. This bit is hardwired to 0b since the bridge does not
18CLK_PMRClock Power Management. This bit is hardwired to 1 to indicate that XIO2001 supports Clock
17:15L1_LATENCYRL1 exit latency. This field indicates the time that it takes to transition from the L1 state to the L0
14:12L0S_LATENCYRL0s exit latency. This field indicates the time that it takes to transition from the L0s state to the
11:10ASLPMSRActive state link PM support. This field indicates the level of active state power management
9:4MLWRMaximum link width. This field is encoded 00 0001b to indicate that the bridge only supports a
3:0MLSRMaximum link speed. This field is encoded 1h to indicate that the bridge supports a maximum
00h indicating that the link is associated with port 0.
bridge.
this capability.
support this capability.
Power Management through CLKREQ protocol.
state. Bit 6 (CCC) in the link control register (offset 80h, see Section 4.53) equals 1b for a
common clock and equals 0b for an asynchronous clock.
For a common reference clock, the value of this field is determined by bits 20:18
(L1_EXIT_LAT_ASYNC) of the control and diagnostic register 1 (offset C4h, see Section 4.62).
For an asynchronous reference clock, the value of this field is determined by bits 17:15
(L1_EXIT_LAT_COMMON) of the control and diagnostic register 1 (offset C4h, see
Section 4.62).
L0 state. Bit 6 (CCC) in the link control register (offset 80h, see Section 4.53) equals 1b for a
common clock and equals 0b for an asynchronous clock.
For a common reference clock, the value of 011b indicates that the L1 exit latency falls between
256 ns to less than 512 ns.
For an asynchronous reference clock, the value of 100b indicates that the L1 exit latency falls
between 512 ns to less than 1 ms.
that the bridge supports. The value 11b indicates support for both L0s and L1 through active
state power management.
x1 PCI Express link.
link speed of 2.5 Gb/s.
4.53 Link Control Register
The link control register controls link specific behavior. See Table 4-29 for a complete description of the
register contents.
Table 4-29. Link Control Register Description (continued)
BITFIELD NAMEACCESSDESCRIPTION
9HWAW_DISRHardware autonomous width disable. This bit is hardwired to 0b since this field is not
supported by this bridge.
8CPM_ENRWClock Power Management Enable. This bit is used to enable the bridge to use CLKREQ
for clock power management
0 = Clock Power Management is disabled. CLKREQ is held low.
1 = Clock Power Management is enabled and the bridge is permitted to use the
CLKREQ signal to allow the REFCLK input to be stopped
The default value for this is bit is determined by bit 23 (CPM_EN_DEF_OVRD) in
the general control register (offset D4h, see Section 4.65).
7ESRWExtended synch. This bit forces the bridge to extend the transmission of FTS ordered sets
and an extra TS2 when exiting from L1 prior to entering to L0.
0 = Normal synch (default)
1 = Extended synch
6CCCRWCommon clock configuration. When this bit is set, it indicates that the bridge and the
device at the opposite end of the link are operating with a common clock source. A value
of 0b indicates that the bridge and the device at the opposite end of the link are operating
with separate reference clock sources. The bridge uses this common clock configuration
information to report the L0s and L1 exit latencies.
0 = Reference clock is asynchronous (default)
1 = Reference clock is common
5RLRRetrain link. This bit has no function and is read-only 0b.
4LDRLink disable. This bit has no function and is read-only 0b.
3RCBRWRead completion boundary. This bit is an indication of the RCB of the root complex. The
state of this bit has no affect on the bridge, since the RCB of the bridge is fixed at 128
bytes.
0 = 64 bytes (default)
1 = 128 bytes
2RSVDRReserved. Returns 0b when read.
1:0ASLPMCRWActive state link PM control. This field enables and disables the active state PM. The
default value for this is bit is determined by bits 29:28 (ASPM_CTRL_DEF_OVRD) in the
general control register (offset D4h, see Section 4.65).
00 = Active state PM disabled (default)
01 = L0s entry enabled
10 = L1 entry enabled
11 = L0s and L1 entry enabled
www.ti.com
4.54 Link Status Register
The link status register indicates the current state of the PCI Express link. See Table 4-30 for a complete
description of the register contents.
15LABWRLink autonomous bandwidth status. This bit has no function and is read-only 0b.
14LBWMRLink bandwidth management status. This bit has no function and is read-only 0b.
13DLLLARData link layer link active. This bit has no function and is read-only 0b.
Table 4-30. Link Status Register Description (continued)
BITFIELD NAMEACCESSDESCRIPTION
12SCCRSlot clock configuration. This bit indicates that the bridge uses the same physical reference
11LTRLink training. This bit has no function and is read-only 0b.
10TERRetrain link. This bit has no function and is read-only 0b.
9:4NLWRNegotiated link width. This field is read-only 00 0001b indicating the lane width is x1.
3:0LSRLink speed. This field is read-only 1h indicating the link speed is 2.5 Gb/s.
clock that the platform provides on the connector. If the bridge uses an independent clock
irrespective of the presence of a reference on the connector, then this bit must be cleared.
0 = Independent 125-MHz reference clock is used
1 = Common 100-MHz reference clock is used
4.55 Serial-Bus Data Register
The serial-bus data register reads and writes data on the serial-bus interface. Write data is loaded into this
register prior to writing the serial-bus slave address register (offset B2h, see Section 4.57) that initiates the
bus cycle. When reading data from the serial bus, this register contains the data read after bit 5
(REQBUSY) of the serial-bus control and status register (offset B3h, see Section 4.58) is cleared. This
register is reset by a PCI Express reset (PERST), a GRST, or the internally-generated power-on reset.
The value written to the serial-bus word address register represents the word address of the byte being
read from or written to the serial-bus device. The word address is loaded into this register prior to writing
the serial-bus slave address register (offset B2h, see Section 4.57) that initiates the bus cycle. This
register is reset by a PCI Express reset (PERST), a GRST, or the internally-generated power-on reset.
The serial-bus slave address register indicates the slave address of the device being targeted by the
serial-bus cycle. This register also indicates if the cycle is a read or a write cycle. Writing to this register
initiates the cycle on the serial interface. See Table 4-31 for a complete description of the register
contents.
(1) These bits are reset by a PCI Express reset (PERST), a GRST, or the internally-generated power-on reset.
SLAVE_ADDRRWSerial-bus slave address. This 7-bit field is the slave address for a serial-bus read or write
(1)
0
RW_CMDRWRead/write command. This bit determines if the serial-bus cycle is a read or a write cycle.
transaction. The default value for this field is 000 0000b.
0 = A single byte write is requested (default).
1 = A single byte read is requested.
www.ti.com
4.58 Serial-Bus Control and Status Register
The serial-bus control and status register controls the behavior of the serial-bus interface. This register
also provides status information about the state of the serial bus. See Table 4-32 for a complete
description of the register contents.
Table 4-32. Serial-Bus Control and Status Register Description (continued)
BITFIELD NAMEACCESSDESCRIPTION
(1)
2
SBTESTRWSerial-bus test. This bit is used for internal test purposes. This bit controls the clock source
for the serial interface clock.
0 = Serial-bus clock at normal operating frequency ~ 60 kHz (default)
1 = Serial-bus clock frequency increased for test purposes ~ 4 MHz
(1)
1
SB_ERRRCUSerial-bus error. This bit is set when an error occurs during a software-initiated serial-bus
cycle.
0 = No error
1 = Serial-bus error
(1)
0
ROM_ERRRCUSerial EEPROM load error. This bit is set when an error occurs while downloading registers
from serial EEPROM.
0 = No error
1 = EEPROM load error
4.59 GPIO Control Register
This register controls the direction of the five GPIO terminals. This register has no effect on the behavior
of GPIO terminals that are enabled to perform secondary functions. The secondary functions share GPIO0
(CLKRUN), GPIO1 (PWR_OVRD), GPIO3 (SDA), and GPIO4 (SCL). See Table 4-33 for a complete
description of the register contents.
This register reads the state of the input mode GPIO terminals and changes the state of the output mode
GPIO terminals. Writing to a bit that is in input mode or is enabled for a secondary function is ignored. The
secondary functions share GPIO0 (CLKRUN), GPIO1 (PWR_OVRD), GPIO3 (SDA), and GPIO4 (SCL).
The default value at power up depends on the state of the GPIO terminals as they default to
general-purpose inputs. See Table 4-34 for a complete description of the register contents.
Table 4-35. Control and Diagnostic Register 0 Description (continued)
BITFIELD NAMESDESCRIPTION
18ALT_ERROR_REPRWAlternate Error Reporting. This bit controls the method that the XIO2001 uses for error
17:16RSVDRReserved. Returns 00b when read.
(1)
15:14
13:12RSVDRReserved. Returns 00b when read.
11:7
RSVDRWReserved. Bits 15:14 default to 00b. If this register is programmed via EEPROM or another
(1)
RSVDRWReserved. Bits 11:7 default to 00000b. If this register is programmed via EEPROM or
6:3RSVDRReserved. Returns 0h when read.
(1)
2
CFG_ACCESSRWConfiguration access to memory-mapped registers. When this bit is set, the bridge allows
_MEM_REGconfiguration access to memory-mapped configuration registers.
(1)
1
RSVDRWReserved. Bit 1 defaults to 0b. If this register is programmed via EEPROM or another
(1)
0
FORCE_CLKREQRWForce CLKREQ. When this bit is set, the bridge will force the CLKREQ output to always be
Table 4-36. Control and Diagnostic Register 1 Description
BITFIELD NAMEACCESSDESCRIPTION
32:21RSVDRReserved. Returns 000h when read.
(1)
20:18
17:15
14:11
10
9:6
L1_EXIT_LAT_ARWL1 exit latency for asynchronous clock. When bit 6 (CCC) of the link control register (offset
SYNC80h, see Section 4.53) is set, the value in this field is mirrored in bits 17:15 (L1_LATENCY)
(1)
L1_EXIT_LAT_CRWL1 exit latency for common clock. When bit 6 (CCC) of the link control register (offset 80h, see
OMMONSection 4.53) is clear, the value in this field is mirrored in bits 17:15 (L1_LATENCY) field in the
(1)
RSVDRWReserved. Bits 14:11 default to 0000b. If this register is programmed via EEPROM or another
(1)
SBUS_RESET_MRWSecondary bus reset bit mask. When this bit is set, the bridge masks the reset caused by bit 6
ASK(SRST) of the bridge control register (offset 3Eh, see Section 4.29). This bit defaults to 0b.
(1)
L1ASPM_TIMERRWL1ASPM entry timer. This field specifies the value (in 512-ns ticks) of the L1ASPM entry timer.
field in the link capabilities register (offset 7Ch, see Section 4.52). This field defaults to 100b.
link capabilities register (offset 7Ch, see Section 4.52). This field defaults to 100b.
mechanism, the value written into this field must be 0000b.
This field defaults to 0100b.
(1) These bits are reset by a PCI Express reset (PERST), a GRST, or the internally-generated power-on reset.
Table 4-37. Control and Diagnostic Register 2 Description
BITFIELD NAME ACCESSDESCRIPTION
(1)
31:24
23:16
15:13PHY_REVRPHY revision number
12:8
4:0
(1) These bits are reset by a PCI Express reset (PERST), a GRST, or the internally-generated power-on reset.
N_FTS_RWN_FTS for asynchronous clock. When bit 6 (CCC) of the link control register (offset A0h, see
ASYNC_CLKSection 4.53) is clear, the value in this field is the number of FTS that are sent on a transition from
(1)
N_FTS_RWN_FTS for common clock. When bit 6 (CCC) of the link control register (offset A0h, see Section 4.53)
COMMON_is set, the value in this field is the number of FTS that are sent on a transition from L0s to L0. This
CLKfield defaults to 14h.
(1)
LINK_NUMRWLink number
(1)
7
EN_L2_PWR_RWEnable L2 Power Savings
SAVE
6RSVDRReserved. Returns 0b when read.
(1)
5
BAR0_ENRWBAR 0 Enable.
(1)
RSVDRWReserved. Bits 4:0 default to 00000b. If this register is programmed via EEPROM or another
L0s to L0. This field shall default to 32h.
0= Power savings not enabled when in L2
1= Power savings enabled when in L2.
0 = BAR at offset 10h is disabled (default)
1 = BAR at offset 10h is enabled
mechanism, then the value written into this field must be 00000b.
4.64 Subsystem Access Register
The contents of this read/write register are aliased to the subsystem vendor ID and subsystem ID registers
at PCI offsets 84h and 86h. See Table 4-38 for a complete description of the register contents.
(1) These bits are reset by a PCI Express reset (PERST), a GRST, or the internally-generated power-on reset.
CFG_RETRY_CNRWConfiguration retry counter. Configures the amount of time that a configuration request must be
TRretried on the secondary PCI bus before it may be completed with configuration retry status on
the PCI Express side.
00 = 25 ms
01 = 1 ms
10 = 25 ms (default)
11 = 50 ms
(1)
ASPM_CTRL_DERWActive State Power Management Control Default Override. These bits are used to determine the
F_OVRDpower up default for bits 1:0 of the Link Control Register in the PCI Express Capability Structure.
00 = Power on default indicates that the active state power management is disable (00b)
01 = (default)
10 = Power on default indicates that the active state power management is enabled for L0s
11 = (01b)
Power on default indicates that the active state power management is enabled for L1s
(10b)
Power on default indicates that the active state power management is enabled for L0s
and L1s (11b)
(1)
LOW_POWER_ERWLow-power enable. When this bit is set, the half-amplitude, no pre-emphasis mode for the PCI
NExpress TX drivers is enabled. The default for this bit is 0b.
(1)
PCI_PM_VERSIORWPCI power management version control. This bit controls the value reported in bits 2:0
N_CTRL(PM_VERSION) in the power management capabilities register (offset 4Ah, see Section 4.36). It
also controls the value of bit 3 (NO_SOFT_RESET) in the power management control/status
register (offset 4Ch, see Section 4.37).
0 = Version fields reports 010b and NO_SOFT_RESET reports 0b for Power
Management 1.1 compliance
1 = Version fields reports 011b and NO_SOFT_RESET reports 1b for Power
Management 1.2 compliance (default)
(1)
RSVDRWReserved. Bit 25 defaults to 0b. If this register is programmed via EEPROM or another
mechanism, then the value written into this field must be 0b.
24RSVDRReserved. Returns 0b when read.
(1)
CPM_EN_DEF_ORWClock power management enable default override. This bit determines the power-up default for
VRDbits 1:0 (CPM_EN) of the link control register (offset 80h, see Section 4.53) in the PCI Express
Capability structure.
0 = Power-on default indicates that clock power management is disabled (00b) (default)
1 = Power-on default indicates that clock power management is enabled for L0s and L1
Table 4-39. General Control Register Description (continued)
BITFIELD NAMEACCESSDESCRIPTION
(1)
22:20
19
18:16
15:13
12
11
10
(2) These bits are sticky and must retain their value when the bridge is powered by V
POWER_OVRDRWPower override. This bit field determines how the bridge responds when the slot power limit is
less than the amount of power required by the bridge and the devices behind the bridge.
000 = Ignore slot power limit (default).
001 = Assert the PWR_OVRD terminal.
010 = Disable secondary clocks selected by the clock mask register.
011 = Disable secondary clocks selected by the clock mask register and assert the
PWR_OVRD terminal.
100 = Respond with unsupported request to all transactions except for configuration
transactions (type 0 or type 1) and set slot power limit messages.
101,110, Reserved
111 =
(1)
READ_PREFETCRWRead Prefetch Disable. This bit is used to control the pre-fetch functionality on PCI memory read
H_DIStransactions.
0 = Memory read, memory read line, and memory read multiple will be treated as
prefetchable reads (default)
1 = Memory read line, and memory read multiple will be treated as pre-fetchable reads.
Memory read will not be prefetchable. No auto-prefetch reads will be made for these
requests.
(1)
L0s_LATENCYRWL0s maximum exit latency. This field programs the maximum acceptable latency when exiting the
L0s state. This sets bits 8:6 (EP_L0S_LAT) in the device capabilities register (offset 74h, see
Section 4.49).
000 = Less than 64 ns (default)
001 = 64 ns up to less than 128 ns
010 = 128 ns up to less than 256 ns
011 = 256 ns up to less than 512 ns
100 = 512 ns up to less than 1 ms
101 = 1 ms up to less than 2 ms
110 = 2 ms to 4 ms
111 = More than 4 ms
(1)
L1_LATENCYRWL1 maximum exit latency. This field programs the maximum acceptable latency when exiting the
L1 state. This sets bits 11:9 (EP_L1_LAT) in the device capabilities register (offset 74h, see
Section 4.49).
000 = Less than 1 ms (default)
001 = 1 ms up to less than 2 ms
010 = 2 ms up to less than 4 ms
011 = 4 ms up to less than 8 ms
100 = 8 ms up to less than 16 ms
101 = 6 ms up to less than 32 ms
110 = 32 ms to 64 ms
111 = More than 64 ms
(1)
VC_CAP_ENRVC Capability Structure Enable. This bit is hardwired to 0b indicating that the VC Capability
structure is permanently disabled.
(2)
BPCC_ERWBus power clock control enable. This bit controls whether the secondary bus PCI clocks are
stopped when the XIO2001 is placed in the D3 state. It is assumed that if the secondary bus
clocks are required to be active, that a reference clock continues to be provided on the PCI
Express interface.
0 = Secondary bus clocks are not stopped in D3 (default)
1 = Secondary bus clocks are stopped on D3
(2)
BEACON_ENABLRWBeacon enable. This bit controls the mechanism for waking up the physical PCI Express link
Ewhen in L2.
0 = WAKE mechanism is used exclusively. Beacon is not used (default)
1 = Beacon and WAKE mechanisms are used
MIN_POWER_VARWMinimum power value. This value is programmed to indicate the minimum power requirements.
LUEThis value is multiplied by the minimum power scale field (bits 9:8) to determine the minimum
power requirements for the bridge. The default is 5Fh, indicating that the bridge requires 0.95 W
of power. This field can be reprogrammed through an EEPROM or the system BIOS.
4.66 Clock Control Register
This register enables and disables the PCI clock outputs (CLKOUT). See Table 4-40 for a complete
description of the register contents.
This register selects which PCI bus clocks are disabled when bits 22:20 (POWER_OVRD) in the general
control register (offset D4h, see Section 4.65) are set to 010h or 011h. This register has no effect on the
clock outputs if the POWER_OVRD bits are not set to 010h or 011h or if the slot power limit is greater
than the power required. See Table 4-41 for a complete description of the register contents.
The arbiter control register controls the bridge internal arbiter. The arbitration scheme used is a two-tier
rotational arbitration. The bridge is the only secondary bus master that defaults to the higher priority
arbitration tier. See Table 4-43 for a complete description of the register contents.
Bus parking mode. This bit determines where the internal arbiter parks the secondary bus.
When this bit is set, the arbiter parks the secondary bus on the bridge. When this bit is
cleared, the arbiter parks the bus on the last device mastering the secondary bus.
0 = Park the secondary bus on the last secondary bus master (default)
1 = Park the secondary bus on the bridge
Bridge tier select. This bit determines in which tier the bridge is placed in the arbitration
scheme.
The arbiter request mask register enables and disables support for requests from specific masters on the
secondary bus. The arbiter request mask register also controls if a request input is automatically masked
on an arbiter time-out. See Table 4-44 for a complete description of the register contents.
ARB_TIMEOUTRWArbiter time-out. This bit enables the arbiter time-out feature. The arbiter time-out is
(1)
6
AUTO_MASKRWAutomatic request mask. This bit enables automatic request masking when an arbiter
(1)
5
REQ5_MASKRW
defined as the number of PCI clocks after the PCI bus has gone idle for a device to assert
FRAME before the arbiter assumes the device will not respond.
0 = Arbiter time disabled (default)
1 = Arbiter time-out set to 16 PCI clocks
The arbiter time-out status register contains the status of each request (request 5–0) time-out. The
time-out status bit for the respective request is set if the device did not assert FRAME after the arbiter
time-out value. See Table 4-45 for a complete description of the register contents.
Poll mode. This bit selects between continuous and quiet mode.
0 = Continuous mode (default)
1 = Quiet mode
RW Drive mode. This bit selects the behavior of the serial IRQ controller during the
recovery cycle.
0 = Drive high (default)
1 = 3-state
4.73 Serial IRQ Edge Control Register
This register controls the edge mode or level mode for each IRQ in the serial IRQ stream. See Table 4-47
for a complete description of the register contents.
This register indicates when a level mode IRQ is signaled on the serial IRQ stream. After a level mode
IRQ is signaled, a write-back of 1b to the asserted IRQ status bit re-arms the interrupt. IRQ interrupts that
are defined as edge mode in the serial IRQ edge control register are not reported in this status register.
See Table 4-48 for a complete description of the register contents.
Request count limit. Determines the number of Pre-Fetch reads that takes place in each
burst.
PFA_REQ_
(1)
11:8
CNT_LIMIT
PFA_CPL_CACHE_
7:6RW
MODE
5:4RSVDRReserved. Returns 00b when read.
RW4'h0 = Auto-prefetch agent is disabled.
4'h1 = Thread is limited to one buffer. No auto-prefetch reads will be generated.
4'h2:F = Thread will be limited to initial read and (PFA_REQ_CNT_LIMIT – 1)
Completion cache mode. Determines the rules for completing the caching process.
00 = No caching.
•Pre-fetching is disabled.
•All remaining read completion data will be discarded after any of the data has been
returned to the PCI master.
01 = Light caching.
•Pre-fetching is enabled.
•All remaining read completion data will be discarded after data has been returned to
the PCI master and the PCI master terminated the transfer.
•All remaining read completion data will be cached after data has been returned to the
PCI master and the bridge has terminated the transfer with RETRY.
10 = Full caching.
•Pre-fetching is enabled.
•All remaining read completion data will be cached after data has been returned to the
PCI master and the PCI master terminated the transfer.
•All remaining read completion data will be cached after data has been returned to the
PCI master and the bridge has terminated the transfer with RETRY.
11 = Reserved.
SCPS212D–MAY 2009–REVISED JANUARY 2010
Request Length Limit. Determines the number of bytes in the thread that the pre-fetch
agent will read for that thread.
(1) These bits are reset by a PCI Express reset (PERST), a GRST, or the internally-generated power-on reset.
4.76 Cache Timer Transfer Limit Register
This register is used to set the number of PCI cycle starts that have to occur without a read hit on the
completion data buffer, before the cache data can be discarded. See Table 4-50 for a complete
description of the register contents.
Table 4-50. Cache Timer Transfer Limit Register Description
BITFIELD NAMEACCESSDESCRIPTION
15:8RSVDRReserved. Returns 00h when read.
CACHE_TMR_XFRNumber of PCI cycle starts that have to occur without a read hit on the completion data
(1)
7:0
(1) These bits are reset by a PCI Express reset (PERST), a GRST, or the internally-generated power-on reset.
_LIMITbuffer, before the cache data can be discarded.
RW
4.77 Cache Timer Lower Limit Register
Minimum number of clock cycles that must have passed without a read hit on the completion data buffer
before the "cache miss limit" check can be triggered. See Table 4-51 for a complete description of the
register contents.
CACHE_TIMERMinimum number of clock cycles that must have passed without a read hit on the
(1)
11:0
(1) These bits are reset by a PCI Express reset (PERST), a GRST, or the internally-generated power-on reset.
_LOWER_LIMITcompletion data buffer before the "cache miss limit" check can be triggered.
RW
4.78 Cache Timer Upper Limit Register
Discard cached data after this number of clock cycles have passed without a read hit on the completion
data buffer. See Table 4-52 for a complete description of the register contents.
The programming model of the PCI Express extended configuration space is compliant to the PCI Express
Base Specification and the PCI Express to PCI/PCI-X Bridge Specification programming models. The PCI
Express extended configuration map uses the PCI Express advanced error reporting capability.
All bits marked with a ┦ are sticky bits and are reset by a global reset (GRST) or the internally-generated
power-on reset. All bits marked with a ┦ are reset by a PCI Express reset (PERST), a GRST, or the
internally-generated power-on reset. The remaining register bits are reset by a PCI Express hot reset,
PERST, GRST, or the internally-generated power-on reset.
(1) These bits are reset by a PCI Express reset (PERST), a GRST, or the internally-generated power-on reset.
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
104h
108h
10Ch
110h
114h
118h
11Ch
120h
124h
128h
12Ch
130h
134h
138h
13Ch
140h
144h
148h
5.1Advanced Error Reporting Capability ID Register
This read-only register identifies the linked list item as the register for PCI Express advanced error
reporting capabilities. The register returns 0001h when read.
5.2Next Capability Offset/Capability Version Register
This read-only register identifies the next location in the PCI Express extended capabilities link list. The
upper 12 bits in this register shall be 000h, indicating that the Advanced Error Reporting Capability is the
last capability in the linked list. The least significant four bits identify the revision of the current capability
block as 1h.
The uncorrectable error status register reports the status of individual errors as they occur on the primary
PCI Express interface. Software may only clear these bits by writing a 1b to the desired location. See
Table 5-2 for a complete description of the register contents.
The uncorrectable error mask register controls the reporting of individual errors as they occur. When a
mask bit is set to 1b, the corresponding error status bit is not set, PCI Express error messages are
blocked, the header log is not loaded, and the first error pointer is not updated. See Table 5-3 for a
complete description of the register contents.
The uncorrectable error severity register controls the reporting of individual errors as ERR_FATAL or
ERR_NONFATAL. When a bit is set, the corresponding error condition is identified as fatal. When a bit is
cleared, the corresponding error condition is identified as nonfatal. See Table 5-4 for a complete
description of the register contents.
0 = Error condition is signaled using ERR_NONFATAL
1 = Error condition is signaled using ERR_FATAL
11:6RSVDRReserved. Returns 000 000b when read.
5SD_ERROR_SEVRRSD error severity. Not supported, returns 1b when read.
(1)
4
DLL_ERROR_SEVRRWData link protocol error severity
0 = Error condition is signaled using ERR_NONFATAL
1 = Error condition is signaled using ERR_FATAL
3:1RSVDRReserved. Retirms 000b wjem read/
0RSVDRReserved. Returns 1h when read.
5.6Correctable Error Status Register
The correctable error status register reports the status of individual errors as they occur. Software may
only clear these bits by writing a 1b to the desired location. See Table 5-5 for a complete description of
the register contents.
The correctable error mask register controls the reporting of individual errors as they occur. When a mask
bit is set to 1b, the corresponding error status bit is not set, PCI Express error messages are blocked, the
header log is not loaded, and the first error pointer is not updated. See Table 5-6 for a complete
description of the register contents.
5.8Advanced Error Capabilities and Control Register
The advanced error capabilities and control register allows the system to monitor and control the
advanced error reporting capabilities. See Table 5-7 for a complete description of the register contents.
Table 5-7. Advanced Error Capabilities and Control Register Description
BITFIELD NAMEACCESSDESCRIPTION
31:9RSVDRReserved. Returns 000 0000 0000 0000 0000 0000b when read.
(1)
8
ECRC_CHK_ENRWExtended CRC check enable
0 = Extended CRC checking is disabled
1 = Extended CRC checking is enabled
7ECRC_CHK_CAPABLERExtended CRC check capable. This read-only bit returns a value of 1b indicating that the
(1)
6
ECRC_GEN_ENRWExtended CRC generation enable
5ECRC_GEN_CAPABLERExtended CRC generation capable. This read-only bit returns a value of 1b indicating
(1)
4:0
FIRST_ERRRUFirst error pointer. This 5-bit value reflects the bit position within the uncorrectable error
(1) These bits are reset by a PCI Express reset (PERST), a GRST, or the internally-generated power-on reset.
bridge is capable of checking extended CRC information.
0 = Extended CRC generation is disabled
1 = Extended CRC generation is enabled
that the bridge is capable of generating extended CRC information.
status register (offset 104h, see Section 5.3) corresponding to the class of the first error
condition that was detected.
5.9Header Log Register
The header log register stores the TLP header for the packet that lead to the most recently detected error
condition. Offset 11Ch contains the first DWORD. Offset 128h contains the last DWORD (in the case of a
4DW TLP header). Each DWORD is stored with the least significant byte representing the earliest
transmitted. This register shall only be reset by a PCI Express reset (PERST), a GRST, or the
internally-generated power-on reset.
5.10 Secondary Uncorrectable Error Status Register
The secondary uncorrectable error status register reports the status of individual PCI bus errors as they
occur. Software may only clear these bits by writing a 1b to the desired location. See Table 5-8 for a
complete description of the register contents.
The secondary uncorrectable error mask register controls the reporting of individual errors as they occur.
When a mask bit is set to 1b, the corresponding error status bit is not set, PCI Express error messages
are blocked, the header log is not loaded, and the first error pointer is not updated. See Table 5-9 for a
complete description of the register contents.
The uncorrectable error severity register controls the reporting of individual errors as ERR_FATAL or
ERR_NONFATAL. When a bit is set, the corresponding error condition is identified as fatal. When a bit is
cleared, the corresponding error condition is identified as nonfatal. See Table 5-10 for a complete
description of the register contents.