Académique Documents
Professionnel Documents
Culture Documents
R
Platform Cable USB
Features
Platform Cable USB has these features: • Configures all Xilinx devices
• Supported on Windows and Red Hat Enterprise Linux ♦ All Virtex™ FPGA families
• Automatically senses and adapts to target I/O voltage ♦ All Spartan™ FPGA families
• Interfaces to devices operating at 5V (TTL), 3.3V ♦ XC9500 / XC9500XL / XC9500XV CPLDs
(LVCMOS), 2.5V, 1.8V, and 1.5V ♦ CoolRunner™ XPLA3 / CoolRunner-II CPLDs
• LED Status Indicator ♦ XC18V00 ISP PROMs
• CE, USB-IF, and FCC compliant ♦ XCF00S / XCF00P Platform Flash PROMs
• Intended for development — not recommended for ♦ XC4000XL / XV / EX / E FPGAs
production programming
software using either Boundary-Scan (IEEE 1149.1 / IEEE Top View Model DLC9
----
----
TDI
INIT
----
DIN
2.10
Power 5V 0.26A TDO DONE
TCK CCLK
1532) or Slave-serial modes. Target clock speeds are Serial UH - 12345 TMS PROG
Vref Vref
Made in U.S.A.
selectable from 750 kHz to 24 MHz. 1.5 < Vref < 5.0 VDC
Platform Cable USB attaches to target systems using a All dimensions are in inches.
14-conductor ribbon cable designed for high-bandwidth 4.55
data transfers. An optional adapter that allows attachment Side View
of a flying lead set is included for backward compatibility 0.65
with target systems that do not use the ribbon cable 1.00
connector.
ds300_02_111904
© 2004-2006 Xilinx, Inc. All rights reserved. All Xilinx trademarks, registered trademarks, patents, and disclaimers are as listed at http://www.xilinx.com/legal.htm.
PowerPC is a trademark of IBM, Inc. All other trademarks are the property of their respective owners. All specifications are subject to change without notice.
Operating Power
Platform Cable USB is a bus-powered device. It
automatically negotiates its operating current to achieve the
highest performance in accordance with the capabilities of
the port to which it is attached. If the host is USB 2.0
compatible and can provide at least 230 mA, Platform
Cable USB operates at Hi-Speed. Otherwise, it requests
150 mA and operates at full speed. Some older root hubs or
bus-powered external hubs might restrict devices to DS300_03_112504
100 mA. Platform Cable USB does not enumerate on these
Figure 3: CPLD Update Notification
ports (see section "Hot Plug and Play," page 3, for an
explanation of enumeration).
Firmware Updates
Platform Cable USB is a RAM-based product. Application
code is downloaded each time the cable is detected by the
host operating system. USB protocol guarantees that the
code is successfully downloaded.
All files necessary for successful cable communication are DS300_04_110604
included with every Xilinx ISE software installation CD.
Revised application code is periodically distributed in Figure 4: CPLD Update Progress Bar
Found New Hardware Wizard (see Figure 5) and for the Platform Cable USB itself (see
Figure 6).
(for Windows Only)
Windows invokes the Found New Hardware flow each time
Platform Cable USB should be disconnected from the host Platform Cable USB is plugged into a different physical USB
system during the initial software installation. The first time port for the first time. The wizard screens could be slightly
a cable is attached after software installation, Windows different for Windows 2000 environments.
invokes the Found New Hardware wizard and registers
device drivers for the Platform Cable USB Firmware Loader
ds300_05_112904
ds300_06_112904
Hot Plug and Play When Platform Cable USB completes the enumeration
process on a Windows system, a "Programming cables"
The cable can be attached and removed from the host entry appears in the Windows Device Manager (see
computer without the need to power-down or reboot. There Figure 7, page 4). To display Device Manager, right-click on
is a momentary delay after connecting the cable to an My Computer, then select Properties → Hardware →
available port before the Status LED illuminates. This Device Manager.
process is called enumeration.
DS300_07_110604
iMPACT Configuration Cable Selection Figure 9: iMPACT Cable Communication Setup Dialog
Platform Cable USB can be designated as the "active" Configuration Clock Speed
configuration cable by following the auto-connect sequence
for configuring devices that is displayed when first starting The Platform Cable USB configuration clock (TCK_CCLK)
an iMPACT session. frequency is selectable. Table 1 shows the complete set of
available TCK_CCLK speed selections for high-power USB
Note: During the auto-connect sequence, iMPACT selects PC4
ports.
as the "active" cable if both PC4 and Platform Cable USB are
connected simultaneously. Table 1: Speed Selection for High-Power Ports
Alternatively, the cable can be manually selected using the Selection TCK_CCLK Frequency Units
Output→Cable Setup option on the iMPACT toolbar (see 1 24 MHz
Figure 8).
2 12 MHz
3 (default) 6 MHz
4 3 MHz
5 1.5 MHz
6 750 kHz
Note: iMPACT versions earlier than 7.1i do not restrict the Cable Type = 3, Revision = 0
TCK_CCLK selections in boundary-scan mode. Accordingly, users Cable Connection Established
should take care to select a TCK_CCLK frequency that matches Note: The actual revision number can be expected to change
the JTAG TCK specifications for the slowest device in the target with new software releases.
boundary-scan chain.
Table 2: Maximum JTAG Clock Frequencies Status Indicator
Maximum JTAG Clock
Device Family Frequency Units Platform Cable USB uses a bi-color Status LED to indicate
the presence of target voltage. When the ribbon cable is
XC9500XL 10 MHz
connected to a mating connector on the target system, the
XPLA3 10 MHz Status LED is illuminated as a function of the voltage
CoolRunner-II 10 MHz present on pin 2 (VREF).
XC18V00 10 MHz Users must design their system hardware with pin 2
XCF00S/XCF00P 15 MHz attached to a voltage plane that supplies the JTAG or
Slave-serial pins on the target device(s). Some devices
Virtex 33 MHz have separate power pins for this purpose (VAUX), while
Virtex-II 33 MHz others have a common supply for both VCCIO and the
Virtex-II Pro 33 MHz JTAG pins (TCK, TMS, TDI, and TDO). Refer to the target
device Data Sheet for details on Slave-serial or JTAG pins.
Virtex-4 33 MHz
The Status LED is amber (see Figure 11) when any one or
Spartan 5 MHz
more of the following conditions exist:
Spartan-II 33 MHz
• The ribbon cable is not connected to a target system
Spartan-3 33 MHz
• The target system is not powered
• The voltage on the VREF pin is < +1.5V.
A Status bar on the bottom edge of the iMPACT GUI
provides useful information about operating conditions. If The Status LED is green when all of the following conditions
the host port is USB 1.1, Platform Cable USB connects at exist:
full speed, and the Status bar shows "usb-fs." If the host
port is USB 2.0, Platform Cable USB connects at Hi-Speed • The ribbon cable is connected to a target system
and the Status bar shows "usb-hs." • The target system is powered
The active TCK_CCLK frequency is shown in the lower • The voltage on the VREF pin is ≥ +1.5V.
right-hand corner of the Status bar (see Figure 10). The Status LED is Off whenever Platform Cable USB enters
a Suspend state, or is disconnected from a powered USB
port.
Full-Speed or
High-Speed
Connection
Active
Active Cable TCK_CCLK Green indicates target voltage present
Identification Frequency
Command Log
Text Display
DS300_10_111904
using the Cable Communication Setup dialog box, the Figure 11: Status LEDs Indicating Target Voltage
command log indicates:
ds300_12_110804
Notes:
1. Ribbon Cable: 14 conductor, 1.0 mm center, round
conductor flat cable, 28 AWG (7x36) stranded
conductors, gray PVC with pin 1 edge marked.
ds300_11a_113004
R
2mm STATUS
CONNECTOR
SIGNALS
Platform Cable USB Gnd
R
JTAG or Serial
---- INIT
Model DLC9 ---- ----
JTAG | SERIAL Vref | Vref
TDI DIN GND | GND
Power 5V 0.26A TDO DONE
TCK CCLK TCK | CCLK
Serial UH - 12345 TMS PROG
--- | INIT
Vref Vref
TDO | DONE
TDI | DIN
Made in U.S.A. 1.5 < Vref < 5.0 VDC
TMS | PROG
ADAPTER
DS300_13_111904
Notes:
1. Some manufacturer pin assignments may not conform to Xilinx pin assignments. Please refer to the manufacturer’s data sheet for more
information.
2. Additional ribbon cables can be purchased separately from the Xilinx Online Store.
DS300_17_113004
DS300_18_110204
Figure 19: TDO_DONE Timing with Respect to TCK_CCLK (CBL_TCK to TCK_CCLK Delay)
DS300_19_110204
Figure 20: TDO_DONE Timing with Respect to TCK_CCLK (TCK_CCLK to TDO_DONE Delay)
DS300_20_110204
Figure 21: TDO_DONE Timing with Respect to TCK_CCLK (TDO_DONE to CBL_TDO Delay)
Notes:
1. There are weak pull-up resistors to VREF_A on each of the three
output drivers (TCK_CCLK, TMS_PROG, and TDI_DIN). The
output drivers are active only during configuration and
programming operations. Between operations, the drivers are DS300_22_113004
set to high-Z.
Figure 23: VREF_A as a Function of VREF
Xilinx applications actively drive the outputs to Logic 1
before setting the respective buffer to high-Z. This avoids Input Receiver Structure
the possibility of a slow rise-time transition caused by a
charge path through the pull-up resistor into parasitic A Schottky diode is used to protect the TDO_DONE voltage
capacitance on the target system. comparator (Figure 24, page 11). In effect, Platform Cable
USB looks for voltages below VIL MAX to detect logic 0, and
Output Driver Structure tolerates voltages much higher than VREF_A because TDO
could be terminated to a supply other than VREF.
Platform Cable USB drives three target signals:
TCK_CCLK, TMS_PROG, and TDI_DIN. Each of these
signals incorporates the same driver topology. A Xilinx
XC2C256 Coolrunner-II CPLD generates the output
signals.
TCK_CCLK
1 TCK_CCLK_1
Four
LT1719 2 mm Connector Buffered
I/O Clocks
XFCE PIN 4 TCK_CCLK_4
BAT54
Signal Integrity Note: If the target system incorporates a buffer for TCK_CCLK
and the 24 MHz clock rate is used, it is recommended that the
Platform Cable USB uses high-slew-rate buffers to drive same buffer type also be provided for TMS_PROG. This maintains
TCK_CCLK, TMS_PROG, and TDI_DIN. Each buffer has a a consistent phase relationship between TCK_CCLK and
30Ω series termination resistor. Users should pay close TMS_PROG. A buffer is not needed for TDI_DIN, because it sees
attention to PCB layout to avoid transmission line effects. only one load.
Visit the Xilinx Signal Integrity Central website, and see
specifically Xilinx Application Note XAPP361, Planning for
High Speed XC9500XV Designs, for detailed signal integrity Target System Connections
assistance. Multiple devices can be cascaded when using either JTAG
If the target system has only one programmable device, the or Slave-serial topology in target systems. Figure 26,
2 mm connector should be located as close as possible to page 12 shows an example of Slave-serial routing, and
the target device. If there are multiple devices in a single Figure 27, page 12 shows typical JTAG connections.
chain on the target system, users should consider buffering The DONE pin on FPGAs can be programmed to be an
TCK_CCLK. Differential driver/receiver pairs provide open-drain or active driver. For cascaded Slave-serial
excellent signal quality when the rules identified in topologies, an external pull-up resistor should be used, and
Figure 25 are followed. Buffering is essential if target all devices should be programmed for open-drain operation.
devices are distributed over a large PCB area.
If the 2 mm connector is located a significant distance from
Each differential driver and/or receiver pair contributes the target device, it is best to buffer TCK_CCLK, at a
approximately 5 ns of propagation delay. This is minimum. These diagrams are intended to represent the
insignificant when using 12 MHz or slower clock speeds. logical relationship between Platform Cable USB and target
Each differential receiver can drive multiple target devices if devices. Refer to "Signal Integrity" for additional buffering
there are no branches on the PCB trace and the total trace and termination information.
length is less than four inches. A series termination resistor
should be placed adjacent to the single-ended output of the
differential receiver.
VCCAUX(2)
2 mm Connector Optional
Pull-Up
VCCAUX(2)
VREF 2
DONE 8
PROG DONE PROG DONE PROG DONE
PROG 4
DIN 10 DIN FPGA1 DOUT DIN FPGA2 DOUT DIN FPGAn DOUT
INIT 14
VCCO INIT CCLK INIT CCLK INIT CCLK
CCLK 6
GND(3) X
Notes:
1. Set Mode pins (M2-M0) on each FPGA to Slave-serial mode when using the USB cable, so that CCLK is treated
as an input.
2. VCCAUX is 3.3V for Virtex-II, 2.5V for Spartan-3 and Virtex-II Pro. Virtex-4 serial configuration pins are on a
dedicated VCC_CONFIG (VCCO_0), 2.5V supply. Other FPGA families do not have a separate VCCAUX supply.
3. Attach the following 2 mm connector pins to digital ground: 1, 3, 5, 7, 9, 11, 13. DS300_25_031006
2 mm
Connector
VCCAUX(1)
VREF 2
TDO 8
ISP
TDI 10 TDI TDO TDI FPGA TDO TDI CPLD TDO
PROM
TMS 4
TMS TCK TMS TCK TMS TCK
TCK 6
GND(2) X
Notes:
1. Example implies that VCCO, VCCJ, VCC_CONFIG and VCCAUX for various devices are set to the
same voltage. See device data sheets for appropriate JTAG voltage-supply levels.
2. Attach the following 2 mm connector pins to digital ground: 1, 3, 5, 7, 9, 11, 13. DS300_26_031006
Platform Cable USB requires approximately 230 mA when If an external 2.0 hub is attached to a 1.1 root hub, operation
operating in Hi-Speed mode while connected to USB 2.0 is at full speed (refer to Figure 28B). Hi-Speed USB
ports. If the port cannot supply 230 mA, Platform Cable operation is guaranteed only if Platform Cable USB is
USB operates in full-speed mode. Operation is always attached directly to a 2.0 root hub, or to an external
full-speed when connected to USB 1.1 ports. self-powered 2.0 hub that is connected to a 2.0 root hub
(refer to Figure 28D and Figure 28E).
Total Bandwidth If Platform Cable USB is attached to an external,
bus-powered 2.0 hub, it could enumerate as a full-speed
The maximum achievable bandwidth for a single USB 1.1 device (refer to Figure 28C). Bus-powered hubs can deliver
full-speed device is 8 Mb/s. The maximum theoretical
a total of 500 mA to all connected devices. If individual ports
bandwidth for a single USB 2.0 Hi-Speed device is 56 Mb/s.
on bus-powered hubs are limited to less than 150 mA,
Because hub bandwidth must be shared among all
Platform Cable USB will not enumerate and will be
connected devices, actual bandwidth could be lower.
unavailable for use by host software applications.
1.X Root Hub 1.X Root Hub 2.0 Root Hub 2.0 Root Hub 2.0 Root Hub
Enumerates at Enumerates at
full speed because < 500 < 500 500 Hi-Speed since
root hub only mA mA mA root hub can
operates at full supply 500 mA
speed — Degraded per port — Best
performance due performance due
to slow bus speed Platform Cable Platform Cable Platform Cable to high bus
USB USB USB speed
Figure 28: Platform Cable USB Performance with Various Hub Types
Notes:
1. All odd pins (1, 3, 5, 7, 9, 11, and 13) should be connected to digital ground on the target end of the ribbon cable. Minimum crosstalk is
achieved when using all grounds.
Notes:
1. Operating at Hi-Speed on a USB 2.0 port.
2. Operating at full speed on a low-power USB 1.1 port.
3. Exposure to Absolute Maximum Rating conditions for extended periods of time can affect product reliability. These are stress ratings only
and functional operation of the product at these or any other condition beyond those listed under Recommended Operating Conditions is not
implied.
TCK_CCLK
TCPD
TMS_PROG /
TDI_DIN
TDO_DONE
FCC Notice
This equipment has been tested and found to comply with Industry Canada Information
the limits for a Class A digital device, pursuant to Part 15 of
the FCC Rules. These limits are designed to provide This Class A digital apparatus complies with Canadian
reasonable protection against harmful interference when ICES-003.
the equipment is operated in a commercial environment.
This equipment generates, uses, and can radiate radio
frequency energy and, if not installed and used in Ordering Information
accordance with the data sheet, could cause harmful The product number is HW-USB.
interference to radio communications. Operation of this
equipment in a residential area is likely to cause harmful
interference, in which case, the user is required to correct
the interference at his own expense.
Revision History
The following table shows the revision history for this document.