Texas Instruments Incorporated and its subsidiaries (TI) reserve the right to make corrections, modifications,
enhancements, improvements, and other changes to its products and services at any time and to discontinue
any product or service without notice. Customers should obtain the latest relevant information before placing
orders and should verify that such information is current and complete. All products are sold subject to TI’s terms
and conditions of sale supplied at the time of order acknowledgment.
TI warrants performance of its hardware products to the specifications applicable at the time of sale in
accordance with TI’s standard warranty. Testing and other quality control techniques are used to the extent TI
deems necessary to support this warranty . Except where mandated by government requirements, testing of all
parameters of each product is not necessarily performed.
TI assumes no liability for applications assistance or customer product design. Customers are responsible for
their products and applications using TI components. To minimize the risks associated with customer products
and applications, customers should provide adequate design and operating safeguards.
TI does not warrant or represent that any license, either express or implied, is granted under any TI patent right,
copyright, mask work right, or other TI intellectual property right relating to any combination, machine, or process
in which TI products or services are used. Information published by TI regarding third-party products or services
does not constitute a license from TI to use such products or services or a warranty or endorsement thereof.
Use of such information may require a license from a third party under the patents or other intellectual property
of the third party, or a license from TI under the patents or other intellectual property of TI.
Reproduction of information in TI data books or data sheets is permissible only if reproduction is without
alteration and is accompanied by all associated warranties, conditions, limitations, and notices. Reproduction
of this information with alteration is an unfair and deceptive business practice. TI is not responsible or liable for
such altered documentation.
Resale of TI products or services with statements different from or beyond the parameters stated by TI for that
product or service voids all express and any implied warranties for the associated TI product or service and
is an unfair and deceptive business practice. TI is not responsible or liable for any such statements.
Following are URLs where you can obtain information on other Texas Instruments products and application
solutions:
ProductsApplications
Amplifiersamplifier.ti.comAudiowww.ti.com/audio
Data Convertersdataconverter.ti.comAutomotivewww.ti.com/automotive
DSPdsp.ti.comBroadbandwww.ti.com/broadband
Interfaceinterface.ti.comDigital Controlwww.ti.com/digitalcontrol
Logiclogic.ti.comMilitarywww.ti.com/military
Power Mgmtpower.ti.comOptical Networkingwww.ti.com/opticalnetwork
Microcontrollersmicrocontroller.ti.comSecuritywww.ti.com/security
Telephonywww.ti.com/telephony
Video & Imagingwww.ti.com/video
Wirelesswww.ti.com/wireless
(LDO-VR) Eliminates the Need for an
External 2.5-V Power Supply
DMix-and-Match 5-V/3.3-V 16-Bit PC Cards
and 3.3-V CardBus Cards
DA Single PC Card or CardBus Slot with Hot
Insertion and Removal
DParallel Interface to TI TPS2211A
Single-Slot PC Card Power Switch
DBurst Transfers to Maximize Data
Throughput with CardBus Cards
DInterrupt Configurations: Parallel PCI,
Serialized PCI, Parallel ISA, and Serialized
ISA
DSerial EEPROM Interface for Loading
Subsystem ID, Subsystem Vendor ID, and
other Configuration Registers
DPipelined Architecture for Greater Than
130-Mbps Throughput from CardBus-to-PCI
and from PCI-to-CardBus
DUp to Five General-Purpose I/Os
DProgrammable Output Select for CLKRUN
DFive PCI Memory Windows and Two I/O
Windows Available for the 16-Bit Interface
DTwo I/O Windows and Two Memory
Windows Available to the CardBus Socket
DExchangeable-Card-Architecture- (ExCA-)
Compatible Registers Are Mapped in
Memory and I/O Space
DIntelE 82365SL-DF and 82365SL Register
Compatible
DRing Indicate, SUSPEND, PCI CLKRUN, and
CardBus CCLKRUN
DSocket Activity LED Terminal
DPCI Bus Lock (LOCK)
DInternal Ring Oscillator
T able 1−1.
Figure 1−1.
MicroStar BGA is a trademark of Texas Instruments.
Other trademarks are the property of their respective owners.
December 2004SCPS114
1
Introduction
2Introduction
The Texas Instruments PCI1510R device, a 144-terminal, 209-terminal, or 253-terminal single-slot CardBus
controller designed to meet the PCI Bus Power Management Interface Specification for PCI to CardBusBridges, is an ultralow-power high-performance PCI-to-CardBus controller that supports a single PC card
socket compliant with the PC Card Standard (rev. 7.2). The controller provides features that make it the best
choice for bridging between PCI and PC Cards in both notebook and desktop computers. The PC CardStandard retains the 16-bit PC Card specification defined in the PCI Local Bus Specification and defines the
32-bit PC Card, CardBus, capable of full 32-bit data transfers at 33 MHz. The controller supports both 16-bit
and CardBus PC Cards, powered at 5 V or 3.3 V, as required.
2.1Controller Functional Description
The controller is compliant with the PCI Local Bus Specification, and its PCI interface can act as either a PCI
master device or a PCI slave device. The PCI bus mastering is initiated during CardBus PC Card bridging
transactions. The controller is also compliant with PCI Bus Power Management Interface Specification (rev.
1.1).
All card signals are internally buffered to allow hot insertion and removal without external buffering. The
controller is register-compatible with the Intel 82365SL-DF and 82365SL ExCA controllers. The controller
internal data path logic allows the host to access 8-, 16-, and 32-bit cards using full 32-bit PCI cycles for
maximum performance. Independent buffering and a pipeline architecture provide an unsurpassed
performance level with sustained bursting. The controller can also be programmed to accept fast posted writes
to improve system-bus utilization.
Multiple system-interrupt signaling options are provided, including parallel PCI, parallel ISA, serialized ISA,
and serialized PCI. Furthermore, general-purpose inputs and outputs are provided for the board designer to
implement sideband functions. Many other features designed into the controller, such as a socket activity
light-emitting diode (LED) outputs, are discussed in detail throughout this document.
An advanced complementary metal-oxide semiconductor (CMOS) process achieves low system power
consumption while operating at PCI clock rates up to 33 MHz. Several low-power modes enable the host
power management system to further reduce power consumption.
2.2Related Documents
•Advanced Configuration and Power Interface (ACPI) Specification (revision 1.1)
•PCI Bus Power Management Interface Specification (revision 1.1)
•PCI Bus Power Management Interface Specification for PCI to CardBus Bridges (revision 0.6)
•PCI to PCMCIA CardBus Bridge Register Description (Yenta) (revision 2.1)
•PCI Local Bus Specification (revision 2.2)
•PCI Mobile Design Guide (revision 1.0)
•PC Card Standard (revision 7.2)
•Serialized IRQ Support for PCI Systems (revision 6)
2.3Trademarks
Intel is a trademark of Intel Corporation.
TI and MicroStar BGA are trademarks of Texas Instruments.
Other trademarks are the property of their respective owners.
2
December 2004SCPS114
2.4Document Conventions
Throughout this data manual, several conventions are used to convey information. These conventions are
listed below:
1. To identify a binary number or field, a lower case b follows the numbers. For example: 000b is a 3-bit binary
field.
2. To identify a hexadecimal number or field, a lower case h follows the numbers. For example: 8AFh is a
12-bit hexadecimal field.
3. All other numbers that appear in this document that do not have either a b or h following the number are
assumed to be decimal format.
Introduction
4. If the signal or terminal name has a bar above the name (for example, GRST
logical NOT function. When asserted, this signal is a logic low, 0, or 0b.
5. RSVD indicates that the referenced item is reserved.
6. In Sections 4 through 6, the configuration space for the controller is defined. For each register bit, the
software access method is identified in an access column. The legend for this access column includes
the following entries:
r – read-only access
ru – read-only access with updates by the controller internal hardware
rw – read and write access
rcu – read access with the option to clear an asserted bit with a write-back of 1b including updates
The PCI1510R controller is available in two 253-terminal MicroStar BGA packages (GVF/ZVF). The GVF
and ZVF packages are mechanically and electrically identical, but the ZVF is a lead-free (Pb, atomic number
82) design. Throughout the remainder of this manual, only the GVF package designator is used for either the
GVF or ZVF package. The terminal layout for the GVF package is shown in Figure 2−1.
Table 2−1 lists the terminal assignments for the GVF package. The signal names for the PC Card slot are given
in a CardBus // 16-bit signal format. Table 2−1 is arranged in order by increasing terminal designator, which
is alphanumeric for this package. Table 2−2 and Table 2−3 list the CardBus and 16-bit signal names,
respectively, in alphanumerical order with the corresponding terminal number for the package.
December 2004SCPS114
3
É
Introduction
GVF PACKAGE
(TOP VIEW)
19
18
17
16
15
14
13
12
11
10
NNNNN
N
NNNNNNNNN
N
NNNNNNNNNNNNNN
NN
NNNNNN
N
NNN
N
NNN
C
NNNN
N
CCC
CC
CC
CC
9
8
7
6
5
C
CC
CC
CC
CC
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
C
CC
T
T
MM
N
N
NNNN
NN
P
P
P
P
P
P
P
P
P
P
P
P
P
N
NNN
P
P
P
P
P
P
P
P
N
N
N
NN
NN
P
P
P
P
P
P
P
P
P
P
P
PP
P
P
4
3
2
C
C
C
1
C
C
CC
CC
CC
C
NNN
C
N
C
N
NNNNNNNN
N
N
NN
N
N
N
N
NN
M
M
T
M
T
M
M
PPP
P
PPPP
PPP
PPPP
ABCDEFGHJKLMNPRTUVW
P
PCI Interface
C
PC Card Interface
T
TPS Power Switch
M
MFUNC Pins
VCC
Ground (GND)
Miscellaneous
N
No Connection
Figure 2−1. PCI1510R GVF Package Terminal Diagram
4
December 2004SCPS114
Table 2−1. Signal Names Sorted by GVF Terminal Number
The terminals are grouped in tables by functionality, such as PCI system function, power-supply function, etc.
The terminal numbers are also listed for convenient reference.
Table 2−4. Power Supply T erminals
TERMINAL
NAMENUMBER
G07, G08, G13,
H13, J09, J10,
GND
V
CC
V
CCCB
V
CCP
VR_ENH02IInternal voltage regulator enable. Active-low
VR_PORTM19
J11, K09, K10,
K11, L08, L09,
L10, L11, L12,
M08
H08, H09, H10,
H11, H12, J08,
J12, K08, K12,
M07, M09, M10,
M12, N07
A05, A11Clamp voltage for PC Card interface. Matches card signaling environment, 5 V or 3.3 V
W03, W10Clamp voltage for PCI and miscellaneous I/O, 5 V or 3.3 V
Device ground terminals
Power supply terminals for I/O and internal voltage regulator
Internal voltage regulator input/output. When VR_EN is low, the regulator is enabled and this
terminal is an output. An external bypass capacitor is required on this terminal. When VR_EN
high, the regulator is disabled and this terminal is an input for an external 2.5 V core power source.
is
TERMINAL
NAMENUMBER
VCCD0
VCCD1
VPPD0
VPPD1
TERMINAL
NAMENUMBER
GRSTT01I
PCLKP05I
PRSTR03I
L06
L05
N02
N01
Table 2−5. PC Card Power Switch T erminals
OLogic controls to the TPS2211A PC Card power interface switch to control AVCC
OLogic controls to the TPS2211A PC Card power interface switch to control AVPP
Table 2−6. PCI System T erminals
Global reset. When the global reset is asserted, the GRST signal causes the controller to place all output
buffers in a high-impedance state and reset all internal registers. When GRST
completely in its default state. For systems that require wake-up from D3, GRST
during initial boot. PRST
transition from D3 to D0.
When the SUSPEND
preserved. All outputs are placed in a high-impedance state.
PCI bus clock. PCLK provides timing for all transactions on the PCI bus. All PCI signals are sampled at the
rising edge of PCLK.
PCI bus reset. When the PCI bus reset is asserted, PRST causes the controller to place all output buffers in
a high-impedance state and reset internal registers. When PRST
signal only if it is enabled. After PRST is deasserted, the controller is in a default state.
PME
When the SUSPEND
preserved. All outputs are placed in a high-impedance state.
must be asserted following initial boot so that PME context is retained during the
mode is enabled, the device is protected from GRST, and the internal registers are
is asserted, the device can generate the
mode is enabled, the device is protected from PRST, and the internal registers are
PCI address/data bus. These signals make up the multiplexed PCI address and data bus on the primary
interface. During the address phase of a primary-bus PCI cycle, AD31–AD0 contain a 32-bit address or
I/O
other destination information. During the data phase, AD31–AD0 contain data.
PCI-bus commands and byte enables. These signals are multiplexed on the same PCI terminals. During the
address phase of a primary-bus PCI cycle, C/BE3
this 4-bit bus is used as a byte enable. The byte enable determines which byte paths of the full 32-bit data
I/O
bus carry meaningful data. C/BE0 applies to byte 0 (AD7–AD0), C/BE1 applies to byte 1 (AD15–AD8),
C/BE2
applies to byte 2 (AD23–AD16), and C/BE3 applies to byte 3 (AD31–AD24).
PCI-bus parity. In all PCI-bus read and write cycles, the controller calculates even parity across the
AD31–AD0 and C/BE3
indicator with a one-PCLK delay. As a target during PCI cycles, the controller compares its calculated parity
to the parity indicator of the initiator. A compare error results in the assertion of a parity error (PERR).
–C/BE0 buses. As an initiator during PCI cycles, the controller outputs this parity
–C/BE0 define the bus command. During the data phase,
Introduction
December 2004SCPS114
11
Introduction
I/O
DESCRIPTION
Table 2−8. PCI Interface Control Terminals
TERMINAL
NAMENUMBER
PCI device select. The controller asserts DEVSEL to claim a PCI cycle as the target device. As a PCI initiator
DEVSELN08I/O
FRAMEV07I/O
GNTT02I
IDSELW05I
IRDYU07I/O
PERRV08I/O
REQU01OPCI bus request. REQ is asserted by the controller to request access to the PCI bus as an initiator.
SERRU08O
STOPW08I/O
TRDYR08I/O
on the bus, the controller monitors DEVSEL
occurs, then the controller terminates the cycle with an initiator abort.
PCI cycle frame. FRAME is driven by the initiator of a bus cycle. FRAME is asserted to indicate that a bus
transaction is beginning, and data transfers continue while this signal is asserted. When FRAME
deasserted, the PCI bus transaction is in the final data phase.
PCI bus grant. GNT is driven by the PCI bus arbiter to grant the controller access to the PCI bus after the
current data transaction has completed. GNT
PCI bus parking algorithm.
Initialization device select. IDSEL selects the controller during configuration space accesses. IDSEL can be
connected to one of the upper 24 PCI address lines on the PCI bus.
PCI initiator ready. IRDY indicates the ability of the PCI bus initiator to complete the current data phase of
the transaction. A data phase is completed on a rising edge of PCLK where both IRDY
asserted. Until IRDY
PCI parity error indicator. PERR is driven by a PCI device to indicate that calculated parity does not match
PAR when PERR
PCI system error. SERR is an output that is pulsed from the controller when enabled through bit 8 of the
command register (PCI offset 04h, see Section 4.4) indicating a system error has occurred. The controller
need not be the target of the PCI cycle to assert this signal. When SERR is enabled in the command register ,
this signal also pulses, indicating that an address parity error has occurred on a CardBus interface.
PCI cycle stop signal. STOP is driven by a PCI target to request the initiator to stop the current PCI bus
transaction. STOP
support burst data transfers.
PCI target ready. TRDY indicates the ability of the primary bus target to complete the current data phase of
the transaction. A data phase is completed on a rising edge of PCLK when both IRDY
Until both IRDY
and TRDY are both sampled asserted, wait states are inserted.
is enabled through bit 6 of the command register (PCI offset 04h, see Section 4.4).
is used for target disconnects and is commonly asserted by target devices that do not
and TRDY are asserted, wait states are inserted.
until a target responds. If no target responds before timeout
may or may not follow a PCI bus request, depending on the
and TRDY are
and TRDY are asserted.
is
12
December 2004SCPS114
Table 2−9. Multifunction and Miscellaneous Terminals
I/O
DESCRIPTION
TERMINAL
NAMENUMBER
MFUNC0N03I/O
MFUNC1M05I/O
MFUNC2P01I/O
MFUNC3/
IRQSER
MFUNC4P03I/O
MFUNC5N05I/O
MFUNC6/
CLKRUN
RI_OUT / PMET03O
SPKROUTL07O
SUSPENDR02I
P02I/O
R01I/O
Introduction
Multifunction terminal 0. MFUNC0 can be configured as parallel PCI interrupt INTA, GPI0, GPO0,
socket activity LED output, ZV switching output, CardBus audio PWM, GPE
Section 4.30, Multifunction Routing Register, for configuration details.
Multifunction terminal 1. MFUNC1 can be configured as GPI1, GPO1, socket activity LED output,
D3_STAT
Multifunction Routing Register, for configuration details.
Serial data (SDA). When VCCD0 and VCCD1 are detected high after a global reset, the MFUNC1
terminal provides the SDA signaling for the serial bus interface. The two-terminal serial interface loads
the subsystem identification and other register defaults from an EEPROM after a global reset. See
Section 3.6.1, Serial Bus Interface Implementation, for details on other serial bus applications.
Multifunction terminal 2. MFUNC2 can be configured as GPI2, GPO2, socket activity LED output, ZV
switching output, CardBus audio PWM, GPE
Multifunction Routing Register, for configuration details.
Multifunction terminal 3. MFUNC3 can be configured as a parallel IRQ or the serialized interrupt signal
IRQSER. This terminal is IRQSER by default. See Section 4.30, Multifunction Routing Register, for
configuration details.
Multifunction terminal 4. MFUNC4 can be configured as PCI LOCK, GPI3, GPO3, socket activity LED
output, ZV switching output, CardBus audio PWM, GPE
Section 4.30, Multifunction Routing Register, for configuration details.
Serial clock (SCL). When VCCD0
terminal provides the SCL signaling for the serial bus interface. The two-terminal serial interface loads
the subsystem identification and other register defaults from an EEPROM after a global reset. See
Section 3.6.1, Serial Bus Interface Implementation, for details on other serial bus applications.
Multifunction terminal 5. MFUNC5 can be configured as GPI4, GPO4, socket activity LED output, ZV
switching output, CardBus audio PWM, D3_STAT
Multifunction Routing Register, for configuration details.
Multifunction terminal 6. MFUNC6 can be configured as a PCI CLKRUN or a parallel IRQ. See
Section 4.30, Multifunction Routing Register, for configuration details.
Ring indicate out and power management event output. Terminal provides an output for ring- indicate
or PME
Speaker output. SPKROUT is the output to the host system that can carry SPKR or CAUDIO through
the controller from the PC Card interface. SPKROUT is driven as the exclusive-OR combination of card
SPKR//CAUDIO inputs.
Suspend. SUSPEND protects the internal registers from clearing when the GRST or PRST signal is
asserted. See Section 3.8.5, Suspend Mode, for details.
, ZV switching output, CardBus audio PWM, GPE, or a parallel IRQ. See Section 4.30,
, RI_OUT, D3_ST AT, or a parallel IRQ. See Section 4.30,
, D3_STAT, RI_OUT, or a parallel IRQ. See
and VCCD1 are detected high after a global reset, the MFUNC4
Table 2−10. 16-Bit PC Card Address and Data Terminals
OPC Card address. 16-bit PC Card address lines. A25 is the most significant bit.
I/OPC Card data. 16-bit PC Card data lines. D15 is the most significant bit.
14
December 2004SCPS114
TERMINAL
I/O
DESCRIPTION
NAMENUMBER
BVD1
(STSCHG
BVD2(SPKR)A02
CD1
CD2
CE1
CE2
INPACKE07
IORDC11
IOWRE11
OEC12
READY
(IREQ
REGC05
RESETA06
VS1
VS2
WAITB03
/RI)
)
B02
C15
E05
G12
B12
C04
A03
E08
Table 2−11. 16-Bit PC Card Interface Control Terminals
Battery voltage detect 1. BVD1 is generated by 16-bit memory PC Cards that include batteries. BVD1
is used with BVD2 as an indication of the condition of the batteries on a memory PC Card. Both BVD1
and BVD2 are high when the battery is good. When BVD2 is low and BVD1 is high, the battery is weak
and must be replaced. When BVD1 is low, the battery is no longer serviceable and the data in the
memory PC Card is lost. See Section 5.6, ExCA Card Status-Change Interrupt Configuration Register,
I
for enable bits. See Section 5.5, ExCA Card Status-Change Register, and Section 5.2, ExCA InterfaceStatus Register, for the status bits for this signal.
Status change. STSCHG
battery voltage dead condition of a 16-bit I/O PC Card.
Ring indicate. RI
Battery voltage detect 2. BVD2 is generated by 16-bit memory PC Cards that include batteries. BVD2
is used with BVD1 as an indication of the condition of the batteries on a memory PC Card. Both BVD1
and BVD2 are high when the battery is good. When BVD2 is low and BVD1 is high, the battery is weak
and must be replaced. When BVD1 is low, the battery is no longer serviceable and the data in the
memory PC Card is lost. See Section 5.6, ExCA Card Status-Change Interrupt Configuration Register,
I
for enable bits. See Section 5.5, ExCA Card Status-Change Register, and Section 5.2, ExCA InterfaceStatus Register, for the status bits for this signal.
Speaker. SPKR
configured for the 16-bit I/O interface.
Card detect 1 and card detect 2. CD1 and CD2 are internally connected to ground on the PC Card.
I
When a PC Card is inserted into a socket, CD1
Section 5.2, ExCA Interface Status Register.
Card enable 1 and card enable 2. CE1 and CE2 enable even- and odd-numbered address bytes. CE1
O
enables even-numbered address bytes, and CE2 enables odd-numbered address bytes.
Input acknowledge. INPACK is asserted by the PC Card when it can respond to an I/O read cycle at
I
the current address.
I/O read. IORD is asserted by the controller to enable 16-bit I/O PC Card data output during host I/O
O
read cycles.
I/O write. IOWR is driven low by the controller to strobe write data into 16-bit I/O PC Cards during host
O
I/O write cycles.
Output enable. OE is driven low by the controller to enable 16-bit memory PC Card data output during
O
host memory read cycles.
Ready. The ready function is provided by READY when the 16-bit PC Card and the host socket are
configured for the memory-only interface. READY is driven low by the 16-bit memory PC Cards to
indicate that the memory card circuits are busy processing a previous write command. READY is
driven high when the 16-bit memory PC Card is ready to accept a new data transfer command.
I
Interrupt request. IREQ
16-bit I/O PC Card requires service by the host software. IREQ
is requested.
Attribute memory select. REG remains high for all common memory accesses. When REG is
asserted, access is limited to attribute memory (OE
O
O
I/O
I
active). Attribute memory is a separately accessed section of card memory and is generally
IOWR
used to record card capacity and other configuration and attribute information.
PC Card reset. RESET forces a hard reset to a 16-bit PC Card.
Voltage sense 1 and voltage sense 2. VS1 and VS2, when used in conjunction with each other,
determine the operating voltage of the PC Card.
Bus cycle wait. WAIT is driven by a 16-bit PC Card to extend the completion of the memory or I/O in
progress.
is used by 16-bit modem cards to indicate a ring detection.
is an optional binary audio signal available only when the card and socket have been
is used to alert the system to a change in the READY, write protect, or
and CD2 are pulled low. For signal status, see
is asserted by a 16-bit I/O PC Card to indicate to the host that a device on the
is high (deasserted) when no interrupt
or WE active) and to the I/O space (IORD or
Introduction
December 2004SCPS114
15
Introduction
I/O
DESCRIPTION
I/O
DESCRIPTION
Table 2−11. 16-Bit PC Card Interface Control Terminals (Continued)
TERMINAL
NAMENUMBER
WEB09O
WP
(IOIS16
)
TERMINAL
NAMENUMBER
CCLKE09O
CCLKRUNC03I/O
CRSTA06O
C03I
Write enable. WE is used to strobe memory write data into 16-bit memory PC Cards. WE is also used for
memory PC Cards that employ programmable memory technologies.
Write protect. WP applies to 16-bit memory PC Cards. WP reflects the status of the write-protect switch on
16-bit memory PC Cards. For 16-bit I/O cards, WP is used for the 16-bit port (IOIS16
I/O is 16 bits. IOIS16
address on the bus corresponds to an address to which the 16-bit PC Card responds, and the I/O port
that is addressed is capable of 16-bit accesses.
applies to 16-bit I/O PC Cards. IOIS16 is asserted by the 16-bit PC Card when the
) function.
Table 2−12. CardBus PC Card Interface System Terminals
CardBus clock. CCLK provides synchronous timing for all transactions on the CardBus interface. All
signals except CRST
sampled on the rising edge of CCLK, and all timing parameters are defined with the rising edge of this
signal. CCLK operates at the PCI bus clock frequency, but it can be stopped in the low state or slowed
down for power savings.
CardBus clock run. CCLKRUN is used by a CardBus PC Card to request an increase in the CCLK
frequency, and by the controller to indicate that the CCLK frequency is going to be decreased.
CardBus reset. CRST brings CardBus PC Card-specific registers, sequencers, and signals to a known
state. When CRST
the controller drives these signals to a valid logic level. Assertion can be asynchronous to CCLK, but
deassertion must be synchronous to CCLK.
, CCLKRUN, CINT, CSTSCHG, CAUDIO, CCD2, CCD1, CVS2, and CVS1 are
is asserted, all CardBus PC Card signals are placed in a high-impedance state, and
Table 2−13. CardBus PC Card Address and Data Terminals
CardBus address and data. These signals make up the multiplexed CardBus address and data bus on the
CardBus interface. During the address phase of a CardBus cycle, CAD31–CAD0 contain a 32-bit address.
During the data phase of a CardBus cycle, CAD31–CAD0 contain data. CAD31 is the most significant bit.
CardBus bus commands and byte enables. CC/BE3–CC/BE0 are multiplexed on the same CardBus
terminals. During the address phase of a CardBus cycle, CC/BE3
During the data phase, this 4-bit bus is used as a byte enable. The byte enable determines which byte
paths of the full 32-bit data bus carry meaningful data. CC/BE0 applies to byte 0 (CAD7–CAD0), CC/BE1
applies to byte 1 (CAD15–CAD8), CC/BE2 applies to byte 2 (CAD23–CAD16), and CC/BE3 applies to byte
(CAD31–CAD24).
CardBus parity. In all CardBus read and write cycles, the controller calculates even parity across the CAD
and CC/BE
delay. As a target during CardBus cycles, the controller compares its calculated parity to the parity indicator
of the initiator; a compare error results in a parity error assertion.
buses. As an initiator during CardBus cycles, the controller outputs CPAR with a one-CCLK
–CC/BE0 define the bus command.
December 2004SCPS114
17
Introduction
I/O
DESCRIPTION
Table 2−14. CardBus PC Card Interface Control Terminals
TERMINAL
NAMENUMBER
CAUDIOA02I
CBLOCKE10I/OCardBus lock. CBLOCK is used to gain exclusive access to a target.
CCD1
CCD2
CDEVSELC09I/O
CFRAMEC08I/O
CGNTB09O
CINTC04I
CIRDYB08I/O
CPERRF10I/O
CREQE07I
CSERRB03I
CSTOPA09I/O
CSTSCHGB02I
CTRDYA08I/O
CVS1
CVS2
C15
E05
A03
E08
CardBus audio. CAUDIO is a digital input signal from a PC Card to the system speaker. The controller
supports the binary audio mode and outputs a binary signal from the card to SPKROUT.
CardBus detect 1 and CardBus detect 2. CCD1 and CCD2 are used in conjunction with CVS1 and CVS2
I
to identify card insertion and interrogate cards to determine the operating voltage and card type.
CardBus device select. The controller asserts CDEVSEL to claim a CardBus cycle as the target device.
As a CardBus initiator on the bus, the controller monitors CDEVSEL
responds before timeout occurs, then the controller terminates the cycle with an initiator abort.
CardBus cycle frame. CFRAME is driven by the initiator of a CardBus bus cycle. CFRAME is asserted to
indicate that a bus transaction is beginning, and data transfers continue while this signal is asserted.
When CFRAME
CardBus bus grant. CGNT is driven by the controller to grant a CardBus PC Card access to the CardBus
bus after the current data transaction has been completed.
CardBus interrupt. CINT is asserted low by a CardBus PC Card to request interrupt servicing from the
host.
CardBus initiator ready. CIRDY indicates the ability of the CardBus initiator to complete the current data
phase of the transaction. A data phase is completed on a rising edge of CCLK when both CIRDY
CTRDY
CardBus parity error. CPERR reports parity errors during CardBus transactions, except during special
cycles. It is driven low by a target two clocks following the data cycle during which a parity error is
detected.
CardBus request. CREQ indicates to the arbiter that the CardBus PC Card desires use of the CardBus
bus as an initiator.
CardBus system error. CSERR reports address parity errors and other system errors that could lead to
catastrophic results. CSERR
pullup; deassertion may take several CCLK periods. The controller can report CSERR
assertion of SERR
CardBus stop. CSTOP is driven by a CardBus target to request the initiator to stop the current CardBus
transaction. CSTOP
not support burst data transfers.
CardBus status change. CSTSCHG alerts the system to a change in the card status, and is used as a
wake-up mechanism.
CardBus target ready. CTRDY indicates the ability of the CardBus target to complete the current data
phase of the transaction. A data phase is completed on a rising edge of CCLK, when both CIRDY
CTRDY
CardBus voltage sense 1 and CardBus voltage sense 2. CVS1 and CVS2 are used in conjunction with
CCD1
I/O
and CCD2 to identify card insertion and interrogate cards to determine the operating voltage and
card type.
is deasserted, the CardBus bus transaction is in the final data phase.
are asserted. Until CIRDY and CTRDY are both sampled asserted, wait states are inserted.
is driven by the card synchronous to CCLK, but deasserted by a weak
on the PCI interface.
is used for target disconnects, and is commonly asserted by target devices that do
are asserted; until this time, wait states are inserted.
until a target responds. If no target
and
to the system by
and
18
December 2004SCPS114
3Principles of Operation
The following sections give an overview of the PCI1510R controller. Figure 3−1 shows a simplified block
diagram of the controller. The PCI interface includes all address/data and control signals for PCI protocol. The
interrupt interface includes terminals for parallel PCI, parallel ISA, and serialized PCI and ISA signaling.
Miscellaneous system interface terminals include multifunction terminals: SUSPEND
management control signal), and SPKROUT.
PCI Bus
Activity LED
Principles of Operation
, RI_OUT/PME (power
INTA
Interrupt
Controller
TPS2211A
Power
Switch
PC Card
Socket
External ZV Port
NOTE: The PC Card interface is 68 terminals for CardBus and 16-bit PC Cards. In ZV mode, 23 terminals are used for routing the ZV signals
to the VGA controller and audio subsystem.
4
PCI1510R
68
23
IRQSER
3
Multiplexer
PCI950
IRQSER
Deserializer
Zoomed Video
19
Zoomed Video
4
IRQ2−15
VGA
Controller
Audio
Subsystem
Figure 3−1. PCI1510R Simplified Block Diagram
3.1Power Supply Sequencing
The controller contains 3.3-V I/O buffers with 5-V tolerance requiring an I/O power supply and an LDO-VR
power supply for core logic. The core power supply, which is always 2.5 V, can be supplied through the
VR_PORT terminal (when VR_EN
supply via the V
terminals. The clamping voltages (V
CC
on the interface. The following power-up and power-down sequences are recommended.
is high) or from the integrated LDO-VR. The LDO-VR needs a 3.3-V power
CCCB
and V
) can be either 3.3 V or 5 V , depending
CCP
The power-up sequence is:
1. Assert GRST
to the device to disable the outputs during power up. Output drivers must be powered up
in the high-impedance state to prevent high current levels through the clamp diodes to the 5-V clamping
rails (V
2. Apply 3.3-V power to V
CCCB
and V
CCP
).
CC
.
3. Apply the clamp voltage.
December 2004SCPS114
19
Principles of Operation
The power-down sequence is:
1. Assert GRST
to the device to disable the outputs during power down. Output drivers must be powered
down in the high-impedance state to prevent high current levels through the clamp diodes to the 5-V
clamping rails (V
CCCB
2. Remove the clamp voltage.
3. Remove the 3.3-V power from V
NOTE: The clamp voltage can be ramped up or ramped down along with the 3.3-V power. The
voltage difference between V
3.2I/O Characteristics
Figure 3−2 shows a 3-state bidirectional buffer. Section 7.2, Recommended Operating Conditions, provides
the electrical characteristics of the inputs and outputs.
NOTE: The controller meets the ac specifications of the PC Card Standard and PCI Local Bus
Specification.
and V
Tied for Open Drain
).
CCP
.
CC
and the clamp voltage must remain within 3.6 V.
CC
V
CCP
OE
Pad
Figure 3−2. 3-State Bidirectional Buffer
NOTE: Unused terminals (input or I/O) must be held high or low to prevent them from floating.
3.3Clamping Voltages
The clamping voltages are set to match whatever external environment the controller is interfaced with, 3.3 V
or 5 V. The I/O sites can be pulled through a clamping diode to a voltage rail that protects the core from external
signals. The core power supply is always 3.3 V and is independent of the clamping voltages. For example,
PCI signaling can be either 3.3 V or 5 V, and the controller must reliably accommodate both voltage levels.
This is accomplished by using a 3.3-V I/O buffer that is 5-V tolerant, with the applicable clamping voltage
applied. If a system designer desires a 5-V PCI bus, then V
can be connected to a 5-V power supply.
CCP
The controller requires three separate clamping voltages because it supports a wide range of features. The
three voltages are listed and defined in Section 7.2, Recommended Operating Conditions. GRST
PME
The controller is fully compliant with the PCI Local Bus Specification. The controller provides all required
signals for PCI master or slave operation, and may operate in either a 5-V or 3.3-V signaling environment by
connecting the V
controller provides the optional interrupt signal INTA
terminal to the desired voltage level. In addition to the mandatory PCI signals, the
CCP
.
3.4.1 PCI GRST Signal
During the power-up sequence, GRST and PRST must be asserted. GRST can only be deasserted 100 µs
after PCLK is stable. PRST
can be deasserted at the same time as GRST or any time thereafter.
, SUSPEND,
20
December 2004SCPS114
3.4.2 PCI Bus Lock (LOCK)
The bus-locking protocol defined in the PCI Local Bus Specification is not highly recommended, but is
provided on the controller as an additional compatibility feature. The PCI LOCK
MFUNC4 terminal by setting the appropriate values in bits 19−16 of the multifunction routing register. See
Section 4.30, Multifunction Routing Register,
PCI-to-CardBus bridges in the downstream direction (away from the processor).
PCI LOCK indicates an atomic operation that may require multiple transactions to complete. When LOCK is
asserted, nonexclusive transactions can proceed to an address that is not currently locked. A grant to start
a transaction on the PCI bus does not guarantee control of LOCK
protocol. It is possible for different initiators to use the PCI bus while a single master retains ownership of
LOCK
. Note that the CardBus signal for this protocol is CBLOCK to avoid confusion with the bus clock.
An agent may need to do an exclusive operation because a critical access to memory might be broken into
several transactions, but the master wants exclusive rights to a region of memory . The granularity of the lock
is defined by PCI to be 16 bytes, aligned. The LOCK
a resource lock without interfering with nonexclusive real-time data transfer, such as video.
Principles of Operation
signal can be routed to the
for details. Note that the use of LOCK is only supported by
; control of LOCK is obtained under its own
protocol defined by the PCI Local Bus Specification allows
The PCI bus arbiter may be designed to support only complete bus locks using the LOCK
scenario, the arbiter does not grant the bus to any other agent (other than the LOCK
asserted. A complete bus lock may have a significant impact on the performance of the video. The arbiter that
supports complete bus lock must grant the bus to the cache to perform a writeback due to a snoop to a modified
line when a locked operation is in progress.
The controller supports all LOCK
protocol associated with PCI-to-PCI bridges, as also defined for
PCI-to-CardBus bridges. This includes disabling write posting while a locked operation is in progress, which
can solve a potential deadlock when using devices such as PCI-to-PCI bridges. The potential deadlock can
occur if a CardBus target supports delayed transactions and blocks access to the target until it completes a
delayed read. This target characteristic is prohibited by the PCI Local Bus Specification, and the issue is
resolved by the PCI master using LOCK
.
3.4.3 Loading Subsystem Identification
The subsystem vendor ID register (PCI offset 40h, see Section 4.26) and subsystem ID register (PCI offset
42h, see Section 4.27) make up a doubleword of PCI configuration space for function 0. This doubleword
register is used for system and option card (mobile dock) identification purposes and is required by some
operating systems. Implementation of this unique identifier register is a PC 99/PC 2001 requirement.
The controller offers two mechanisms to load a read-only value into the subsystem registers. The first
mechanism relies upon the system BIOS providing the subsystem ID value. The default access mode to the
subsystem registers is read-only, but can be made read/write by clearing bit 5 (SUBSYSRW) in the system
control register (PCI offset 80h, see Section 4.29). Once this bit is cleared, the BIOS can write a subsystem
identification value into the registers at PCI offset 40h. The BIOS must set the SUBSYSRW bit such that the
subsystem vendor ID register and subsystem ID register is limited to read-only access. This approach saves
the added cost of implementing the serial electrically erasable programmable ROM (EEPROM).
protocol. In this
master) while LOCK is
In some conditions, such as in a docking environment, the subsystem vendor ID register and subsystem ID
register must be loaded with a unique identifier via a serial EEPROM. The controller loads the data from the
serial EEPROM after a reset of the primary bus. Note that the SUSPEND
input gates the PCI reset from the
entire controller core, including the serial-bus state machine (see Section 3.8.5, Suspend Mode, for details
on using SUSPEND
).
The controller provides a two-line serial-bus host controller that can interface to a serial EEPROM. See
Section 3.6, Serial-Bus Interface,for details on the two-wire serial-bus controller and applications.
December 2004SCPS114
21
Principles of Operation
3.5PC Card Applications
This section describes the PC Card interfaces of the controller.
•Card insertion/removal and recognition
•Zoomed video support
•Speaker and audio applications
•LED socket activity indicators
•CardBus socket registers
3.5.1 PC Card Insertion/Removal and Recognition
The PC Card Standard (release 7.2) addresses the card-detection and recognition process through an
interrogation procedure that the socket must initiate on card insertion into a cold, nonpowered socket. Through
this interrogation, card voltage requirements and interface (16-bit versus CardBus) are determined.
The scheme uses the card-detect and voltage-sense signals. The configuration of these four terminals
identifies the card type and voltage requirements of the PC Card interface. The encoding scheme is defined
in the PC Card Standard (release 7.2) and in Table 3−1.
Table 3−1. PC Card Card-Detect and Voltage-Sense Connections
GroundGroundOpenOpen5 V16-bit PC Card5 V
GroundGroundOpenGround5 V16-bit PC Card5 V and 3.3 V
GroundGroundGroundGround5 V16-bit PC Card5 V, 3.3 V, and X.X V
GroundGroundOpenGroundLV16-bit PC Card3.3 V
GroundConnect to CVS1OpenConnect to CCD1LVCardBus PC Card3.3 V
GroundGroundGroundGroundLV16-bit PC Card3.3 V and X.X V
Connect to CVS2GroundConnect to CCD2GroundLVCardBus PC Card3.3 V and X.X V
Connect to CVS1GroundGroundConnect to CCD2LVCardBus PC Card3.3 V, X.X V, and Y.Y V
GroundGroundGroundOpenLV16-bit PC CardX.X V
Connect to CVS2GroundConnect to CCD2OpenLVCardBus PC CardX.X V
GroundConnect to CVS2Connect to CCD1OpenLVCardBus PC CardX.X V and Y.Y V
Connect to CVS1GroundOpenConnect to CCD2LVCardBus PC CardY.Y V
GroundConnect to CVS1GroundConnect to CCD1Reserved
GroundConnect to CVS2Connect to CCD1GroundReserved
3.5.2 Parallel Power-Switch Interface (TPS2211A)
The controller provides a parallel interface for control of the PC Card power switch. The VCCD and VPPD
terminals are used with the TI TPS2211A single-slot PC Card power-switch interface to provide power-switch
support. Figure 3−3 illustrates a typical application, where the controller represents the PC Card controller.
22
December 2004SCPS114
Loading...
+ 81 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.