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
Low Power Wireless www.ti.com/lpwTelephonywww.ti.com/telephony
Video & Imagingwww.ti.com/video
Wirelesswww.ti.com/wireless
The TI PCI2040 is a PCI-DSP bridge that provides a glueless connection between the 8-bit host port interface (HPI)
port on the TMS320C54X or the 16-bit HPI port on TMS320C6X to the high performance PCI bus. It provides a PCI
bus target interface compliant with the PCI Local Bus Specification.
The PCI2040 provides several external interfaces: the PCI bus interface with compact PCI support, the HPI port
interface with support for up to four DSPs, a serial ROM interface, a general-purpose input/output interface (GPIOs),
and a 16-bit general-purpose bus to provide a glueless interface to TI JTAG test bus controller (TBC). The PCI2040
universal target-only PCI interface is compatible with 3.3-V or 5-V signaling environments.
The PCI2040 interfaces with DSPs via a data bus (HPI port). The PCI2040 also provides a serial ROM interface for
preloading several registers including the subsystem ID and subsystem vendor ID.
The PCI2040, compliant with the latest PCI Bus Power Management Interface Specification, provides several
low-power features that reduce power consumption. Furthermore, an advanced CMOS process achieves low system
power consumption.
Unused PCI2040 inputs must be pulled to a valid logic level using a pullup resistor.
1.2Features
The PCI2040 supports the following features:
•PCI bus target only, supporting both single-word reads and writes
•Write transaction posting for improved PCI bus performance
•Provides glueless interface to host port interface (HPI) port of C54x and/or C6x
•Up to four DSP devices on HPI
•Allows direct access to program and control external devices connected to PCI2040
•Serial ROM interface for loading subsystem ID and subsystem vendor ID
•A 16-bit general-purpose bus (GPB) that provides glueless interface to TI JTAG TBC
•3.3-V core logic with universal PCI interface compatible with 3.3-V or 5-V signaling environments
•Advanced submicron, low-power CMOS technology
•144-pin device and choice of surface mount packaging: TQFP or 12 mm x 12 mm MicroStar BGA
•Up to 33 MHz PCI bus frequency
1.3Related Documents
•Compact PCI Hot Swap Specification PICMG 2.1 (Revision 1.0)
•PCI Bus Power Management Interface Specification (Revision 1.1)
Global reset. This is a power-on reset to PCI2040 that indicates that a power has been applied to
the VCC terminals. GRST
Power management event. This output indicates PCI power management wake-up events to the
host, and requires open-drain, fail-safe signaling per the PCI Bus Power Management InterfaceSpecification.
General-purpose inputs/output. With some exceptions, these terminals provide basic generalpurpose input and output functionality programmable through the PCI2040.
The GPIO3 and GPIO2 inputs may be programmed to generate generic interrupt events. See
Section 3.7.4, General-Purpose Interrupts, for details.
GPIO0 is sampled on GRST
I/O
on GRST
ROM data line (SDA) is routed to the GPIO1 terminal.
GPIO4. GP write strobe. This active low signal is used to indicate a read from a device on the bus.
The data on the bus is valid on the rising edge of WR
GPIO5. GP read strobe. This active low signal is used to indicate a write to a device on the bus. The
data on the bus is valid on the rising edge of RD
NCReserved. These terminals are not connected in PCI2040 implementations.
assertions, then the serial ROM clock (SCL) is routed to the GPIO0 terminal and the serial
resets all register bits in PCI2040.
to determine if a serial ROM is implemented. If GPIO0 is sampled high
Data. A 16-bit parallel, bidirectional, and 3-state data bus used to access registers on external
I/O
devices controlled by PCI2040. HAD15 is MSB and HAD0 is LSB.
Read/Write. The PCI2040 drives this signal to 0 on a host port interface for a write and to 1
on a host port interface for a read.
Read strobe/data strobe. Active low signal that controls the transfer of data during an HPI
cycle, and indicates to the DSP that the data on HAD15−HAD0 is valid. This signal must be
connected to HDS1 or HDS2 on the DSP. Unused DSP HDSx inputs must be tied high.
HPI Interrupts. These four interrupts from the DSPs are connected point-to-point between
PCI2040 and each implemented DSP. The PCI2040 may be programmed to assert a PCI
interrupt when the DSPs assert any HINT3−HINT0. From the DSP perspective, these signals
I
are controlled by the HINT bit in the HPI control register and are driven high when the DSPs
are being reset (and placed in high impedance when EMU1/OFF
Byte enables. These active low signals are only used when communicating with the C6x DSP.
They indicate which bytes of the data bus are valid when writing to the C6x HPI data register
O
and are not meaningful in any other conditions.
Half-word identification select. Identifies first or second half-word of transfer. HWIL is low for
the first half-word and high for the second half-word. This is not to be confused with the BOB
bit in the DSP HPI control register which controls MSB/LSB from the DSP perspective.
Control signals for DSP access mode. Selects an access to DSP HPI address register, HPI
control register, or HPI data register (and controls auto-increment). The HCNTL1 and HCNTL0
O
combinations are different for C54x and C6x DSPs.
Chip selects. These four chip selects to the DSPs are connected point-to-point between
PCI2040 and each implemented DSP. The input to the DSP serves as an enable input for the
O
HPI and must be low during an access and may stay low between accesses.
Host ready signals. These ready signals from the DSPs are connected point-to-point between
C8
D8
A9
B9
D9
PCI2040 and each implemented DSP. This ready signal is active high for C54x DSPs and
active low for C6x DSPs. When asserted, it indicates that the DSP is ready for a transfer to
be performed, and is deasserted when the DSP is busy completing the internal portion of the
I
previous transaction. HCS
the chip selects are deasserted. The DSP places this ready signal in high impedance when
EMU1/OFF
Host-to-DSP resets. These active low reset signals to the DSPs are connected point-to-point
between PCI2040 and each implemented DSP. The PCI2040 resets the DSPs when GRST
O
is asserted. It is software’s responsibility to deassert HRSTn.
is active (low).
enables HRDY for the DSP; that is, HRDY is always asserted when
is asserted).
2−7
Table 2−7. Compact PCI Hot Swap Interface
NAME
I/O
DESCRIPTION
NAME
I/O
DESCRIPTION
TERMINAL
HSENUM
HSLED
HSSWITCH
NO.
PGE GGU
71N12O
72M12O
73N13I
I/ODESCRIPTION
Hot swap ENUM. This is an active low open drain signaling output that is asserted when either bit 7 (INS)
or bit 6 (EXT) are set and bit 1 (EIM) is cleared in the CPCI hot swap control and status register (see
Section 4.35). This output indicates to the system that an insertion event occurred or that a removal event
is about to occur.
Hot swap LED. This output is controlled via bit 3 (LOO) in the CPCI hot swap control and status register
(see Section 4.35) and is provided to indicate when a hot-swap device is about to be removed. When
PCI_RST
and the ejector switch has been closed indicated by the HSSWITCH input.
Hot swap handle switch. This input provides status of the ejector handle state and is used in the bit 7 (INS)
and bit 6 (EXT) logic in the CPCI hot swap control and status register (see Section 4.35). The status of
HSSWITCH is not directly read via CPCI hot swap control and status register but can be read through bit 8
(HSSWITCH_STS) in the miscellaneous control register (see Section 4.26).
is asserted to PCI2040, it drives this LED output until the serial ROM has completed preload
Table 2−8. General-Purpose Bus Interface
TERMINAL
NO.
PGE GGU
GPD15
GPD14
GPD13
GPD12
GPD11
GPD10
GPD9
GPD8
GPD7
GPD6
GPD5
GPD4
GPD3
GPD2
GPD1
GPD0
GPA5
GPA4
GPA3
GPA2
GPA1
GPA0
GP_CS112A11OGP chip select
GP_INT74M13I/OGP interrupt. Interrupt from a device on the GP bus.
GP_RD130B6I/OGP read.
GP_RDY75L12I/O
GP_RST70L11OGP reset. An active low output that will follow the state of GRST.
GP_WR129A6I/OGP write.
100
99
98
97
96
94
93
92
90
89
88
86
85
84
83
82
106
107
108
109
110
111
I/ODESCRIPTION
E10
E11
E12
E13
F10
F12
F13
G10
I/OGP data bus. 16-bit data bus.
G13
G12
H13
H11
H10
J13
J12
J11
C11
B13
B12
I/OGP address lines. 6-bit address bus.
A13
A12
B11
GP ready. Whenever the device on the GP bus is ready to accept a read or write from PCI2040, GP_RDY
is asserted. GP_RDY is deasserted when the device is in recovery from a read or write operation.
2−8
3 PCI2040 Functional Description
This section covers the functional description for PCI2040. The PCI2040 provides a 32-bit PCI host interface and an
interface for 8-bit and 16-bit host port interface (HPI) ports for TI’s C54x and C6x families of DSP processors. The
following conventions are used in this document:
•DSPC54x or C6x
•Word16 bits for PCI, 16 bits for C54x, 32 bits for C6x
•Half-word8 bits for C54x, 16 bits for C6x
•Double-word32 bits for PCI
Figure 3−1 shows a simplified block diagram of the PCI2040.
CPCI Hot-Swap
Miscellaneous
Interface
PCI Host Bus Interface
PCI Power
Management
Serial ROM
GPIO
PCI
Target
SM
HPI
Interface
Registers
&
PCI
Registers
C6x
Host
Port
Extensions
HPI Interface
C54x
Host
Port
SM
GP BUS
Interface
Interrupt
Figure 3−1. PCI2040 System Block Diagram
3.1PCI Interface
PCI2040 provides an integrated 32-bit PCI bus interface compliant with the PCI Local Bus Specification. The PCI2040
incorporates a PCI target interface for configuration cycles, accesses to internal registers, and access to the HPI
interface via memory-mapped space. The PCI2040 does not provide PCI mastering.
As a PCI bus target, PCI2040 incorporates the following features:
•Supports the memory read, memory write, configuration read, and configuration write
•Aliases the memory read multiple, memory read line, and memory write and invalidate to the basic
memory commands (i.e., memory read and memory write)
•Supports PCI_LOCK
3−1
3.2Accessing Internal PCI2040 Registers
PCI configuration space is accessed via PCI configuration read and PCI configuration write cycles. These registers
may be accessed using byte, word, or double-word transfers.
The PCI2040 provides a set of registers specifically for interfacing with the HPI port. These registers are called the
HPI control and status registers (HPI CSRs) (see Section 5), and they may be memory- and I/O-mapped. The HPI
CSR memory base address register (see Section 4.11) provides the mechanism for mapping the HPI CSRs into
memory space. When mapped into memory space, the HPI CSRs may be accessed using bytes, words, or
double-word transfers. Memory mapping the HPI CSR registers is recommended.
The HPI control and status registers may also be mapped into I/O space via the HPI CSR I/O base address register
(see Section 4.32). When this register is programmed to a nonzero value, PCI2040 maps the HPI CSRs into I/O
space, and the index/data access scheme is used to access the registers using byte transfers.
The HPI CSR I/O base address register identifies the I/O address of the index port. I/O address index + 1 is the data
port. To access a HPI CSR register, software writes the offset of the HPI CSR register into the index port. I/O reads
from the data port provide the contents of the indexed register and writes to the data port result in PCI2040 updating
the indexed register.
3.3PCI_LOCK
PCI2040 supports exclusive access via the LOCK protocol defined by PCI and the PCI_LOCK terminal. As a PCI
target, PCI2040 locks all DSP access and internal resources to a particular master when PCI_LOCK
deasserted during the address phase of a PCI cycle that it claims. Once LOCK
locked until both FRAME
(see Section 5.1).
and LOCK are sampled deasserted or bit 30 (HPIError) is set in the interrupt event register
is established, the PCI2040 remains
is sampled
The master that owns the exclusive access lock on PCI2040 drives PCI_LOCK
deasserts PCI_LOCK
addressed to it when PCI_LOCK
addressing a locked PCI2040 and will be retried.
Note that when the PCI2040 is not locked, it can claim and complete data transfers even if PCI_LOCK
asserted in the address phase.
(and asserts FRAME) when addressing the PCI2040. The PCI2040 claims and retries cycles
is asserted. Other masters will not be able to force the PCI_LOCK signal high when
while the lock is established and
is sampled
3.4Serial ROM Interface
The PCI2040 provides a two-wire serial ROM interface that may be used to preload PCI2040 registers following a
power-on reset (GRST
input/output. The SCL signal maps to the GPIO0 terminal and the SDA signal maps to the GPIO1 terminal. The
two-wire serial ROM interface is enabled by pulling up both GPIO0 and GPIO1 terminals to V
PCI2040 will only sense GPIO0 on GRST
the serial ROM interface.
The registers that may be preloaded are given in the following list, and only write accessible bits in these registers
may be preloaded. Figure 3−2 illustrates the PCI2040 serial ROM data format.
Word Address 0
Word Address 1
Word Address 2
Word Address 3
Word Address 4
Word Address 5
Word Address 6
Word Address 7
Word Address 8
Word Address 9
Word Address 10
Word Address 11
Word Address 12
Word Address 13
Word Address 14
Word Address 15
Word Address 16 (10h)
Word Address 17
Word Address 18
Word Address 19
Word Address 20
Word Address 21
Word Address 22
Word Address 23
Word Address 24
Word Address 25
Word Address 26
Word Address 27
Word Address 28
Word Address 29
Word Address 30
Word Address 31
Figure 3−2. PCI2040 Serial ROM Data Format
When PCI2040 accesses an implemented serial ROM, it always addresses the serial ROM at slave address
8’b10100000. The serial ROM data format described above utilizes 32 bytes of address space, some of which are
reserved for future generations of the PCI2040. A byte at address 31 is reserved for diagnostic software purposes
and will not be allocated to future generations of the PCI2040. Serial ROM addresses above word address 31 are
available for use by PCI2040 applications. If the data at word address 0 is FFh, then the PCI2040 will stop reading
from the serial ROM. This feature prevents the uninitialized data from being loaded into the PCI2040’s registers.
3.5PCI2040 Host Port Interface
The PCI2040 HPI interface is used to access TI’s TMS320C54X or TMS320C6X DSP chips. The devices connected
to the HPI interface are memory-mapped in host memory. The host system processor accesses the HPI interface
via slave accesses to PCI2040. The DSP devices can generate interrupts, and the PCI2040 passes these interrupt
requests to the PCI bus via INTA
The HPI port on DSP devices is a parallel port that allows access to the DSP’s memory space and internal registers.
The PCI2040 has to configure the HPI interface on the DSP by accessing the DSP’s HPI control register (HPIC). Other
DSP HPI registers include the HPI data register (HPID) and the HPI address register (HPIA). See Section 6, DSPHPI Overview for more information on DSP registers.
3.5.1Identifying Implemented Ports and DSP Types
The PCI2040 supports up to four DSPs of both the C54x and C6x types. It may be useful for generic software to
discover what number and type of DSPs are connected to the PCI2040. This is accomplished by using the HPI DSP
implementation register (see Section 5.5) and HPI data width register (see Section 5.6) in the HPI control and status
register space. The HPI DSP implementation register identifies how many DSPs are implemented and what HCSn
outputs are connected, and the HPI data width register identifies whether the HPI port per connected DSP is 8 bits
(C54x) or 16 bits (C6x).
. See Section 3.7, Interrupts, for more information on PCI2040 interrupts.
3−3
The HPI DSP implementation register and HPI data width register may be loaded from a serial ROM. Also, these
registers are implemented as read/write so intelligent software can load them with the proper values.
3.5.2DSP Chip Selects
The PCI2040 provides four chip select outputs (HCS3−HCS0) that uniquely select each HPI port DSP (or other HPI
peripheral) per transaction. This section describes how software encodes the chip select in the PCI address to access
a particular DSP interfacing with PCI2040.
The PCI2040’s control space base address register (see Section 4.12) is a standard PCI base address register
requesting 32K bytes of control space nonprefetchable memory to access up to four DSPs. The PCI2040 claims PCI
memory access transactions that fall within the 32-Kbyte memory window by comparing the upper 17 bits of the PCI
address (PCI_AD31−PCI_AD15) to bits 31−15 (A VAIL_ADD field) in the control space base address register. When
a cycle is claimed, the chip select is determined by decoding bits 14 and 13 of the PCI address. PCI_AD14 and
PCI_AD13 determine the chip select according to Table 3−1.
Only when the PCI cycle is claimed (by decoding PCI_AD31−PCI_AD15) is the chip select asserted.
Table 3−1. PCI2040 Chip Select Decoding
PCI_AD(14−13)CHIP SELECT ASSERTED
2’b00HCS0
2’b01HCS1
2’b10HCS2
2’b11HCS3
3.5.3HPI Register Access Control
The HCNTL1 and HCNTL0 terminals are driven by the PCI2040 to select the DSP HPI register and access mode
on a cycle-by-cycle basis. The PCI2040 determines the type of DSP register access from the PCI address, similarly
to the chip select decode as described in Section 3.5.2, DSP Chip Selects.
When a cycle is claimed by decoding PCI_AD31−PCI_AD15, the HCNTL1 and HCNTL0 control signals are
determined by decoding bits 12 and 11 of PCI address. PCI_AD12 maps to HCNTL1 and PCI_AD11 maps to
HCNTL0, and the selected HCNTL1 and HCNTL0 are driven to the HPI interface when the cycle is forwarded.
Table 6−1 and Table 6−3 provides more information on the usage of HCNTL1 and HCNTL0 for both C54x and C6x
DSPs.
3.5.4Mapping HPI DSP Memory to the Host
The PCI address bits PCI_AD10−PCI_AD0 are not forwarded to the HPI interface, and these address bits are not
decoded by PCI2040 for any purpose. This 2-Kbyte of addressable space per DSP (and control) allows the host to
directly map 2K bytes of host memory to the HPI interface for each DSP. This allows for fast memory block copies
rather than an I/O port mechanism.
The PCI2040 does not automatically generate accesses to the HPI address registers based upon
PCI_AD10−PCI_AD0, and it is left to software to synchronize the HPI address register with copies to and from HPI
memory space.
3.5.5Read/Write Procedure
The following procedure illustrates how to read and write HPI space, and covers some of the initialization that must
be done to successfully transfer data to and from DSP memory via the HPI data register.
After a power-on reset (GRST
•PCI2040 preloads several registers if a serial ROM is implemented, and this rewrites the HPI
implementation and HPI data width registers (software can also rewrite these registers).
):
3−4
Loading...
+ 54 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.