XIO2213B
PCI Express™ TO 1394b OHCI WITH 3-PORT PHY
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.
• Fully Compliant With PCI Express Base
Specification, Revision 1.1
• Utilizes 100-MHz Differential PCI Express
Common Reference Clock or 125-MHz SingleEnded Reference Clock• EEPROM Configuration Support to Load Global
• Fully Supports Provisions of IEEE Std P1394b2002• Support for D1, D2, D3
• Fully Compliant With Provisions of IEEE Std• Active-State Link Power Management Saves
1394-1995 for a High-Performance Serial BusPower When Packet Activity on the PCI
and IEEE Std 1394a-2000Express Link Is Idle, Using Both L0s and L1
• Fully Compliant With 1394 Open Host
Controller Interface (OHCI) Specification,• Eight 3.3-V Multifunction General-Purpose I/O
Revision 1.1 and Revision 1.2 Draft(GPIO) Terminals
• Three IEEE Std 1394b Fully Compliant Cable
Ports at 100M Bit/s, 200M Bit/s, 400M Bit/s, and
800M Bit/s
• Cable Ports Monitor Line Conditions for Active
Connection to Remote Node
• Cable Power Presence Monitoring
Unique ID for 1394 Fabric
hot
States
1
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.
2OHCI-Lynx is a trademark of Texas Instruments.
3PCI Express is a trademark of PCI-SIG.
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.
XIO2213B
www.ti.com
2Overview
The Texas Instruments XIO2213B is a single-function PCI Express™ (PCIe) to PCI local bus translation
bridge, where the PCI bus interface is internally connected to a 1394b open host controller/link-layer
controller with a 3-port 1394b physical layer (PHY). When the XIO2213B is properly configured, this
solution provides full PCIe and 1394b functionality and performance.
The TI XIO2213B is a PCIe to PCI translation bridge, where the PCI bus interface is internally connected
to a 1394b open host controller/link-layer controller with a 3-port 1394b PHY. The PCIe to PCI translation
bridge is fully compatible with the PCI Express to PCI/PCI-X Bridge Specification, Revision 1.0. Also, the
bridge supports the standard PCI-to-PCI bridge programming model. The 1394b OHCI controller function
is fully compatible with IEEE Std 1394b and the latest 1394 Open Host Controller Interface (OHCI)
Specification.
The XIO2213B simultaneously supports up to four posted write transactions, four nonposted transactions,
and four completion transactions pending in each direction at any time. Each posted write data queue and
completion data queue can store up to 8K bytes of data. The nonposted data queues can store up to 128
bytes of data.
The PCIe interface supports a ×1 link operating at full 250 Mbit/s packet throughput in each direction
simultaneously. Also, the bridge supports the advanced error reporting capability including ECRC as
defined in the PCI Express Base Specification, Revision 1.1. Supplemental firmware or software is
required to fully utilize both of these features.
Robust pipeline architecture is implemented to minimize system latency. If parity errors are detected,
packet poisoning is supported for both upstream and downstream operations.
SCPS210F –OCTOBER 2008–REVISED MAY 2013
PCIe power management (PM) features include active-state link PM, PME mechanisms, and all
conventional PCI D states. If the active-state link PM is enabled, 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. The bridge is compliant with the latest PCI Bus Power Management Specification and provides
several low-power modes, which enable the host power system to further reduce power consumption
Eight general-purpose inputs and outputs (GPIOs), configured through accesses to the PCIe configuration
space, allow for further system control and customization.
Deep FIFOs are provided to buffer 1394 data and accommodate large host bus latencies. The device
provides physical write posting and a highly tuned physical data path for SBP-2 performance. The device
is capable of transferring data between the PCIe bus and the 1394 bus at 100M bit/s, 200M bit/s, 400M
bit/s, and 800M bit/s. The device provides three 1394 ports that have separate cable bias (TPBIAS).
As required by the 1394 Open Host Controller Interface (OHCI) Specification, internal control registers are
memory mapped and nonprefetchable. This configuration header is accessed through configuration cycles
specified by PCIe, and it provides plug-and-play (PnP) compatibility.
The PHY provides the digital and analog transceiver functions needed to implement a 3-port node in a
cable-based 1394 network. Each cable port incorporates two differential line transceivers. The
transceivers include circuitry to monitor the line conditions as needed for determining connection status,
for initialization and arbitration, and for packet reception and transmission. An optional external 2-wire
serial EEPROM interface is provided to load the global unique ID for the 1394 fabric.
The XIO2213B requires an external 98.304-MHz crystal oscillator to generate a reference clock. The
external clock drives an internal phase-locked loop (PLL), which generates the required reference signal.
This reference signal provides the clock signals that control transmission of the outbound encoded
information. The power-down (PD) function, when enabled by asserting the PD terminal high, stops
operation of the PLL. Data bits to be transmitted through the cable ports are latched internally, combined
serially, encoded, and transmitted at 98.304, 196.608, 393.216, 491.52, or 983.04 Mbit/s (referred to as
S100, S200, S400, S400B, or S800 speed, respectively) as the outbound information stream.
To ensure that the XIO2213B conforms to IEEE Std 1394b-2002, the BMODE terminal must be asserted.
The BMODE terminal does not select the cable-interface mode of operation. BMODE selects the internal
PHY-section/LLC-section interface mode of operation and affects the arbitration modes on the cable.
BMODE must be pulled high during normal operation.
Three package terminals are used as inputs to set the default value for three configuration status bits in
the self-ID packet. They can be pulled high through a 1-kΩ resistor or hardwired low as a function of the
equipment design. The PC0, PC1, and PC2 terminals indicate the default power class status for the node
(the need for power from the cable or the ability to supply power to the cable). The contender bit in the
PHY register set indicates that the node is a contender either for the isochronous resource manager (IRM)
or for the bus manager (BM). On the XIO2213B, this bit can only be set by a write to the PHY register set.
If a node is to be a contender for IRM or BM, the node software must set this bit in the PHY register set.
2.1Related 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:
•To identify a binary number or field, a lower-case b follows the numbers. For example, 000b is a 3-bit
binary field.
•To identify a hexadecimal number or field, a lower-case h follows the numbers. For example, 8AFh is a
12-bit hexadecimal field.
•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.
•If the signal or terminal name has a bar above the name (for example, GRST), this indicates the logical
NOT function. When asserted, this signal is a logic low, 0, or 0b.
•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.
•RSVD indicates that the referenced item is reserved.
•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
•The XIO2213B consists of a PCIe to PCI translation bridge, where the secondary PCI bus is internally
connected to a 1394b OHCI with a 3-port PHY. When describing functionality that is specific to the
PCIe to PCI translation bridge, the term bridge is used to reduce text. The term 1394b OHCI is used to
reduce text when describing the 1394b OHCI with 3-port PHY function.
•LLC refers to the 1394 link layer controller.
SCPS210F –OCTOBER 2008–REVISED MAY 2013
2.3Ordering Information
PACKAGEVOLTAGEORDERABLE PART NUMBER
167-terminal (Lead-Free) PBGA – ZAY3.3-V and 1.5-V power terminals
168-terminal (Lead-Free) BGA – ZAJ3.3-V and 1.5-V power terminalsXIO2213BZAJ
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
•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
•Feedthrough = Terminals that connect directly to macros within the part and not through an input or
output cell
G03 H03C07 H03PWRBypass1.5-V digital core power for the link
K10 M06H09 J03capacitors
B08 P07J09 L06
V
DDA_15
V
DD_33
B10 B09B04 B05PWRFilter1.5-V analog power for the link
B07 B05C04 C05
E03 M05D10 K03PWRBypass3.3-V digital I/O power for the link
J10 H10K08 L03capacitors
G10L08
V
DD_33_AUX
V
DDA_33
B12C09This terminal is connected to VSS through a pulldown resistor,
C03 A10A01 C08PWRFilter3.3-V analog power for the link. This supply terminal is
DVDD_COREC09 F03D08 D09PWRBypassDigital 1.95-V circuit power for the PHY. A combination of high-
M09K09capacitors frequency decoupling capacitors near each terminal is
PLLVDD_COREM07N06PWRBypassPLL 1.95-V circuit power for the PHY. A combination of high-
DVDD_33C08 J03E04 K05PWRBypass3.3-V digital I/O power for the PHY
K03K06capacitors
AVDD_33M04 E10E10 F10PWRFilter3.3-V analog power for the PHY
F10 J09H10 J10
K09 M10M04
PLLVDD_33N07N07PWRBypassPLL 3.3-V circuit power for the PHY. This supply terminal is
V
DD_15_COMB
V
DD_33_COMB
V
DD_33_COMBIO
C12B11PWRBypassInternal 1.5-V main power output for external bypass capacitor
B11B09PWRBypassInternal 3.3-V main power output for external bypass capacitor
C11B10PWRBypassInternal 3.3-V IO power output for external bypass capacitor
I/OEXTERNAL
TYPEPARTS
capacitors frequency decoupling capacitors near each terminal is
capacitors separated from the other power terminals internal to the device
capacitors filtering
capacitors filtering
capacitors filtering
since the XIO2213B does not support auxiliary power.
separated from the other power terminals internal to the device
to provide noise isolation.
suggested, such as paralleled 0.1 μF and 0.001 μF. An
additional 1-μF capacitor is required for voltage regulation.
These supply terminals are separated from the other power
terminals internal to the device to provide noise isolation.
suggested, such as paralleled 0.1 μF and 0.001 μF. An
additional 1-μF capacitor is required for voltage regulation, and
the PLLVDD_CORE terminals must be separate from the
DVDD_CORE terminals. These supply terminals are separated
from the other power terminals internal to the device to provide
noise isolation.
to provide noise isolation. The PLLVDD_33 and V
should be connected together with a low-dc-impedance
DDA_33
pins
connection on the circuit board.
Caution: Do not use this terminal to supply external power to
other devices.
Caution: Do not use this terminal to supply external power to
other devices.
Caution: Do not use this terminal to supply external power to
other devices.
C04 C05 C06 C07C06 D05 D06 E06GNDAnalog ground for PCIe function
H09 J05 J06 J07 J08H05 H06 H07 H08 J04
K05 K06 K07 K08J05 J06 J07 J08 K07
L07
I/O
TYPE
impedance circuit-board ground plane.
Table 2-7. PCIe Terminals
BALL NO.
SIGNALDESCRIPTION
PERSTB13B12IPCI Express reset. PERST identifies when the system power is stable
REF0_PCIEA13A11I/OExternalExternal reference resistor + and terminals for setting TX driver current.
REF1_PCIEA12A10resistorAn external resistor is connected between terminals REF0_PCIE and
RXPA04A05DIHigh-speed receive pair. RXP and RXN comprise the differential
RXNA03A04receive pair for the single PCIe lane supported.
TXPA09A08DOSeriesHigh-speed transmit pair. TXP and TXN comprise the differential
TXNA08A07capacitorstransmit pair for the single PCIe lane supported.
ZAYZAJ
PACKAGEPACKAGE
I/OEXTERNAL
TYPEPARTS
and generates an internal power-on reset.
Note: The PERST input buffer has hysteresis.
REF1_PCIE.
Table 2-8. Clock Terminals
BALL NO.
SIGNALDESCRIPTION
REFCLK_SELH13G11IPullup orReference clock select. This terminal selects the reference clock input.
REFCLK+A01B01DIReference clock positive. REFCLK+ and REFCLK– comprise the
REFCLK–B01C01DICapacitor to Reference clock negative. REFCLK+ and REFCLK– comprise the
CLKREQJ12H12OClock request. This terminal is used to support the clock request
XIP04N05IOscillator input. This terminal connects to a 98.304-MHz low-jitter
ZAYZAJ
PACKAGEPACKAGE
I/OEXTERNAL
TYPEPARTS
pulldown
resistor
VSSfordifferential input pair for the 100-MHz system reference clock. For a
single-single-ended, 125-MHz system reference clock, attach a capacitor from
endedREFCLK– to VSS.
mode
0 = 100-MHz differential common reference clock used
1 = 125-MHz single-ended reference clock used
differential input pair for the 100-MHz system reference clock. For a
single-ended, 125-MHz system reference clock, use the REFCLK+
input.
protocol.
external oscillator. XI is a 1.8-V CMOS input. Oscillator jitter must be 5ps RMS or better. If only 3.3-V oscillators can be acquired, great care
must be taken to not introduce significant jitter by the means used to
level shift from 3.3 V to 1.8 V. If a resistor divider is used, a high-current
oscillator and low-value resistors must be used to minimize RC time
constants.
CNAA02A02I/OCable not active. This terminal is asserted high when there are no ports receiving
CPSP12N09ICable power status. This terminal is normally connected to cable power through a
DS0N09N08IData-strobe-only mode for port 0. IEEE Std 1394a-2000-only port-0-enable
DS1P09M07IData-strobe-only mode for port 1. IEEE Std 1394a-2000-only port-1-enable
PC0E09C11IPower-class programming. On hardware reset, these inputs set the default value of
PC1E08A09the power class indicated during self-ID. Programming is done by tying the terminals
PC2A11B08high through a 1-kΩ or smaller resistor or by tying directly to ground through a 1-kΩ
R0N01N03I/OCurrent-setting resistor. These terminals are connected to an external resistance to
R1M01N02set the internal operating currents and cable driver output currents. A resistance of
TPA0PK14J13I/OPort 0 twisted-pair cable A differential. Board trace lengths from each pair of positive
TPA0NL14K13and negative differential signal pins must be matched and as short as possible to the
TPB0PM14L13external load resistors and to the cable connector. For an unused port, TPA+ and
TPB0NN14M13TPA– can be left open.
TPA1PF14E13I/OPort 1 twisted-pair cable A differential. Board trace lengths from each pair of positive
TPA1NG14F13and negative differential signal pins must be matched and as short as possible to the
TPB1PH14G13external load resistors and to the cable connector. For an unused port, TPA+ and
TPB1NJ14H13TPA– can be left open.
TPA2PB14A13I/OPort 2 twisted-pair cable A differential. Board trace lengths from each pair of positive
TPA2NC14B13and negative differential signal pins must be matched and as short as possible to the
TPB2PD14C13external load resistors and to the cable connector. For an unused port, TPA+ and
TPB2NE14D13TPA– can be left open.
TPBIAS0K13J12OTwisted-pair bias. These terminals provide the 1.86-V nominal bias voltage needed
TPBIAS1G13E12for proper operation of the twisted-pair cable drivers and receivers, and for signaling
TPBIAS2E13A12to the remote nodes that there is an active cable connection in IEEE Std 1394a-2000
PCLK_LG01F03IPHY-section clock. This terminal must be connected to the PCLK_P output of the
PCLK_PF01F02OPHY-section clock. This terminal must be connected to the PCLK_L input of the LLC
LCLK_LG02G03OLLC-section clock. This terminal must be connected to the LCLK_P input terminal of
LCLK_PH02G02ILLC-section clock. This terminal must be connected to the LCLK_L output terminal of
LPS_LC01C03OLLC-section power status. This terminal must be connected to the LPS_P input
LPS_PC02D03ILink power status. This terminal must be connected to the LPS_L ouput terminal of
PINT_LD02E02IPHY-section interrupt. The PHY section uses this signal to transfer status and
ZAYZAJ
PACKAGE PACKAGE
I/O
TYPE
incoming bias voltage. If it is not used, this terminal should be left unconnected.
400-kΩ resistor. This circuit drives an internal comparator that detects the presence
of cable power. If CPS is not used to detect cable power, this terminal must be
connected to V
programming terminal. On hardware reset, this terminal allows the user to select
whether port 0 acts like an IEEE Std 1394b-2002 bilingual port (terminal at logic 0) or
as an IEEE Std 1394a-2000-only port (terminal at logic 1). Programming is
accomplished by tying the terminal low through a 1-kΩ or smaller resistor (to enable
IEEE Std 1394b-2002 bilingual mode) or high through a 10-kΩ or smaller resistor (to
enable IEEE Std 1394a-2000-only mode).
programming terminal. On hardware reset, this terminal allows the user to select
whether port 1 acts like an IEEE Std 1394b-2002 bilingual port (terminal at logic 0) or
as an IEEE Std 1394a-2000-only port (terminal at logic 1). Programming is
accomplished by tying the terminal low through a 1-kΩ or smaller resistor (to enable
IEEE Std 1394b-2002 bilingual mode) or high through a 10-kΩ or smaller resistor (to
enable IEEE Std 1394a-2000-only mode).
or smaller resistor. Bus holders are built into these terminals.
6.34 kΩ ± 1% is required to meet the IEEE Std 1394-1995 output voltage limits.
mode. Each of these terminals, except for an unused port, must be decoupled with a
1-μF capacitor to ground. For the unused port, this terminal can be left unconnected.
PHY section.
section.
the PHY section.
the LLC section.
terminal of the PHY section.
the LLC section.
interrupt information serially to the LLC section. This terminal must be connected to
the PINT_P output of the PHY section.
PINT_PD03E03OPHY-section interrupt. PINT_P is a serial input to the LLC section from the PHY
LKON/DS2_PD01D02I/OLink-on notification. If port is to operate in DS mode or is unused then it is necessary
LINKON_LE01C02I/OLink-on notification. LINKON_L is an input to the LLC section from the PHY section
LREQ_LF02D01OLLC-section request. The LLC section uses this output to initiate a service request to
LREQ_PE02E01ILLC-section request. LREQ_P is a serial input from the LLC section to the PHY
PHY_RESETB04A06IReset for the 1394 PHY logic
CTL1J01G01I/OControl. CTL[1:0] are bidirectional control bus signals that are used to indicate the
CTL0H01F01phase of operation of the PHY link interface. Upon a reset of the interface, this bus is
D0J02H01I/OData. D[7:0] comprise a bidirectional data bus that is used to carry 1394 packet data,
D1K02H02packet speed, and grant type information between the PHY and the link. Upon a
D2K01J02reset of the interface, this bus is driven by the PHY. When driven by the PHY,
D3L01J01information on D[7:0] is synchronous to PCLK. When driven by the link, information
D4L02K02on D[7:0] is synchronous to LCLK. If not implemented, these terminals should be left
D5L03K01unconnected.
D6M02L01
D7M03M01
ZAYZAJ
PACKAGE PACKAGE
I/O
TYPE
section that is used to transfer status, register, interrupt, and other information to the
link. Information encoded on PINT_P is synchronous to PCLK_P. This terminal must
be connected to the PINT_L input of the LLC section.
to pull the terminal high through a 470-Ω or smaller resistor. This terminal must also
be connected to the LINKON_L input terminal of the LLC section via a 1-kΩ series
resistor. A bus holder is built into this terminal. If the port is to operate in bilingual
mode then the terminal should be tied low via a 1-kΩ resistor and directly connected
to the link's LINKON_L pin with no series termination. After hardware reset, this
terminal is the link-on output, which notifies the LLC section or other power-up logic
to power up and become active. The link-on output is a square-wave signal with a
period of approximately 163 ns (eight PCLK cycles) when active. The link-on output
is otherwise driven low, except during hardware reset when it is high impedance. The
link-on output is activated if the LLC section is inactive (the LPS input inactive or the
LCtrl bit cleared) and when any of the following occurs:
a) The XIO2213B receives a link-on PHY packet addressed to this node.
b) The PEI (port-event interrupt) register bit is 1.
c) Any of the configuration-timeout interrupt (CTOI), cable-power-status interrupt
(CPSI), or state-time-out interrupt (STOI) register bits are 1, and the resuming-port
interrupt enable (RPIE) register bit also is 1.
d) The PHY is power cycled and the power class is 0 through 4.
Once activated, the link-on output is active until the LLC section becomes active
(both the LPS_L input active and the LCtrl bit set). The PHY section also deasserts
the link-on output when a bus reset occurs unless the link-on output is otherwise
active because one of the interrupt bits is set (that is, the link-on output is active due
solely to the reception of a link-on PHY packet). In the case of power cycling, the
LKON signal must stop after 167 ms if the previous conditions have not been met.
Note: If an interrupt condition exists that otherwise causes the link-on output to be
activated if the LLC section were inactive, the link-on output is activated when the
LLC section subsequently becomes inactive.
that is used to provide notification that a link-on packet has been received or an
event, such as a port connection, has occurred. This I/O only has meaning when
LPS is disabled. This includes the D0 (uninitialized), D2, and D3 power states. If
LINKON_L becomes active in the D0 (uninitialized), D2, or D3 power state, the
XIO2213B device sets bit 15 (PME_STS) in the power-management control and
status register in the PCI configuration space at offset 48h. This terminal must be
connected to the LKON output terminal of the PHY section.
the PHY section.This terminal must be connected to the LREQ_P input of the PHY
section.
section used to request packet transmissions, read and write PHY section registers,
and to indicate the occurrence of certain link events that are relevant to the PHY
section. Information encoded on LREQ_P is synchronous to LCLK_P.This terminal
must be connected to the LREQ_L output of the LLC section.
driven by the PHY. When driven by the PHY, information on CTL[1:0] is synchronous
to PCLK. When driven by the link, information on CTL[1:0] is synchronous to LCLK.
If not implemented, these terminals should be left unconnected.
RSVDE12 F12 F13 K12 L12 L13D11 E11 F12 J11 K10 K11I/OReserved, do not connect to external signals.
M11 M12 M13 N10 N11 N12K12 L10 L11 L12 M05 M11
RSVDD12 D13 G12 M08C10 D12 F11 M09IMust be connected to VSS.
ZAYZAJ
PACKAGEPACKAGE
N13 P03 P10 P11M12 N11 N12 N13
Table 2-11. Miscellaneous Terminals
BALL NO.
SIGNALDESCRIPTION
GPIO0P01M02I/OGeneral-purpose I/O 0. This terminal functions as a GPIO controlled by bit 0
GPIO1N02N01I/OGeneral-purpose I/O 1. This terminal functions as a GPIO controlled by bit 1
GPIO2P02L02I/OGeneral-purpose I/O 2. This terminal functions as a GPIO controlled by bit 2
GPIO3N03L04I/OGeneral-purpose I/O 3. This terminal functions as a GPIO controlled by bit 3
GPIO4N04M03I/OGeneral-purpose I/O 4. This terminal functions as a GPIO controlled by bit 4
GPIO5P05K04I/OGeneral-purpose I/O 5. This terminal functions as a GPIO controlled by bit 5
GPIO6P06M06I/OGeneral-purpose I/O 6. This terminal functions as a GPIO controlled by bit 6
GPIO7N06L05I/OGeneral-purpose I/O 7. This terminal functions as a GPIO controlled by bit 7
OHCI_PMEP08M08OOHCI power-management event. This is an optional signal that can be used by a
CYCLEOUTN08L09OCycle out. This terminal provides an 8-kHz cycle timer synchronization signal. If not
PDB03B03IPower down. A high on this terminal turns off all internal circuitry, except the cable-
GRSTC13C12IGlobal power reset. This reset brings all of the XIO2213B internal link registers to
SCLJ13G12I/OSerial-bus clock. This signal is used as a serial bus clock when a pullup is detected
ZAYZAJ
PACKAGEPACKAGE
I/O
TYPE
(GPIO0_DIR) in the GPIO control register (see Section 4.60).
Note: This terminal has an internal active pullup resistor.
(GPIO1_DIR) in the GPIO control register (see Section 4.60).
Note: This terminal has an internal active pullup resistor.
(GPIO2_DIR) in the GPIO control register (see Section 4.60).
Note: This terminal has an internal active pullup resistor.
(GPIO3_DIR) in the GPIO control register (see Section 4.60).
Note: This terminal has an internal active pullup resistor.
(GPIO4_DIR) in the GPIO control register (see Section 4.60).
Note: This terminal has an internal active pullup resistor.
(GPIO5_DIR) in the GPIO control register (see Section 4.60).
Note: This terminal has an internal active pullup resistor.
(GPIO6_DIR) in the GPIO control register (see Section 4.60).
Note: This terminal has an internal active pullup resistor.
(GPIO7_DIR) in the GPIO control register (see Section 4.60).
Note: This terminal has an internal active pullup resistor.
device to request a change in the device or system power state. This signal must be
enabled by software.
implemented, this terminal should be left unconnected.
active monitor circuits that control the CNA output. Asserting PD high also activates
an internal pulldown to force a reset of the internal control logic. If PD is not used,
this terminal must be connected to VSS.
their default states. This should be a one-time power-on reset. This terminal has
hysteresis and an integrated pullup resistor.
on SDA or when the SBDETECT bit is set in the serial bus control and status
register.
Note: This terminal has an internal active pullup resistor.
SDAH12H11I/OSerial-bus data. This signal is used as serial bus data when a pullup is detected on
BMODEA05B06IBeta mode. This terminal determines the PHY-section/LLC-section interface
TESTMB02A03ITest control. This input is used in the manufacturing test of the XIO2213B. For
VREG_PDA06B07IVoltage regulator power-down input. When asserted logic high, this pin will power-
SEP13M10ITest control. This input is used in the manufacturing test of the XIO2213B. For
SMP14N10ITest control. This input is used in the manufacturing test of the XIO2213B. For
ZAYZAJ
PACKAGEPACKAGE
I/O
TYPE
SDA or when the SBDETECT bit is set in the serial bus control and status register.
Note: In serial-bus mode, an external pullup resistor is required to prevent the SDA
signal from floating.
connection protocol. When logic high (asserted), the PHY-section/LLC-section
interface complies with the IEEE Std 1394b-2002 Revision 1.33 beta interface.
When logic low (deasserted), the PHY-section/LLC-section interface complies with
legacy IEEE Std 1394a-2000. This terminal must be pulled high with a 1-kΩ resistor
during normal operation.
normal use, this terminal must be pulled high through a 1-kΩ resistor to VDD.
down the internal 3.3- to 1.95V regulator. For single 3.3V supply operation, this pin
should be tied to GND. When using the internal regulator, the XIO2213B can
support a maximum of 2-Beta and 1-DS connection simultaneously. If 3-Beta ports
are required to be simultaneously supported, it is recommended to use an external
1.95V regulator.
normal use, this terminal must be pulled low either through a 1-kΩ resistor to GND
or directly to GND.
normal use, this terminal must be pulled low either through a 1-kΩ resistor to GND
or directly to GND.
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 PCIe to PCI bridge with 1394b OHCI and 3-port PHY. The
top of the diagram is the PCIe interface, and the 1394b OHCI with 3-port PHY is located at the bottom of
the diagram.
SCPS210F –OCTOBER 2008–REVISED MAY 2013
Figure 3-1. XIO2213B Block Diagram
3.1Power-Up/Power-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
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 PCIe 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 VDD_33_AUX terminal is to remain
powered after a system shutdown, the bridge power-down sequence is the same as shown in Figure 3-3.
There are five XIO2213B 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 PCIe hot reset
or setting a configuration register bit. Table 3-1 identifies these reset sources and describes how the
XIO2213B responds to each reset.
Table 3-1. XIO2213B Reset Options
RESET
OPTION
XIO2213BDuring a power-on cycle, the XIO2213B asserts an internalWhen the internal power-on reset is asserted, all control
internally-reset and monitors the V
generatedthis terminal reaches 90% of the nominal input voltagemanagement state machines are initialized to their default
power-on reset specification, power is considered stable. After stable power, state.
the XIO2213B monitors the PCIe reference clock (REFCLK) In addition, the XIO2213B asserts the internal PCI bus
and waits 10 s after active clocks are detected. Then,reset.
internal power-on reset is deasserted.
PCIe reset input This XIO2213B input terminal is used by an upstream PCIeWhen PERST is asserted low, all control register bits that
(PERST, B12)device to generate a PCIe reset and to signal a systemare not sticky are reset. Within the configuration register
power good condition.maps, the sticky bits are indicated by the symbol. Also, all
When PERST is asserted low, the XIO2213B generates an
internal PCIe reset as defined in the PCI Express
Specification.
When PERST transitions from low to high, a system powerIn addition, the XIO2213B asserts the internal PCI bus
good condition is assumed by the XIO2213B.reset.
Note: The system must assert PERST before power isWhen the rising edge of PERST occurs, the XIO2213B
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
PCIe trainingThe XIO2213B responds to a training control hot resetIn the DL_DOWN state, all remaining configuration register
control hot reset received on the PCIe interface. After a training control hotbits and state machines are reset. All remaining bits
reset, the PCIe interface enters the DL_DOWN state.exclude sticky bits and EEPROM loadable bits. All
PCI bus resetSystem software has the ability to assert and deassert theWhen bit 6 (SRST) in the XIO2213B control register at
PCI bus reset on the secondary PCI bus interface.offset 3Eh (see Section 4.30) is asserted, the XIO2213B
XIO2213B FEATURERESET RESPONSE
DD_15_COMB
(B11) terminal. Whenregisters, state machines, sticky register bits, and power
state machines that are not associated with sticky
functionality are reset.
detected, a download cycle is initiated. Also, the process to
configure and initialize the PCIe link is started. The
XIO2213B starts link training within 80 ms after PERST is
deasserted.
remaining state machines exclude sticky functionality and
EEPROM functionality.
Within the configuration register maps, the sticky bits are
reset by a global reset (GRST) or the internally-generated
power-on reset and EEPROM loadable bits are rest by a
PCIe reset (PERST), GRST, or internally generated poweron reset.
In addition, the XIO2213B asserts the internal PCI bus
reset.
asserts the internal PCI bus reset. A 0b in the SRST bit
deasserts the PCI bus reset.
The XIO2213B requires either a differential, 100-MHz common clock reference or a single-ended, 125MHz clock reference. The selected clock reference must meet all PCI Express Electrical Specification
requirements for frequency tolerance, spread-spectrum clocking, and signal electrical characteristics.
If the REFCLK_SEL input is connected to VSS, a differential, 100-MHz common clock reference is
expected by the XIO2213B. If the REFCLK_SEL terminal is connected to V
clock reference is expected by the XIO2213B.
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
noncommon clock architecture. System jitter budgets will have to be verified to ensure interoperability (see
the PCI Express Jitter and BER white paper from PCI-SIG).
3.3.2Beacon and Wake
Since the 1394b OHCI function in the XIO2213B does not support PME from D3cold, it is not necessary
for the PCIe to PCI bridge portion of the design to support beacon generation or WAKE signaling. As a
result, the XIO2213B does not implement VAUX power support.
SCPS210F –OCTOBER 2008–REVISED MAY 2013
, a single-ended 125-MHz
DD_33
3.3.3Initial Flow Control Credits
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
Nonposted header (NPH)4
PCIe messages are both initiated and received by the bridge. Table 3-3 outlines message support within
the bridge.
Table 3-3. Messages Supported by 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
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
www.ti.com
All supported message transactions are processed per the PCI Express Base Specification.
The bridge converts interrupts from the PCI bus sideband interrupt signals to PCIe interrupt messages.
Since the 1394a OHCI only generates INTA interrupts, only PCIe INTA messages are generated by the
bridge.
PCIe Assert_INTA messages are generated when the 1394a OHCI signals an INTA interrupt. The
requester ID portion of the Assert_INTA message uses the value stored in the primary bus number
register (see Section 4.12) as the bus number, 0 as the device number, and 0 as the function number.
The tag field for each Assert_INTA message is 00h.
PCIe Deassert_INTA messages are generated when the 1394a OHCI deasserts the INTA interrupt. The
requester ID portion of the Deassert_INTA message uses the value stored in the primary bus number
register as the bus number, 0 as the device number, and 0 as the function number. The Tag field for each
Deassert_INTA message is 00h.
Figure 3-4 and Figure 3-5 show the format for both the assert and deassert INTA messages.
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 are SCL and SDA.
3.5.1Serial-Bus Interface Implementation
To enable the serial-bus interface, a pullup resistor must be implemented on the SDA signal. At the rising
edge of PERST or GRST, whichever occurs later in time, the SDA terminal is checked for a pullup
resistor. If one is detected, bit 3 (SBDETECT) in the serial-bus control and status register (see
Section 4.59) 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, the serial-bus interface is permanently disabled by
attaching a pulldown resistor to the SDA 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-6 shows an example application implementing the two-wire serial bus.
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 (see Figure 3-7). 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 (see Figure 3-7). 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-7. Serial-Bus Start/Stop Conditions and Bit Transfers
SCPS210F –OCTOBER 2008–REVISED MAY 2013
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-8 shows the
acknowledge protocol.
Figure 3-8. 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 PCIe reset (see Section 3.5.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.
Figure 3-9 shows 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, bit 1 (SB_ERR) is set in the serial-bus control and status
register (PCI offset B3h, see Section 4.59). Next, the EEPROM word address is sent by the bridge, and
another slave acknowledgment is expected. Then the bridge delivers the data-byte most significant bit
(MSB) first and expects a final acknowledgment before issuing the stop condition.
Figure 3-10 shows 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-11 shows the serial interface protocol during a multibyte 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.
Figure 3-11. Serial-Bus Protocol Multibyte Read
Submit Documentation Feedback
Product Folder Links: XIO2213B
XIO2213B
www.ti.com
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 show 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.5.3Serial-Bus EEPROM Application
The registers and corresponding bits that are loaded through the EEPROM are provided in Table 3-4.
Table 3-4. EEPROM Register Loading Map
SERIAL EEPROM
WORD ADDRESS
00hPCIe to PCI bridge function indicator (00h)
01hNumber of bytes to download (1Eh)s
02hPCI 84h, subsystem vendor ID, byte 0
03hPCI 85h, subsystem vendor ID, byte 1
04hPCI 86h, subsystem ID, byte 0s
05hPCI 87h, 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
0AhTI Proprietary register load 00h (PCI D8h)
0BhTI Proprietary register load 00h (PCI D9h)
0ChReserved — no bits loaded 00h (PCI DAh)
0DhPCI DCh, arbiter control
0EhPCI DDh, arbiter request mask
0FhPCI C0h, TL control and diagnostic register, byte 0
10hPCI C0h, TL control and diagnostic register, byte 1
11hPCI C0h, TL control and diagnostic register, byte 2
12hPCI C0h, TL control and diagnostic register, byte 3
13hPCI C4h, DLL control and diagnostic register, byte 0
14hPCI C5h, DLL control and diagnostic register, byte 1
15hPCI C6h, DLL control and diagnostic register, byte 2
16hPCI C7h, DLL control and diagnostic register, byte 3
17hPCI C8h, PHY control and diagnostic register, byte 0
18hPCI C9h, PHY control and diagnostic register, byte 1
19hPCI CAh, PHY control and diagnostic register, byte 2
1AhPCI CBh, PHY control and diagnostic register, byte 3
1BhReserved — no bits loaded 00h (PCI CEh)
1ChReserved — no bits loaded 00h (PCI CFh)
1DhTI proprietary register load 00h (PCI E0h)
1EhTI proprietary register load 00h (PCI E2h)
1FhTI proprietary register load 00h (PCI E3h)
20h1394 OHCI function indicator (01h)
21hNumber of bytes (18h)
22hPCI 3Fh, maximum latency, bits 7-4PCI 3Eh, minimum grant, bits 3-0
23hPCI 2Ch, subsystem vendor ID, byte 0
24hPCI 2Dh, subsystem vendor ID, byte 1
25hPCI 2Eh, subsystem ID, byte 0
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-6) 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.5.4Accessing Serial-Bus Devices Through Softwaree
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-5 lists the registers that program a serial-bus device through software.
Table 3-5. Registers Used To Program Serial-Bus Devices
PCI OFFSETREGISTER NAMEDESCRIPTION
B0hSerial-bus dataContains 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
(see Section 4.56)commands.
(see Section 4.57)not used in the quick command protocol. Bit 7 (PROT_SEL) in the serial-bus control and status
register (offset B3h, see Section 4.59) is set to 1b to enable the slave address to be sent.
(see Section 4.58)the R/W command selector are programmed through this register.
status (see Section 4.59)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, 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, the serial-bus data byte is now valid.
3.6Advanced Error Reporting Registers
In the extended PCIe configuration space, the bridge supports the advanced error reporting capabilities
structure. For the PCIe 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 PCIe interface. The primaryside 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, all transmitted TLPs contain a valid ECRC field.
3.7Data Error Forwarding Capability
The bridge supports the transfer of data errors in both directions.
If a downstream PCIe transaction with a data payload is received that targets the internal PCI bus and the
EP bit is set indicating poisoned data, 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 PCIe interface and a data parity
error is detected, this information is passed to the PCIe interface. To do this, the bridge sets the EP bit in
the upstream PCIe header.
Up to eight 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 eight GPIO terminals. When any of
the three shared functions are enabled, the associated GPIO terminal is disabled.
All eight GPIO terminals are individually configurable as either inputs or outputs by writing the
corresponding bit in the GPIO control register at offset B4h. 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.9Set 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 PCIe device capabilities register at offset 94h (see Section 4.50, Device
Capabilities Register, for details). The bridge writes these fields when a set slot power limit message is
received on the PCIe interface.
After the deassertion of PERST, the XIO2213B 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.66,
General Control Register, for details). If the CSPLS and CSPLV fields are less than the
MIN_POWER_SCALE and MIN_POWER_VALUE fields, respectively, the bridge takes the appropriate
action that is defined below.
www.ti.com
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 two options:
•Ignore slot power limit fields.
•Respond with unsupported request to all transactions except type 0/1 configuration transactions, and
set slot power limit messages.
3.10 PCIe 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 50h. Active-state power management control registers
are located in the PCIe capabilities structure located at offset 90h.
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 powermanagement state machine is also responsible for gating internal clocks based on the power state.
Table 3-6 identifies the relationship between the D-states and bridge clock operation.
Table 3-6. Clocking In Low Power States
CLOCK SOURCED0/L0D1/L1D2/L1D3/L2/L3
PCIe reference clock input (REFCLK)OnOnOnOn/Off
Internal PCI bus clock to bridge functionOnOffOffOff
Internal PCI bus clock to 1394b OHCI functionOnOnOnOn/Off
The link power management (LPM) state machine manages active-state power by monitoring the PCIe
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, the LPM state machine transitions the link to
either the L0s or L1 state. By reading the bridges 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 options.
Finally, the bridge generates the PM_Active_State_Nak Message if a PM_Active_State_Request_L1
DLLP is received on the PCIe interface and the link cannot be transitioned to L1.
The 1394b OHCI controller complies with the PCI Bus Power Management Interface Specification. The
controller supports the D0 (uninitialized), D0 (active), D1, D2, and D3 power states as defined by the
power-management definition in the 1394 Open Host Controller Interface Specification, Appendix A4.
Table 3-7 identifies the supported power-management registers within the 1394 OHCI configuration
register map.
Table 3-7. 1394b OHCI Configuration Register Map
REGISTER NAMEOFFSET
Power management capabilitiesNext item pointerCapability ID44h
PM dataPower management control/status register bridge support extensions Power management control/status (CSR)48h
3.11.2 1394b OHCI and V
The 1394b OHCI function within the XIO2213B is powered by V
power-management state, V
This implies that the 1394b OHCI function does not implement sticky bits must be initialized after a D3
power-management state. An external serial EEPROM interface is available to initialize critical
configuration register bits. The EEPROM download is triggered by the deassertion of the PERST input.
Otherwise, the BIOS must initialize the 1394b OHCI function.
AUX
DD_MAIN
is not supplied to the 1394b OHCI function.
AUX
only. Therefore, during the D3
cold
cold
3.11.3 1394b OHCI and Reset Options
The 1394b OHCI function is completely reset by the internal power-on reset feature, GRST input, or
PERST input. This includes all EEPROM loadable bits, power-management functions, and all remaining
configuration register bits and logic.
A PCIe training control hot reset or the PCI bus configuration register reset bit (SRST) excludes the
EEPROM loadable bits, power-management functions, and 1394 PHY. All remaining configuration
registers and logic are reset.
If the OHCI controller is in the power-management D2 or D3 state, or if the OHCI configuration register
reset bit (SoftReset) is set, the OHCI controller DMA logic and link logic is reset.
Finally, if the OHCI configuration register PHY reset bit (ISBR) is set, the 1394 PHY logic is reset.
3.11.4 1394b OHCI PCI Bus Master
As a bus master, the 1394 OHCI function supports the memory commands specified in Table 3-8. The
commands include memory read, memory read line, memory read multiple, memory write, and memory
write and invalidate.
The read command usage for read transactions of greater than two data phases are determined by the
selection in bits 9:8 (MR_ENHANCE field) of the PCI miscellaneous configuration register at offset F0h
(see Section 7.21). For read transactions of one or two data phases, a memory read command is used.
The write command usage is determined by the MWI_ENB bit 4 of the command configuration register at
offset 04h (see Section 4.3). If bit 4 is asserted and a memory write starts on a cache boundary with a
length greater than one cache line, memory write and invalidate commands are used. Otherwise, memory
write commands are used.
Memory read0110DMA read from memory
Memory write0111DMA write to memory
Memory read multiple1100DMA read from memory
Memory read line1110DMA read from memory
Memory write and invalidate1111DMA write to memory
3.11.5 1394b OHCI Subsystem Identification
The subsystem identification register at offset 2Ch is used for system and option card identification
purposes. This register can be initialized from the serial EEPROM or programmed via the subsystem
access register at offset F8h in the 1394a OHCI PCI configuration space (see Section 7.23).
Write access to the subsystem access register updates the subsystem identification registers identically to
OHCI-Lynx™ integrated circuits. The contents of the subsystem access register are aliased to the
subsystem vendor ID and subsystem ID registers at PCI offsets 2Ch and 2Eh, respectively. The
subsystem ID value written to this register may also be read back from this register.
3.11.6 1394b OHCI PME Support
Since the 1394b OHCI controller is not connected to VAUX, PME generation is disabled for D3cold powermanagement states.
The programming model of the XIO2213B PCIe 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.
Sticky bits are reset by a global reset (GRST) or the internally-generated power-on reset. EEPROM
loadable bits are reset by a PCIe reset (PERST), GRST, or the internally-generated power-on reset. The
remaining register bits are reset by a PCIe 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 typePrimary latency timerCache line size00Ch
Device contol base address010h
Scratchpad RAM base address014h
Secondary latency timerSubordinate bus numberSecondary bus numberPrimary bus number018h
10INT_DISABLERINTx disable. This bit enables device specific interrupts. Since the bridge does not
generate any internal interrupts, this bit is read-only 0b.
9FBB_ENBRFast back-to-back enable. The bridge does not generate fast back-to-back transactions;
therefore, this bit returns 0b when read.
8SERR_ENBRWSERR enable. When this bit is set, the bridge can signal fatal and nonfatal errors on the
PCIe 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
7STEP_ENBRAddress/data stepping control. The bridge does not support address/data stepping, and
this bit is hardwired to 0b.
6PERR_ENBRWControls the setting of bit 8 (DATAPAR) in the status register (offset 06h, see Section 4.4)
in response to a received poisoned TLP from PCIe. 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
5VGA_ENBRVGA palette snoop enable. The bridge does not support VGA palette snooping; therefore,
this bit returns 0b when read.
4MWI_ENBRWMemory write and invalidate enable. When this bit is set, the bridge translates PCIe
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
3SPECIALRSpecial cycle enable. The bridge does not respond to special cycle transactions; therefore,
this bit returns 0b when read.
2MASTER_ENBRWBus master enable. When this bit is set, the bridge is enabled to initiate transactions on
the PCIe interface.
0 = PCIe interface cannot initiate transactions. The bridge must disable the response
to memory and I/O transactions on the PCI interface (default).
1 = PCIe interface can initiate transactions. The bridge can forward memory and I/O
transactions from PCI secondary interface to the PCIe interface.
1MEMORY_ENBRWMemory space enable. Setting this bit enables the bridge to respond to memory
transactions on the PCIe interface.
0 = PCIe receiver cannot process downstream memory transactions and must
respond with an unsupported request (default)
1 = PCIe receiver can process downstream memory transactions. The bridge can
forward memory transactions to the PCI interface.
0IO_ENBRWI/O space enable. Setting this bit enables the bridge to respond to I/O transactions on the
PCIe interface.
0 = PCIe receiver cannot process downstream I/O transactions and must respond
with an unsupported request (default)
1 = PCIe receiver can process downstream I/O transactions. The bridge can forward
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
completion-with-unsupported-request status.
0 = Unsupported request not received on the PCIe interface
1 = Unsupported request received on the PCIe interface
completion-with-completer-abort status.
0 = Completer abort not received on the PCIe interface
1 = Completer abort received on the PCIe interface
completer abort status.
0 = Completer abort not signaled on the PCIe interface
1 = Completer abort signaled on the PCIe interface
04h, see Section 4.3) is set and the bridge receives a completion with data marked as
poisoned on the PCIe interface or poisons a write request received on the PCIe interface.
0 = No uncorrectable data error detected on the primary interface
1 = Uncorrectable data error detected on the primary interface
and is hardwired to 0b.
hardwired to 0b.
PCI capabilities.
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 (00h). See Table 4-4 for a complete description of the register contents.
PCI register offset:08h
Register type:Read only
Default value:0604 0001h
BIT NUMBER31302928272625242322212019181716
RESET STATE0000011000000100
BIT NUMBER1514131211109876543210
RESET STATE0000000000000001
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
If the EN_CACHE_LINE_CHECK bit in the TL control and diagnostic register is 0, Cheetah- Express shall
use side-band signals from the 1394b OHCI core to determine how much data to fetch when handling
delayed read transactions. In this case, the cache line size register will have no effect on the design and
will essentially be a read/write scratchpad register. If the EN_CACHE_LINE_CHECK bit is 1, the cache
line size register is used by the bridge to determine how much data to prefetch when handling delayed
read transactions. In this case, the value in this register must be programmed to a power of 2, and any
value greater than 32 DWORDs will be treated as 32 DWORDs.
This read-only register indicates that this function has a type 1 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
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
SCPS210F –OCTOBER 2008–REVISED MAY 2013
4.10 Device Control Base Address Register
This read/write register programs the memory base address that accesses the device control registers.
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 XIO2213B uses 20 read/write bits indicating
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
0MEM_INDRMemory space indicator. This field returns 0b indicating that memory space is used.
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,
these bits are read only and return zeros when read. If the BAR0_EN bit is 1, these bits are
read/write.
Table 4-6. Device Control Base Address Register Description
BITFIELD NAMEACCESSDESCRIPTION
31:12ADDRESSR or RWMemory address. The memory address field for XIO2213B uses 20 read/write bits indicating
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
0MEM_INDRMemory space indicator. This field returns 0b indicating that memory space is used.
that 4096 bytes of memory space are required. If the BAR1_EN bit (bit 6 at C8h) is 0, these
bits are read only and return zeros when read. If the BAR1_EN bit is 1, these bits are
read/write.
in the 32-bit address space.
4.12 Primary Bus Number Register
This read/write register specifies the bus number of the PCI bus segment that the PCIe 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. Since the PCI bus is internal and only connects to the 1394a OHCI, this
register must always be equal to the secondary bus number register (offset 19h, see Section 4.13). 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-7 for a complete description of the register contents.
This read/write register specifies the upper limit of the I/O addresses that the bridge forwards downstream.
See Table 4-8 for a complete description of the register contents.
7:4IOLIMITRWI/O limit. Defines the top address of the I/O address range that determines when to forward I/O
transactions from one interface to the other. These bits correspond to address bits [15:12] in the I/O
address. The lower 12 bits are assumed to be FFFh. The 16 bits corresponding to address bits
[31:16] of the I/O address are defined in the I/O limit upper 16 bits register (offset 32h, see
Section 4.26).
3:0IOTYPERI/O type. This field is read-only 1h indicating that the bridge supports 32-bit I/O addressing.
15PAR_ERRRCUDetected parity error. This bit reports the detection of an uncorrectable address, attribute, or data
14SYS_ERRRCUReceived system error. This bit is set when the bridge detects an SERR assertion.
13MABORTRCUReceived master abort. This bit is set when the PCI interface of the bridge reports the detection of a
12TABORT_RECRCUReceived target abort. This bit is set when the PCI interface of the bridge receives a target abort.
11TABORT_SIGRCUSignaled target abort. This bit reports the signaling of a target abort termination by the bridge when it
10:9 PCI_SPEEDRDEVSEL timing. These bits are 01b indicating that this is a medium-speed decoding device.
8DATAPARRCUMaster data parity error. This bit is set if the bridge is the bus master of the transaction on the PCI
7FBB_CAPRFast back-to-back capable. This bit returns a 1b when read indicating that the secondary PCI
6RSVDRReserved. Returns 0b when read.
566MHZR66-MHz capable. The bridge operates at a PCI bus CLK frequency of 66 MHz; therefore, this bit
4:0RSVDRReserved. Returns 00000b when read.
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.
The bridge detects an uncorrectable data error when it is the master of a read transaction
(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.30).
0 = Uncorrectable address, attribute, or data error not detected on secondary interface
1 = Uncorrectable address, attribute, or data error detected on secondary interface
0 = No error asserted on the PCI interface
1 = SERR asserted on the PCI interface
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
0 = Target abort not received on the PCI interface
1 = Target abort received on the PCI interface
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
bus, bit 0 (PERR_EN) in the bridge control register (offset 3Eh see Section 4.30) 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
interface of bridge supports fast back-to-back transactions.
This read/write register specifies the lower limit of the memory addresses that the bridge forwards
downstream. See Table 4-10 for a complete description of the register contents.
15:4MEMBASERWMemory base. Defines the lowest address of the memory address range that determines when to
3:0RSVDRReserved. Returns 0h when read.
forward memory transactions from one interface to the other. These bits correspond to address bits
[31:20] in the memory address. The lower 20 bits are assumed to be 00000h.
4.20 Memory Limit Register
This read/write register specifies the upper limit of the memory addresses that the bridge forwards
downstream. See Table 4-11 for a complete description of the register contents.
15:4MEMLIMITRWMemory limit. Defines the highest address of the memory address range that determines when to
3:0RSVDRReserved. Returns 0h when read.
forward memory transactions from one interface to the other. These bits correspond to address bits
[31:20] in the memory address. The lower 20 bits are assumed to be FFFFFh.
This read/write register specifies the lower limit of the prefetchable memory addresses that the bridge
forwards downstream. See Table 4-12 for a complete description of the register contents.
Table 4-12. Prefetchable Memory Base Register Description
BITFIELD NAMEACCESSDESCRIPTION
15:4PREBASERWPrefetchable memory base. Defines the lowest address of the prefetchable memory address range
3:064BITR64-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
correspond to address bits [31:20] in the memory address. The lower 20 bits are assumed to be
00000h. The prefetchable base upper 32 bits register (offset 28h, see Section 4.23) specifies the bit
[63:32] of the 64-bit prefetchable memory address.
memory window.
4.22 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-13 for a complete description of the register contents.
15:4PRELIMITRWPrefetchable memory limit. Defines the highest address of the prefetchable memory address range
3:064BITR64-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
correspond to address bits [31:20] in the memory address. The lower 20 bits are assumed to be
FFFFFh. The prefetchable limit upper 32 bits register (offset 2Ch, see Section 4.24) specifies the bit
[63:32] of the 64-bit prefetchable memory address.
Table 4-16. I/O Base Upper 16 Bits Register Description
BITFIELD NAMEACCESSDESCRIPTION
15:0IOBASERWI/O base upper 16 bits. Defines the upper 16 bits of the lowest address of the I/O address range
that determines when to forward I/O transactions downstream. These bits correspond to address
bits [31:20] in the I/O address. The lower 20 bits are assumed to be 00000h.
4.26 I/O Limit Upper 16 Bits Register
This read/write register specifies the upper 16 bits of the I/O limit register. See Table 4-17 for a complete
description of the register contents.
15:0IOLIMITRWI/O limit upper 16 bits. Defines the upper 16 bits of the top address of the I/O address range that
determines when to forward I/O transactions downstream. These bits correspond to address bits
[31:20] in the I/O address. The lower 20 bits are assumed to be FFFFFh.
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 50h, this register is
hardwired to 50h.
PCI register offset:34h
Register type:Read only
Default value:50h
BIT NUMBER76543210
RESET STATE01010000
4.28 Interrupt Line Register
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 scratchpad 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.
PCI register offset:3Dh
Register type:Read only
Default value:00h
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_DTRW selects the number of PCI clocks that the bridge waits for the 1394a OHCI master on
8PRI_DECRPrimary discard timer. This bit has no meaning in PCIe 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
the secondary 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, the bridge deletes the delayed transaction from
its queue and sets the discard timer status bit.
3VGARWVGA enable. This bit modifies the response by the bridge to VGA compatible addresses.
If this bit is set, 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, 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 previously defined) 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 previously
defined) 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, 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 1-KB
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-18. 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 PCIe 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.31 PM Capability ID Register
This read-only register identifies the linked list item as the register for PCI power management. The
register returns 01h when read.
PCI register offset:50h
Register type:Read only
Default value:01h
BIT NUMBER76543210
RESET STATE00000001
4.32 Next Item Pointer Register
The contents of this read-only register indicate the next item in the linked list of capabilities for the bridge.
This register reads 80h pointing to the subsystem ID capabilities registers.
PCI register offset:51h
Register type:Read only
Default value:60h
This read-only register indicates the capabilities of the bridge related to PCI power management. See
Table 4-19 for a complete description of the register contents.
PCI register offset:52h
Register type:Read only
Default value:0603h
BIT NUMBER1514131211109876543210
RESET STATE0000011000000011
Table 4-19. 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.66) is 0b, this field returns 010b indicating revision 1.1
compatibility. If PCI_PM_VERSION_CTRL is 1b, this field returns 011b indicating revision
This register determines and changes the current power state of the bridge. No internal reset is generated
when transitioning from the D3
register contents.
Table 4-20. 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
state to the D0 state. See Table 4-20 for a complete description of the
hot
register.
register.
this bit is 0b.
D4h, see Section 4.66) is 0b, this bit returns 0b for compatibility with version 1.1 of the PCI
Power Management Specification. If PCI_PM_VERSION_CTRL is 1b, 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.35 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-21 for a complete description of the register contents.
PCI register offset:56h
Register type:Read only
Default value:40h
BIT NUMBER76543210
RESET STATE01000000
Table 4-21. 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.66).
0 = Secondary bus clocks are not stopped in D3.
1 = 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.36 Power Management Data Register
The read-only register is not applicable to the bridge and returns 00h when read.
PCI register offset:57h
Register type:Read only
Default value:00h
BIT NUMBER76543210
RESET STATE00000000
4.37 MSI Capability ID Register
This read-only register identifies the linked list item as the register for message signaled interrupts
capabilities. The register returns 05h when read.
PCI register offset:60h
Register type:Read only
Default value:05h
The contents of this read-only register indicate the next item in the linked list of capabilities for the bridge.
This register reads 80h pointing to the subsystem ID capabilities registers.
PCI register offset:61h
Register type:Read only
Default value:80h
BIT NUMBER76543210
RESET STATE10000000
4.39 MSI Message Control Register
This register controls the sending of MSI messages. See Table 4-22 for a complete description of the
register contents.
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.
NOTE
Enabling MSI messaging in the XIO2213B has no effect.
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-23 for a complete description of the register contents.
Enabling MSI messaging in the XIO2213B has no effect.
www.ti.com
4.41 MSI Message Upper Address Register
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, 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-24 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.
Enabling MSI messaging in the XIO2213B has no effect.
4.43SSID/SSVID 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.
PCI register offset:80h
Register type:Read only
Default value:0Dh
BIT NUMBER76543210
RESET STATE00001101
4.44 Next Item Pointer Register
The contents of this read-only register indicate the next item in the linked list of capabilities for the bridge.
This register reads 90h pointing to the PCI Express capabilities registers.
PCI register offset:81h
Register type:Read only
Default value:90h
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 shall only be reset by a fundamental reset (FRST).
PCI register offset:84h
Register type:Read only
Default value:0000h
BIT NUMBER1514131211109876543210
RESET STATE0000000000000000
4.46 Subsystem ID Register
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 shall only be reset by FRST.
PCI register offset:86h
Register type:Read only
Default value:0000h
www.ti.com
BIT NUMBER1514131211109876543210
RESET STATE0000000000000000
4.47 PCI Express Capability ID Register
This read-only register identifies the linked list item as the register for PCIe capabilities. The register
returns 10h when read.
PCI register offset:90h
Register type:Read only
Default value:10h
BIT NUMBER76543210
RESET STATE00010000
4.48 Next Item Pointer Register
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.
PCI register offset:91h
Register type:Read only
Default value:00h
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 000b when read.
15RBERRRole-based error reporting. This bit is hardwired to 1 indicating that the XIO2213B supports
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.001x1
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.
role-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.66). The default value
for this field is 000b, which indicates a range less than 1s. 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.66). The default value
for this field is 000b, which indicates a range less than 1s. 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
11ENSRWEnable no snoop. Controls the setting of the no snoop flag within the TLP header for upstream
10*APPERWAuxiliary 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 read-
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 read-
3URRERWUnsupported request reporting enable. If this bit is set, the bridge sends an ERR_NONFATAL
completion with completion retry status on PCIe 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 in conjunction
with the cache line size register (offset 0Ch, see Section 7.6) to determine how much data to
fetch on a read request. This field is encoded as:
Table 4-27. Device Control Register Description (continued)
BITFIELD NAMEACCESSDESCRIPTION
2FERERWFatal error reporting enable. If this bit is set, the bridge is enabled to send ERR_FATAL
messages to the root complex when a system error event occurs.
0 = Do not report fatal errors to the root complex (default)
1 = Report fatal errors to the root complex
1NFERERWNonfatal error reporting enable. If this bit is set, 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, 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.52 Device Status Register
The device status register provides PCIe device specific information to the system. See Table 4-28 for a
complete description of the register contents.
PCI register offset:9Ah
Register type:Read only
Default value:0000h
www.ti.com
BIT NUMBER1514131211109876543210
RESET STATE0000000000000000
Table 4-28. Device Status Register Description
BITFIELD NAMEACCESSDESCRIPTION
15:6RSVDRReserved. Returns 00 0000 0000b when read.
5PENDRUTransaction pending. This bit is set when the bridge has issued a nonposted transaction that has
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.
The link capabilities register indicates the link-specific capabilities of the bridge. See Table 4-29 for a
complete description of the register contents.
PCI register offset:9Ch
Register type:Read only
Default value:0006 XC11h
BIT NUMBER31302928272625242322212019181716
RESET STATE0000000000000110
BIT NUMBER1514131211109876543210
RESET STATE0xxx110000010001
Table 4-29. Link Capabilities Register Description
BITFIELD NAMEACCESSDESCRIPTION
31:24PORT_NUMRPort number. This field indicates port number for the PCIe link. This field is read-only 00h
23:19RSVDRReserved. Return 00 0000b when read.
18CLK_PMRClock power management. This bit is hardwired to 1 to indicate that XIO2213B 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
indicating that the link is associated with port 0.
power management through CLKREQ protocol.
state. Bit 6 (CCC) in the link control register (offset A0h, see Section 4.54) 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.63).
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.63).
L0 state. Bit 6 (CCC) in the link control register (offset A0h, see Section 4.54) 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 s.
that the bridge supports. The value 11b indicates support for both L0s and L1 through activestate power management.
8CPM_ENRWClock power management enable. This bit is used to enable XIO2213B to use CLKREQ
for clock power management
0 = Clock power management is disabled and XIO2213B shall hold the CLKREQ
signal low.
1 = Clock power management is enabled and XIO2213B is permitted to use the
CLKREQ signal to allow the REFCLK input to be stopped.
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 se te reference clock sources. The bridge uses this common clock configuration
information to report the correct 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 effect 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 link status register indicates the current state of the PCIe link. See Table 4-31 for a complete
description of the register contents.
PCI register offset:A2h
Register type:Read only
Default value:X011h
BIT NUMBER1514131211109876543210
RESET STATE000x000000010001
Table 4-31. Link Status Register Description
BITFIELD NAMEACCESSDESCRIPTION
15:13RSVDRReserved. Returns 000b when read.
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 1×.
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, this bit must be cleared.
0 = Independent 125-MHz reference clock is used.
1 = Common 100-MHz reference clock is used.
4.56 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.58) 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.59) is cleared. This
register shall only be reset by FRST.
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.58) that initiates the bus cycle. This
register shall only be reset by FRST.
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-32 for a complete description of the register
contents.
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-33 for a complete
description of the register contents.
This register controls the direction of the eight GPIO terminals. This register has no effect on the behavior
of GPIO terminals that are enabled to perform secondary functions. The secondary functions share GPIO4
(SCL) and GPIO5 (SDA). See Table 4-34 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 GPIO4 (SCL) and GPIO5 (SDA). The default value at power up depends on
the state of the GPIO terminals as they default to general-purpose inputs. See Table 4-35 for a complete
description of the register contents.
0 = PME input signal to the bridge is enabled and connected to the PME signal
from the 1394 OHCI function (default).
1 = PME input signal to the bridge is disabled.
0 = OHCI_PME pin is enabled and connected to the PME signal from the 1394
OHCI function (default).
1 = OHCI_PME pin is disabled.
to configuration accesses to any function number.
credits.
credits immediately.
0 = Bridge shall use side-band signals to determine the transaction size (default).
1 = Bridge shall use the cache line size register to determine the transaction size.
www.ti.com
(1) These bits shall only be reset by a fundamental reset (FRST). FRST is asserted (low) whenever PERST or GRST is asserted.
(2) These bits are reset only by a global reset (GRST) or the internally generated power-on reset.
Table 4-36. Control and Diagnostic Register 0 Description (continued)
BITFIELD NAMEACCESSDESCRIPTION
(1)
6
PREFETCH_4XRWPrefetch 4× enable
0 = Bridge prefetches up to two cache lines, as defined in the cache line size
register (offset 0Ch, see Section 7.6) for upstream memory read multiple
(MRM) transactions (default).
1 = Bridge prefetches up to four cache lines, as defined in the cache line size
register (offset 0Ch, see Section 7.6) for upstream memory read multiple
(MRM) transactions.
Note: When this bit is set and the FORCE_MRM bit in the general control register is
set, both upstream memory read multiple transactions and upstream memory
transactions prefetch up to four cache lines.
Note: When the READ_PREFETCH_DIS bit in the general control register is set, this bit
has no effect and only one DWORD will be fetched on a burst read.
This bit only affects the XIO2213B design when the EN_CACHE_LINE_CHECK bit is
set.
(1)
5:4
UP_REQ_BUF_VALUERWPCI upstream req-res buffer threshold value. The value in this field controls the buffer
space that must be available for the device to accept a PCI bus transaction. If the
cache line size is not valid, the device will use eight DW for calculating the threshold
value.
CFG_ACCESS_MEM_RWConfiguration access to memory-mapped registers. When this bit is set, the bridge
REGallows configuration access to memory-mapped configuration registers.
(1)
1
RSVDRWReserved. Bit 1 defaults to 0b. If this register is programmed via EEPROM or another
mechanism, the value written into this field must be 0b.
Table 4-37. Control and Diagnostic Register 1 Description
BITFIELD NAMEACCESSDESCRIPTION
32:21RSVDRReserved. Returns 000h when read.
(1)
20:18
17:15
14:11
10
9:6
5:2
1:0
(1) These bits shall only be reset by a fundamental reset (FRST). FRST is asserted (low) whenever PERST or GRST is asserted.
L1_EXIT_LAT_RWL1 exit latency for asynchronous clock. When bit 6 (CCC) of the link control register (offset
ASYNCA0h, see Section 4.54) is set, the value in this field is mirrored in bits 17:15 (L1_LATENCY)
(1)
L1_EXIT_LAT_RWL1 exit latency for common clock. When bit 6 (CCC) of the link control register (offset A0h, see
COMMONSection 4.54) 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_RWSecondary bus reset bit mask. When this bit is set, the bridge masks the reset caused by bit 6
MASK(SRST) of the bridge control register (offset 3Eh, see Section 4.30). This bit defaults to 0b.
(1)
L1ASPM_TIMERRWL1ASPM entry timer. This field specifies the value (in 512-ns ticks) of the L1ASPM entry timer.
(1)
L0s_TIMERRWL0s entry timer. This field specifies the value (in 62.5-MHz clock ticks) of the L0s entry timer.
(1)
RSVDRWReserved. Bits 1:0 default to 00b. If this register is programmed via EEPROM or another
field in the link capabilities register (offset 9Ch, see Section 4.53). This field defaults to 100b.
link capabilities register (offset 9Ch, see Section 4.53). This field defaults to 100b.
mechanism, the value written into this field must be 0000b.
This field defaults to 0100b.
This field defaults to 0010b.
mechanism, the value written into this field must be 00b.
The contents of this register are used for monitoring status and controlling behavior of the PHY macro for
diagnostic purposes. See Table 4-38 for a complete description of the register contents. It is
recommended that all values within this register be left at the default value. Improperly programming fields
in this register may cause interoperability or other problems.
Table 4-38. Control and Diagnostic Register 2 Description
BITFIELD NAMEACCESSDESCRIPTION
(1)
31:24
23:16
15:13PHY_REVRPHY revision number
12:8
(1) These bits shall only be reset by a fundamental reset (FRST). FRST is asserted (low) whenever PERST or GRST is asserted.
N_FTS_ ASYNC_RWN_FTS for asynchronous clock. When bit 6 (CCC) of the link control register (offset A0h,
CLKsee Section 4.54) is clear, the value in this field is the number of FTS that are sent on a
(1)
N_FTS_COMMON_RWN_FTS for common clock. When bit 6 (CCC) of the link control register (offset A0h, see
CLKSection 4.54) is set, the value in this field is the number of FTS that are sent on a transition
(1)
LINK_NUMRWLink number
7EN_L2_PWR_RWEnable L2 power savings
SAVE
6BAR1_ENRWBAR 1 enable
5BAR0_ENRWBAR 0 enable
4REQ_RECOVERYRWREQ_RECOVERY to LTSSM
3REQ_RECONFIGRWREQ_RECONFIGURE to LTSSM
2REQ_HOT_RESETRWREQ_HOT_RESET to LTSSM
1REQ_DIS_RWREQ_DISABLE_SCRAMBLER to LTSSM
SCRAMBLER
0REQ_LOOPBACKRWREQ_LOOPBACK to LTSSM
transition from L0s to L0. This field shall default to 32h.
from L0s to L0. This field defaults to 14h.
0 = Power savings not enabled when in L2
1 = Power savings enabled when in L2
0 = BAR at offset 14h is disabled (default).
1 = BAR at offset 14h is enabled.
0 = BAR at offset 10h is disabled (default).
1 = BAR at offset 10h is enabled.
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-39 for a complete description of the register contents.
CFG_RETRY_RWConfiguration retry counter. Configures the amount of time that a configuration request must be
CNTRretried on the secondary PCI bus before it may be completed with configuration retry status on
the PCIe side.
00 = 25 s
01 = 1 ms
10 = 25 ms (default)
11 = 50 ms
(1)
ASPM_CTRL_RWActive-state power-management control default override. These bits are used to determine the
DEF_OVRDpower up default for bits 1:0 of the link control register in the PCIe capability structure.
00 = Power-on default indicates that the active-state power management is disabled (00b)
01 = (default).
10 = Power-on default indicates that the active-state power management is enabled for
11 = L0s (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).
(2)
LOW_POWER _RWLow-power enable. When this bit is set, the half-ampitude, no preemphasis mode for the PCIe TX
ENdrivers is enabled. The default for this bit is 0b.
(1)
PCI_PM_RWPCI power management version control. This bit controls the value reported in bits 2:0
VERSION_ CTRL(PM_VERSION) in the power management capabilities register (offset 52h, see Section 4.33). It
also controls the value of bit 3 (NO_SOFT_RESET) in the power management control/status
register (offset 54h, see Section 4.34).
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)
STRICT_RWStrict priority enable. When this bit is 0, the default LOW_PRIORITY_COUNT will be 001. When
PRIORITY_ENthis bit is 1, the default LOW_PRIORITY_COUNT will be 000. This default value for this bit is 1.
When this bit is set and the LOW_PRIORITY_COUNT is 000, meaning that strict priority VC
arbitration is used and the extended virtual channel always receives priority over VC0 at the PCIe
port.
0 = Default LOW_PRIORITY_COUNT is 001b.
1 = Default LOW_PRIORITY_COUNT is 000b (default).
(1)
FORCE_MRMRWForce memory read multiple
0 = Memory read multiple transactions are disabled (default).
1 = All upstream memory read transactions initiated on the PCI bus are treated as though
they are memory read multiple transactions in which prefetching is supported for the
transaction. This bit shall only affect the XIO2213B design when the
EN_CACHE_LINE_CHECK bit in the TL control and diagnostic register is set.
(1)
CPM_EN_RWClock power-management enable default override. This bit is used to determine the power up
DEF_OVRDdefault for bit 8 of the link control register in the PCIe 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
(11b).
(1)
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. This
field shall be hardwired to 000b since XIO2213B does not support slot power limit functionality.
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, 111 = Reserved
SCPS210F –OCTOBER 2008–REVISED MAY 2013
(1) These bits shall only be reset by a fundamental reset (FRST). FRST is asserted (low) whenever PERST or GRST is asserted.
(2) These bits are reset only by a global reset (GRST) or the internally generated power-on reset.
Table 4-40. General Control Register Description (continued)
BITFIELD NAMEACCESSDESCRIPTION
(1)
19
18:16
15:13
12
11
10
9:8
7:0
(3) These bits shall only be reset by a fundamental reset (FRST). FRST is asserted (low) whenever PERST or GRST is asserted.
(4) These bits are reset only by a global reset (GRST) or the internally generated power-on reset.
READ_RWRead prefetch disable. This bit controls the prefetch functionality on PCI memory read
PREFETCH_ DIStransactions.
0 = Prefetch to the next cache line boundary on a burst read (default)
1 = Fetch only a single DWORD on a burst read
Note: When this bit is set, the PREFETCH_4X bit in the TL control and diagnostic register shall
have no effect on the design. This bit shall only affect the XIO2213B when the
EN_CACHE_LINE_CHECK bit in the TL control and diagnostic register is set.
(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 94h, see
Section 4.50).
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 s
101 = 1 s up to less than 2 s
110 = 2 s to 4 s
111 = More than 4 s
(3)
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 94h, see
Section 4.50).
000 = Less than 1 s (default)
001 = 1 s up to less than 2 s
010 = 2 s up to less than 4 s
011 = 4 s up to less than 8 s
100 = 8 s up to less than 16 s
101 = 6 s up to less than 32 s
110 = 32 s to 64 s
111 = More than 64 s
(3)
VC_CAP_ENRVC capability structure enable. This bit enables the VC capability structure by changing the next
offset field of the advanced error reporting capability register at offset 102h. This bit is a read only
0b indicating that the VC capability structure is permanently disabled.
0 = VC capability structure disabled (offset field = 000h)
1 = VC capability structure enabled (offset field = 150h)
(3)
BPCC_ERWBus power clock control enable. This bit controls whether the secondary bus PCI clocks are
stopped when the XIO2213B 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 PCIe
interface.
0 = Secondary bus clocks are not stopped in D3 (default).
1 = Secondary bus clocks are stopped on D3.
(4)
BEACON_RWBeacon enable. This bit controls the mechanism for waking up the physical PCIe link when in L2.
ENABLE
0 = WAKE mechanism is used exclusively. Beacon is not used (default).
1 = Beacon and WAKE mechanisms are used.
(3)
MIN_POWER_RWMinimum power scale. This value is programmed to indicate the scale of bits 7:0
SCALE(MIN_POWER_VALUE).
MIN_POWER_RWMinimum power value. This value is programmed to indicate the minimum power requirements.
VALUEThis 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 XIO2213B requires 0.95 W
of power. This field can be reprogrammed through an EEPROM or the system BIOS.
This read/write TI proprietary register is located at offset D8h and controls TI proprietary functions. This
register must not be changed from the specified default state. This register shall only be reset by FRST.
This read/write TI proprietary register is located at offset D9h and controls TI proprietary functions. This
register must not be changed from the specified default state. This register shall only be reset by FRST.
This read-only TI proprietary register is located at offset DAh and controls TI proprietary functions. This
register must not be changed from the specified default state. This register shall only be reset by FRST.
PCI register offset:DAh
Register type:Read only
Default value:00h
The arbiter control register controls the device's internal arbiter. The arbitration scheme used is a twotier rotational arbitration. The device is the only secondary bus master that defaults to the higherpriority arbitration tier. See Table 4-41 for a complete description of the register contents.
PARKRWBus parking mode. This bit determines where the internal arbiter parks the secondary bus.
(1)
6
BRIDGE_TIER_SELRWBridge tier select. This bit determines in which tier the bridge is placed in the arbitration
(1)
5:1
(1) These bits shall only be reset by a fundamental reset (FRST). FRST is asserted (low) whenever PERST or GRST is asserted.
RSVDRWReserved. These bits are reserved and must not be changed from their default value of
(1)
0
TIER_SEL0RWGNT0 tier select. This bit determines in which tier GNT0 is placed in the arbitration
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
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-42 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:1
(1) These bits shall only be reset by a fundamental reset (FRST). FRST is asserted (low) whenever PERST or GRST is asserted.
RSVDRWReserved. These bits are reserved and must not be changed from their default value of
(1)
0
REQ0_MASKRWRequest 0 (REQ0) mask. Setting this bit forces the internal arbiter to ignore requests
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 50) 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-43 for a complete description of the register contents.
This read/write TI proprietary register is located at offset E0h and controls TI proprietary functions. This
register must not be changed from the specified default state. This register shall only be reset by FRST.
This read/write TI proprietary register is located at offset E2h and controls TI proprietary functions. This
register must not be changed from the specified default state. This register shall only be reset by FRST.
This read/clear TI proprietary register is located at offset E4h and controls TI proprietary functions. This
register must not be changed from the specified default state.
The programming model of the PCIe extended configuration space is compliant to the PCI Express Base
Specification and the PCI Express to PCI/PCI-X Bridge Specification programming models. The PCIe
extended configuration map uses the PCIe advanced error reporting capability and PCIe virtual channel
(VC) capability headers.
Sticky bits are reset by a global reset (GRST) or the internally-generated power-on reset. EEPROM
loadable bits are reset by a PCIe reset (PERST), GRST, or the internally-generated power-on reset. The
remaining register bits are reset by a PCIe hot reset, PERST, GRST, or the internally-generated power-on
reset.
(1) This register shall only be reset by a fundamental reset (FRST). FRST is asserted (low) whenever PERST or GRST is asserted.
(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 PCIe 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 PCIe 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.
PCIe extended register102h
offset:
Register type:Read only
Default value:0001h
BIT NUMBER1514131211109876543210
RESET STATE0000000000000001
5.3Uncorrectable Error Status Register
The uncorrectable error status register reports the status of individual errors as they occur on the primary
PCIe 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, PCIe 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.