PLX Technology, Inc. retains the right to make changes to this product at any time, without notice.
Products may have minor variations to this publication, known as errata. PLX assumes no liability
whatsoever, including infringement of any patent or copyright, for sale and use of PLX products.
PLX Technology and the PLX logo are registered trademarks of PLX Technology, Inc. Other brands and
names are property of their respective owners.
These devices are not designed, intended, authorized, or warranted to be suitable for use in
medical, life-support applications, devices or systems or other critical applications.
PLX Part Number: PCI 6152-CC33BC; Former HiNT Part Number: HB1-SE33B
PLX Part Number: PCI 6152-CC33PC; Former HiNT Part Number: HB1-SE33P
PLX Part Number: PCI 6152-CC66BC; Former HiNT Part Number: HB1-SE66
Order Number: 6152-SIL-DB-P1-2.0
Printed in the USA, May 2003
Page 5
PCI 6152 PCI-to-PCI Bridge
The PLX PCI 6152 is a family of three very low power 32-bit PCI-to-PCI bridges: PCI 6152 33BC, PCI 6152 33PC
and PCI 6152 66PC. PCI 6152 66PC is capable of running at 66 MHz PCI Bus and PCI 6152 33BC and PCI 6152
33PC runs at 33 MHz. All parts are specially designed for applications that require high performance 32-bit PCI
bus expansion. Add-in card designers can use PCI 6152 to expand PCI connection capacity beyond the limitation
of a single PCI device. Designers can use PCI 6152 to build multi-device PCI cards such as RAID controllers and
other multimedia applications.
Part numbers and Description:
Part NumberDescriptionPackage Type
PCI 6152 33BC33 MHz, 32-bit PCI interface160-pin Tiny BGA
PCI 6152 66PC66 MHz, 32-bit PCI interface
•PCI Local Bus Specification Rev. 2.2 with VPD support
PCI 6152 66BC
•
• Synchronous primary and secondary PCI bus operation
• Compact PCI Hot Swap Friendly support with Ejector connection
• High performance, no retry penalty flow with uninterrupted 0 wait state burst up to 1K bytes
• Provides 4 Dwords buffering for posted write transactions and 4 Dwords for prefetchable read transactions
each direction
• PCI Mobile Design Guide Rev. 1.1
• Power Management D3 Cold Wakeup capable
• Concurrent primary and secondary port operation supports traffic isolation
• Provides programmable arbitration support for 4 bus masters on secondary interface
• 5 Buffered secondary PCI clock outputs
• 4 GPIO pins
• Enhanced address decoding
- Support 32-bit I/O address range
- Support 64-bit memory- address range
- ISA aware mode for legacy support in the first 64KB of I/O address range
- VGA addressing and VGA palette snooping support
•Supports 3.3V PCI with 5V tolerant I/O
is 66 MHz capable and
PCI 6152 33BC and 33PC
run at 33 MHz
160-pin Tiny BGA
GPIO Interface
PCI 6152
Primary PCI BusSecondary PCI Bus
PCI-to-PCI
Bridge
Up to Four
Master PCI Devices
PCI 6152 Data Book v2.0
2003 PLX Technology, Inc. All rights reserved.5
Page 6
History
RevisionDateDescription
1.13/27/01Corrected register C4h, bit 4,5 description. Default should be 2 clocks delay.
1.24/9/01Updated Company Address
1.34/24/01Corrected description of register 28h and 2Ch register.
1.44/30/01Updated Revision ID description at register 8h.
1.57/12/01Enhanced EEPROM Section description.
This release reflects PLX part numbering.
! Changed “SRST_L to “S_RST_L”, 3 places, in Register 3Eh
! Changed Register 82h, bits 11-15 description
! Changed Dual Address Cycle (1101) values from “N” to “Y” in Table 8-1
2.005/28/03
! Globally changed LDEV, LDEV#, and DEVSEL to DEVSEL_L
! Changed Case 1 and 3 descriptions in Section 8.6
! Removed secondary clock information from bullet 2 and S_RST# bullets (4
from Section 13.2
! Updated Master on primary and secondary response in Section 14
! Removed synchronous design information from Section 16
th
and 6th)
PCI 6152 Data Book v2.0
2003 PLX Technology, Inc. All rights reserved.6
Page 7
Contents
HISTORY ...................................................................................................................................................... 6
PCI 6152 Data Book v2.0
2003 PLX Technology, Inc. All rights reserved.11
Page 12
2 Introduction
This document describes the implementation and functionality of PLX’s 32-bit, 66/33 MHz PCI 6152 PCI-to-PCI
Bridge chip. The specification includes required function and limitations.
PCI 6152 has the following features:
• PCI Local Bus Specification Revision 2.2 features including VPD
• Support delayed transactions for PCI configuration, I/O and memory read commands
• Provides memory write data buffering in both directions
• Provides concurrent primary and secondary bus operation to isolate traffic
• Provides separate arbitration support for individual secondary port
- Programmable 2-level arbiter
•Enhanced address decoding
- 32-bit I/O and memory address decoding
•Supports PCI transaction forwarding for
- Type 1 to Type 0 downstream only configuration commands
- Type 1 to Type 1 configuration commands
- Type 1 configuration write to special cycle
• Three-stating of I/O during power up and power down
• Supports 3.3V, 5V tolerant signaling
3 Ordering Information
The following parts are available:
Part NumberDescriptionPackage Type
PCI 6152-CC33BC 33 MHz, 32-bit PCI interface 160-pin Tiny BGA
PCI 6152-CC66BC 66 MHz, 32-bit PCI interface
PSTSPCI Sustained three-state Output. (Active LOW signal which must be driven inactive for
one cycle before being three-stated to ensure HIGH performance on a shared signal
line)
ODOutput which either drives LOW (active state) or is three-stated
ICMOS Input
OCMOS Output
IOCMOS Bidirect
5.1 Primary Bus Interface Signals
NameTypeDescription
P_AD[31:0]PTSPrimary address/data: Multiplexed address and data bus. Address is
indicated by P_FRAME_L assertion. Write data is stable and valid when
P_IRDY_L is asserted and read data is stable and valid when P_TRDY_L
is asserted. Data is transferred on rising clock edges when both
P_IRDY_L and P_TRDY_L are asserted. During bus idle, PCI 6152 drives
P_AD to a valid logic level when P_GNT_L is asserted.
P_CBE[3:0]PTSPrimary command/byte enables: Multiplexed command field and byte
enable field. During address phase, the initiator drives the transaction type
on these pins. After that the initiator drives the byte enables during data
phases. During bus idle, PCI 6152 drives P_CBE[3:0] to a valid logic level
when P_GNT_L is asserted.
P_PARPTSPrimary Parity: Parity is even across P_AD[31:0], P_CBE[3:0], and
P_PAR (i.e. an even number of ‘1’s). P_PAR is an input and is valid and
stable one cycle after the address phase (indicated by assertion of
P_FRAME_L) for address parity. For write data phases, P_PAR is an
input and is valid one clock after P_IRDY_L is asserted. For read data
phase, P_PAR is an output and is valid one clock after P_TRDY_L is
asserted. Signal P_PAR is three-stated one cycle after the PAD lines are
three-stated. During bus idle, PCI 6152 drives PPAR to a valid logic level
when P_GNT_L is asserted.
P_FRAME_LPSTSPrimary FRAME: Driven by the initiator of a transaction to indicate the
beginning and duration of an access. The deassertion of P_FRAME_L
indicates the final data phase requested by the initiator. Before being
three-stated, it is driven to a deasserted state for one cycle.
PCI 6152 Data Book v2.0
2003 PLX Technology, Inc. All rights reserved.14
Page 15
P_IRDY_LPSTSPrimary IRDY: Driven by the initiator of a transaction to indicate its ability
to complete the current data phase on the primary side. Once asserted in
a data phase, it is not deasserted until end of the data phase. Before
being three-stated, it is driven to a deasserted state for one cycle.
P_TRDY_LPSTSPrimary TRDY: Driven by the target of a transaction to indicate its ability
to complete the current data phase on the primary side. Once asserted in
a data phase, it is not deasserted until end of the data phase. Before
being three-stated, it is driven to a deasserted state for one cycle.
P_DEVSEL_LPSTSPrimary Device Select: Asserted by the target indicating that the device
is accepting the transaction. As a master, PCI 6152 waits for the assertion
of this signal within 5 cycles of P_FRAME_L assertion; otherwise,
terminate with master abort. Before being three-stated, it is driven to a
deasserted state for one cycle.
P_STOP_LPSTSPrimary STOP: Asserted by the target indicating that the target is
requesting the initiator to stop the current transaction. Before being threestated, it is driven to a deasserted state for one cycle.
P_IDSELPIPrimary ID Select. Used as chip select line for Type 0 configuration
access to PCI 6152 configuration space.
P_PERR_LPSTSPrimary Parity Error: Asserted when a data parity error is detected for
data received on the primary interface. Before being three-stated, it is
driven to a deasserted state for one cycle.
P_SERR_LODPrimary System Error: Can be driven LOW by any device to indicate a
system error condition, PCI 6152 drives this pin on
• Address parity error
• Posted write data parity error on target bus
• Secondary bus S_SERR_L asserted
• Master abort during posted write transaction
• Target abort during posted write transaction
• Posted write transaction discarded
• Delayed write request discarded
• Delayed read request discarded
• Delayed transaction master timeout
This signal is pulled up through an external resistor.
P_REQ_LPTSPrimary Request: This is asserted by PCI 6152 to indicate that it wants
to start a transaction on the primary bus. PCI 6152 deasserts this pin for
at least 2 PCI clock cycles before asserting it again.
P_GNT_LPIPrimary Grant: When asserted, PCI 6152 can access the primary bus.
During idle and P_GNT_L asserted, PCI 6152 will drive P_AD, P_CBE
and P_PAR to valid logic level.
PCI 6152 Data Book v2.0
2003 PLX Technology, Inc. All rights reserved.15
Page 16
5.2 Secondary Bus Interface Signals
NameTypeDescription
S_AD[31:0]PTSSecondary Address/Data: Multiplexed address and data bus. Address is
indicated by S_FRAME_L assertion. Write data is stable and valid when
S_IRDY_L is asserted and read data is stable and valid when S_TRDY_L
is asserted. Data is transferred on rising clock edges when both
S_IRDY_L and S_TRDY_L are asserted. During bus idle, PCI 6152 drives
S_AD to a valid logic level when the S_GNT_L is asserted
S_CBE[3:0]PTSSecondary Command/Byte Enables: Multiplexed command field and
byte enable field. During the address phase, the initiator drives the
transaction type on these pins. After that the initiator drives the byte
enables during data phases. During bus idle, PCI 6152 drives S_CBE[3:0]
to a valid logic level when the internal grant is asserted.
S_PARPTSSecondary Parity: Parity is even across S_AD[31:0], S_CBE[3:0], and
S_PAR (i.e. an even number of ‘1’s). S_PAR is an input and is valid and
stable one cycle after the address phase (indicated by assertion of
S_FRAME_L) for address parity. For write data phases, S_PAR is an
input and is valid one clock after S_IRDY_L is asserted. For read data
phase, S_PAR is an output and is valid one clock after S_TRDY_L is
asserted. Signal S_PAR is three-stated one cycle after the S_AD lines are
three-stated. During bus idle, PCI 6152 drives S_PAR to a valid logic level
when the internal grant is asserted.
S_FRAME_LPSTSSecondary FRAME: Driven by the initiator of a transaction to indicate the
beginning and duration of an access. The deassertion of S_FRAME_L
indicates the final data phase requested by the initiator. Before being
three-stated, it is driven to a deasserted state for one cycle
S_IRDY_LPSTSSecondary IRDY: Driven by the initiator of a transaction to indicate its
ability to complete the current data phase on the primary side. Once
asserted in a data phase, it is not deasserted until end of the data phase.
Before being three-stated, it is driven to a deasserted state for one cycle.
S_TRDY_LPSTSSecondary TRDY: Driven by the target of a transaction to indicate its
ability to complete the current data phase on the primary side. Once
asserted in a data phase, it is not deasserted until end of the data phase.
Before being three-stated, it is driven to a deasserted state for one cycle.
S_DEVSEL_LPSTSSecondary Device Select: Asserted by the target indicating that the
device is accepting the transaction. As a master, PCI 6152 waits for the
assertion of this signal within 5 cycles of S_FRAME_L assertion;
otherwise, terminate with master abort. Before being three-stated, it is
driven to a deasserted state for one cycle.
S_STOP_LPSTSSecondary STOP: Asserted by the target indicating that the target is
requesting the initiator to stop the current transaction. Before being threestated, it is driven to a deasserted state for one cycle.
S_PERR_LPSTSSecondary Parity Error: Asserted when a data parity error is detected
for data received on the primary interface. Before being three-stated, it is
driven to a deasserted state for one cycle.
S_SERR_LPISecondary System Error: Can be driven LOW by any device to indicate
a system error condition.
PCI 6152 Data Book v2.0
2003 PLX Technology, Inc. All rights reserved.16
Page 17
S_REQ_L[3:0]PISecondary Requests: This is asserted by external device to indicate that
it wants to start a transaction on the Secondary bus. They are external
pulled up through resistors to VDD.
S_GNT_L[3:0]POSecondary Grant: PCI 6152 asserts this pin to access the secondary
bus. PCI 6152 deasserts this pin for at least 2 PCI clock cycles before
asserting it again. During idle and S_GNT_L asserted, PCI 6152 will drive
S_AD, S_CBE and S_PAR to valid logic levels.
5.3 Clock Signals
NameTypeDescription
P_CLKIPrimary CLK input: Provides timing for all transaction on primary
interface.
S_CLKISecondary CLK input: Provides timing for all transaction on secondary
P_RST_LIPrimary Reset: When P_RST_L is active, outputs and should be
asynchronously three-stated and P_SERR_L and P_GNT_L floated.
S_RST_LPOSecondary Reset: Asserted when any of the following conditions is met:
1. Signal P_RST_L is asserted.
2. The secondary reset bit in the bridge control register in configuration
space is set.
When asserted, all control signals are three-stated and zeros are driven
on S_AD, S_CBE and S_PAR.
5.5 Hot Swap Signals
NameTypeDescription
ENUM_LOHot Swap Interrupt: An open drain bussed signal to signal a change in
status for the chip. Leave floating if not used.
EJECTIHot Swap Eject: Indicates the status of software connection process. If
pin is used to detect the insertion of Hot Swap devices. Pin should be tied
to ground if not used.
L_STATIOHot Swap LED: Indicates the status of software connection process.
Signal should be pulled down to ground if not used.
PCI 6152 Data Book v2.0
2003 PLX Technology, Inc. All rights reserved.17
Page 18
5.6 Miscellaneous Signals
NameTypeDescription
P_CLKRUN_LI/ODPrimary CLKRUN: Used by the central resource to stop the PCI clock or
to slow it down. If not used, this pin should be connected to ground to
signify that PCLK is always running.
S_CLKRUN_LI/OSecondary CLKRUN: Drive high to stop or slow down secondary PCI
clock, driven by secondary PCI device to keep clock running. If secondary
PCI devices do not support CLKRUN#, this pin needs to be pulled low by
a 300ohm resistor.
BPCC_ENIBus/power clock control management pin. When signal is tied high
and the PCI 6152 is placed in the D3hot power state, the PCI 6152 places
the secondary bus in the B2 power state. The PCI 6152 disables the
secondary clocks and drives them to 0. When tied low, placing the PCI
6152 in the D3hot power state has no effect on the secondary bus clocks.
GPIO[3:0]PTSGeneral Purpose Input Output pins. These 4 general purpose signals
are programmable as either input-only or bi-directional signals by writing
the GPIO output enable control register
EEPCLKOEEPROM Clock. This pin is the clock signal to the EEPROM interface
used during autoload and for VPD functions.
EEPDATAI/OEEPROM Serial Data. This pin is serial data interface to the EEPROM.
PVIOIPrimary Interface I/O Voltage This signal must be tied to either 3.3V or
5V, depending on the signaling voltage of the primary interface.
SVIOISecondary Interface I/O Voltage This signal must be tied to either 3.3V
or 5V, depending on the signaling voltage of the secondray interface.
GOZ_LIDiagnostic three-state control. This signal, when asserted, three-states
all
bidirectional and three-statable output pins. This pin must be pulled
high or connected to VDD for normal operation.
NAND_OONand tree diagnostic output. This signal is dedicated to the diagnostic
Nand tree. The GOZ_L signal should be asserted when the Nand tree
mechanism is used.
5.7 Power Signals
NameTypeDescription
VDD+3.3V
VSSGround
PCI 6152 Data Book v2.0
2003 PLX Technology, Inc. All rights reserved.18
Page 19
6 Pin Assignment
1011121314987654321
BPCCE
SCBE1_LSAD15
SAD13
SAD10
SCBE0_L
SAD5
SAD4
SAD1
PAD1
PAD6
CBE0_L
PCLKRUN_LPAD3
A
SPAR
VSS
SCLKRUN_L
ENUM_L
SAD11
SAD8
SAD6
SAD0
L_STATSAD3PAD7PAD4
VSS
PAD8
B
SPERR_L
SSERR_L
VSS
SAD14
SAD12
SAD9
SAD7
SAD2
PAD0
PAD5PAD2
VSS
PAD9
EJECT
C
STRDY_L
SDEVSEL_L
SSTOP_L
VDD
VDD
VDDVSS
VDDVSS
VSS
VSS
PAD10
PAD11
PAD12
D
EEPD
SFRAME_L
SIRDY_L
VSS
VSS
PAD13
PAD14
PAD15
E
SAD17
SAD16
SCBE2_L
VDD
VDD
PCBE1_L
PPAR
PSERR_L
F
SAD20
SAD19
SAD18
VDD
VDD
PPERR_LEEPCLK
PSTOP_L
G
SAD21
SAD22
SAD23
VDD
VDD
PIRDY_L
PTRDY_L
PDEVSEL_L
H
SCBE3_L
SAD24
SAD25
VDD
VDD
CBE2_LPAD16
PFRAME_L
J
SAD26
GPIO0
SAD27
VSS
VSS
PAD19
PAD18
PAD17
K
SAD28
SAD29
SAD30
VSS
VDDVDDVDDVSS
VDD
VSS
VSS
PAD22
PAD21
PAD20
L
SREQ0_L
SAD31
VSS
SGNT2_L
SCLK1SCLK
SCLK4PAD26
PCLK
PREQ_L
PAD29
VSS
GPIO3
PAD23
M
SREQ1_L
VSS
SGNT0_L
SCLK2
NAND_O
PGNT_LSVIOSGNT3_LPAD24
GPIO1
PAD30
PAD27
VSS
PIDSEL
N
SREQ2_L
SREQ3_L
SGNT1_L
SCLK0
SCLK3
GOZ_LPVIO
RST_L
PAD28
PAD25
CBE3_L
GPIO2PAD31SRST_L
P
PCI 6152 Top View
PCI 6152 Data Book v2.0
2003 PLX Technology, Inc. All rights reserved.19
This register sets the value for Master Latency Timer which starts counting when the master asserts FRAME_L.
Reset to 0.
Header Type Register (Read Only) – Offset 0Eh
Hardwired to 01h.
Primary Bus Number Register (Read/Write) – Offset 18h
Programmed with the number of the PCI bus to which the primary bridge interface is connected. This value is set
with configuration software. Reset to 0.
Secondary Bus Number Register (Read/Write) – Offset 19h
Programmed with the number of the PCI bus to which the secondary bridge interface is connected. This value is
set with configuration software. Reset to 0.
Subordinate Bus Number Register (Read/Write) –Offset 1Ah
Programmed with the number of the PCI bus with the highest number that is subordinate to the bridge. This value
is set with configuration software. Reset to 0.
Secondary Latency Timer (Read/Write) – Offset 1Bh
This register is programmed in units of PCI bus clocks. Reset to 0. The latency timer checks for master accesses
on the secondary side that remain unclaimed by any target.
I/O Base Register (Read/Write) – Offset 1Ch
This register defines the bottom address of the I/O address range for the bridge. The upper four bits define the
bottom address range used by the chip to determine when to forward I/O transactions from one interface to the
other. These 4 bits correspond to address bits <15:12> and are writeable. The upper 16 bits corresponding to
address bits <31:16> are defined in the I/O base address upper 16 bits register. The address bits <11:0> are
assumed to be 000h. The lower four bits (3:0) of this register set to ‘0001’ (read-only) to indicate 32-bit I/O
addressing. Reset to 0.
I/O Limit Register (Read/Write) – Offset 1Dh
This register defines the top address of the I/O address range for the bridge. The upper four bits define the top
address range used by the chip to determine when to forward I/O transactions from one interface to the other.
These 4 bits correspond to address bits <15:12> and are writeable. The upper 16 bits corresponding to address
bits <31:16> are defined in the I/O limit address upper 16 bits register. The address bits <11:0> are assumed to be
FFFh. The lower four bits (3:0) of this register set to ‘0001’ (read-only) to indicate 32-bit I/O addressing. Reset to 0.
PCI 6152 Data Book v2.0
2003 PLX Technology, Inc. All rights reserved.29
Page 30
Secondary Status Register (Read/Write) – Offset 1Eh
BitFunctionTypeDescription
0-4reservedR/OReserved (set to ‘0’s).
566 MHzR/O66 MHz Capable : Indicates if primary interface can run at 66 MHz.
This bit is set to ‘0’ for PCI 6152 33BC and set to ‘1’ for PCI 6152
66BC.
6UDFR/ONo User-Definable Features (set to ‘0’).
7Fast Back to
Back Capable
8Data Parity
Error Detected
9-10DEVSEL_L
timing
11Signaled
Target Abort
12Received
Target Abort
13Received
Master Abort
14Received
System Error
R/OFast back-to-back write capable on secondary port (set to ‘1’).
R/WCIt is set when the following conditions are met:
1. SPERR_L is asserted
2. Bit 6 of Command Register is set
Reset to 0.
R/OMedium DEVSEL_L timing (set to ‘01’)
R/WCShould be set (by a target device) whenever a Target Abort cycle
occurs. Should be ‘0’ after reset.
Reset to 0.
R/WCSet to ‘1’ (by a master device) when transactions are terminated
with Target Abort.
Reset to 0.
R/WCSet to ‘1’ (by a master) when transactions are terminated with
Master Abort.
Reset to 0.
R/WCShould be set whenever SSERR_L is detected. Should be a ‘0 after
reset.
Reset to 0.
15Detected
Parity Error
R/WCShould be set whenever a parity error is detected regardless of the
state of the bit 6 of command register.
Reset to 0.
PCI 6152 Data Book v2.0
2003 PLX Technology, Inc. All rights reserved.30
Page 31
Memory Base Register (Read/Write) – Offset 20h
This register defines the base address of the memory-mapped address range for forwarding the cycle through the
bridge. The upper twelve bits corresponding to address bits <31:20> are writeable. The lower 20 address bits
(19:0) are assumed to be 00000h. The 12 bits are reset to 0. The lower 4 bits are read only and set to 0.
Memory Limit Register (Read/Write) – Offset 22h
This register defines the upper limit address of the memory-mapped address range for forwarding the cycle
through the bridge. The upper twelve bits corresponding to address bits <31:20> are writeable. The 12 bits are
reset to 0. The lower 4 bits are read only and are set to 0. The lower 20 address bits (19:0) are assumed to be
FFFFFh. Reset to 0.
Prefetchable Memory Base Register (Read/Write) - Offset 24h
This register defines the base address of the prefetchable memory-mapped address range for forwarding the
cycle through the bridge. The upper twelve bits corresponding to address bits <31:20> are writeable. The 12 bits
are reset to 0. The lower 4 bits are read only and are set to 0. The lower 20 address bits (19:0) are assumed to be
00000h. Reset to 0.
This register defines the upper limit address of the memory-mapped address range for forwarding the cycle
through the bridge. The upper twelve bits correspond to address bits <31:20> are writeable. The 12 bits are reset
to 0. The lower 4 bits are read only and are set to 0. The lower 20 address bits (19:0) are assumed to be FFFFFh.
Reset to 0.
This register defines the upper 32 bit <63:32> memory base address of the prefetchable memory-mapped address
for forwarding the cycle through the bridge. Reset to 0.
This register defines the upper 32 bit <63:32> memory limit address of the prefetchable memory-mapped address
for forwarding the cycle through the bridge. Reset to 0.
This register defines the upper 16 bits of a 32-bit limit I/O address range used for forwarding the cycle through the
bridge. Reset to 0.
ECP Pointer (Read/Only) – Offset 34h
BitFunctionTypeDescription
7-0ECP PointerR/OEnhanced capabilities port offset pointer. This register reads as 80h
to indicate the offset of the power management registers.
PCI 6152 Data Book v2.0
2003 PLX Technology, Inc. All rights reserved.31
Page 32
Interrupt Pin Register (Read Only) – Offset 3Dh
Reads as 0 to indicate that PCI 6152 does not use any interrupt pin.
Bridge Control Register (Read/Write) – Offset 3Eh
BitFunctionTypeDescription
0Parity Error
Response
Enable
1S_SERR_L
Enable
2ISA EnableR/WControls the bridge’s response to ISA I/O addresses, which is limited
R/WControls the bridge’s response to parity errors on the secondary
interface.
0=ignore address and data parity errors on the secondary
interface
1=enable parity error reporting and detection on the secondary
interface
Reset to 0.
R/WControls the forwarding of S_SERR_L to the primary interface.
0=disable the forwarding S_SERR_L to primary
1=enable the forwarding of S_SERR_L to primary
Reset to 0.
to the first 64K.
0=forward all I/O addresses in the range defined by the I/O Base
and I/O Limit registers
1=block forwarding of ISA I/O addresses in the range defined by the
I/O Base and I/O Limit registers that are in the first 64K of I/O space
that address the last 768 bytes in each 1Kbytes block. Secondary
I/O transactions are forwarded upstream if the address falls within
the last 768 bytes in each 1Kbytes block
Reset to 0.
3VGA EnableR/WControls the bridge’s response to VGA compatible addresses.
0=do not forward VGA compatible memory and I/O addresses
from primary to secondary
1=forward VGA compatible memory and I/O address from primary to
secondary regardless of other settings
Reset to 0.
4ReservedR/OReserved (set to 0).
PCI 6152 Data Book v2.0
2003 PLX Technology, Inc. All rights reserved.32
Page 33
5Master Abort
Mode
R/WControls the bridge behavior in responding to master aborts on
secondary interface
0=do not report master aborts (return ffff_ffffh on reads and
discards data on writes)
1=report master aborts by signaling target abort if possible by the
assertion of P_SERR_L if enabled
Reset to 0.
Note: During lock cycles, PCI 6152 ignores this bit, and always
completes the cycle as a target abort.
6Secondary
Interface
Reset
R/WForces the assertion of S_RST_L signal pin on the secondary
interface.
0=do not force the assertion of S_RST_L pin
1=force the assertion of S_RST_L pin
Reset to 0.
7Fast Back to
Back Enable
R/WControls the bridge’s ability to generate fast back-to-back
transactions to different devices on the secondary interface.
0=no fast back to back transaction
1=enable fast back to back transaction
Reset to 0.
8-11ReservedR/WCan be used as a software register
15-12ReservedR/OReserved (set to ‘0’s).
Chip Control Register (Read/Write) – Offset 40h
BitFunctionTypeDescription
3-0ReservedR/OReserved (Set to 0)
4Secondary
bus prefetch
disable
R/WControls PCI 6152’s ability to prefetch during upstream memory read
transactions. When 0 the chip prefetches and does not forward byte
enable bits during memory read transactions. When 1, PCI 6152
requests only one Dword from the target during memory read
transactions and forwards read enable bits. PCI 6152 returns a
target disconnect to the requesting master on the first data transfer.
Memory read line and memory read multiple transactions are still
prefetchable. Reset to 0.
7-6ReservedR/OReserved
PCI 6152 Data Book v2.0
2003 PLX Technology, Inc. All rights reserved.33
Page 34
Arbiter Control Register (Read/Write) – Offset 42h
BitFunctionTypeDescription
3-0Arbiter ControlR/WEach bit controls whether a secondary bus master is assigned to the
high priority group or the low priority group. Bits [3:0] correspond to
request inputs S_REQ_L[3:0], respectively. Reset value is 0.
6-4ReservedR/OReserved
8-7ReservedR/WCan be used as software register
9PCI 6152
priority
15:10ReservedR/OReserved (set to ‘0’s)
R/WDefines whether the secondary port of PCI 6152 is in high priority
group or the low priority group
0=low priority group
1=high priority group.
Reset to 1.
Secondary Clock Control Register (Read/Write) – Offset 68h
BitFunctionTypeDescription
1:0Clock 0
Disable
3:2Clock 1
Disable
5:4Clock 2
Disable
7:6Clock 3
Disable
R/WIf either bit is 0, S_CLKOUT[0] is enabled.
When both bits are 1, S_CLKOUT[0] is disabled.
R/WIf either bit is 0, S_CLKO[1] is enabled.
When both bits are 1, S_CLKO[1] is disabled.
R/WIf either bit is 0, S_CLKO[2] is enabled.
When both bits are 1, S_CLKO[2] is disabled.
R/WIf either bit is 0, S_CLKO[3] is enabled.
When both bits are 1, S_CLKO[3] is disabled.
8Clock 4
Disable
15:9ReservedR/OReserved
PCI 6152 Data Book v2.0
2003 PLX Technology, Inc. All rights reserved.34
R/WIf 0, S_CLKO[3] is enabled.
Otherwise, it is disabled.
Page 35
Clkrun Register (Read/Write) – Offset 6Fh
BitFunctionTypeDescription
0Secondary
Clock Stop
Status
1Secondary
Clkrun Enable
2Primary Clock
Stop
3Primary
Clkrun Enable
R/OSecondary clock stop status
0 = Secondary clock not stopped
1 = Secondary clock stopped
Defaults to 0
R/WSecondary clkrun protocol enable
0 = disable
1 = enable
Defaults to 0
R/WPrimary clock stop
0 = allow primary clock to stop if secondary clock is stopped
1 = always keep primary clock running
Defaults to 0
R/WPrimary clkrun protocol enable
0 = disable
1 = enable
Defaults to 0
4Clkrun ModeR/WClkrun mode
0 = Stop the secondary clock only on request from the primary bus
1 = Stop the secondary clock whenever the secondary bus is idle
and there are no requests from the primary bus.
Defaults to 0
PCI 6152 Data Book v2.0
2003 PLX Technology, Inc. All rights reserved.35
Page 36
Hot Swap and Power Management Registers
Capability Identifier (R/O) - Offset 80h
This register is set to 01h to indicate power management interface registers.
Next Item Pointer (R/O) – Offset 81h
Set to 90h. This field provides an offset into the function's PCI Configuration Space pointing to the location of next
item in the function's capability list. In PCI 6152, this points to the Hot Swap registers.
Power Management Capabilities(R/O) – Offset 82h
BitFunctionTypeDescription
0-2VersionR/OThis register is set to 001b, indicating that this function complies with
Rev 1.0 of the PCI Power Management Interface Specification
3PME ClockR/OThis bit is a '0', indicating that PCI 6152 does not support PME#
signaling.
4Auxiliary
Power Source
5DSIR/ODevice Specific Initialization . Returns ‘0’ indicating that PCI 6152 does
6-8ReservedR/OReserved
9D1 SupportR/OReturns ‘1’ indicating that PCI 6152 supports the D1 device power
10D2 SupportR/OReturns ‘1’ indicating that PCI 6152 supports the D2 device power
11-15PME SupportR/OSet to “F602” in Revision BA.
R/OThis bit is set to ‘0’ since PCI 6152 does not support PME# signaling
not need special initialization
state
state
Set to “7E02” in Revision CC.
PCI 6152 Data Book v2.0
2003 PLX Technology, Inc. All rights reserved.36
Page 37
Power Management Control/ Status(R/W) – Offset 84h
BitFunctionTypeDescription
0-1Power StateR/WThis 2-bit field is used both to determine the current power state of a
function and to set the function into a new power state. The definition of
the field values is given below.
00b - D0
01b - D1 : valid only if D1 capable bit is 1
10b - D2 : valid only if D2 capable bit is 1
11b - D3hot : if BCPPE is 1, SCLK output will be stopped
2-7ReservedR/OReserved
8PME EnableR/OThis bit is set to ‘0’ since PCI 6152 does not support PME# signaling
9-12Data SelectR/WThis 4-bit field is used to select which data is to be reported through the
Data registers and Data Scale field
13-14Data ScaleR/OThis 2-bit field indicates the scaling factor to be used when interpreting
the value of the Data register. The value and meaning of this field will
vary depending on which data value has been selected by the Data
Select field
15PME StatusR/OThis bit is set to ‘0’ since PCI 6152 does not support PME# signaling
PMCSR Bridge Support(R/W) – Offset 86h
BitFunctionTypeDescription
0-5ReservedR/OReserved
6B2/B3 Support
for D3hot
7Bus Power
Control Enable
R/OThis bit returns a ‘1’ when read indicating that when PCI 6152 is
programmed to D3hot state the secondary bus’s clock is stopped.
R/OReturns ‘1’ indicating that the power management state of the
secondary bus follows that of PCI 6152 with one exception , D3hot
state.
Data Register(R/W) – Offset 87h
BitFunctionTypeDescription
0-7Data RegisterR/OThis register is used to report the state dependent data requested by
the Data Select field. The value of this register is scaled by the value
reported by the Data Scale field. This register is EEPROM loadable
Capability Identifier (R/O) - Offset 90h
This register is set to 06h to indicate Hot Swap interface registers.
Next Item Pointer (R/O) - Offset 91h
Set to A0h. This field provides an offset into the function's PCI Configuration Space pointing to the location of next
item in the function's capability list. In PCI 6152, this points to the Vital Product Data (VPD) registers.
PCI 6152 Data Book v2.0
2003 PLX Technology, Inc. All rights reserved.37
Page 38
Hot Swap Register(R/W) – Offset 92h
BitFunctionTypeDescription
0ReservedR/OReserved
1ENUM# Mask
Status
2ReservedR/OReserved
3LED statusR/WIndicates if LED is on or off. Writing a ‘1’ to this bit drives the LSTAT
4-5ReservedR/OReserved
6Extraction
State
7Insertion StateW1TCIndicates assertion of ENUM# due to the device being inserted. Writing
R/WEnables or disables ENUM# assertion
0 = enable ENUM# signal
1 = mask off ENUM# signal
signal high. Writing a ‘0’ drives the pin low.
0 = LED is off
1 = LED is on
W1TCIndicates assertion of ENUM# due to the device being extracted. Writing
a ‘1’ to this bit clears the status.
0 = ENUM# is set to ‘1’
1 = ENUM# is asserted low
a ‘1’ to thisbit clears the status
0 = ENUM# is set to ‘1’
1 = ENUM# is asserted low
Hot Swap Switch (R/W) – Offset 94h
BitFunctionTypeDescription
0Hot Swap
extraction
switch
1-7ReservedR/OReserved
R/OHot Swap extraction switch : Software switch used to signal
extraction of board. If set, board is in inserted state. Writing a ‘0’ to this
bit will signal the pending extraction of the board.
Capability Identifier (R/O) - Offset A0h
This register is set to 03h to indicate VPD registers.
Next Item Pointer (R/O) - Offset A1h
Set to 00h. End of Capability list.
PCI 6152 Data Book v2.0
2003 PLX Technology, Inc. All rights reserved.38
Page 39
VPD Register (R/W) – Offset A2h
BitFunctionTypeDescription
1-0ReservedR/OReserved
7-2VPD AddressR/WVPD Address: Contains Dword address that will be used when
generating a read or write cycle to the VPD table.
14-8ReservedR/OReserved
15VPD
Operation
R/WVPD operation: Writing a ‘0’ to this bit generates a read cycle from the
EEPROM at the VPD address specified in bits 7-2 of this register. This
bit will remain at a logic ‘0’ value until EEPROM cycle is finished, then it
be set to ‘1’. Data for reads is available at register 9ch
Writing a ‘1’ to this bit generates a write cycle to the EEPROM at the
VPD address specified in bits 7-2 of this register. This bit will remain at
a logic ‘1’ value until EEPROM cycle is finished, then it be cleared to ‘0’.
VPD Data Register (R/W) – Offset A4h
BitFunctionTypeDescription
31-0VPD DataR/WVPD Data (EEPROM data[addr + 0x40]) - The least significant byte of
this register corresponds to the byte of VPD at the address specified by
the VPD Address register. The data read from or written to this register
uses the normal PCI byte transfer capabilities. Reads to this register will
return the last data read from or written to the EEPROM.
PCI 6152 Data Book v2.0
2003 PLX Technology, Inc. All rights reserved.39
Page 40
Miscellaneous Control Register (R/W) – Offset C1h
BitFunctionTypeDescription
0ISA IOR/WThis bit enables several I/O addresses to be located behind PCI 6152. If
set, the following I/O addresses belong to the secondary bus.
• 0207h – 0200h : Game port
• 038bh – 0388h : FM
• 0233h – 0220h: Audio
• 0331h – 0330h: MIDI
1Memory Read
Line control
R/WIf 1, PCI 6152 will always stop prefetch on cacheline boundaries on
memory read line transactions.
2Read BE
control
R/WIf 1, PCI 6152 will force all byte enables to be active during read burst
cycles.
3ReservedR/WReserved.
4Low priority
group fixed
R/WIf 1, the low priority group uses the fixed priority arbitration scheme,
otherwise a rotating priority arbitration scheme is used
arbitration
5Low priority
group
arbitration
order
R/WThis bit is only valid when the low priority arbitration group is set to a
fixed arbitration scheme. If 1, priority decreases in ascending numbers
of the master, for example master #4 will have higher priority than
master #3. If 0, the reverse is true. This order is relative to the master
with the highest priority for this group, as specified in bits 7-4 of this
register.
6High priority
group fixed
R/WIf 1, the high priority group uses the fixed priority arbitration scheme,
otherwise a rotating priority arbitration scheme is used
arbitration
7High priority
group
arbitration
order
R/WThis bit is only valid when the high priority arbitration group is set to a
fixed arbitration scheme. If 1, priority decreases in ascending numbers
of the master, for example master #4 will have higher priority than
master #3. If 0, the reverse is true. This order is relative to the master
with the highest priority for this group, as specified in bits 11-8 of this
register.
PCI 6152 Data Book v2.0
2003 PLX Technology, Inc. All rights reserved.40
Page 41
Internal Arbiter Control Register - Offset C3h
BitFunctionTypeDescription
0-3Highest
priority master
in low priority
group
4-7Highest
priority master
in high priority
group
R/WControls which master in the low priority group has the highest
priority. It is valid only if the group uses the fixed arbitration scheme.
0000 : master#0 has highest priority
0001 :
…
1001 : PCI 6152 has highest priority
1010-1111 : Reserved
R/WControls which master in the high priority group has the highest
priority. It is valid only if the group uses the fixed arbitration scheme.
0000 : master#0 has highest priority
0001 :
…
1001 : PCI 6152 has highest priority
1010-1111 : Reserved
Miscellaneous Control Register (R/W) – Offset C4h
BitFunctionTypeDescription
0-2ReservedR/OReserved
3SGNT_L
deassertion
4Secondary to
Primary
transaction
delay
5Primary to
Secondary
transaction
delay
6Retry
Secondary
Master
7Back to Back
Cycle Enable
R/WIf 1, PCI 6152 deasserts SGNT_L 1 clock after PGNT_L is deasserted,
else, SGNT_L is deasserted at the same time as PGNT_L. This bit
defaults to 1 in Rev B and Rev BA parts.
R/WSpecify delay for transactions going from secondary to primary PCI
interface
0 = delay Secondary bus to Primary bus transfer by 2 PCLK
1 = delay Secondary bus to Primary bus transfer by 1 PCLKs
R/WSpecify delay for transactions going from primary to secondary PCI
interface
0 = delay Primary bus to Secondary bus transfer by 2 PCLK
1 = delay Primary bus to Secondary bus transfer by 1 PCLKs
R/WIf 0, and if PCI 6152 has been granted access to the primary bus, and a
secondary master initiates a cycle to access the primary bus while it is
still busy, PCI 6152 will wait for the primary bus to be idle instead of
immediately retrying the secondary master.
If 1, PCI 6152 will immediately retry the secondary master if granted
access to the primary bus while the primary bus is busy.
R/WThis bit enables back to back cycles on the primary interface, if bit 9 of
the primary command register is also enabled.
PCI 6152 Data Book v2.0
2003 PLX Technology, Inc. All rights reserved.41
Page 42
GPIO Control Register (R/W) – Offset C5h
BitFunctionTypeDescription
0GPIO0 InputR/OContains the state of the GPIO0 pin
1GPIO0 Output
R/WIf 1, GPIO0 is configured as output. If 0, GPIO0 is an input pin
Enable
2GPIO0 Output
R/WValue written here will be output to GPIO0 pin if configured as output
Register
3ReservedR/OReserved
4GPIO1 InputR/OContains the state of the GPIO1 pin
5GPIO1 Output
R/WIf 1, GPIO1 is configured as output. If 0, GPIO1 is an input pin
Enable
6GPIO1 Output
R/WValue written here will be output to GPIO1 pin if configured as output
Register
7ReservedR/OReserved
8GPIO2 InputR/OContains the state of the GPIO2 pin
9GPIO2 Output
R/WIf 1, GPIO2 is configured as output. If 0, GPIO2 is an input pin
Enable
10GPIO2 Output
R/WValue written here will be output to GPIO2 pin if configured as output
Register
11ReservedR/OReserved
12GPIO3 InputR/OContains the state of the GPIO3 pin
13GPIO3 Output
R/WIf 1, GPIO3 is configured as output. If 0, GPIO3 is an input pin
Enable
14GPIO3 Output
R/WValue written here will be output to GPIO3 pin if configured as output
Register
15ReservedR/OReserved
PCI 6152 Data Book v2.0
2003 PLX Technology, Inc. All rights reserved.42
Page 43
EEPROM Control - Offset C8
BitFunctionTypeDescription
0StartR/WStarts the EEPROM read or write cycle.
1EEPROM
command
2EEPROM
Error
3EEPROM
autoload
successful
5-4ReservedR/OReserved. Returns ‘0’ when read.
7-6EEPROM
clock rate
R/WControls the command sent to the EEPROM
1 : write
0 : read
R/OThis bit is set to 1 if EEPROM ack was not received during EEPROM
cycle.
R/OThis bit is set to 1 if EEPROM autoload occurred succesfully after
reset, and some configuration registers were loaded with values
programmed in the EEPROM. If zero, EEPROM autoload was
unsuccessful or was disabled.
R/WControls frequency of EEPROM clock. EEPROM clock is derived
from the primary PCI clock.
00 = Reserved
01 = PCLK/256 (Used for 33 MHz PCI)
10 = PCLK/128
11 = PCLK (test mode)
defaults to 01
EEPROM Address - Offset C9h
BitFunctionTypeDescription
0ReservedR/OReserved
7-1EEPROM
address
R/WWord address for EEPROM cycle.
EEPROM Data - Offset CAh
BitFunctionTypeDescription
15-0EEPROM
Data
R/WContains data to be written to the EEPROM. During reads, this
register contains data received from the EEPROM after a read cycle
has completed.
PCI 6152 Data Book v2.0
2003 PLX Technology, Inc. All rights reserved.43
Page 44
PCI 6152 Test Register - Offset CDh
BitFunctionTypeDescription
3-7ReservedR/OReserved
PCI 6152 Test Register - Offset CEh
BitFunctionTypeDescription
3-7ReservedR/OReserved
PCI 6152 Test Register - Offset CFh
BitFunctionTypeDescription
0EEPROM
Autoload
control
1Fast EEPROM
Autoload
2EEPROM
autoload
status
3-7ReservedR/OReserved
R/WIf 1, disables EEPROM autoload
R/WIf 1, speeds up EEPROM autoload
R/OStatus of EEPROM autoload
Subsystem Vendor ID (Read Only)- Offset F0h
This register is a nonstandard implementation of the Subsystem Vendor ID register. It is EEPROM loadable.
Defaults to 3388h
Subsystem ID (Read Only) - Offset F2h
This register is a nonstandard implementation of the Subsystem ID register. It is EEPROM loadable.
Defaults to 0021h
PCI 6152 Data Book v2.0
2003 PLX Technology, Inc. All rights reserved.44
Page 45
8 PCI Bus Operation
This chapter presents detailed information about PCI transactions PCI 6152 responds to and transactions initiated
by the PCI 6152.
PCI 6152 provides a simple, but complete PCI-to-PCI bridge capability, allowing PCI master and slave on its either
side. It passes control and data between primary and secondary bus to guarantee complete visibility from either
side. PCI 6152 is designed to behave like an intelligent buffer.
PCI 6152 achieves its zero wait state bridging function by controlling the direction of control and data. It divides
control and data into 3 signal groups; the FRAME#/IRDY#/CBE#, DEVSEL_L/TRDY#/STOP#, and AD signal
groups.
Direction of FRAME#/IRDY#/CBE# is determined by P_GNT#. If P_GNT# is asserted at the time FRAME# is
active, direction of DEVSEL_L/TRDY#/STOP# is determined by address decode, as described in the address
decode section. Direction of AD[31:0] is determined by the combination of address decode and location of slave.
8.1 Types of Transactions
This section provides a summary of PCI transactions performed by PCI 6152. Table 8–1 lists the command code
and name of each PCI transaction. The Master and Target columns indicate support for each transaction when
PCI 6152 initiates transactions as a master, on the primary bus and on the secondary bus, and when PCI 6152
responds to transactions as a target, on the primary bus and on the secondary bus.
Table 8–1 PCI Transactions
Type of TransactionInitiates as MasterResponds as Target
PCI 6152 Data Book v2.0
2003 PLX Technology, Inc. All rights reserved.45
Page 46
As indicated in Table 8–1, the following PCI commands are not supported by PCI 6152:
•PCI 6152 never initiates a PCI transaction with a reserved command code and, as a target, PCI 6152
ignores reserved command codes.
•PCI 6152 never initiates an interrupt acknowledge transaction and, as a target, PCI 6152 ignores interrupt
acknowledge transactions. Interrupt acknowledge transactions are expected to reside entirely on the
primary PCI bus closest to the host bridge.
•PCI 6152 does not respond to special cycle transactions. To generate special cycle transactions on other
PCI buses, either upstream or downstream, a Type 1 configuration command must be used.
•PCI 6152 does not generate Type 0 configuration transactions on the primary interface, nor does it
respond to Type 0 configuration transactions on the secondary PCI interface. The PCI-to-PCI Bridge
Architecture Specification does not support configuration from the secondary bus.
8.2 Address Phase
A 32-bit address uses a single address phase. This address is driven on AD<31:0>, and the bus command is
driven on P_CBE[3:0]
8.3 Device Select (DEVSEL_L) Generation
PCI 6152 always performs positive address decoding when accepting transactions on either the primary or
secondary buses. PCI 6152 never subtractively decodes. Medium DEVSEL_L timing is used on both interfaces.
8.4 Data Phase
The address phase or phases of a PCI transaction are followed by one or more data phases. A data phase is
completed when IRDY# and either TRDY# or STOP# are asserted. A transfer of data occurs only when both
IRDY# and TRDY# are asserted during the same PCI clock cycle. The last data phase of a transaction is indicated
when FRAME# is de-asserted and both TRDY# and IRDY# are asserted, or when IRDY# and STOP# are
asserted.
PCI 6152 Data Book v2.0
2003 PLX Technology, Inc. All rights reserved.46
Page 47
8.5 Write Transactions
Acting as PCI bus extender, PCI 6152 responds differently according to the address and initiator.
Case 1: Primary master access device on primary bus
PCI 6152 will forward all PCI signals from primary to secondary so that any device there can track the PCI bus.
Case 2: Primary master access device on secondary bus
PCI 6152 will forward address, command, data, byte enable, P_IRDY# to secondary while forwarding
S_DEVSEL_L, S_TRDY# and S_STOP# to primary bus.
Case 3: Secondary master access device on secondary bus
PCI 6152 will forward all PCI signals from secondary to primary so that any device there can track the PCI bus.
Case 4: Secondary master access device on primary bus
PCI 6152 will forward address, command, data, byte enable, S_IRDY# to primary while forwarding P_DEVSEL_L,
P_TRDY# and P_STOP# to secondary.
8.6 Read Transactions
PCI 6152 responds according to the address and initiator of the read command.
Case 1: Primary master access device on primary bus
PCI 6152 will not forward PCI signals from primary to secondary.
Case 2: Primary master access device on secondary bus
PCI 6152 will forward address, command, byte enable, P_IRDY# to secondary while forwarding data,
S_DEVSEL_L, S_TRDY# and S_STOP# to primary bus.
Case 3: Secondary master access device on secondary bus
PCI 6152 will not forward PCI signals from secondary to primary, except in the case of dummy arbitration.
Case 4: Secondary master access device on primary bus
PCI 6152 will forward address, command, byte enable, S_IRDY# to primary while forwarding data, P_DEVSEL_L,
P_TRDY# and P_STOP# to secondary.
PCI 6152 Data Book v2.0
2003 PLX Technology, Inc. All rights reserved.47
Page 48
8.7 Configuration Transactions
Configuration transactions are used to initialize a PCI system. Every PCI device has a configuration space that is
accessed by configuration commands. All registers are accessible in configuration space only.
In addition to accepting configuration transactions for initialization of its own configuration space, PCI 6152 also
forwards configuration transactions for device initialization in hierarchical PCI systems, as well as for special cycle
generation.
To support hierarchical PCI bus systems, two types of configuration transactions are specified: Type 0 and
Type 1.
Type 0 configuration transactions are issued when the intended target resides on the same PCI bus as the
initiator. A Type 0 configuration transaction is identified by the configuration command and the Lowest 2 bits of the
address set to 00b.
Type 1 configuration transactions are issued when the intended target resides on another PCI bus, or when a
special cycle is to be generated on another PCI bus. A Type 1 configuration command is identified by the
configuration command and the Lowest 2 address bits set to 01b.
The register number is found in both Type 0 and Type 1 formats and gives the Dword address of the configuration
register to be accessed. The function number is also included in both Type 0 and Type 1 formats and indicates
which function of a multifunction device is to be accessed. For single-function devices, this value is not decoded.
Type 1 configuration transaction addresses also include a 5-bit field designating the device number that identifies
the device on the target PCI bus that is to be accessed. In addition, the bus number in Type 1 transactions
specifies the PCI bus to which the transaction is targeted.
8.7.1 Type 0 Access to PCI 6152
The configuration space is accessed by a Type 0 configuration transaction on the primary interface. The
configuration space cannot be accessed from the secondary bus. PCI 6152 responds to a Type 0 configuration
transaction by asserting P_DEVSEL_L when the following conditions are met during the address phase:
• The bus command is a configuration read or configuration write transaction.
• Low 2 address bits P_AD<1:0> must be 00b.
• Signal P_IDSEL must be asserted.
• The function code is 0.
PCI 6152 limits all configuration accesses to a single Dword data transfer and returns a target disconnect with the
first data transfer if additional data phases are requested. Because read transactions to configuration space do not
have side effects, all bytes in the requested Dword are returned, regardless of the value of the byte enable bits.
Type 0 configuration write and read transactions do not use data buffers; that is, these transactions are completed
immediately.
PCI 6152 ignores all Type 0 transactions initiated on the secondary interface.
PCI 6152 Data Book v2.0
2003 PLX Technology, Inc. All rights reserved.48
Page 49
8.7.2 Type 1 to Type 0 Translation
Type 1 configuration transactions are used specifically for device configuration in a hierarchical PCI bus system. A
PCI-to-PCI bridge is the only type of device that should respond to a Type 1 configuration command. Type 1
configuration commands are used when the configuration access is intended for a PCI device that resides on a
PCI bus other than the one where the Type 1 transaction is generated.
PCI 6152 performs a Type 1 to Type 0 translation when the Type 1 transaction is generated on the primary bus
and is intended for a device attached directly to the secondary bus. PCI 6152 must convert the configuration
command to a Type 0 format so that the secondary bus device can respond to it. Type 1 to Type 0 translations are
performed only in the downstream direction; that is, PCI 6152 generates a Type 0 transaction only on the
secondary bus, and never on the primary bus.
PCI 6152 responds to a Type 1 configuration transaction and translates it into a Type 0 transaction on the
secondary bus when the following conditions are met during the address phase:
• The low 2 address bits on P_AD<1:0> are 01b.
• The bus number in address field P_AD<23:16> is equal to the value in the secondary bus number register
in configuration space.
•The bus command on P_CBE<3:0> is a configuration read or configuration write transaction.
When PCI 6152 translates the Type 1 transaction to a Type 0 transaction on the secondary interface, it performs
the following translations to the address:
• Sets the low 2 address bits on S_AD<1:0> to 00b.
• Decodes the device number and drives the bit pattern specified in Table 4–6 on S_AD<31:16> for the
purpose of asserting the device’s IDSEL signal.
• Sets S_AD<15:11> to 0.
• Leaves unchanged the function number and register number fields.
PCI 6152 Data Book v2.0
2003 PLX Technology, Inc. All rights reserved.49
Page 50
PCI 6152 asserts a unique address line based on the device number. These address lines may be used as
secondary bus IDSEL signals. The mapping of the address lines depends on the device number in the Type 1
address bits P_AD<15:11>. Table 8–2 presents the mapping that PCI 6152 uses.
PCI 6152 can assert up to 16 unique address lines to be used as IDSEL signals for up to 16 devices on the
secondary bus, for device numbers ranging from 0 through 15. Because of electrical loading constraints of the PCI
bus, more than 16 IDSEL signals should not be necessary. However, if device numbers greater than 15 are
desired, some external method of generating IDSEL lines must be used, and no upper address bits are then
asserted. The configuration transaction is still translated and passed from the primary bus to the secondary bus. If
no IDSEL pin is asserted to a secondary device, the transaction ends in a master abort.
-
PCI 6152 forwards Type 1 to Type 0 configuration read or write transactions as delayed transactions. Type 1 to
Type 0 configuration read or write transactions are limited to a single 32-bit data transfer.
PCI 6152 Data Book v2.0
2003 PLX Technology, Inc. All rights reserved.50
Page 51
8.7.3 Type 1 to Type 1 Forwarding
Type 1 to Type 1 transaction forwarding provides a hierarchical configuration mechanism when two or more levels
of PCI-to-PCI bridges are used.
When PCI 6152 detects a Type 1 configuration transaction intended for a PCI bus downstream from the
secondary bus, PCI 6152 forwards the transaction unchanged to the secondary bus. Ultimately, this transaction is
translated to a Type 0 configuration command or to a special cycle transaction by a downstream PCI-to-PCI
bridge. Downstream Type 1 to Type 1 forwarding occurs when the following conditions are met during the address
phase:
• The low 2 address bits are equal to 01b.
• The bus number falls in the range defined by the lower limit (exclusive) in the secondary bus number
register and the upper limit (inclusive) in the subordinate bus number register.
•The bus command is a configuration read or write transaction.
PCI 6152 also supports Type 1 to Type 1 forwarding of configuration write transactions upstream to support
upstream special cycle generation. A Type 1 configuration command is forwarded upstream when the following
conditions are met:
• The low 2 address bits are equal to 01b.
• The bus number falls outside the range defined by the lower limit (inclusive) in the secondary bus number
register and the upper limit (inclusive) in the subordinate bus number register.
• The device number in address bits AD<15:11> is equal to 11111b.
• The function number in address bits AD<10:8> is equal to 111b.
• The bus command is a configuration write transaction.
PCI 6152 forwards Type 1 to Type 1 configuration write transactions as delayed transactions. Type 1 to Type 1
configuration write transactions are limited to a single data transfer.
PCI 6152 Data Book v2.0
2003 PLX Technology, Inc. All rights reserved.51
Page 52
8.7.4 Special Cycles
The Type 1 configuration mechanism is used to generate special cycle transactions in hierarchical PCI systems.
Special cycle transactions are ignored by acting as a target and are not forwarded across the bridge. Special cycle
transactions can be generated from Type 1 configuration write transactions in either the upstream or the
downstream direction.
PCI 6152 initiates a special cycle on the target bus when a Type 1 configuration write transaction is
detected on the initiating bus and the following conditions are met during the address phase:
• The low 2 address bits on AD<1:0> are equal to 01b.
• The device number in address bits AD<15:11> is equal to 11111b.
• The function number in address bits AD<10:8> is equal to 111b.
• The register number in address bits AD<7:2> is equal to 000000b.
• The bus number is equal to the value in the secondary bus number register in configuration space for
downstream forwarding or equal to the value in the primary bus number register in configuration space for
upstream forwarding.
•The bus command on P_CBE# is a configuration write command.
When PCI 6152 initiates the transaction on the target interface, the bus command is changed from configuration
write to special cycle. The address and data are forwarded unchanged. Devices that use special cycles ignore the
address and decode only the bus command. The data phase contains the special cycle message. The transaction
is forwarded as a delayed transaction, but in this case the target response is not forwarded back (because special
cycles result in a master abort). Once the transaction is completed on the target bus, through detection of the
master abort condition, PCI 6152 responds with TRDY# to the next attempt of the configuration transaction from
the initiator.
PCI 6152 Data Book v2.0
2003 PLX Technology, Inc. All rights reserved.52
Page 53
8.8 Transaction Termination
This section describes how PCI 6152 returns transaction termination conditions back to the initiator.
The initiator can terminate transactions with one of the following types of termination:
• Normal termination
• Normal termination occurs when the initiator de-asserts FRAME# at the beginning of the last data phase,
and de-asserts IRDY# at the end of the last data phase in conjunction with either TRDY# or STOP#
assertion from the target.
• Master abort
• A master abort occurs when no target response is detected. When the initiator does not detect a
DEVSEL_L from the target within five clock cycles after asserting FRAME#, the initiator terminates the
transaction with a master abort. If FRAME# is still asserted, the initiator de-asserts FRAME# on the next
cycle, and then de-asserts IRDY# on the following cycle. IRDY# must be asserted in the same cycle in
which FRAME# de-asserts. If FRAME# is already de-asserted, IRDY# can be de-asserted on the next
clock cycle following detection of the master abort condition.
• The target can terminate transactions with one of the following types of termination:
• Normal termination—TRDY# and DEVSEL_L asserted in conjunction with FRAME# de-asserted and
IRDY# asserted.
• Target retry—STOP# and DEVSEL_L asserted without TRDY# during the first data phase. No data
transfers occur during the transaction. This transaction must be repeated.
•Target disconnect with data transfer—STOP# and DEVSEL_L asserted with TRDY#. Signals that this is
the last data transfer of the transaction.
•Target disconnect without data transfer—STOP# and DEVSEL_L asserted without TRDY# after previous
data transfers have been made. Indicates that no more data transfers will be made during this transaction.
• Target abort—STOP# asserted without DEVSEL_L and without TRDY#.
• Indicates that the target will never be able to complete this transaction. DEVSEL_L must be asserted for at
least one cycle during the transaction before the target abort is signaled.
8.8.1 Master Termination Initiated by PCI 6152
PCI 6152, as an initiator, uses normal termination if DEVSEL_L is returned by the target within five clock cycles of
PCI 6152’s assertion of FRAME# on the target bus. PCI 6152 terminates a transaction when the target terminates
the transaction with last data transfer, retry, disconnect, or target abort.
PCI 6152 Data Book v2.0
2003 PLX Technology, Inc. All rights reserved.53
Page 54
8.8.2 Master Abort Received by PCI 6152
If the initiator initiates a transaction on the target bus and does not detect DEVSEL_L returned by the target within
five clock cycles of PCI 6152’s assertion of FRAME#, PCI 6152 terminates the transaction with a master abort.
This sets the received master abort bit in the status register corresponding to the target bus.
For delayed read and write transactions, PCI 6152 is able to reflect the master abort condition back to the initiator.
When PCI 6152 detects a master abort in response to a delayed transaction, and when the initiator repeats the
transaction, PCI 6152 does not respond to the transaction with DEVSEL_L. This passes the master abort
condition back to the initiator.
Note
When PCI 6152 performs a Type 1 to special cycle translation, a master abort is the expected termination for the
special cycle on the target bus. In this case, the master abort received bit is not set, and the Type 1 configuration
transaction is disconnected after the first data phase.
8.8.3 Target Termination Received by PCI 6152
When PCI 6152 initiates a transaction on the target bus and the target responds with DEVSEL_L, the target can
end the transaction with one of the following types of termination:
• Normal termination (upon de-assertion of FRAME#)
• Target retry
• Target disconnect
• Target abort
PCI 6152 handles these terminations in different ways, depending on the type of transaction being performed.
PCI 6152 Data Book v2.0
2003 PLX Technology, Inc. All rights reserved.54
Page 55
8.8.3.1 Delayed Write Target Termination Response
When PCI 6152 initiates a delayed write transaction, the type of target termination received from the target can be
passed back to the initiator. Table 8–3 shows the response to each type of target termination that occurs during a
delayed write transaction.
• PCI 6152 repeats a delayed write transaction until one of the following conditions is met:
• PCI 6152 completes at least one data transfer.
• PCI 6152 receives a master abort.
• PCI 6152 receives a target abort.
PCI 6152 makes 2
Table 8-3 Response to Delayed Write Target Termination
24
write attempts resulting in a response of target retry.
Target Termination Response
NormalReturn disconnect to initiator with first data
transfer only if multiple data phases requested.
Target retryReturn target retry to initiator. Continue write
attempts to target.
Target disconnectReturn disconnect to initiator with first data
transfer only if multiple data phases requested.
Target abortReturn target abort to initiator.
Set received target abort bit in target interface
status register.
Set signaled target abort bit in initiator interface
status register.
PCI 6152 Data Book v2.0
2003 PLX Technology, Inc. All rights reserved.55
Page 56
8.8.3.2 Delayed Read Target Termination Response
When PCI 6152 initiates a delayed read transaction, the abnormal target responses can be passed back to the
initiator. Other target responses depend on how much data the initiator requests. Table 8-4 shows the response to
each type of target termination that occurs during a delayed read transaction.
Table 8-4 Response to Delayed Read Target Termination
Target termination Response
NormalIf prefetchable, target disconnect only if initiator
requests more data than read from target. If
nonprefetchable, target disconnect on first data
phase.
Target retryReinitiate read transaction to target
Target disconnectIf initiator requests more data than read from
target, return target disconnect to initiator
Target abortReturn target abort to initiator.
Set received target abort bit in the target
interface status register.
Set signaled target abort bit in the initiator
interface status register.
PCI 6152 repeats a delayed read transaction until one of the following conditions is met:
• PCI 6152 completes at least one data transfer.
• PCI 6152 receives a master abort.
• PCI 6152 receives a target abort.
PCI 6152 Data Book v2.0
2003 PLX Technology, Inc. All rights reserved.56
Page 57
8.8.4 Target Termination Initiated by PCI 6152
PCI 6152 can return a target retry, target disconnect, or target abort to an initiator for reasons other than detection
of that condition at the target interface.
8.8.4.1 Target Retry
PCI 6152 returns a target retry to the initiator when it cannot accept write data or return read data as a result of
internal conditions. PCI 6152 returns a target retry to an initiator when any of the following conditions is met:
•For delayed write transactions:
o The transaction is being entered into the delayed transaction queue.
o The transaction has already been entered into the delayed transaction queue, but target response has not yet
been received.
o The delayed transaction queue is full, and the transaction cannot be queued.
o A transaction with the same address and command has been queued.
o Uses more than 16 clocks to accept this transaction.
• For delayed read transactions:
o The transaction is being entered into the delayed transaction queue.
o The read request has already been queued, but read data is not yet available.
o The delayed transaction queue is full, and the transaction cannot be queued.
o A delayed read request with the same address and bus command has already been queued.
o Uses more than 16 clocks to accept this transaction.
When a target retry is returned to the initiator of a delayed transaction, the initiator must repeat the transaction with
the same address and bus command as well as the data if this is a write transaction, within the time frame
specified by the master timeout value; otherwise, the transaction is discarded from the buffer.
8.8.4.2 Target Disconnect
PCI 6152 returns a target disconnect to an initiator when the target returns target disconnect.
8.8.4.3 Target Abort
PCI 6152 returns a target abort to an initiator when one of the following conditions is met:
• PCI 6152 is returning a target abort from the intended target.
• PCI 6152 is unable to obtain delayed read data from the target or to deliver delayed write data to the
target after 2•
attempts.
When PCI 6152 returns a target abort to the initiator, it sets the signaled target abort bit in the status register
corresponding to the initiator interface.
PCI 6152 Data Book v2.0
2003 PLX Technology, Inc. All rights reserved.57
Page 58
9 Address Decoding
PCI 6152 uses three address ranges that control I/O and memory transaction forwarding. These address ranges
are defined by base and limit address registers in the configuration space. This chapter describes these address
ranges, as well as ISA-mode and VGA-addressing support.
9.1 Address Ranges
PCI 6152 uses the following address ranges to determine which I/O and memory transactions are forwarded from
the primary PCI bus to the secondary PCI bus, and from the secondary bus to the primary bus:
•Two 32-bit I/O address ranges
Transactions falling within these ranges are forwarded downstream from the primary PCI bus to the two secondary
PCI buses. Transactions falling outside these ranges are forwarded upstream from the two secondary PCI buses
to the primary PCI bus.
PCI 6152 uses a flat address space; that is, it does not perform any address translations. The address space has
no ‘‘gaps’’—addresses that are not marked for downstream forwarding are always forwarded upstream.
9.2 I/O Address Decoding
PCI 6152 uses the following mechanisms that are defined in the configuration space to specify the I/O address
space for downstream and upstream forwarding:
• I/O base and limit address registers
• The ISA enable bit
• The VGA mode bit
• The VGA snoop bit
This section provides information on the I/O address registers and ISA mode.
To enable downstream forwarding of I/O transactions, the I/O enable bit must be set in the command register in
configuration space. If the I/O enable bit is not set, all I/O transactions initiated on the primary bus are ignored. To
enable upstream forwarding of I/O transactions, the master enable bit must be set in the command register. If the
master enable bit is not set, PCI 6152 ignores all I/O and memory transactions initiated on the secondary bus.
Setting the master enable bit also Allows upstream forwarding of memory transactions.
Caution
If any configuration state affecting I/O transaction forwarding is changed by a configuration write operation on the
primary bus at the same time that I/O transactions are ongoing on the secondary bus, the
PCI 6152 response to the secondary bus I/O transactions is not predictable. Configure the I/O base and limit
address registers, ISA enable bit, VGA mode bit, and VGA snoop bit before setting the I/O enable and master
enable bits, and change them subsequently only when the primary and secondary PCI buses are idle.
PCI 6152 Data Book v2.0
2003 PLX Technology, Inc. All rights reserved.58
Page 59
9.2.1 I/O Base and Limit Address Registers
PCI 6152 implements one set of I/O base and limit address registers in configuration space that define an I/O
address range per port downstream forwarding. PCI 6152 supports 32-bit I/O addressing, which Allows I/O
addresses downstream of PCI 6152 to be mapped anywhere in a 4GB I/O address space.
I/O transactions with addresses that fall inside the range defined by the I/O base and limit registers are forwarded
downstream from the primary PCI bus to the secondary PCI bus. I/O transactions with addresses that fall outside
this range are forwarded upstream from the secondary PCI bus to the primary PCI bus.
The I/O range can be turned off by setting the I/O base address to a value greater than that of the I/O limit
address. When the I/O range is turned off, all I/O transactions are forwarded upstream, and no I/O transactions
are forwarded downstream.
The I/O range has a minimum granularity of 4KB and is aligned on a 4KB boundary. The maximum I/O range is
4GB in size.
The I/O base register consists of an 8-bit field at configuration address 1Ch, and a 16-bit field at address 30h. The
top 4 bits of the 8-bit field define bits <15:12> of the I/O base address. The bottom 4 bits read only as 1h to
indicate that PCI 6152 supports 32-bit I/O addressing. Bits <11:0> of the base address are assumed to be 0,
which naturally aligns the base address to a 4KB boundary. The 16 bits contained in the I/O base upper 16 bits
register at configuration offset 30h define AD<31:16> of the I/O base address. All 16 bits are read/write. After
primary bus reset or chip reset, the value of the I/O base address is initialized to 0000 0000h.
The I/O limit register consists of an 8-bit field at configuration offset 1Dh and a 16-bit field at offset 32h. The top 4
bits of the 8-bit field define bits <15:12> of the I/O limit address. The bottom 4 bits read only as 1h to indicate that
32-bit I/O addressing is supported. Bits <11:0> of the limit address are assumed to be FFFh, which naturally aligns
the limit address to the top of a 4KB I/O address block. The 16 bits contained in the I/O limit upper 16 bits register
at configuration offset 32h define AD<31:16> of the I/O limit address. All 16 bits are read/write. After primary bus
reset or chip reset, the value of the I/O limit address is reset to 0000 0FFFh.
Note
The initial states of the I/O base and I/O limit address registers define an I/O range of 0000 0000h to 0000 0FFFh,
which is the bottom 4KB of I/O space. Write these registers with their appropriate values before setting either the
I/O enable bit or the master enable bit in the command register in configuration space.
PCI 6152 Data Book v2.0
2003 PLX Technology, Inc. All rights reserved.59
Page 60
9.2.2 ISA Mode
PCI 6152 supports ISA mode by providing an ISA enable bit in the bridge control register in configuration space.
ISA mode modifies the response of PCI 6152 inside the I/O address range in order to support mapping of I/O
space in the presence of an ISA bus in the system. This bit only affects the response of PCI 6152 when the
transaction falls inside the address range defined by the I/O base and limit address registers, and only when this
address also falls inside the first 64KB of I/O space (address bits <31:16> are 0000h).
When the ISA enable bit is set, PCI 6152 does not forward downstream any I/O transactions addressing the top
768 bytes of each aligned 1KB block. Only those transactions addressing the bottom 256 bytes of an aligned 1KB
block inside the base and limit I/O address range are forwarded downstream. Transactions above the 64KB I/O
address boundary are forwarded as defined by the address range defined by the I/O base and limit registers.
Accordingly, if the ISA enable bit is set, PCI 6152 forwards upstream those I/O transactions addressing the top
768 bytes of each aligned 1KB block within the first 64KB of I/O space. The master enable bit in the command
configuration register must also be set to enable upstream forwarding. All other I/O transactions initiated on the
secondary bus are forwarded upstream only if they fall outside the I/O address range.
When the ISA enable bit is set, devices downstream of PCI 6152 can have I/O space mapped into the first 256
bytes of each 1KB chunk below the 64KB boundary, or anywhere in I/O space above the 64KB boundary.
9.3 Memory Address Decoding
PCI 6152 has three mechanisms for defining memory address ranges for forwarding of memory transactions:
• Memory-mapped I/O base and limit address registers
• Prefetchable memory base and limit address registers
• VGA mode
This section describes the first two mechanisms.
To enable downstream forwarding of memory transactions, the memory enable bit must be set in the command
register in configuration space. To enable upstream forwarding of memory transactions, the master enable bit
must be set in the command register. Setting the master enable bit also Allows upstream forwarding of I/O
transactions.
Caution
If any configuration state affecting memory transaction forwarding is changed by a configuration write operation on
the primary bus at the same time that memory transactions are ongoing on the secondary bus, response to the
secondary bus memory transactions is not predictable. Configure the memory-mapped I/O base and limit address
registers, prefetchable memory base and limit address registers, and VGA mode bit before setting the memory
enable and master enable bits, and change them subsequently only when the primary and secondary PCI buses
are idle.
PCI 6152 Data Book v2.0
2003 PLX Technology, Inc. All rights reserved.60
Page 61
9.3.1 Memory-Mapped I/O Base and Limit Address Registers
Memory-mapped I/O is also referred to as nonprefetchable memory. Memory addresses that cannot automatically
be prefetched but that can conditionally prefetch based on command type should be mapped into this space. Read
transactions to nonprefetchable space may exhibit side effects; this space may have non-memory-like behavior.
PCI 6152 prefetches in this space only if the memory read line or memory read multiple commands are used;
transactions using the memory read command are limited to a single data transfer.
The memory-mapped I/O base address and memory-mapped I/O limit address registers define an address range
that PCI 6152 uses to determine when to forward memory commands. PCI 6152 forwards a memory transaction
from the primary to the secondary interface if the transaction address falls within the memory-mapped I/O address
range. PCI 6152 ignores memory transactions initiated on the secondary interface that fall into this address range.
Any transactions that fall outside this address range are ignored on the primary interface and are forwarded
upstream from the secondary interface (provided that they do not fall into the prefetchable memory range or are
not forwarded downstream by the VGA mechanism).
The memory-mapped I/O range supports 32-bit addressing only. The PCI-to-PCI Bridge Architecture Specification
does not provide for 64-bit addressing in the memory-mapped I/O space. The memory-mapped I/O address range
has a granularity and alignment of 1MB. The maximum memory-mapped I/O address range is 4GB.
The memory-mapped I/O address range is defined by a 16-bit memory-mapped I/O base address register at
configuration offset 20h and by a 16-bit memory-mapped I/O limit address register at offset 22h. The top 12 bits of
each of these registers correspond to bits <31:20> of the memory address. The low 4 bits are hardwired to 0. The
low 20 bits of the memory-mapped I/O base address are assumed to be 0 0000h, which results in a natural
alignment to a 1MB boundary. The low 20 bits of the memory-mapped I/O limit address are assumed to be F
FFFFh, which results in an alignment to the top of a 1MB block.
Note
The initial state of the memory-mapped I/O base address register is 0000 0000h. The initial state of the memorymapped I/O limit address register is 000F FFFFh. Note that the initial states of these registers define a memorymapped I/O range at the bottom 1MB block of memory. Write these registers with their appropriate values before
setting either the memory enable bit or the master enable bit in the command register in configuration space.
To turn off the memory-mapped I/O address range, write the memory-mapped I/O base address register with a
value greater than that of the memory-mapped I/O limit address register.
PCI 6152 Data Book v2.0
2003 PLX Technology, Inc. All rights reserved.61
Page 62
10 PCI Bus Arbitration
PCI 6152 must arbitrate for use of the primary bus when forwarding upstream transactions, and for use of the
secondary bus when forwarding downstream transactions. The arbiter for the primary bus resides external to the
typically on the motherboard. For the secondary PCI bus, PCI 6152 implements an internal arbiter.
10.1 Primary PCI Bus Arbitration
PCI 6152 implements a request output pin, P_REQ#, and a grant input pin, P_GNT#, for primary PCI bus
arbitration. PCI 6152 asserts P_REQ# when forwarding transactions upstream; that is, it acts as initiator on the
primary PCI bus. However, if a target retry, target disconnect, or a target abort is received in response to a
transaction initiated by PCI 6152 on the primary PCI bus, PCI 6152 de-asserts P_REQ# for two PCI clock cycles.
When P_GNT# is asserted LOW by the primary bus arbiter after PCI 6152 has asserted P_REQ#, PCI 6152
initiates a transaction on the primary bus on behalf of master on secondary. When P_GNT# is asserted to PCI
6152 when P_REQ# is not asserted, PCI 6152 parks P_AD, P_CBE, and P_PAR by driving them to valid logic
levels. When the primary bus is parked at PCI 6152 and PCI 6152 then has a transaction to initiate on the primary
bus, PCI 6152 starts the transaction if P_GNT# was asserted during the previous cycle.
10.2 Secondary PCI Bus Arbitration
PCI 6152 implements an internal secondary PCI bus arbiter. This arbiter supports 4 external masters in addition to
PCI 6152.
The PCI 6152 Secondary to Primary Frame Delay can be adjusted by programming Register C4h bit 4. At 66
MHz, 2 clock delay is recommended. However if faster Frame propagation is desired, especially in the case of
handling an aggressive PCI arbitor on the Host bus, 1 clock delay is recommended.
PCI 6152 Data Book v2.0
2003 PLX Technology, Inc. All rights reserved.62
Page 63
11 Transaction Delay
PCI 6152 transaction delay from one interface to the other can be controlled through register C4h, bits 4 and 5.
Primary to secondary transaction delay and secondary to primary transaction delay can be configured separately
at 1 or 2 clocks delay.
PCI 6152 supports 1 clock latency mode in order to minimize the delay. In this mode, there is strictly 1 clock delay
between the originating FRAME and the bridge FRAME. PCI 6152 passes all memory and I/O cycles, regardless
of the address. On the 2nd clock of the cycle, PCI 6152 checks which side the cycle belongs to. If it is determined
to be the wrong side, PCI 6152 will self terminate its own cycle by asserting STOP_L.
This mode can be independently enabled for the Primary to Secondary transfer, and for the Secondary to Primary
transfer. It is used primarily to minimize the delay between the assertion of the PGNT_L on the Primary side and
the assertion of PFRAME_L due to the transaction initiated on the secondary side. PCI 6152 is designed to restrict
SGNT_L based on the assertion of PGNT_L.
The control flow is as follows:
1. Primary asserts PGNT_L in response to the PREQ_L asserted by PCI 6152
2. Secondary asserts SGNT_L in response to PGNT_L
3. Secondary master asserts SFRAME_L in response to SGNT_L
4. PCI 6152 passes through the SFRAME_L to PFRAME_L.
There could be up to 4 clocks delay from step 1 to 4. This mode will decrease the delay to 3 clocks.
If 2 clock latency mode is enabled, which is the default, then the delay for step 4 above is 2 clocks instead of 1,
with everything else the same.
PCI 6152 Data Book v2.0
2003 PLX Technology, Inc. All rights reserved.63
Page 64
12 Error Handling
PCI 6152 checks, forwards, and generates parity on both the primary and secondary interfaces. To maintain
transparency, PCI 6152 always tries to forward the existing parity condition on one bus to the other bus, along with
address and data.
To support error reporting on the PCI bus, PCI 6152 implements the following:
• S_SERR# signal on the secondary interface
• Primary status and secondary status registers
This chapter provides detailed information about how PCI 6152 handles errors. It also describes error status
reporting and error operation disabling.
12.1 Address Parity Errors
PCI 6152 checks address parity for all transactions on both buses, for all address and all bus commands.
When PCI 6152 detects an address parity error on the primary interface, the following events occur:
•If the parity error response bit is set in the command register, PCI 6152 does not claim the transaction with
P_DEVSEL_L; this may allow the transaction to terminate in a master abort.
If the parity error response bit is not set, PCI 6152 proceeds normally and accepts the transaction if it is
directed to or across the PCI 6152.
• PCI 6152 sets the detected parity error bit in the status register.
• PCI 6152 asserts P_SERR# and sets the signaled system error bit in the status register, if both of the
following conditions are met:
o The SERR# enable bit is set in the command register.
o The parity error response bit is set in the command register.
When PCI 6152 detects an address parity error on the secondary interface, the following events occur:
•If the parity error response bit is set in the bridge control register, PCI 6152 does not claim the transaction
with S_DEVSEL_L; this may allow the transaction to terminate in a master abort.
If the parity error response bit is not set, PCI 6152 proceeds normally and accepts the transaction if it is directed to
or across the PCI 6152.
o PCI 6152 sets the detected parity error bit in the secondary status register.
o PCI 6152 asserts S_SERR# and sets the signaled system error bit in the status register, if both of the
following conditions are met:
o The SERR# enable bit is set in the command register.
o The parity error response bit is set in the bridge control register.
PCI 6152 Data Book v2.0
2003 PLX Technology, Inc. All rights reserved.64
Page 65
12.2 Data Parity Errors
When forwarding transactions, PCI 6152 attempts to pass the data parity condition from one interface to the other
unchanged, whenever possible, to allow the master and target devices to handle the error condition.
The following sections describe, for each type of transaction, the sequence of events that occurs when a parity
error is detected and the way in which the parity condition is forwarded across PCI 6152.
12.2.1 Configuration Write Transactions to Configuration Space
When PCI 6152 detects a data parity error during a Type 0 configuration write transaction to configuration space,
the following events occur:
•If the parity error response bit is set in the command register, PCI 6152 asserts P_TRDY# and writes the
data to the configuration register. PCI 6152 also asserts S_SERR#.
•If the parity error response bit is not set, PCI 6152 does not assert P_SERR#.
PCI 6152 sets the detected parity error bit in the status register, regardless of the state of the parity error response
bit.
12.2.2 Read Transactions
When PCI 6152 detects a parity error during a read transaction, the target drives data and data parity, and the
initiator checks parity and conditionally asserts SERR#.
For downstream transactions, when PCI 6152 detects a read data parity error on the secondary bus, the following
events occur:
•PCI 6152 asserts P_SERR# two cycles following the data transfer, if the secondary interface parity error
response bit is set in the bridge control register.
• PCI 6152 sets the detected parity error bit in the secondary status register.
• PCI 6152 sets the data parity detected bit in the secondary status register, if the secondary interface parity
error response bit is set in the bridge control register.
• PCI 6152 forwards the bad parity with the data back to the initiator on the primary bus.
• PCI 6152 completes the transaction normally.
For upstream transactions, when PCI 6152 detects a read data parity error on the primary bus, the following
events occur:
•PCI 6152 asserts P_SERR# two cycles following the data transfer, if the primary interface parity error
response bit is set in the command register.
• PCI 6152 sets the detected parity error bit in the primary status register.
• PCI 6152 sets the data parity detected bit in the primary status register, if the primary interface parity error
response bit is set in the command register.
• PCI 6152 forwards the bad parity with the data back to the initiator on the secondary bus.
• PCI 6152 completes the transaction normally.
PCI 6152 returns to the initiator the data and parity that was received from the target. When the initiator detects a
parity error on this read data and is enabled to report it, the initiator asserts PERR# two cycles after the data
transfer occurs. It is assumed that the initiator takes responsibility for handling a parity error condition.
PCI 6152 Data Book v2.0
2003 PLX Technology, Inc. All rights reserved.65
Page 66
12.3 Data Parity Error Reporting Summary
In the previous sections, the PCI 6152’s responses to data parity errors are presented according to the type of
transaction in progress. This section organizes the PCI 6152’s responses to data parity errors according to the
status bits that the PCI 6152 sets and the signals that it asserts.
Table 12-1 shows setting the detected parity error bit in the status register, corresponding to the primary interface.
This bit is set when PCI 6152 detects a parity error on the primary interface.
Table 12–1 Setting the Primary Interface Detected Parity Error Bit
Primary detected
parity error bit
0ReadDownstreamPrimaryx/x
0ReadDownstreamSecondaryx/x
1ReadUpstreamPrimaryx/x
0ReadUpstreamSecondaryx/x
1Delayed writeDownstreamPrimaryx/x
0Delayed writeDownstreamSecondaryx/x
0Delayed writeUpstreamPrimaryx/x
Transaction typeDirectionBus where error
was detected
Primary/secondary
parity error response
bits
1
0Delayed writeUpstreamSecondaryx/x
1
x =don’t care
PCI 6152 Data Book v2.0
2003 PLX Technology, Inc. All rights reserved.66
Page 67
Table 12–2 shows setting the detected parity error bit in the secondary status register, corresponding to the
secondary interface. This bit is set when PCI 6152 detects a parity error on the secondary interface.
Table 12–2 Setting the Secondary Interface Detected Parity Error Bit
Secondary
detected parity
error bit
0ReadDownstreamPrimaryx/x
Transaction typeDirectionBus where error
was detected
Primary/secondary
parity error response
bits
1
1ReadDownstreamSecondaryx/x
0ReadUpstreamPrimaryx/x
0ReadUpstreamSecondaryx/x
0Delayed writeDownstreamPrimaryx/x
0Delayed writeDownstreamSecondaryx/x
0Delayed writeUpstreamPrimaryx/x
1Delayed writeUpstreamSecondaryx/x
1
x =don’t care
Table 12-3 shows setting the data parity detected bit in the status register, corresponding to the primary interface.
This bit is set under the following conditions:
• PCI 6152 must be a master on the primary bus.
• The parity error response bit in the command register, corresponding to the primary interface, must be set.
Table 12-3 Setting the Primary Interface Data Parity Detected Bit
Primary data
parity detected
bit
0ReadDownstreamPrimaryx/x
Transaction typeDirectionBus where error
was detected
Primary/secondary
parity error response
bits
1
0ReadDownstreamSecondaryx/x
1ReadUpstreamPrimary1/x
0ReadUpstreamSecondaryx/x
0Delayed writeDownstreamPrimaryx/x
0Delayed writeDownstreamSecondaryx/x
1Delayed writeUpstreamPrimary1/x
0Delayed writeUpstreamSecondaryx/x
1
x =don’t care
PCI 6152 Data Book v2.0
2003 PLX Technology, Inc. All rights reserved.67
Page 68
Table 12–4 shows setting the data parity detected bit in the secondary status register, corresponding to the
secondary interface. This bit is set under the following conditions:
• The PCI 6152 must be a master on the secondary bus.
• The parity error response bit in the bridge control register, corresponding to the secondary interface, must
be set.
Table 12–4 Setting the Secondary Interface Data Parity Detected Bit
Secondary data
parity detected
bit
0ReadDownstreamPrimaryx/x
Transaction typeDirectionBus where error
was detected
Primary/secondary
parity error response
bits
1
1ReadDownstreamSecondaryx/1
0ReadUpstreamPrimaryx/x
0ReadUpstreamSecondaryx/x
0Delayed writeDownstreamPrimaryx/x
1Delayed writeDownstreamSecondaryx/1
0Delayed writeUpstreamPrimaryx/x
0Delayed writeUpstreamSecondaryx/x
1
x =dont care
PCI 6152 Data Book v2.0
2003 PLX Technology, Inc. All rights reserved.68
Page 69
Table 12-5 shows assertion of S_SERR#. This signal is set under the following conditions:
•The parity error response bit on the command register and the parity error response bit on the bridge
control register must both be set.
•The SERR# enable bit must be set in the command register.
Table 12-5 Assertion of S_SERR# for Data Parity Errors
Transaction typeDirectionBus where error
was detected
Primary/secondary
parity error
response bits
ReadDownstreamPrimaryx/x
1
ReadDownstreamSecondaryx/x
ReadUpstreamPrimaryx/x
ReadUpstreamSecondaryx/x
Delayed writeDownstreamPrimaryx/x
Delayed writeDownstreamSecondaryx/x
Delayed writeUpstreamPrimaryx/x
Delayed writeUpstreamSecondaryx/x
1
x =don’t care
2
The parity error was detected on the target (secondary) bus but not on the initiator (primary) bus.
3
The parity error was detected on the target (primary) bus but not on the initiator (secondary) bus.
12.4 System Error (SERR#) Reporting
PCI 6152 uses the P_SERR# signal to report conditionally a number of system error conditions in addition to the
special case parity error conditions.
Whenever the assertion of P_SERR# is discussed in this document, it is assumed that the following conditions
apply:
•For PCI 6152 to assert P_SERR# for any reason, the SERR# enable bit must be set in the command
register.
•Whenever PCI 6152 asserts P_SERR#, PCI 6152 must also set the signaled system error bit in the status
register.
When S_SERR# is asserted by secondary device, PCI 6152 sets the received system error bit in the secondary
status register.
The PCI 6152 also conditionally asserts P_SERR# when parity error reported on target bus during write
transaction.
PCI 6152 Data Book v2.0
2003 PLX Technology, Inc. All rights reserved.69
Page 70
13 Reset
This chapter describes the primary interface, secondary interface, and chip reset mechanisms.
13.1 Primary Interface Reset
PCI 6152 has one reset input, P_RST#. When P_RST# is asserted, the following events occur:
• PCI 6152 immediately three-states all primary and secondary PCI interface signals.
• PCI 6152 performs a chip reset.
• Registers that have default values are reset.
The P_RST# asserting and de-asserting edges can be asynchronous to P_CLK and S_CLK.
13.2 Secondary Interface Reset
PCI 6152 is responsible for driving the secondary bus reset signal, S_RST#.
PCI 6152 asserts S_RST# when any of the following conditions is met:
• Signal P_RST# is asserted.
• Signal S_RST# remains asserted as long as P_RST# is asserted and does not de-assert until P_RST# is
de-asserted.
• The secondary reset bit in the bridge control register is set.
• The chip reset bit in the diagnostic control register is set.
When S_RST# is asserted, all secondary PCI interface control signals, including the secondary grant outputs, are
immediately three-stated. Signals S_AD, S_CBE#, and S_PAR are driven LOW for the duration of S_RST#
assertion. All posted write and delayed transaction data buffers are reset; therefore, any transactions residing in
buffers at the time of secondary reset are discarded.
When S_RST# is asserted by means of the secondary reset bit, PCI 6152 remains accessible during secondary
interface reset and continues to respond to accesses to its configuration space from the primary interface.
PCI 6152 Data Book v2.0
2003 PLX Technology, Inc. All rights reserved.70
Page 71
14 Bridge Behavior
A PCI cycle is initiated by asserting the FRAME# signal. In a bridge, there are a number of possibilities. These are
summarized in the table below.
Bridge Actions for Various Cycle Types
InitiatorTargetResponse
Master on primaryTarget on PrimaryPCI 6152 does not forward signals to secondary.
Master on primaryTarget on secondaryPCI 6152 asserts P_DEVSEL_L, then passes the
cycle to the secondary. When cycle is complete on
the target port, it will wait for the initiator to end with
normal termination.
Master on primaryTarget not on
primary nor
secondary port
Master on
secondary
Master on
secondary
Master on
secondary
A target then has up to three cycles to respond before subtractive decoding is initiated. If the target detects an
address hit, it should assert its DEVSEL_L signal in the cycle corresponding to the values of bits 9 and 10 in the
Configuration Status Register.
Termination of a PCI cycle can occur in a number of ways. Normal termination begins by the initiator (master) deasserting FRAME# with IRDY# being asserted (or remaining asserted) on the same cycle. The cycle completes
when TRDY# and IRDY# are both asserted simultaneously. The target should de-assert TRDY# for one cycle
following final assertion (sustained three-state signal).
Target on the
secondary port
Target on primary
port
Target not on
primary nor the other
secondary
PCI 6152 does not respond and the cycle will
terminate as master abort.
PCI 6152 does not forward signals to primary,
except in the case of dummy arbitration.
PCI 6152 asserts S_DEVSEL_L, then passes the
cycle to the appropriate port. When cycle is
complete on the target port, it will wait for the
initiator to end with normal termination.
PCI 6152 does not respond.
PCI 6152 Data Book v2.0
2003 PLX Technology, Inc. All rights reserved.71
Page 72
14.1 Abnormal Termination (Initiated by Bridge Master)
14.1.1 Master Abort
Master abort indicates that PCI 6152 acting as a master receives no response (i.e., no target asserts
P_DEVSEL_L or S_DEVSEL_L) from a target., the bridge de-asserts FRAME# and then de-asserts IRDY#.
14.1.2 PCI Master on Primary Bus
The table illustrates the direction of the PCI control/data path when a PCI transaction is initiated by a PCI master
residing on the primary bus. It guarantees the integrity of the cycle, viewed from the primary and the secondary
side.
Slave locationCommandFRAME/CBE
IRDY
Primary busreadS->PP->SP->S
Primary buswriteS->PP->SP<-S
Secondary busreadS->PP<-S---
Secondary buswriteS->PP<-S---
PCI 6152 is designed to pass almost all the primary cycles to the secondary side, except configuration cycle in the
1 clock delay case, as described below. PCI 6152 performs configuration type #1 to type #0 conversion, on the
cycle with a matched bus-number. It will pass the type #1 configuration cycle that locates on the secondary side of
the bridge.
DEVSEL_L/
TRDY
STOP
AD
14.2 Configuration Type #1 to type #0 Conversion
When a type #1 configuration cycle appears on the primary side with a bus-number equaling to PCI 6152 bridge
bus-number, PCI 6152 performs the type #1 to type #0 conversion cycle, as follows.
First, it will retry all the subsequent all the primary cycles, until its completion. And it will de-grant the secondary
bus to block the secondary master. The conversion cycle will appear on the secondary bus only, without being
reflected to the primary side.
Then, it issues the converted type #0 configuration cycle on the secondary side. The termination of the cycle can
be either normal, master abort or slave abort. In the case of read, PCI 6152 will latch the data, and wait for the
same type #1 configuration cycle on the primary side.
PCI 6152 Data Book v2.0
2003 PLX Technology, Inc. All rights reserved.72
Page 73
14.3 Configuration Type #1 to Type #1 By-Passing
When a type #1 configuration cycle appears on the primary side with a bus-number greater than PCI 6152 bridge
bus-number, but smaller than the secondary sub-ordinate bus-number, the same type #1 configuration cycle will
appear on the secondary side. Otherwise, the bypassing process is very similar to the type #1 to type #0
conversion process. PCI 6152's internal state machine will generate the secondary cycle, retry all the primary
cycle, and block any secondary master.
14.4 Type-0 Configuration Cycle Filter Mode
In this Type-0 configuration cycle filter mode, PCI 6152 will filter out all the primary Type-0 configuration cycle by
delaying passing of primary P_FRAME# by one PCI clock. In case of Type-1 configuration cycle through the
bridge, it will return retry and relies on the internal state machine to do the conversion cycle to generate Type-0 or
Type-1 on the secondary side.
14.5 Decoding
PCI 6152 uses decoding circuit to determine the slave device location.
During the memory cycle, PCI 6152 uses Memory Base/Limit and PrefetchBase/Limit. Slave is on the secondary
side if one of the following is true:
All the type #0 configuration cycle, interrupt acknowledge cycle and the special cycle appearing on the primary
side is considered to have slave on the primary side. Likewise, all the similar cycle appearing on the secondary
side is considered to have slave on the secondary side.
PCI 6152 Data Book v2.0
2003 PLX Technology, Inc. All rights reserved.73
Page 74
14.6 Secondary Master
The secondary master issues S_REQ#[3:0] to request the bus. PCI 6152 will generate P_REQ# on the primary
side. When P_GNT# is active, PCI 6152 will use the round-robin algorithm to grant one secondary master using
S_GNT#[3:0].
The control/data path is illustrated below. PCI 6152 will pass all the cycle from the secondary side to the primary.
Slave
location
primaryreadS->PP->SP->S
primarywriteS->PP->SP<-S
slavereadS->PP<-S---
slavewriteS->PP<-S---
read/
Write
FRAME/CBE
IRDY
DEVSEL_L /
TRDY
STOP
AD
14.7 PCI Clock Run Feature
PCI 6152 supports PCI clock run protocol defined in the PCI Mobile Design Guide 1.0. P_CLKRUN# is set high
when the system's central resource wants to stop P_CLK, and then PCI 6152 will either signal that it allows PCI
clock to be stopped by letting P_CLKRUN# remain high, or it will signal to the system to keep P_CLK running by
driving P_CLKRUN# low for 2 clocks then release by then the system’s central resource will keep P_CLKRUN#
low. There are three situations that PCI 6152 will keep primary clock running. First is bit 2 of clock run control
register is set, second there is a pending cycle on going through the chip, third is on behalf of secondary PCI
device.
Secondary clock run is enabled by bit 1 of the clock run control register, by default the initiation of stopping/slowing
down secondary comes from primary, however if bit 4 of clock run control register is set, secondary clock will be
stopped when the bus is idle and there is no cycle from primary bus.
PCI 6152 Data Book v2.0
2003 PLX Technology, Inc. All rights reserved.74
Page 75
15 Clocks
This chapter provides information about the clocks.
15.1 Primary and Secondary Clock Inputs
PCI 6152 implements a separate clock input for each PCI interface. The primary interface is synchronized to the
primary clock input, P_CLK, and the secondary interface is synchronized to the secondary clock input, S_CLK.
15.2 Secondary Clock Outputs
PCI 6152 has 5 secondary clock outputs that can be used as clock inputs for up to 4 external secondary bus
devices with one feedback to S_CLK.
The rules for using secondary clocks are:
• Each secondary clock output is limited to no more than 2 loads.
• One of the secondary clock outputs must be used for the PCI 6152 S_CLK input
• Using an equivalent amount of etch on the board for all secondary clocks is recommended, to minimize skew
between them, and a maximum delay of the etch of 2ns.
•Terminating or disabling unused secondary clock outputs is recommended to reduse power dissipation and
noise in the system
PCI 6152 Data Book v2.0
2003 PLX Technology, Inc. All rights reserved.75
Page 76
16 66-MHz Operation
PCI 6152 66BC supports a maximum frequency of 66 MHz. There are no special procedures necessary to
configure PCI 6152 66BC as a 66 MHz device. Bit 5 of the PCI status register is supported, and shows PCI 6152
66BC as a 66 MHz capable device to the system. PCI 6152 66BC does not have an M66EN pin. It is up to the
system designer to implement the M66EN connection when using the PCI 6152 66BC.
PCI 6152 supports only 1:1 frequency ratio on the primary and secondary bus interfaces.
PCI 6152 Data Book v2.0
2003 PLX Technology, Inc. All rights reserved.76
Page 77
17 Miscellaneous Options
17.1 EEPROM Interface
PCI 6152 has an interface to EEPROM device. The interface can control an ISSI IS24C02 or compatible part,
which is organized as 256X8 bits. The EEPROM is used to initialize the registers. After PRST_L is deasserted,
PCI 6152 will automatically load data from the EEPROM. The data structure is defined in the following section.
The EEPROM interface is organized on 16 bit base in little endian format, and PCI 6152 supplies a 7-bit EEPROM
word address.
The following pins are used for the EEPROM interface:
• EEPCLK: EEPROM clock output
• EEPDATA: EEPROM bi-directional serial data pin
The PCI 6152 does not control the EEPROM address inputs, it can only access EEPROM with address inputs set
to 0.
17.1.1 Auto Mode EEPROM Access
Using auto mode, the PCI 6152 can access the EEPROM on a word basis via hardware sequencer. User need
only to access word data via PCI 6152 configuration registers for EEPROM START control, address, read/write
command. Before each access, software should check the Auto Mode Cycle in Progress status before issuing the
next START.
17.1.2 EEPROM Mode at Reset
During RESET, the PCI 6152 will autoload input for EEPROM automatic load condition. The first offset in the
EEPROM contains a signature. If the signature is recognized, register auto-load will commence right after RESET.
During the auto-load, PCI 6152 will read sequential words from the EEPROM and write to the appropriate
registers.
Before the PCI 6152 registers can be accessed through host, user should check the auto-load condition by
reading the EEPAUTO bit. Host access is allowed only after EEPAUTO status becomes '0' which means that the
auto load initialization sequence is complete.
PCI 6152 Data Book v2.0
2003 PLX Technology, Inc. All rights reserved.77
Page 78
17.1.3 EEPROM Data Structure
Following the reset, if the condition above is met, PCI 6152 will auto-load the register with data from
EEPROM. The following table describes the data structure used in EEPROM.
The PCI 6152 accesses the EEPROM one word at a time. It is important to note that in the data phase, bit
orders are reverse of that of the address phase. PCI 6152 only supports EEPROM Device Address 0.
Write:
Read:
S
T
A
R
T
S
T
A
R
T
10
10
Device
Address
10 000
Device
Address
10 000
W
R
A
I
C
T
K
E
Word
Address (n)
A
C
K
Data (n)Data (n +1)
A
C
K
S
A
T
C
O
K
P
0
M
S
B
W
R
A
I
C
T
K
E
M
S
B
Word
Address (n)
L
L
S
S
B
B
S
T
A
A
C
R
K
T
0
L
S
B
Device
Address
10
10 000
M
L
S
S
B
B
R
A
E
C
A
K
D
Data (n)Data (n +1)
L
S
B
M
S
B
N
O
S
A
C
K
M
L
S
S
B
B
A
T
C
O
K
P
M
S
B
PCI 6152 Data Book v2.0
2003 PLX Technology, Inc. All rights reserved. 78
Page 79
17.1.4 EEPROM Address and Corresponding PCI 6152 Register
EEPROM
Byte Address
PCI Configuration
Offset
Description
00-01hEEPROM signature: Autoload will only proceed if it reads a
value of 1516h on the first word loaded.
0x1516=valid signature, otherwise disable autoloading
02hRegion Enable: Enables or disables certain regions of the PCI
configuration space from being loaded from the EEPROM.
Valid combinations are:
Bits 0, 7-5: Reserved
Bits 4-1:
0000 = stop autoload at offset 02h
0001 = stop autoload at offset 04h
0011 = stop autoload at offset 07h
0111 = stop autoload at offset 11h
1111 = autoload all EEPROM loadable registers.
Other combinations are undefined.
PCI 6152 Data Book v2.0
2003 PLX Technology, Inc. All rights reserved.79
Page 80
17.2 General Purpose I/O Interface
The PCI 6152 implements a 4-pin general-purpose I/O GPIO interface. Each pin can be configured as input or
output through the GPIO control register at offset C5h.
17.3 Vital Product Data
PCI 6152 contains the VPD registers as specified in the PCI Local Bus Specification Revision 2.2. The VPD
information is stored in the EEPROM device along with the autoload information. PCI 6152 provides for storage of
224 bytes of VPD data in the EEPROM device. VPD related registers are located starting at offset A0h of the PCI
configuration space. VPD also uses the enhanced capabilities port address mechanism
PCI 6152 Data Book v2.0
2003 PLX Technology, Inc. All rights reserved.80
Page 81
18 PCI Power Management
PCI 6152 incorporates functionality that meets the requirements of the PCI Power Management Specification,
Revision 1.0. These features include:
• PCI power management registers using the enhanced capabilities port (ECP) address mechanism
• Support for D0, D3
and D3
hot
• Support for D0, D1, D2, D3
• Support of the B2 secondary bus power state when in the D3
The table below shows the states and related actions that the PCI 6152 performs during power management
transitions. (no other transactions are permitted.)
power management states
cold
and D3
hot
power management states for devices behind the bridge
cold
power management state
hot
Current State
D0
D0D3
D0D2
D0D1
D3
hot
D3
hot
D3
cold
Next State
D3
D3
D0
D0
cold
cold
Action
Power has been removed from the PCI 6152.
A power-up reset must be performed to bring the
PCI 6152 to D0.
If enabled to do so by the BPCCE pin, the PCI 6152
hot
will disable the secondary clocks and drive them
low.
Unimplemented power state. The PCI 6152 will
ignore the write to the power state bits (power state
remains at D0).
Unimplemented power state. The PCI 6152 will ignore
the write to the power state bits (power state remains
at D0).
The PCI 6152 enables secondary clock outputs and
performs an internal chip reset. Signal S_RST_L will
not be asserted. All registers will be returned to the
reset values and buffers will be cleared.
Power has been removed from the PCI 6152. A
power-up reset must be performed to bring the PCI
6152 to D0.
Power-up reset. The PCI 6152 performs the
standard power-up reset functions.
PME# signals are routed from downstream devices around PCI-to PCI bridges. PME# signals do not pass through
PCI-to-PCI bridges.
PCI 6152 Data Book v2.0
2003 PLX Technology, Inc. All rights reserved.81
Page 82
19 Hot Swap
PCI 6152 incorporates functionality that meets the requirements of the CompactPCI Specification, Rev2.1. PCI
6152 is a Hot Swap friendly device, it contains support for Software Connection Control. The CompactPCI Hot
Swap register block is located at PCI configuration offset E4h. The Hot Swap specification allows active insertion
and extraction by controlling ENUM_L and LED signals.
PCI 6152 has the following Hot Swap related pins:
• ENUM_L: Signal to notify system of insertion/extraction of Hot Swap cards.
• LED: Hot Swap status light
• EJECT: Indicates PCI 6152 of insertion/extraction of Hot Swap card, should be connected
to switch of Hot Swap card.
19.1 Hot Swap Insertion
After reset, PCI 6152 will wait for the EJECT pin to be asserted to indicate successful insertion. It will signal the
host by asserting ENUM_L. The host reads register 92h, to determine if ENUM_L was asserted as a result of a
card insertion. The host will then set bit[7] of the Hot Swap register to acknowledge the insertion. Software drivers
will then perform initialization and deassert ENUM_L after which the PCI 6152 will enter normal operation.
19.2 Hot Swap Extraction
During the extraction phase, user first has to deassert EJECT by toggling the switch on the Hot Swap card.
PCI 6152 will signal the host by asserting ENUM_L. The host will set bit[6] of the configuration register 92h to
acknowledge the extraction. PCI 6152 deasserts ENUM_L, and waits for the extraction. During the extraction
phase, user can optionally cancel the extraction by setting asserting EJECT again.
Note that Hot Swap is an independent section of PCI 6152. Its function has no impact on the rest of the chip. If Hot
Swap feature is not needed, simply leave ENUM_L unconnected.
PCI 6152 Data Book v2.0
2003 PLX Technology, Inc. All rights reserved.82
Page 83
20 Package Specifications
20.1 160-pin Tiny BGA
This specification outlines the mechanical dimensions for 160 pin Tiny BGA package as shown below. All
dimensions are in millimeters (mm).
A
1.4
0.7 0.36
A2
0.27
1.0
C
A1
SIDE VIEW
D
15.0
D1
13.0
e
E
E1
13.0 15.0
b
BOTTOM VIEW
PCI 6152 Data Book v2.0
2003 PLX Technology, Inc. All rights reserved.83
Page 84
The following table lists the package dimensions in millimeters.
SymbolDimensionMinimumNominalMaximum
eBall pitch1.00
AOverall package height1.40
A1Package standoff height0.27
A2Encapsulation thickness0.70
bBall diameter0.350.400.45
CSubstrate thickness0.36
DOverall package width15.00
D1Overall Encapsulation width13.00
EOverall package width15.00
E1Overall Encapsulation width13.00
PCI 6152 Data Book v2.0
2003 PLX Technology, Inc. All rights reserved.84
Page 85
20.2 160-pin Standard PQFP
This specification outlines the mechanical dimensions for 160 pin standard PQFP (plastic quad flat pack) package
as shown below. All dimensions are in millimeters (mm).
PCI 6152 Data Book v2.0
2003 PLX Technology, Inc. All rights reserved.85
Page 86
160-pin PQFP package dimensions
MillimetersSymbol
MinNomMax
A- - 4.45
A10.350.450.65
A23.43.63.8
b0.20.30.4
c0.100.150.25
D31.632.032.4
D127.828.028.2
E31.632.032.4
E127.828.028.2
e0.65 BSC
L0.60.81.0
Zd1.325 TYP
Ze1.325 TYP
θ0°
-
10°
aaa0.1
bbb0.13
N160
PCI 6152 Data Book v2.0
2003 PLX Technology, Inc. All rights reserved.86
Page 87
21 Electrical Specifications
21.1 Maximum Ratings
(Above which the useful life may be impaired. For user guidelines, not tested.)
ParameterMinimumMaximum
Storage Temperature Range-55 °C125 °C
Junction Temperature125 °C
Supply Voltage, V
DD
3.9V
Maximum Voltage to signal pins5.5V
Maximum Power300mW
Note: Stresses greater than those listed under MAXIMUM RATINGS may cause permanent damage to the
device. This is a stress rating only and functional operation of the device at these or any conditions above those
indicated in the operational sections of this specification is not implied. Exposure to absolute maximum rating
conditions for extended periods of time may affect reliability.
21.2 Functional Operating Range
ParameterMinimumMaximum
Supply Voltage3.0 V3.6 V
Operating ambient temperature0 °C70 °C
PCI 6152 Data Book v2.0
2003 PLX Technology, Inc. All rights reserved.87
Page 88
21.3 DC Electrical Characteristics
SymbolParameterConditionMinMaxUnitNotes
V
DD
V
IO
V
ih
V
il
V
ol
V
ol5V
V
oh
V
oh5V
I
il
C
in
Supply Voltage3.03.6V
PVIO, SVIO pin Interface I/O Voltage3.05.5V
Input HIGH Voltage0.5 V
DD
Input LOW Voltage-0.50.3 V
Output LOW Voltage
5V Signalling Output LOW VoltageI
Output HIGH Voltage
5V Signalling Output HIGH VoltageI
Input Leakage Current0 < Vin < V
= 1500 µA
I
iout
= 6 mA0.1 V
iout
= -500 µA
I
iout
= -2 mA2.7V
iout
DD
0.9 V
DD
V
IO
0.1 V
±2
V
DD
DD
DD
V
V
V
V
µA
Input Pin Capacitance10.0pF
PCI 6152 Data Book v2.0
2003 PLX Technology, Inc. All rights reserved.88
Page 89
21.4 PCI Clock Signal AC Parameter Measurements
NOTE: Vt1 - 2.0V for 5V clocks; 0.5VCC for 3.3V clocks
Vt2 - 1.5V for 5V clocks; 0.4VCC for 3.3V clocks
V
– 0.8V for 5V clocks; 0.3VCC for 3.3V clocks
t3
21.4.1 33 MHz PCI Clock Signal AC parameters
SymbolParameterMinimumMaximumUnit
T
cyc
T
high
T
low
T
sclk
T
sclkr
T
sclkf
T
skew
PCLK, SCLK cycle time30ns
PCLK, SCLK high time11-ns
PCLK, SCLK low time11-ns
PCLK, SCLK slew rate14V/ns
Delay from PCLK to SCLK07ns
PCLK rising to SCLKO rising05ns
PCLK falling to SCLKO falling05
SCLKO[x] to SCLKO[y]-0.500ns
PCI 6152 Data Book v2.0
2003 PLX Technology, Inc. All rights reserved.89
Delay from PCLK to SCLK05ns
PCLK rising to SCLKO rising05ns
PCLK falling to SCLKO falling05
SCLKO[x] to SCLKO[y]-0.500ns
21.5 PCI Signal Timing Specification
PCI 6152 Data Book v2.0
2003 PLX Technology, Inc. All rights reserved.90
Page 91
21.5.1 33 MHz PCI Signal Timing
SymbolParameterMinimumMaximumUnit
T
val
CLK to signal valid delay - bused
211ns
signals
T
val(ptp)
CLK to signal valid delay – point
212ns
to point
T
on
T
off
T
su
Float to active delay2-ns
Active to float delay-28ns
Input setup time to CLK – bused
7- ns
signals
T
su(ptp)
Input setup time to CLK – point to
10,12-
point
T
h
Input signal hold time from CLK0-ns
21.5.2 66 MHz PCI Signal Timing
SymbolParameterMinimumMaximumUnit
T
T
T
T
T
T
T
val
val(ptp)
on
off
su
su(ptp)
h
CLK to signal valid delay - bused
26 ns
signals
CLK to signal valid delay – point
26 ns
to point
Float to active delay2-ns
Active to float delay-14ns
Input setup time to CLK – bused
3- ns
signals
Input setup time to CLK – point to
5point
Input signal hold time from CLK0-ns
PCI 6152 Data Book v2.0
2003 PLX Technology, Inc. All rights reserved.91
Page 92
Appendix A: PCI 6152 33PC Part Description
Part number PCI 6152 33PC is a 160 pin PQFP which is designed to be a pin compatible part for Intel 21152
Bridge. Even though it is PCI 6152 33BC internally, some PCI 6152 functions are not available in this
configuration. This section will highlight these features.
internal or external arbitration. PCI 6152 33PC
only supports internal arbitration, so will only
function correctly in designs that do not use an
external arbiter.
102p_lock_lN/CThe PCI 6152 33PC does not support the PCI
lock mechanism on its primary interface.
3
125vddN/CThis is a power pin, and has no effect on
operation.
1
N/C: No Connect.
2,3
In most cases, this will not present a problem, as very few devices implement lock functionality.
PCI 6152 Data Book v2.0
2003 PLX Technology, Inc. All rights reserved.97
Page 98
Appendix B : Sample Schematics
PCI 6152 PCI-to-PCI BRIDGE REFERANCE SCHEMATIC
FUNCTIONAL
DESCRIPTION
PAGE
1.
COVER
2.
PCI 6152 PCI-to-PCI BRIDGE
3.
PCI BUS GOLD FINGER
4.
PCI SLOT 0 and 1
5.
PCI SLOT 2 and 3
6.
PCI SLOT 4
7.
POWER
REVISION HISTORY:
REV. C 2/14/01
U1
1
UP
L1
CHASIS
1
0_F
2
BOT
PCI_BRACKET
ORCAD Capture for Windows - Ver. 9.00.1153
PLX Technology, Inc.
Title
PCI 6152 DEMO BOARD
SizeDocument NumberRev
C
Date:Sheet of
16Wednesday, February 14, 2001
C
PCI 6152 Data Book v2.0
2003 PLX Technology, Inc. All rights reserved.98