Xilinx University Program
Virtex-II Pro Development
System
Hardware Reference Manual
UG069 (v1.0) March 8, 2005
R
R
"Xilinx" and the Xilinx logo shown above are registered trademarks of Xilinx, Inc. Any rights not expressly granted herein are reserved.
CoolRunner, RocketChips, Rocket IP, Spartan, StateBENCH, StateCAD, Virtex, XACT, XC2064, XC3090, XC4005, and XC5210 are
registered trademarks of Xilinx, Inc.
The shadow X shown above is a trademark of Xilinx, Inc.
ACE Controller, ACE Flash, A.K.A. Speed, Alliance Series, AllianceCORE, Bencher, ChipScope, Configurable Logic Cell, CORE Generator,
CoreLINX, Dual Block, EZTag, Fast CLK, Fast CONNECT, Fast FLASH, FastMap, Fast Zero Power, Foundation, Gigabit Speeds...and
Beyond!, HardWire, HDL Bencher, IRL, J Drive, JBits, LCA, LogiBLOX, Logic Cell, LogiCORE, LogicProfessor, MicroBlaze, MicroVia,
MultiLINX, NanoBlaze, PicoBlaze, PLUSASM, PowerGuide, PowerMaze, QPro, Real-PCI, RocketIO, SelectIO, SelectRAM, SelectRAM+,
Silicon Xpresso, Smartguide, Smart-IP, SmartSearch, SMARTswitch, System ACE, Testbench In A Minute, TrueMap, UIM, VectorMaze,
VersaBlock, VersaRing, Virtex-II Pro, Virtex-II EasyPath, Wave Table, WebFITTER, WebPACK, WebPOWERED, XABEL, XACTFloorplanner, XACT-Performance, XACTstep Advanced, XACTstep Foundry, XAM, XAPP, X-BLOX +, XC designated products, XChecker,
XDM, XEPLD, Xilinx Foundation Series, Xilinx XDTV, Xinfo, XSI, XtremeDSP and ZERO+ are trademarks of Xilinx, Inc.
The Programmable Logic Company is a service mark of Xilinx, Inc.
All other trademarks are the property of their respective owners.
Xilinx, Inc. does not assume any liability arising out of the application or use of any product described or shown herein; nor does it convey
any license under its patents, copyrights, or maskwork rights or any rights of others. Xilinx, Inc. reserves the right to make changes, at any
time, in order to improve reliability, function or design and to supply the best product possible. Xilinx, Inc. will not assume responsibility for
the use of any circuitry described herein other than circuitry entirely embodied in its products. Xilinx provides any design, code, or
information shown or described herein “as is.” By providing the design, code, or information as one possible implementation of a feature,
application, or standard, Xilinx makes no representation that such implementation is free from any claims of infringement. You are
responsible for obtaining any rights you may require for your implementation. Xilinx expressly disclaims any warranty whatsoever with
respect to the adequacy of any such implementation, including but not limited to any warranties or representations that the implementation
is free from claims of infringement, as well as any implied warranties of merchantability or fitness for a particular purpose. Xilinx, Inc. devices
and products are protected under U.S. Patents. Other U.S. and foreign patents pending. Xilinx, Inc. does not represent that devices shown
or products described herein are free from patent infringement or from any other third party right. Xilinx, Inc. assumes no obligation to
correct any errors contained herein or to advise any user of this text of any correction if such be made. Xilinx, Inc. will not assume any liability
for the accuracy or correctness of any engineering or software support or assistance provided to a user.
Xilinx products are not intended for use in life support appliances, devices, or systems. Use of a Xilinx product in such applications without
the written consent of the appropriate Xilinx officer is prohibited.
The contents of this manual are owned and copyrighted by Xilinx. Copyright 1994-2005 Xilinx, Inc. All Rights Reserved. Except as stated
herein, none of the material may be copied, reproduced, distributed, republished, downloaded, displayed, posted, or transmitted in any form
or by any means including, but not limited to, electronic, mechanical, photocopying, recording, or otherwise, without the prior written consent
of Xilinx. Any unauthorized use of any material contained in this manual may violate copyright laws, trademark laws, the laws of privacy and
publicity, and communications regulations and statutes.
XUP Virtex-II Pro Development System
UG069 (v1.0) March 8, 2005
The following table shows the revision history for this document.
VersionRevision
03/08/051.0Initial Xilinx release. (DRAFT)
XUP Virtex-II Pro Development Systemwww.xilinx.comUG069 (v1.0) March 8, 2005
UG069 (v1.0) March 8, 2005www.xilinx.comXUP Virtex-II Pro Development System
Appendix A: Configuring the FPGA from the Embedded USB
Configuration Port
Appendix B: Programming the Platform FLASH PROM User Area
Appendix C: Restoring the Golden FPGA Configuration
Appendix D: Using the Golden FPGA Configuration for System Self-
Test
Appendix E: User Constraint Files (UCF)
Appendix F: Links to the Component Data Sheets
XUP Virtex-II Pro Development Systemwww.xilinx.comUG069 (v1.0) March 8, 2005
R
Chapter 1
XUP Virtex-II Pro Development System
Features
•Virtex™-II Pro FPGA with PowerPC™ 405 cores
•Up to 2 GB of Double Data Rate (DDR) SDRAM
•System ACE™ controller and Type II CompactFlash™ connector for FPGA
configuration and data storage
•Embedded Platform Cable USB configuration port
•High-speed SelectMAP FPGA configuration from Platform Flash In-System
Programmable Configuration PROM
•Support for “Golden” and “User” FPGA configuration bitstreams
•On-board 10/100 Ethernet PHY device
•Silicon Serial Number for unique board identification
•RS-232 DB9 serial port
•Two PS-2 serial ports
•Four LEDs connected to Virtex-II Pro I/O pins
•Four switches connected to Virtex-II Pro I/O pins
•Five push buttons connected to Virtex-II Pro I/O pins
•Six expansion connectors joined to 80 Virtex-II Pro I/O pins with over-voltage
protection
•High-speed expansion connector joined to 40 Virtex-II Pro I/O pins that can be used
differentially or single ended
•AC-97 audio CODEC with audio amplifier and speaker/headphone output and line
level output
•Microphone and line level audio input
•On-board XSGA output, up to 1200 x 1600 at 70 Hz refresh
•Three Serial ATA ports, two Host ports and one Target port
•Off-board expansion MGT link, with user-supplied clock
•100 MHz system clock, 75 MHz SATA clock
•Provision for user-supplied clock
•On-board power supplies
•Power-on reset circuitry
•PowerPC 405 reset circuitry
XUP Virtex-II Pro Development Systemwww.xilinx.com13
UG069 (v1.0) March 8, 2005
R
General Description
The XUP Virtex-II Pro Development System provides an advanced hardware platform that
consists of a high performance Virtex-II Pro Platform FPGA surrounded by a
comprehensive collection of peripheral components that can be used to create a complex
system and to demonstrate the capability of the Virtex-II Pro Platform FPGA.
Block Diagram
Figure 1-1 shows a block diagram of the XUP Virtex-II Pro Development System.
Chapter 1: XUP Virtex-II Pro Development System
External Power
Internal Power Supplies
4.5-5.5V
CPU Debug Port
100 MHz System Clock
75 MHz SATA Clock
User Clocks (2)
Platform Flash Configurations (2)
Compact Flash Configurations (8)
USB2 High Speed Configuration
3.3V
2.5V
1.5V
Figure 1-1:XUP Virtex-II Pro Development System Block Diagram
Board Components
Virtex-II Pro
FPGA
AC97 Audio CODEC & Stereo Amp
XSGA Video Output
User LEDs (4)
User Switches (4)
User Push-button Switches (5)
10/100 Ethernet PHY
RS-232 & PS/2 Ports (2)
Serial ATA Por ts (3)
Multi-Gigabit Transceiver Port
2 GB DDR SDRAM DIMM Module
5V Tolerant Expansion Headers
High Speed Expansion Port
UG069_01_012105
This section contains a concise overview of several important components on the XUP
Virtex-II Pro Development System (see Figure 1-2). The most recent documentation for the
system can be obtained from the XUP Virtex-II Pro Development System support website
at: http://www.xilinx.com/univ/xup2vp.html
14www.xilinx.comXUP Virtex-II Pro Development System
UG069 (v1.0) March 8, 2005
General Description
R
Figure 1-2: XUP Virtex-II Pro Development System Board Photo
Virtex-II Pro FPGA
U1 is a Virtex-II Pro FPGA device packaged in a flip-chip-fine-pitch FF896 BGA package.
Two different capacity FPGAs can be used on the XUP Virtex-II Pro Development System
with no change in functionality. Ta bl e 1-1 lists the Virtex-II Pro device features.
Table 1-1:XC2VP20 and XC2VP30 Device Features
FeaturesXC2VP20XC2VP30
Slices928013969
Array Size56 x 4680 x 46
Distributed RAM290 Kb428 Kb
Multiplier Blocks88136
XUP Virtex-II Pro Development Systemwww.xilinx.com15
UG069 (v1.0) March 8, 2005
R
Chapter 1: XUP Virtex-II Pro Development System
Table 1-1:XC2VP20 and XC2VP30 Device Features (Continued)
FeaturesXC2VP20XC2VP30
Block RAMs1584 Kb2448 Kb
DCMs88
PowerPC RISC Cores22
Multi-Gigabit Transceivers88
Figure 1-3 identifies the I/O banks that are used to connect the various peripheral devices
to the FPGA.
AC97 Audio SXGA port
10/100 Ethernet
1
0
2
7
OVER VOLTAGE CLAMPS
EXPANSION CONNECTORS
LEDs & SWITCHES
PS/2 KBD & MOUSE
PUSH BUTTONS
RS-232
System ACE port
Figure 1-3: I/O Bank Connections to Peripheral Devices
Power Supplies and FPGA Configuration
The XUP Virtex-II Pro Development System is powered from a 5V regulated power supply.
On-board switching power supplies generate 3.3V, 2.5V, and 1.5V for the FPGA, and
peripheral components and linear regulators power the MGTs.
The board has provisioning for current measurement for all of the FPGA digital power
supplies, as well as application of external power if the capacity of the on-board switching
power supplies is exceeded.
3
6
45
256M x 64/72 DDR SDRAM DIMM MODULE
3.3V IO
2.5V IO
UG069_03_012105
The XUP Virtex-II Pro Development System provides several methods for the
configuration of the Virtex-II Pro FPGA. The configuration data can originate from the
internal Platform Flash PROM (two potential configurations), the internal CompactFlash
storage media (eight potential configurations), and external configurations delivered from
the embedded Platform Cable USB or parallel port interface.
16www.xilinx.comXUP Virtex-II Pro Development System
UG069 (v1.0) March 8, 2005
General Description
Multi-Gigabit Transceivers
System RAM
R
Four of the eight Multi-Gigabit Transceivers (MGTs) that are present in the Virtex-II Pro
FPGA are brought out to connectors and can be utilized by the user. Three of the
bidirectional MGT channels are terminated at Serial Advanced Technology Attachment
(SATA) connectors and the fourth channel terminates at user-supplied Sub-Miniature A
(SMA) connectors. The MGT transceivers are equipped with a 75 MHz clock source that is
independent for the system clock to support standard SATA communication. An
additional MGT clock source is available through a differential user-supplied (SMA)
connector pair. Two of the ports with SATA connectors are configured as Host ports and
the third SATA port is configured as a Target port to allow for simple board-to-board
networking.
The XUP Virtex-II Pro Development System has provision for the installation of usersupplied JEDEC-standard 184-pin dual in-line Double Data Rate Synchronous Dynamic
RAM memory module. The board supports buffered and unbuffered memory modules
with a capacity of 2 GB or less in either 64-bit or 72-bit organizations. The 72-bit
organization should be used if ECC error detection and correction is required.
System ACE Compact Flash Controller
The System Advanced Configuration Environment (System ACE™) Controller manages
FPGA configuration data. The controller provides an intelligent interface between an
FPGA target chain and various supported configuration sources. The controller has several
ports: the Compact Flash port, the Configuration JTAG port, the Microprocessor (MPU)
port and the Test JTAG port. The XUP Virtex-II Pro Development System supports a single
System ACE Controller. The Configuration JTAG ports connect to the FPGA and front
expansion connectors. The Test JTAG port connects to the JTAG port header and USB2
interface CPLD, and the MPU ports connect directly to the FPGA.
Fast Ethernet Interface
The XUP Virtex-II Pro Development System provides an IEEE-compliant Fast Ethernet
transceiver that supports both 100BASE-TX and 10BASE-T applications. It supports full
duplex operation at 10 Mb/s and 100 Mb/s, with auto-negotiation and parallel detection.
The PHY provides a Media Independent Interface (MII) for attachment to the 10/100
Media Access Controller (MAC) implemented in the FPGA. Each board is equipped with a
Silicon Serial Number that uniquely identifies each board with a 48-bit serial number. This
serial number is retrieved using “1-Wire” protocol. This serial number can be used as the
system MAC address.
Serial Ports
The XUP Virtex-II Pro Development System provides three serial ports: a single RS-232
port and two PS/2 ports. The RS-232 port is configured as a DCE with hardware
handshake using a standard DB-9 serial connector. This connector is typically used for
communications with a host computer using a standard 9-pin serial cable connected to a
COM port. The two PS/2 ports could be used to attach a keyboard and mouse to the XUP
Virtex-II Pro Development System. All of the serial ports are equipped with level-shifting
circuits, because the Virtex-II Pro FPGAs cannot interface directly to the voltage levels
required by RS-232 or PS/2.
XUP Virtex-II Pro Development Systemwww.xilinx.com17
UG069 (v1.0) March 8, 2005
R
Chapter 1: XUP Virtex-II Pro Development System
User LEDs, Switches, and Push Buttons
A total of four LEDs are provided for user-defined purposes. When the FPGA drives a
logic 0, the corresponding LED turns on. A single four-position DIP switch and five push
buttons are provided for user input. If the DIP switch is up, closed, or on, or the push button
is pressed, a logic 0 is seen by the FPGA, otherwise a logic 1 is indicated.
Expansion Connectors
A total of 80 Virtex-II Pro I/O pins are brought out to four user-supplied 60-pin headers
and two 40-pin right angle connectors for user-defined use. The 60-pin headers are
designed to accept ribbon-cable connectors, with every second signal a ground for signal
integrity. Some of these signals are shared with the front-mounted right-angle connectors.
The front-mounted connectors support Digilent expansion modules. In addition, a highspeed connector is provided to support Digilent high-speed expansion modules. This
connector provides 40 single-ended or differential I/O signals in addition to three clocks.
Consult the Digilent website at www.diglentinc.com
compatible with the XUP Virtex-II Pro Development System.
XSGA Output
The XUP Virtex-II Pro Development System includes a video DAC and 15-pin highdensity D-sub connector to support XSGA output. The video DAC can operate with a pixel
clock of up to 180 MHz. This allows for a VESA-compatible output of 1280 x 1024 at 75 Hz
refresh and a maximum resolution of 1600 x 1200 at 70 Hz refresh.
for a list of expansion boards that are
AC97 Audio CODEC
An audio CODEC and stereo power amplifier are included on the XUP Virtex-II Pro
Development System to provide a high-quality audio path and provide all of the analog
functionality in a PC audio system. It features a full-duplex stereo ADC and DAC, with an
analog mixer, combining the line-level inputs, microphone input, and PCM data.
CPU Trace and Debug Port
The FPGA is equipped with a CPU debugging interface and a 16-pin header. This
connector can be used in conjunction with third party tools, the Xilinx Parallel Cable IV, or
the Xilinx Platform Cable USB to debug software as it runs on either PowerPC 405
processor core.
ChipScope Pro™ can also be used to perform real-time debug and verification of the FPGA
design. ChipScope Pro inserts logic analyzer, bus analyzer, and Virtual I/O low-profile
software cores into the FPGA design. These cores allow the designer to view all the internal
signals and nodes within the FPGA including the Processor Local Bus (PLB) or On-Chip
Peripheral Bus (OPB) supporting the PowerPC 405 cores. Signals are captured and brought
out through the embedded Platform Cable USB programming interface for analysis using
the ChipScope Pro Logic Analyzer tool.
USB 2 Programming Interface
The XUP Virtex-II Pro Development System includes an embedded USB 2.0
microcontroller capable of communications with either high-speed (480 Mb/s) or fullspeed (12 Mb/s) USB hosts. This interface is used for programming or configuring the
Virtex-II Pro FPGA in Boundary-Scan (IEEE 1149.1/IEEE 1532) mode. Target clock speeds
are selectable from 750 kHz to 24 MHz. The USB 2.0 microcontroller attaches to a desktop
or laptop PC with an off-the-shelf high-speed A-B USB cable.
18www.xilinx.comXUP Virtex-II Pro Development System
UG069 (v1.0) March 8, 2005
R
Using the System
Configuring the Power Supplies
The XUP Virtex-II Pro Development System supports the independent creation of the
power supplies for the core voltage of 1.5V (FPGA_VINT), 2.5V general-purpose power,
I/O and/or VCCAUX supplies (VCC2V5), and 3.3V I/O and general-purpose power
(VCC3V3). These voltages are created by synchronous buck-switching regulators derived
from the 4.5V-5.5V power input provided at the center-positive barrel-jack power input
(J26) or the terminal block pair (J34-J35). Each of these supplies can be disabled through the
insertion of jumpers (JP2, JP4, and JP6), and the external application of power from the
terminal blocks (J28-J33). If external power is supplied, the associated internal power
supply must be disabled (through the insertion of JP6, JP2, or JP4) and the associated onboard power delivery jumpers (JP5, JP1, or JP3) must be removed. The power consumption
from each of the on-board power supplies can be monitored through the removal of JP5,
JP1, or JP3 and the insertion of a current monitor. If any of the power supplies are outside
the recommended tolerance, internally or externally provided, the system enters a RESET
state indicated by the illumination of the RESET_PS_ERROR LED (D6) and the assertion of
the RESET_Z signal. A typical switching power supply is shown in Figure 2-1.
Chapter 2
ug069_04_021505
Figure 2-1:Typical Switching Power Supply
XUP Virtex-II Pro Development Systemwww.xilinx.com19
UG069 (v1.0) March 8, 2005
VCC3V3
R
Chapter 2: Using the System
Because of the analog nature of the MGTs, the power for those elements are created by low
noise, low dropout linear regulators. Figure 2-2 shows the power supply for the MGTs.
U20
FIXED 2.5V LDO
TA B
TA B
4
3
+
6
4
3
6
C428
330UF 6.3V
C433
+
330UF 6.3V
C430
0.1UF
C434
0.1UF
VCC_MGT
C427
1000PF
VTT_MGT
C432
1000PF
UG069_05_010605
C431
+
33OUF 6.3V
C429
+
33OUF 6.3V
FERRITE BEAD
2961666671
L32
2
INOUT
1
SHDNGND
5
SENSE
LT1963AEQ-25
U21
FIXED 2.5V LDO
2
INOUT
1
SHDNGND
5
SENSE
LT1963AEQ-25
GND_MGT
Configuring the FPGA
At power up, or when the RESET_RELOAD push button (SW1) is pressed for longer than
2 seconds, the FPGA begins to configure. The two configuration methods supported, JTAG
and master SelectMAP, are determined by the CONFIG SOURCE switch, the most
significant switch (left side) of SW9.
If the CONFIG SOURCE switch is closed, on, or up, a high-speed SelectMap byte-wide
configuration from the on-board Platform Flash configuration PROM (U3) is selected as
the configuration source. This is identified to the user through the illumination of the
PROM CONFIG LED (D19).
The Platform Flash configuration PROM supports two different FPGA configurations
(versions) selected by the position of the PROM VERSION switch, the least significant
switch (right side) of SW9.
If the PROM VERSION switch is closed, on, or up, the GOLDEN configuration from the onboard Platform Flash configuration PROM is selected as the configuration data. This is
identified to the user through the illumination of the GOLDEN CONFIG LED (D14). This
configuration can be a board test utility provided by Xilinx, or another safe default
configuration. It is important to note that the PROM VERSION switch is only sampled on
board powerup and after a complete system reset. This means that if this switch is changed
after board powerup, the RESET_RELOAD pushbutton (SW1) must be pressed for more
than 2 seconds for the new state of the switch to be recognized.
Figure 2-2:MGT Power
If the PROM VERSION switch is open, off, or down, a User configuration from the on-board
Platform Flash configuration PROM is selected as the configuration data. This
configuration must be programmed into the Platform Flash PROM from the JTAG
Platform Cable USB interface or the USB interface following the instructions in Appendix
B, “Programming the Platform FLASH PROM User Area.”
20www.xilinx.comXUP Virtex-II Pro Development System
UG069 (v1.0) March 8, 2005
Configuring the FPGA
The Platform Flash is normally disabled after the FPGA is finished configuring and has
asserted the DONE signal. If additional data is made available to the FPGA after the
completion of configuration, jumper JP9 must be moved from the NORMAL to the
EXTENDED position to permanently enable the PROM and allow the FPGA to clock out
the additional data using the FPGA_PROM_CLOCK signal. The process of loading
additional non-configuration data into the FPGA is outlined in application note:
XAPP694:
Reading User Data from Configuration PROMs.
If the CONFIG SOURCE switch is open, off, or down, a lower speed JTAG-based
configuration from Compact Flash or external JTAG source is selected as the configuration
source. This is identified to the user through the illumination of the JTAG CONFIG LED
(D20).
The JTAG-based configuration can originate from several sources: the Compact Flash card,
a PC4 cable connection through J27, and a USB to PC connection through J8 the embedded
Platform Cable USB interface.
If a JTAG-based configuration is selected, the default source is from the Compact Flash
port (J7). The System ACE controller checks the associated Compact Flash socket and
storage device for the existence of configuration data. If configuration data exists on the
storage device, the storage device becomes the source for the configuration data. The file
structure on the Compact Flash storage device supports up to eight different configuration
data files, selected by the triple CF CONFIG SELECT DIP switch (SW8). During JTAG
configuration, the SYSTEMACE STATUS LED (D12) flashes until the configuration process
is completed, and the FPGA asserts the FPGA_DONE signal and illuminates the DONE
LED (D4). At any time, the RESET_RELOAD pushbutton (SW1) can be used to load any of
the eight different configuration data files by pressing the switch for more than 2 seconds.
R
If a JTAG-based configuration is selected and a valid configuration file is not found on the
Compact Flash card by the System ACE controller (U2), the SYSTEMACE ERROR LED
(D11) flashes, and the System ACE controller connects to an external JTAG port for FPGA
configuration.
The default external source for FPGA configuration is the high-speed embedded Platform
Cable USB configuration port (J8) and is enabled when the System ACE controller does not
find configuration data on the storage device. Detailed instructions on using the highspeed Platform Cable USB interface can be found in Appendix A, “Configuring the FPGA
from the Embedded USB Configuration Port.”
If a USB-equipped host PC is not available as a configuration source, then a Parallel Cable
4 (PC4) interface can be used instead by connecting a PC4 cable to J27.
It should be noted that if SelectMap byte-wide configuration from the on-board Platform
Flash configuration PROM is enabled, the FPGA Start-Up Clock should be set to CCLK in
the Startup Options section of the Process Options for the generation of the programming
file, otherwise JTAG Clock should be selected.
XUP Virtex-II Pro Development Systemwww.xilinx.com21
UG069 (v1.0) March 8, 2005
R
Chapter 2: Using the System
Figure 2-3 illustrates the configuration data path.
USB2
Microcontroller
& CPLD
GOLDEN
VERSION SELECT
USER
JTAG Port
JTAG Port
PLATFORM
FLASH
SMAP Port
Test JTAG PortConfig JTAG Port
SystemACE
Controller
PROM
CONFIG SOURCE
JTAG
CF Card/
MicroDrive
SMAP Port
Micro Port
CF CONFIG SELECT
FPGA
Micro PortJTAG Port
UG069_06_122704
Figure 2-3:Configuration Data Path
Four status LEDs show the configuration state of the XUP Virtex-II Pro Development
System at all times. The user can see the configuration source, configuration version, and
tell when the configuration has completed from the status LEDs shown in Tab le 2- 1.
Table 2-1: System Configuration Status LEDs
LED Status
System Status
D19 (Green)
PROM Config
D20 (Green)
CF Config
D14 (Amber)
GOLDEN Config
D4 (Red)
Done
SelectMAP USER LOADINGONOFFOFFOFF
SelectMAP USER COMPLETEDONOFFOFFON
SelectMAP GOLDEN LOADINGONOFFONOFF
SelectMAP GOLDEN
ONOFFONON
COMPLETED
JTAG COMPACT FLASH
OFFONOFFOFF
LOADING
JTAG COMPACT FLASH
OFFONOFFON
COMPLETED
22www.xilinx.comXUP Virtex-II Pro Development System
UG069 (v1.0) March 8, 2005
Clock Generation and Distribution
Table 2-1: System Configuration Status LEDs (Continued)
LED Status
System Status
D19 (Green)
PROM Config
D20 (Green)
CF Config
D14 (Amber)
GOLDEN Config
D4 (Red)
Done
JTAG USB or PC4 LOADINGOFFONOFFOFF
JTAG USB or PC4 COMPLETEDOFFONOFFON
Clock Generation and Distribution
The XUP Virtex-II Pro Development System supports six clock sources:
•A 100 MHz system clock (Y2),
•A 75 MHz clock (U10) for the MGTs operating the Serial Advanced Technology
•A 32 MHz clock (Y4) for the System ACE interfaces, and
•A clock from the Digilent high-speed expansion module.
R
The 75 MHz SATA clock is obtained from a high stability (20 ppm) 3.3V LVDSL differential
output oscillator, and the external MGT clock is obtained from two user-supplied SMA
connectors. The remaining three oscillators are all 3.3V single-ended LVTTL sources. Each
of the oscillators is equipped with a power supply filter to reduce the noise on the clock
outputs.
Tab le 2 -2 identifies the various clock connections for the FPGA.
Table 2-2:Clock Connections
SignalFPGA PinI/O Type
SYSTEM_CLOCKAJ15LVCMOS25
ALTERNATE_CLOCKAH16LVCMOS25
HS_CLKIN (from high speed
B16LVCMOS25
expansion port)
MGT_CLK_PF16LVDS_25
MGT_CLK_NG16LVDS_25
EXTERNAL_CLOCK_PG15LVDS_25
EXTERNAL_CLOCK_NF15LVDS_25
FPGA_SYSTEMACE_CLOCKAH15LVCMOS25
For the user to take advantage of the external differential clock inputs, two SMA
connectors must be installed at J23 and J24. These SMA connectors can be purchased from
Digi-Key® under the part number A24691-ND. Figure 2-4 identifies the location of the
external differential clock inputs.
XUP Virtex-II Pro Development Systemwww.xilinx.com23
UG069 (v1.0) March 8, 2005
R
Chapter 2: Using the System
Figure 2-4: External Differential Clock Inputs
The alternate clock input is obtained from a user-supplied 3.3V oscillator. The footprint on
the printed circuit board supports either a full size (21mm x 13mm) or half size (13mm x
13mm) through-hole oscillator. Figure 2-5 identifies the location of the alternate clock
input oscillator.
Figure 2-5: Alternate Clock Input Oscillator
Using the DIMM Module DDR SDRAM
The XUP Virtex-II Pro Development System is equipped with a 184-pin Dual In-line
Memory Module (DIMM) socket that provides access up to 2 GB of Double Data Rate
SDRAM. The DDR SDRAM is an enhancement to the traditional Synchronous DRAM. It
supports data transfer on both edges of each clock cycle, effectively doubling the data
throughput of the memory device.
The DDR SDRAM operates with a differential clock: CLK and CLK_Z (the transition of
CLK going high and CLK_Z going low is considered the positive edge of the CLK)
commands (address and control signals) are registered at every positive edge of the CLK.
Input data is registered on both edges of the data strobe (DQS), and output data is
referenced to both edges of DQS, as well as both edges of CLK.
A bidirectional data strobe is transmitted by the DDR SDRAM during Reads and by the
FPGA DDR SDRAM memory controller during Writes. DQS is edge-aligned with the data
for Reads and center-aligned with the data for Writes.
24www.xilinx.comXUP Virtex-II Pro Development System
UG069 (v1.0) March 8, 2005
Using the DIMM Module DDR SDRAM
Read and Write accesses to the DDR SDRAM are burst oriented: accesses start at a selected
location and continue for a programmed number of locations in a programmed sequence.
Accesses begin with the registration of an Active command, which is followed by a Read or
Write command. The address bits registered coincident with the Read or Write command
are used to select the bank and starting column location for the burst address.
DDR SDRAM provides for 2, 4, 8, or full-page programmable Read or Write burst lengths.
The allowable burst lengths depend on the specific DDR SDRAM used on the DIMM
module. This information can be obtained from the serial presence detect (SPD) EEPROM.
An auto-precharge function can be enabled to provide a self-timed precharge that is
initiated at the end of the burst sequence. As with standard SDRAMs, the pipelined
multibank architecture of DDR SDRAMs allows for concurrent operation, thereby,
providing high effective bandwidth by hiding row precharge and activation time.
The modules incorporate a serial presence detect (SPD) function implemented using a
2048-bit EEPROM. The first 128 bytes of the EEPROM are programmed by the module
manufacturer to identify the module type and various SDRAM timing parameters. The
remaining 128 bytes of EEPROM are available for use as non-volatile memory. The
EEPROM is accessed using a standard I
clock) and SDRAM_SDA (serial data) signals.
Data on the SDRAM_SDA signal can change only when the clock signal SDRAM_SCL is
low. Changes in the SDRAM_SDA data signal when SDRAM_SCL is high; this indicates a
start or stop bit condition as shown in Figure 2-6. A high-to-low transition of
SDRAM_SDA when SDRAM_SCL is high indicates a start bit condition, the start of all
commands. A low-to-high transition of SDRAM_SDA when SDRAM_ SCL is high
indicates a stop bit condition, terminating the command placing the SPD device into a low
power mode.
2
C bus protocol using the SDRAM_SCL (serial
R
SDRAM_SCL
SDRAM_SDA
START BITSTOP BIT
UG069_07_082604
Figure 2-6:Definition of Start and Stop Conditions
All commands commence with a start bit, followed by eight data bits. The transmitting
device, either the bus master or slave, releases the bus after transmitting eight bits. During
the ninth clock cycle, the receiver pulses the SDA data signal low to acknowledge that it
received the eight bits of data as shown in Figure 2-7.
XUP Virtex-II Pro Development Systemwww.xilinx.com25
UG069 (v1.0) March 8, 2005
R
SCL FROM
MASTER
SDA OUTPUT FROM
TRANSMITTER
SDA OUTPUT FROM
RECEIVER
Chapter 2: Using the System
1289
START BITACKNOWLEDGE
UG069_08_021405
Figure 2-7: Acknowledge Response from Receiver
The SPD device always responds with an acknowledge after recognition of a start
condition and its slave address (100). If a read command was issued, the SPD device
transmits eight bits of data, releases the SDRAM_SDA data line, and monitors the
SDRAM_SDA data line for an acknowledge. If an acknowledge is detected and no stop bit is
generated by the master, the SPD device continues to transmit data. If no acknowledge is
detected, the SPD device terminates further data transmission and waits for the stop bit
condition to return to low power mode.
MASTER
(FPGA)
SDRAM_SDA
SLAVE
(SPD EEPROM)
MASTER
(FPGA)
SDRAM_SDA
SPD device read and write operations are shown in Figure 2-8 and Figure 2-9.
SLAVE ADDRESS
READDATA nDATA n+1
START
001100011
A2A1A0
R/W
ACK
ACK
Figure 2-8: EEPROM Sequential Read
SLAVE ADDRESS
WRITEWORD ADDRESSDATA
START
001100011
A2
A1A0R/W
ACK
STOP
UG069_09_021405
STOP
SLAVE
(SPD EEPROM)
ACK
ACK
ACK
UG069_10_021405
Figure 2-9:EEPROM Write
26www.xilinx.comXUP Virtex-II Pro Development System
UG069 (v1.0) March 8, 2005
Using the DIMM Module DDR SDRAM
The ability to read the SPD EEPROM is important because the module specific timing
parameters are included in the EEPROM data and are required by the DDR SDRAM
controller to provide the highest memory throughput. The definitions of the SPD data
bytes are outlined in Tab le 2 -3.
Table 2-3:SPD EEPROM Contents
ByteDescription
0Number of used bytes in SPD EEPROM
1Total number of bytes on SPD EEPROM
2Memory type (DDR SDRAM = 07h)
3Number of row addresses
4Number of column addresses
5Number of ranks (01h)
6-7Module data width
8Module interface voltage (SSTL 2.5V = 04h)
R
9SDRAM cycle time (tck) (CAS LATENCY = 2.5)
10SDRAM access time (tac) (CAS LATENCY = 2.5)
11Module configuration type
12Refresh rate
13Primary SDRAM component width
14Error checking SDRAM component width
15Minimum clock delay from
Back-to-Back Random Column Addresses
16Supported burst lengths
17Number of banks on SDRAM component
18CAS latencies supported
19CS latency
20WE latency
21SDRAM module attributes
22SDRAM attributes
23SDRAM cycle time (tck) (CAS LATENCY =2)
24SDRAM access time (tac) (CAS LATENCY =2)
25SDRAM cycle time (tck) (CAS LATENCY =1)
26SDRAM access time (tac) (CAS LATENCY =1)
27Minimum ROW PRECHARGE time (trp)
28Minimum ROW ACTIVE to ROW ACTIVE (trrd)
XUP Virtex-II Pro Development Systemwww.xilinx.com27
UG069 (v1.0) March 8, 2005
R
Chapter 2: Using the System
Table 2-3:SPD EEPROM Contents (Continued)
ByteDescription
29Minimum RAS# to CAS# delay (trcd)
30Minimum RAS# pulse width (tras)
31Module rank density
32Command and address setup time (tas, tcms)
33Command and address hold time (tah, tcmh)
34Data setup time (tds)
35Data hold time (tdh)
36-40Reserved
41Minimum ACTIVE/AUTO REFRESH time
42Minimum AUTO REFRESH to ACTIVE/AUTO REFRESH
command period
43Max cycle time
44Max DQS-DQ skew
45Max READ HOLD time
46Reserved
47DIMM height
48-61Reserved
62SPD revision
63CHECKSUM for bytes 0-62
64-71Manufacturer's JEDEC ID code
72Manufacturing location
73-90Module part number (ASCII)
91-92Module revision code
93Year of manufacture (BCD)
94Week of manufacturer (BCD)
95-98Module serial number
99-127Reserved
128-255User defined contents
The DIMM module is supplied with three differential clocks. These three clock signals are
matched in length to each other and the DDR SDRAM feedback signals to allow for fully
synchronous operation across all banks of memory. The DDR SDRAM clocks are driven by
Double Data Rate (DDR) output registers, connected to a Digital Clock Manager (DCM)
with an optional external feedback connection. The DDR SDRAM controller logic is
described in DS425
28www.xilinx.comXUP Virtex-II Pro Development System
, PLB Double Data Rate (DDR) Synchronous DRAM (SDRAM) Controller.
UG069 (v1.0) March 8, 2005
Using the DIMM Module DDR SDRAM
The Xilinx PLB DDR SDRAM controller is a soft IP core designed for Xilinx FPGAs that
support different CAS latencies and memory data widths set by design parameters.
The DDR SDRAM controller logic instantiates DDR input and output registers on the
address, data, and control signals, so the clock to output delays match the clock output
delay. The DDR SDRAM clocking structure as shown in Figure 2-10 is a simplified version
of the clocking structure mentioned in DS425
R
.
ug069_23_021505
Figure 2-10: Clock Generation for the DDR SDRAM
XUP Virtex-II Pro Development Systemwww.xilinx.com29
UG069 (v1.0) March 8, 2005
R
Chapter 2: Using the System
Xilinx has qualified several different types of PC2100 memory modules for use in the XUP
Virtex-II Pro Development System. These modules cover various densities, organizations,
and features. The qualified memory modules are identified in Ta bl e 2-4 .
For an updated list of supported modules, consult the XUP Virtex-II Pro Development
System support Web site at:
http://www.xilinx.com/univ/xupv2p.html
The data bus width, number of ranks, address range, clock latency, and output type are all
parameters that are used by the DDR memory controller design to create the correct
memory controller for the user application.
Table 2-4:Qualified SDRAM Memory Modules
Crucial® Technology
Part Number
Memory
Organization
Number of
Ranks
Unbuffered or
Registered
CAS
Latency
CT6472Z265.18T*512 MB 64M X 72DualUnbuffered2.5
CT6464Z265.16T*512 MB 64M X 64DualUnbuffered2.5
CT6472Z265.9T*512 MB 64M X 72SingleUnbuffered2.5
CT6464Z265.8T*512 MB 64M X 64SingleUnbuffered2.5
CT1664Z265.4T*128 MB 16M X 64SingleUnbuffered2.5
Notes:
The * in the Crucial part number represents the revision number of the module, which is not
required to order the module.
These memory modules are designed for a maximum clock frequency of at least 133 MHz
and have a CAS latency of 2.5 (18.8 ns). The PLB Double Data Rate Synchronous DRAM
Controller supports CAS latencies of two or three clock cycles.
If the memory system is to operate at 100 MHz, then set the CAS latency parameter in the
controller design to 2 (20 ns). If full speed (133MHz) memory operation is required, then
set the CAS latency parameter in the controller design to 3 (22.6 ns).
Tab le 2 -5 provides the details on the FPGA to DDR SDRAM DIMM module connections.
Table 2-5:DDR SDRAM Connections
SignalDirection
DIMM
Module Pin
FPGA
Pin
I/O Type
SDRAM_DQ[0]I/O2C27SSTL2-II
SDRAM_DQ[1]I/O4D28SSTL2-II
SDRAM_DQ[2]I/O6D29SSTL2-II
SDRAM_DQ[3]I/O8D30SSTL2-II
SDRAM_DQ[4]I/O94H25SSTL2-II
SDRAM_DQ[5]I/O95H26SSTL2-II
SDRAM_DQ[6]I/O98E27SSTL2-II
SDRAM_DQ[7]I/O99E28SSTL2-II
SDRAM_DQS[0]I/O5E30SSTL2-II
SDRAM_DM[0]097U26SSTL2-II
30www.xilinx.comXUP Virtex-II Pro Development System
UG069 (v1.0) March 8, 2005
Using the DIMM Module DDR SDRAM
Table 2-5:DDR SDRAM Connections (Continued)
R
SignalDirection
DIMM
Module Pin
FPGA
Pin
I/O Type
SDRAM_DQ[8]I/O12J26SSTL2-II
SDRAM_DQ[9]I/O13G27SSTL2-II
SDRAM_DQ[10]I/O19G28SSTL2-II
SDRAM_DQ[11]I/O20G30SSTL2-II
SDRAM_DQ[12]I/O105L23SSTL2-II
SDRAM_DQ[13]I/O106L24SSTL2-II
SDRAM_DQ[14]I/O109H27SSTL2-II
SDRAM_DQ[15]I/O110H28SSTL2-II
SDRAM_DQS[1]I/O14J29SSTL2-II
SDRAM_DM[1]0107V29SSTL2-II
SDRAM_DQ[16]I/O23J27SSTL2-II
SDRAM_DQ[17]I/O24J28SSTL2-II
SDRAM_DQ[18]I/O28K29SSTL2-II
SDRAM_DQ[19]I/O31L29SSTL2-II
SDRAM_DQ[20]I/O114N23SSTL2-II
SDRAM_DQ[21]I/O117N24SSTL2-II
SDRAM_DQ[22]I/O121K27SSTL2-II
SDRAM_DQ[23]I/O123K28SSTL2-II
SDRAM_DQS[2]I/O25M30SSTL2-II
SDRAM_DM[2]0119W29SSTL2-II
SDRAM_DQ[24]I/O33R22SSTL2-II
SDRAM_DQ[25]I/O35M27SSTL2-II
SDRAM_DQ[26]I/O39M28SSTL2-II
SDRAM_DQ[27]I/O40P30SSTL2-II
SDRAM_DQ[28]I/O126P23SSTL2-II
SDRAM_DQ[29]I/O127P24SSTL2-II
SDRAM_DQ[30]I/O131N27SSTL2-II
SDRAM_DQ[31]I/O133N28SSTL2-II
SDRAM_DQS[3]I/O36P29SSTL2-II
SDRAM_DM[3]0129T22SSTL2-II
SDRAM_DQ[32]I/O53V27SSTL2-II
XUP Virtex-II Pro Development Systemwww.xilinx.com31
UG069 (v1.0) March 8, 2005
R
Chapter 2: Using the System
Table 2-5:DDR SDRAM Connections (Continued)
SignalDirection
DIMM
Module Pin
FPGA
Pin
I/O Type
SDRAM_DQ[33]I/O55Y30SSTL2-II
SDRAM_DQ[34]I/O57U24SSTL2-II
SDRAM_DQ[35]I/O60U23SSTL2-II
SDRAM_DQ[36]I/O146V26SSTL2-II
SDRAM_DQ[37]I/O147V25SSTL2-II
SDRAM_DQ[38]I/O150Y29SSTL2-II
SDRAM_DQ[39]I/O151AA29SSTL2-II
SDRAM_DQS[4]I/O56V23SSTL2-II
SDRAM_DM[4]0149W28SSTL2-II
SDRAM_DQ[40]I/O61Y26SSTL2-II
SDRAM_DQ[41]I/O64AA28SSTL2-II
SDRAM_DQ[42]I/O68AA27SSTL2-II
SDRAM_DQ[43]I/O69W24SSTL2-II
SDRAM_DQ[44]I/O153W23SSTL2-II
SDRAM_DQ[45]I/O155AB28SSTL2-II
SDRAM_DQ[46]I/O161AB27SSTL2-II
SDRAM_DQ[47]I/O162AC29SSTL2-II
SDRAM_DQS[5]I/O67AA25SSTL2-II
SDRAM_DM[5]0159W27SSTL2-II
SDRAM_DQ[48]I/O72AB25SSTL2-II
SDRAM_DQ[49]I/O73AE29SSTL2-II
SDRAM_DQ[50]I/O79AA24SSTL2-II
SDRAM_DQ[51]I/O80AA23SSTL2-II
SDRAM_DQ[52]I/O165AD28SSTL2-II
SDRAM_DQ[53]I/O166AD27SSTL2-II
SDRAM_DQ[54]I/O170AF30SSTL2-II
SDRAM_DQ[55]I/O171AF29SSTL2-II
SDRAM_DQS[6]I/O78AC25SSTL2-II
SDRAM_DM[6]0169W26SSTL2-II
SDRAM_DQ[56]I/O83AF25SSTL2-II
SDRAM_DQ[57]I/O84AG30SSTL2-II
32www.xilinx.comXUP Virtex-II Pro Development System
UG069 (v1.0) March 8, 2005
Using the DIMM Module DDR SDRAM
Table 2-5:DDR SDRAM Connections (Continued)
R
SignalDirection
DIMM
Module Pin
FPGA
Pin
I/O Type
SDRAM_DQ[58]I/O87AG29SSTL2-II
SDRAM_DQ[59]I/O88AD26SSTL2-II
SDRAM_DQ[60]I/O174AD25SSTL2-II
SDRAM_DQ[61]I/O175AG28SSTL2-II
SDRAM_DQ[62]I/O178AH27SSTL2-II
SDRAM_DQ[63]I/O179AH29SSTL2-II
SDRAM_DQS[7]I/O86AH26SSTL2-II
SDRAM_DM[7]0177W25SSTL2-II
SDRAM_CB[0]I/O44R28SSTL2-II
SDRAM_CB[1]I/O45U30SSTL2-II
SDRAM_CB[2]I/O49V30SSTL2-II
SDRAM_CB[3]I/O51T26SSTL2-II
SDRAM_CB[4]I/O134T25SSTL2-II
SDRAM_CB[5]I/O135T28SSTL2-II
SDRAM_CB[6]I/O142T27SSTL2-II
SDRAM_CB[7]I/O144U28SSTL2-II
SDRAM_DQS[8]I/O47T23SSTL2-II
SDRAM_DM[8]0140U22SSTL2-II
SDRAM_A[0]O48M25SSTL2-II
SDRAM_A[1]O43N25SSTL2-II
SDRAM_A[2]O41L26SSTL2-II
SDRAM_A[3]O130M29SSTL2-II
SDRAM_A[4]O37K30SSTL2-II
SDRAM_A[5]O32G25SSTL2-II
SDRAM_A[6]O125G26SSTL2-II
SDRAM_A[7]O29D26SSTL2-II
SDRAM_A[8]O122J24SSTL2-II
SDRAM_A[9]O27K24SSTL2-II
SDRAM_A[10]O141F28SSTL2-II
SDRAM_A[11]O118F30SSTL2-II
SDRAM_A[12]O115M24SSTL2-II
XUP Virtex-II Pro Development Systemwww.xilinx.com33
UG069 (v1.0) March 8, 2005
R
Chapter 2: Using the System
Table 2-5:DDR SDRAM Connections (Continued)
SignalDirection
DIMM
Module Pin
FPGA
Pin
I/O Type
SDRAM_A[13]O167M23SSTL2-II
SDRAM_CK0O137AC27SSTL2-II
SDRAM_CK0_ZO138AC28SSTL2-II
SDRAM_CK1O16AD29SSTL2-II
SDRAM_CK1_ZO17AD30SSTL2-II
SDRAM_CK2O76AB23SSTL2-II
SDRAM_CK2_ZO75AB24SSTL2-II
CLK_FEEDBACKO–G23LVCMOS25
CLK_FEEDBACKI–C16LVCMOS25
SDRAM_CKE0O21R26SSTL2-II
SDRAM_CKE1O111R25SSTL2-II
SDRAM_RAS_ZO154N29SSTL2-II
SDRAM_CAS_ZO65L27SSTL2-II
SDRAM_WE_ZO63N26SSTL2-II
SDRAM_S0_ZO157R24SSTL2-II
SDRAM_S1_ZO158R23SSTL2-II
SDRAM_BA0O59M26SSTL2-II
SDRAM_BA1O52K26SSTL2-II
SDRAM_SDAI/O91AF23LVCMOS25
SDRAM_SCLO92AF22LVCMOS25
SDRAM_SA0NA181–NA
SDRAM_SA1NA182–NA
SDRAM_SA2NA183–NA
Using the XSGA Output
The XSGA output on the XUP Virtex-II Pro Development System is made up from a triple
8-bit DAC (U29), a high density 15-pin D-Sub connector (J13), and IP placed in the FPGA
fabric. The FMS3818 video DAC is a low-cost DAC tailored to fit graphics and video
applications, with a maximum pixel clock of 180 MHz. The TTL data inputs and control
signals are converted into analog current outputs that can drive 25Ω to 37.5Ω loads,
corresponding to a doubly-terminated 50Ω to 75Ω load. The VGA_OUT_BLANK_Z input
overrides the RGB inputs and blanks the display output. This signal is equipped with a
pull-down resistor (R120) to keep the display blanked when the FPGA is not programmed
or XSGA output is not required by the user application. The XSGA output circuit is shown
in Figure 2-11.
34www.xilinx.comXUP Virtex-II Pro Development System
UG069 (v1.0) March 8, 2005
Using the XSGA Output
R
Design files supplied by Xilinx generate the required timing signals
VGA_OUT_BLANK_Z, VGA_HSYNCH, VGA_VSYNCH, and VGA_COMP_SYNCH, as
well as memory addressing for bit- and character-mapped display RAM. Charactermapped mode allows for the display of extended ASCII characters in an 8 x 8 pixel block
without having to draw the character pixel by pixel. Compile time parameters are passed
to the Verilog code that defines the XSGA controller operation. The 100 MHz clock is used
as a source for one of the DCMs to create the video clock. By setting appropriate M and D
values for the DCM, various VGA_OUT_PIXEL_CLOCK rates can be created.
XUP Virtex-II Pro Development Systemwww.xilinx.com35
UG069 (v1.0) March 8, 2005
R
J13
123456789
VGA OUTPUT
VGA_RED_OUT
VGA_GREEN_OUT
VGA_BLUE_OUT
R116
1011121314
R117
82R5 1%
15
HD-15PIN VGA DSUB
VGA_GND
82R5 1%
Chapter 2: Using the System
UG069_12_101804
VGA_GND
R115
R114
R113
VGA_HSYNCH
75R0 1%
75R0 1%
75R0 1%
33
IOR
U29
R0R1R2R3R4R5R6R7G0G1G2G3G4G5G6G7B0B1B2B3B4B5B6
40
41424344454647
VGA_VSYNCH
32
IOG
2345678
29
IOB
9
16171819202122
VGA_VCC
C458
VGA_GND
0.1UF
C457
0.1UF
R119
348.1%
GND1
GND2
GND3
GND4
VAA1
VAA2NCNCNCNC
GND5
GND6
39382827151448
R120
GND7
3K3
TRIPLE 8 BIT
VIDEO DAC
FMS3818KRC
GND
1
36
35
34
RSET
CLOCK
VGA_VCC
GND0
VDD
31123013242537
COMP
VREF
BLANK
SYNC
B7
23
11
10
VGA_OUT_RED0
VGA_OUT_RED1
VGA_OUT_RED2
VGA_OUT_RED3
VGA_OUT_RED4
VGA_OUT_RED5
VGA_OUT_RED6
VGA_OUT_RED7
VGA_OUT_GREEN0
VGA_OUT_GREEN1
VGA_OUT_GREEN2
VGA_OUT_GREEN3
VGA_OUT_BLUE0
VGA_OUT_GREEN4
VGA_OUT_BLUE1
VGA_OUT_GREEN5
VGA_OUT_GREEN6
VGA_OUT_GREEN7
VGA_OUT_BLUE2
VGA_OUT_BLUE3
VGA_OUT_BLUE4
VGA_OUT_BLUE5
VGA_OUT_BLUE6
VGA_OUT_BLUE7
VGA_COMP_SYNCH
VGA_OUT_BLANK_Z
R118
20R0 1%
VGA_OUT_PIXEL_CLOCK
Figure 2-11: XSGA Output
36www.xilinx.comXUP Virtex-II Pro Development System
UG069 (v1.0) March 8, 2005
Using the XSGA Output
R
Tab le 2 -6 lists the Verilog parameter values and the DCM settings for various XSGA output
formats.
Note:
The highlighted settings are exact VESA settings; the others are approximations.
Table 2-6: DCM and XSGA Controller Settings for Various XSGA Formats
Verilog Horizontal Timing Parameters
Output
Format
Pixel
Clock
DCM
Settings
H ActiveH FPH SynchH BPH Total
MHzMDPixelsPixelsPixelsPixelsPixels
640 x 480 @ 60 Hz25.0014640169648800
640 x 480 @ 72 Hz31.255166402440128832
640 x 480 @ 75 Hz31.25516640189642796
640 x 480 @ 85 Hz35.715146403248108828
800 x 600 @ 60 Hz40.0041080040128881056
800 x 600 @ 72 Hz50.001280056120641040
800 x 600 @ 75 Hz50.001280016801681064
800 x 600 @ 85 Hz55.00112080032641441040
1024 x 768 @ 60 Hz65.0013201024241361601344
1024 x 768 @ 72 Hz75.001520102416961721308
1024 x 768 @ 75 Hz80.00810102424961841328
1024 x 768 @ 85 Hz95.001920102448962081376
1280 x 1024 @ 60 Hz110.0011101280521202561708
1280 x 1024 @ 72 Hz130.0013101280161442481688
1280 x 1024 @ 75 Hz135.0027201280161442481688
1280 x 1024 @ 85 Hz150.00321280401442241688
1200 x 1600 @ 60 Hz160.0016101600561922962144
1200 x 1600 @ 70 Hz180.0018101600401842562080
Verilog Vertical Timing Parameters
Output
Format
Pixel
Clock
DCM
Settings
V Active V FPV SynchV BPV Total
MHzMDPixelsPixelsPixelsPixelsPixels
640 x 480 @ 60 Hz25.00144809229520
640 x 480 @ 72 Hz31.2551648010329522
640 x 480 @ 75 Hz31.2551648011231524
640 x 480 @ 85 Hz35.715144801323507
800 x 600 @ 60 Hz40.004106001423628
800 x 600 @ 72 Hz50.001260037623666
XUP Virtex-II Pro Development Systemwww.xilinx.com37
UG069 (v1.0) March 8, 2005
R
Chapter 2: Using the System
Table 2-6: DCM and XSGA Controller Settings for Various XSGA Formats (Continued)
Verilog Horizontal Timing Parameters
Output
Format
Pixel
Clock
DCM
Settings
H ActiveH FPH SynchH BPH Total
MHzMDPixelsPixelsPixelsPixelsPixels
800 x 600 @ 75 Hz50.00126001223626
800 x 600 @ 85 Hz55.0011206001318622
1024 x 768 @ 60 Hz65.0013207683629806
1024 x 768 @ 72 Hz75.0015207681324796
1024 x 768 @ 75 Hz80.008107682429803
1024 x 768 @ 85 Hz95.0019207682438812
1280 x 1024 @ 60 Hz110.001110102435421074
1280 x 1024 @ 72 Hz130.001310102424401070
1280 x 1024 @ 75 Hz135.002720102413381066
1280 x 1024 @ 85 Hz150.0032102413281056
1200 x 1600 @ 60 Hz160.001610120013401244
1200 x 1600 @ 70 Hz180.001810120013381242
The connections between the FPGA and the XSGA output DAC and connector are listed in
Tab le 2 -7 along with the required I/O characteristics.
Table 2-7: XSGA Output Connections
SignalDirection
Video
DAC or Output
Connector Pin
FPGA
Pin
I/O TypeDriveSlew
VGA_OUT_RED[0]O40G8LVTTL8 mASLOW
VGA_OUT_RED[1]O41H9LVTTL8 mASLOW
VGA_OUT_RED[2]O42G9LVTTL8 mASLOW
VGA_OUT_RED[3]O43F9LVTTL8 mASLOW
VGA_OUT_RED[4]O44F10LVTTL8 mASLOW
VGA_OUT_RED[5]O45D7LVTTL8 mASLOW
VGA_OUT_RED[6]O46C7LVTTL8 mASLOW
VGA_OUT_RED[7]O47H10LVTTL8 mASLOW
VGA_OUT_GREEN[0]O2G10LVTTL8 mASLOW
VGA_OUT_GREEN[1]O3E10LVTTL8 mASLOW
VGA_OUT_GREEN[2]O4D10LVTTL8 mASLOW
VGA_OUT_GREEN[3]O5D8LVTTL8 mASLOW
VGA_OUT_GREEN[4]O6C8LVTTL8 mASLOW
38www.xilinx.comXUP Virtex-II Pro Development System
UG069 (v1.0) March 8, 2005
Using the AC97 Audio CODEC and Power Amp
Table 2-7: XSGA Output Connections (Continued)
R
SignalDirection
Video
DAC or Output
Connector Pin
FPGA
Pin
I/O TypeDriveSlew
VGA_OUT_GREEN[5]O7H11LVTTL8 mASLOW
VGA_OUT_GREEN[6]O8G11LVTTL8 mASLOW
VGA_OUT_GREEN[7]O9E11LVTTL8 mASLOW
VGA_OUT_BLUE[0]O16D15LVTTL8 mASLOW
VGA_OUT_BLUE[1]O17E15LVTTL8 mASLOW
VGA_OUT_BLUE[2]O18H15LVTTL8 mASLOW
VGA_OUT_BLUE[3]O19J15LVTTL8 mASLOW
VGA_OUT_BLUE[4]O20C13LVTTL8 mASLOW
VGA_OUT_BLUE[5]O21D13LVTTL8 mASLOW
VGA_OUT_BLUE[6]O22D14LVTTL8 mASLOW
VGA_OUT_BLUE[7]O23E14LVTTL8 mASLOW
VGA_OUT_PIXEL_CLOCKO26H12LVTTL12 mASLOW
VGA_COMP_SYNCHO11G12LVTTL12 mASLOW
VGA_OUT_BLANK_ZO10A8LVTTL12 mASLOW
VGA_HSYNCHOJ13.14B8LVTTL12 mASLOW
VGA_VSYNCHOJ13.13D11LVTTL12 mASLOW
Using the AC97 Audio CODEC and Power Amp
The audio system on the XUP Virtex-II Pro Development System consists of a National
Semiconductor® LM4550 AC97 audio CODEC paired with a stereo power amplifier
(TPA6111A) made by Texas Instruments. The AC97-compliant audio CODEC is widely
used as the audio system in PCs and MACs, ensuring availability of drivers for these
devices.
The LM4550 audio CODEC supports the following features:
•Greater than 90 dB dynamic range
•18-bit Σ∆ converter architecture
•18-bit full-duplex, stereo CODEC
•Four analog line-level stereo inputs (one is used on the XUP Virtex-II Pro
Development System)
•Two analog line-level stereo outputs
•Mono MIC input with built-in 20 dB preamp, selectable for two sources (one used)
•VREF_OUT, reference voltage provides bias current for Electret microphones
•Power management support
•Full-duplex variable sample rates from 4 kHz to 48 kHz in 1 Hz increments
XUP Virtex-II Pro Development Systemwww.xilinx.com39
UG069 (v1.0) March 8, 2005
R
Chapter 2: Using the System
•Independently adjustable input volume controls with mute and a maximum gain of
12 dB and attenuation of 34.5 dB in 1.5 dB steps
•3D stereo enhancement
•PC Beep tone input passthrough to Line Out
The TPA6111A audio power amplifier supports the following features:
•Fixed Gain
•Stereo Power Amplifier delivers 150 mW per channel into 16Ω
•Click and Pop suppression
The National Semiconductor LM4550 uses 18-bit Sigma-Delta A/Ds and D/As, providing
90 dB of dynamic range. The implementation on this board, shown in Figure 2-12, allows
for full-duplex stereo A/D and D/A with one stereo input and two mono inputs, each of
which has separate gain, attenuation, and mute control. The mono inputs are a
microphone input with 2.2V bias and a beep tone input from the FPGA. The
BEEP_TONE_IN (TTL level) is applied to both outputs, even if the CODEC is held in reset
to allow test tones to be heard. The CODEC has two stereo line-level outputs with
independent volume controls. One of the line-level outputs drives the audio output
connector and the second line-level output drives the on-board power amplifier shown in
Figure 2-13.
The power amplifier is capable of producing 150 mW of continuous power per channel
into 16Ω loads, such as headphones. The assertion of the AUDIO_AMP_SHUTDOWN
signal by the CODEC causes the audio power amplifier to turn off.
The TPA6111A audio power amplifier contains circuitry to minimize turn-on transients,
that is, click or pops. Tu rn - o n refers to either power supply turn-on or the device coming out
of CODEC controlled shutdown. When the device is turning on, the amplifiers are
internally muted until the bypass pin has reached half the supply voltage. The turn-on
time is controlled by C9.
The power amplifier was included to support two output modes, line out mode and power
amp output mode. The line level output attenuation is controlled by the CODEC volume
control register 04h, and the power amp output attenuation is controlled by CODEC
volume control register 02h.
40www.xilinx.comXUP Virtex-II Pro Development System
UG069 (v1.0) March 8, 2005
Using the AC97 Audio CODEC and Power Amp
AC97_SDATA_OUT
AC97_SYNCH
R170
3K3
R169
3K3
AUDIO_RESET_Z
AC97_SDATA_IN
AC97_BIT_CLOCK
R
UG069_14_101804
VCC3V3
AUDIO_5V
C31C30C29
10UF 16V
C28C27C26
0.1UF0.1UF
C32
10UF 16V
0.1UF0.1UF
7
4
9
1
40
1UF
43
44
38
25
42
26
AUDIO_GND
VCC3V3
R15
3K3
GND
DVSS1
DVSS0
DVDD1
DVDD0
NC2
NC1
NC0
AVDD1
AVDD0
AVSS1
AVSS0
12242321222019181716151413
BEEP_TONE
C33
R167 56R2 1%
RESET
SDATA_IN
SDATA_OUT
U9
PC_BEEP
LINE_IN_R
LINE_IN_L
AUDIO_LINE_IN_LEFT
AUDIO_LINE_IN_RIGHT
1UF
R168 56R2 1%
R18
10K
46
45
6108511
CS0
CS1
SYNCH
BIT_CLOCK
AC97 CODEC
AUDIO MIXER AND CODEC
MIC1
MIC2
CD_4
CD_GND
CD_L
MIC_IN
AUDIO_AMP_SHUTDOWN
AUDIO_LINE_OUT_LEFT
AUDIO_LINE_OUT_RIGHT
47
413938
LNLVL_OUT_L
LNLVL_OUT_R
AMP_PWR_DWN
VIDEO_R
VIDEO_L
AUX_R
AUDIO_RIGHT
AUDIO_LEFT
35
LINE_OUT_L
LINE_OUT_R
AUX_L
PHONE_IN
37
MONO
C34
MONO_OUT
48
1UF
R19
SPDIF
47K
XTAL_OUT
XTAL_IN
VREF
VREF_OUT
RX3D
CX3D
FILT_R
FILT_L
AFLT2
AFILT1
0.1UF
C35
3
2
27
28
33
C37
34
32
31
30
29
AUDIO_GND
AUDIO_GND
AUDIO_5V
R21
10K
Y1
100NF
C38
270PF
C36
C39
270PF
24.576 MHz
R20
47NF
1M0
22PF22PF
C43
C40C41C42
AUDIO_GND
GNDGND
1UF
1UF
AUDIO_GND
MIC_POWER
C45
C44
10UF 16V
100NF
AUDIO_GND
R17
4K7
AUDIO_GND
R16
6K8
BEEP_TONE_IN
Figure 2-12: AC97 Audio CODEC
XUP Virtex-II Pro Development Systemwww.xilinx.com41
UG069 (v1.0) March 8, 2005
R
Chapter 2: Using the System
UPPER
J14B
HZ0805E601R-00
HZ0805E601R-00
L1
L2
22OUF 10V
22OUF 10V
C1
C3
AMP_OUT_LEFT
AMP_OUT_RIGHT
UPPER
MIC_IN
DUAL_STEREO_JACK
J15B
DUAL_STEREO_JACK
MIC_POWER
UG069_13_101804
1UF
HZ0805E601R-00
HZ0805E601R-00
470PF
C13
L4
L3
R3
47K
470PF470PF
C6C7
R2
47K
AUDIO_GND AUDIO_GND AUDIO_GND AUDIO_GNDAUDIO_GND
1UF
C10
R7
47K
470PF
C12
R6
47K
1UF
C11
AUDIO_LINE_OUT_LEFT
AUDIO_LINE_OUT_RIGHT
AUDIO_GND AUDIO_GND AUDIO_GNDAUDIO_GND
AUDIO_GND
2K0
R10
47K
R12
HZ0805E601R-00
HZ0805E601R-00
L6
L8
J14A
LOWER
C18
C21C22C23
DUAL_STEREO_JACK
AUDIO_GND
470PF0.1UF
470PF
AUDIO_GNDAUDIO_GND
AUDIO_GND
AUDIO_5V
AUDIO_GND
0.1UF10UF 16V
C4C5
AMP_OUT_LEFT
AMP_OUT_RIGHT
7
150 mW AUDIO
POWER AMP
20K0
1UF
4
7
4
3
1UF20K0
BYPASSGND
TPA6111A2DR
1UF
C9
AUDIO_GND
AUDIO_GND
OUT_B
IN_B
6
R4
C8
1
VDD
OUT_A
U8
SHUTDOWN
IN_A
58
2
R1
C2
AUDIO_AMP_SHUTDOWN
AUDIO_LINE_IN_RIGHT
AUDIO_LINE_IN_LEFT
1UF
1UF
C17
C16
47K
R9
R5
C14
27K4
22pF
C15
R8
27K4
22pF
J15A
HZ0805E601R-00
L5
R14
R13
47K47K
470PF
C20
47K
R11
470PF
C19
AUDIO_GND AUDIO_GND AUDIO_GND AUDIO_GND
HZ0805E601R-00L7
AUDIO_GND
DUAL_STEREO_JACK
LOWER
AUDIO_RIGHT
AUDIO_LEFT
Figure 2-13: Audio Power Amplifier
42www.xilinx.comXUP Virtex-II Pro Development System
UG069 (v1.0) March 8, 2005
Using the LEDs and Switches
The FPGA contains the AC97 controller that provides control information and PCM data
on the outbound link and receives status information and PCM data in the inbound link.
The complete AC97 interface consists of four signals, the clock AC97_BIT_CLOCK, a
synchronization pulse AC97_SYNCH, and the two serial data links AC97_SDATA_IN and
AC97_SDATA_OUT listed in Tabl e 2-8 .
The CODEC is held in a reset state until the AUDIO_RESET_Z signal is driven high by the
FPGA overriding a pull-down resistor (R15).
Table 2-8:AC97 Audio CODEC Connections
AC97_SDATA_OUTOE8LVTTL8 mASLOW
AC97_SDATA_INIE9LVTTL––
AC97_SYNCHOF7LVTTL8 mASLOW
AC97_BIT_CLOCKIF8LVTTL––
AUDIO_RESET_ZOE6LVTTL8 mASLOW
BEEP_TONE_INOE7LVTTL8 mASLOW
R
SignalDirectionFPGA PinI/O TypeDriveSlew
Using the LEDs and Switches
The XUP Virtex-II Pro Development System includes four LEDs as visual indicators for the
user to define, as well as four DIP switches and five pushbuttons for user-defined use. The
pushbuttons are arranged in a diamond shape with the ENTER pushbutton in the center of
the diamond. This placement can be used for object movement in a game. None of the DIP
switches or pushbuttons have external de-bouncing circuitry, because this should be
provided in the FPGA application. Ta bl e 2 -9 identifies the connections between the user
switches, user LEDs, and the FPGA.
Table 2-9:User LED and Switch Connections
SignalDirectionFPGA PinI/O TypeDriveSlew
LED_0OAC4LVTTL12 mASLOW
LED_1OAC3LVTTL12 mASLOW
LED_2OAA6LVTTL12 mASLOW
LED_3OAA5LVTTL12 mASLOW
SW_0IAC11LVCMOS25––
SW_1IAD11LVCMOS25––
SW_2IAF8LVCMOS25––
SW_3IAF9LVCMOS25––
PB_ENTERIAG5LVTTL––
PB_UPIAH4LVTTL––
PB_DOWNIAG3LVTTL––
XUP Virtex-II Pro Development Systemwww.xilinx.com43
UG069 (v1.0) March 8, 2005
R
Chapter 2: Using the System
Table 2-9:User LED and Switch Connections (Continued)
SignalDirectionFPGA PinI/O TypeDriveSlew
PB_LEFTIAH1LVTTL––
PB_RIGHTIAH2LVTTL––
Using the Expansion Headers and Digilent Expansion Connectors
The XUP Virtex-II Pro Development System allows for four user-supplied expansion
headers that are tailored to accept ribbon cables, and two front mounted connectors that
are designed to accept Digilent peripheral devices and a single Digilent high-speed port. A
total of 80 low-speed signals are provided, with most of the signals shared between the
headers (J1-4) and the front-mounted connectors (J5-6). All of these signals are equipped
with over-voltage protection devices (J34-41) to protect the Virtex-II Pro FPGA. The IDT™
QuickSwitch devices (IDTQS32861) provide protection from signal sources up to 7V.
Tab le 2 -1 0 through Ta bl e 2 -1 6 provide the FPGA connection information and outline the
signals that are shared between the two expansion connector types.
Various power supply voltages are available on the expansion connectors, 2.5V, 3.3V, and
5.0V, depending on the connector type. The expansion headers are positioned to prevent
the installation of a ribbon cable connector across two of the expansion headers. Every
second signal in the ribbon cable is a ground signal to provide the best signal integrity at
the user’s target. The output of the over-voltage protection device follows the input
voltage up to a diode drop below the V
with a V
of 3.3V, the output clamps at -2.5V. This gives 500 mV of input switching
CC
margin for both LVTTL and LVCMOS3.3, which have a V
The expansion headers (J1-J4) are user installed items. These headers can be purchased
from Digikey under the part number S2012-30-ND. Figure 2-14 identifies the location of
the expansion headers.
rail; at which time, the voltage is clamped. So
CC
of 2.0V minimum.
IH
Figure 2-14: Expansion Headers
44www.xilinx.comXUP Virtex-II Pro Development System
UG069 (v1.0) March 8, 2005
Using the Expansion Headers and Digilent Expansion Connectors
In addition to the two low-speed expansion connectors, a single 100-pin high-speed
connector is also provided. This connector provides 40 single-ended user I/Os or 34
differential pairs with additional clock resources. These signals are not shared with any
other connector. Ta bl e 2- 17 provides the pinout information.
The front-mounted Digilent expansion connectors, low speed and high speed, provide the
capability of extending the JTAG-based configuration bitstream to the attached peripheral
cards if required.
For pinout information on the Digilent peripheral boards that are compatible with the XUP
Virtex-II Pro Development System, consult the Digilent Web site at:
http://www.digilentinc.com
Note: In Ta bl e 2 - 10 through Ta bl e 2 - 1 6 , the power rails available on the expansion headers and
connectors are color coded, so they can be easily located in the pinout tables.
Table 2-10:Top Expansion Header Pinout
R
J1
Pin
1
3
5
7
9
Signal
VCC2V5–––
VCC2V5–––
VCC3V3–J5.3 J6.3–
VCC3V3–J5.3 J6.3–
VCC3V3–J5.3 J6.3–
FPGA
Pin
Digilent
EXP Pin
I/O Type
11EXP_IO_0K2–LVTTL
13EXP_IO_1L2–LVTTL
15EXP_IO_2N8–LVTTL
17EXP_IO_3N7–LVTTL
19EXP_IO_4K4–LVTTL
21EXP_IO_5K3–LVTTL
23EXP_IO_6L1–LVTTL
25EXP_IO_7M1–LVTTL
27EXP_IO_8N6J5.4LVTTL
29EXP_IO_9N5J5.5LVTTL
31EXP_IO_10L5J5.6LVTTL
33EXP_IO_11L4J5.7LVTTL
35EXP_IO_12M2J5.8LVTTL
37EXP_IO_13N2J5.9LVTTL
39EXP_IO_14P9J5.10LVTTL
41EXP_IO_15R9J5.11LVTTL
43EXP_IO_16M4J5.12LVTTL
XUP Virtex-II Pro Development Systemwww.xilinx.com45
The CPU Debug port (J36) is a right angle header that provides connections to the
debugging resources of the PowerPC 405 CPU core.
The PowerPC 405 CPU cores include dedicated debug resources that support a variety of
debug modes for debugging during hardware and software development. These debug
resources include:
•Internal debug mode for use by ROM monitors and software debuggers
•External debug mode for use by JTAG debuggers
•Debug wait mode, which allows the servicing of interrupts while the processor
appears to be stopped
•Real-time trace mode, which supports event triggering for real time tracing
FPGA
Pin
Differential
Pair
I/O Type
Debug modes and events are controlled using debug registers in the processor. The debug
registers are accessed either through software running on the processor or through the
JTAG port. The debug modes, events, controls, and interfaces provide a powerful
combination of debug resources for hardware and software development tools.
The JTAG port interface supports the attachment of external debug tools, such as the
powerful ChipScope™ Integrated Logic Analyzer, a powerful tool providing logic
analyzer capabilities for signals inside an FPGA, without the need for expensive external
instrumentation. Using the JTAG test access port, a debug tool can single-step the
processor and examine the internal processor state to facilitate software debugging. This
capability complies with standard JTAG hardware for boundary scan system testing.
External debug mode can be used to alter normal program execution. It provides the
ability to debug system hardware as well as software. The mode supports multiple
functions: starting and stopping the processor, single-stepping instruction execution,
setting breakpoints, as well as monitoring processor status. Access to processor resources
is provided through the CPU Debug Port.
The PPC405 JTAG Debug Port supports the four required JTAG signals: CPU_TCK,
CPU_TMS, CPU_TDO, and CPU_TDI. It also implements the optional CPU_TRST signal.
The frequency of the JTAG clock signal, CPU_TCK, can range from 0 MHz up to one-half
of the processor clock frequency. The JTAG debug port logic is reset at the same time the
system is reset, using the CPU_TRST signal. When CPU_TRST is asserted, the JTAG TAP
controller returns to the test-logic reset state.
58www.xilinx.comXUP Virtex-II Pro Development System
UG069 (v1.0) March 8, 2005
Using the CPU Debug Port and CPU Reset
Figure 2-15 shows the pinout of the header used to debug the operation of software in the
CPU. This is accomplished using debug tools, such as the Xilinx Parallel Cable IV or third
party tools.
R
CPU TMS
CPU HALT Z
151
16
GND
CPU TCK
CPU TDI
CPU TDO
2
CPU TRST
3.3V
UG069_15_082404
Figure 2-15:CPU Debug Connector Pinouts
The JTAG debug resources are not hardwired to specific pins and are available for
attachment in the FPGA fabric, making it possible to route these signals to whichever
FPGA pins the user prefers to use. The signal-pin connections used on the XUP VirtexII Pro Development System are identified in Tab le 2- 17 along with the recommended I/O
characteristics. Level shifting circuitry is provided for all signals to convert from the 3.3V
levels at the connector to the 2.5V levels at the FPGA.
Table 2-17:CPU Debug Port Connections and CPU Reset
SignalDirectionFPGA PinI/O TypeDRIVESlew
PROC_RESET_ZIAH5LVTTL––
CPU_TDOOAG16LVCMOS2512 mASLOW
CPU_TDIIAF15LVCMOS25––
CPU_TMSIAJ16LVCMOS25––
CPU_TCKIAG15LVCMOS25––
CPU_TRSTIAC21LVCMOS25––
CPU_HALT_ZIAJ23LVCMOS25––
The RESET_RELOAD pushbutton (SW1) provides two different functions depending on
how long the switch is depressed. If the switch is activated for more than 2 seconds, the
XUP Virtex-II Pro Development System undergoes a complete reset and reloads the
selected configuration. If, however, the switch is activated for less than 2 seconds, a
XUP Virtex-II Pro Development Systemwww.xilinx.com59
UG069 (v1.0) March 8, 2005
R
Chapter 2: Using the System
processor reset pulse of 100 microseconds is applied to the PROCESSOR_RESET_Z signal.
The RESET_RELOAD circuit is shown in Figure 2-16.
ug069_16_021505
Figure 2-16: RELOAD and CPU RESET Circuit
Using the Serial Ports
Serial ports are useful as simple, low-speed interfaces. These ports can provide
communication between a Host machine and a Peripheral machine, or Host-to-Host
communications. The XUP Virtex-II Pro Development System provides two different types
of serial ports, a single RS-232 port and two PS/2 ports.
The RS-232 standard specifies output voltage levels between -5V to -15V for a logical 1, and
+5V to +15V for a logical 0. Inputs must be compatible with voltages in the range -3V to 15V for a logical 1 and +3V to +15V for a logical 0. This ensures that data is correctly read
even at the maximum cable length of 50 feet. These signaling levels are outside the range of
voltages that can be supported by the Virtex-II Pro family of FPGAs, requiring the use of a
transceiver. The connector is a DCE-style that allows the use of a straight-through 9-pin
serial cable to connect to the DTE-style serial port connector available on most personal
computers and workstations. A null-modem cable is not required. Figure 2-17 shows the
implementation of the serial port used on the XUP Virtex-II Pro Development System.
The MAX3388E is a 2.5V powered device that operates as a transceiver to shift the
signaling levels from the voltages supported by the FPGA to those required by the RS-232
specification. The MAX3388E has two receivers and three transmitters and is capable of
running at data rates up to 460 kb/s while maintaining RS-232-compliant output levels.
There are five signals from the FPGA to the RS-232 serial port: RS232_TX_DATA,
RS232_DSR_OUT, RS232_CTS_OUT, RS232_RX_DATA, and RS232_RTS_IN. The Transmit
Data and Receive Data provide bidirectional data transmission, while Request To Send,
Clear To Send, and Data Set Ready provide for hardware flow control across the serial link.
Tab le 2 -1 7 identifies the RS-232 signal connections to the FPGA.
IBM developed the PS/2 ports for peripherals as an alternative to serial ports and
dedicated keyboard ports. These ports have become standard connectors on PCs for
connecting both keyboards and mice. They use a 6-pin mini-DIN connector and a
bidirectional synchronous serial interface, with a bidirectional data signal and a
unidirectional clock. The XUP Virtex-II Pro Development System provides two PS/2 ports,
for keyboard and mouse attachment. The PC mouse and keyboard use the two-wire RS/2
serial bus to communicate with the host FPGA. The PS/2 bus includes both clock and data
with identical signal timings and both user 11-bit data words that include a start bit, stop
60www.xilinx.comXUP Virtex-II Pro Development System
UG069 (v1.0) March 8, 2005
Using the Serial Ports
R
bit, and odd parity. The data packets are organized differently for mouse and keyboard
data. In addition, the keyboard interface supports bidirectional data transfer so the host
device can drive the statusLEDs on the keyboard.
VCC2V5
RS232_DSR_OUT
RS232_TX_DATA
RS232_CTS_OUT
RS232_RX_DATA
RS232_RTS_IN
0.1UF
0.1UF
C446
C449
1
3
4
5
7
8
9
13
12
10
11
242314
SHDN
VCCVL
C1+
2.5V RS-232
C1-
Transceiver
C2+
C1-
T1IN
T2IN
T3IN
R1OUT
R2OUT
LOUT
SWOUT
GND
T1OUT
T2OUT
T3OUT
R1IN
R2IN
SWIN
22
2
V+
6
V-
21
20
19
18
17
16
LIN
15
MAC3388ECUG
C447
0.1UF
C448
0.1UF
DSR
RXD
CTS
TXD
RTS
C445U28
0.1UF
J11
1
2
3
4
5
6
7
8
9
RS-232 DCE
UG069_17_021405
Figure 2-17: RS-232 Serial Port Implementation
The PS/2 port operates as a serial interface with a bidirectional data signal and a
unidirectional clock signal. Both of these signals operate as open-drain signals, defaulting
to a logical 1, at 5V through the use of a week pull-up resistor. To transmit a logical 0, the
signal line is actively pulled to ground. In the case of the data line, both the host and the
attached peripheral are able to drive the signal low. In the case of the clock signal, only the
host is able to drive the signal low, giving the host control of the speed of the interface.
Figure 2-18 shows the implementation of the PS/2 keyboard port used on the XUP Virtex-
II Pro Development System. The implementation of the PS/2 mouse port is identical
except for the signal names and the part reference designator.
The bidirectional level shifter shown in Figure 2-18 is used to interconnect two sections of
the PS/2 port, each section with a different power supply voltage and different logic levels.
The level shifter for each signal consists of one discrete N-channel enhancement MOS-FET.
The gate of the transistor must be connected to the lowest supply voltage (VCC3V3); the
source connects to the signal on the lower voltage side; and the drain connects to the signal
on the higher voltage side.
XUP Virtex-II Pro Development Systemwww.xilinx.com61
UG069 (v1.0) March 8, 2005
R
VCC5V0
Chapter 2: Using the System
.
VCC3V3
R106
2K0
KBD_CLOCK
KBD_DATA
UG069_18_101804
J12A
UPPER
STACKED_PS2_6PIN
L54
HZ0805E601R-00
L53 HZ0805E601R-00
C441
470PF
BIDIRECTIONAL
LEVEL
SHIFTER
R108
R107
3K3
3K3
C442
470PF
GNDGNDGND
3
3
U24
BSS138
D
U25
U24
BSS138
BSS138
D
3
0
3
0
H CHAHH CHAH
2
1
2
1
R105
2K0
Figure 2-18:PS/2 Serial Port Implementation
If no device is actively pulling the signal low, the pull-up resistor pulls up the signal on the
FPGA side. The gate and source of the MOS-FET are both at the same potential and the
MOS-FET is not conducting. This allows the signal on the peripheral side to be pulled up
by the pull-up resistor. So both sections of the signal are high, but at different voltage
levels.
If the FPGA actively pulls the signal low, the MOS-FET begins to conduct and pulls the
peripheral side low as well.
If the peripheral side pulls the signal low, the FPGA side is initially pulled low via the
drain-substrate diode of the MOS-FET. After the threshold is passed, the MOS-FET begins
to conduct and the signal is further pulled down via the conducting MOS-FET.
Tab le 2 -1 8 identifies the PS/2 signal connections to the FPGA.
Table 2-18:Keyboard, Mouse, and RS-232 Connections
SignalDirectionFPGA PinI/O TypeDriveSlew
KBD_CLOCKI/OAG2LVTTL8 mASLOW
KBD_DATAI/OAG1LVTTL8 mASLOW
MOUSE_CLOCKI/OAD6LVTTL8 mASLOW
MOUSE_DATAI/OAD5LVTTL8 mASLOW
RS232_TX_DATAOAE7LVCMOS258 mASLOW
RS232_RX_DATAIAJ8LVCMOS25––
RS232_DSR_OUTOAD10LVCMOS258 mASLOW
RS232_CTS_OUTOAE8LVCMOS258 mASLOW
RS232_RTS_INIAK8LVCMOS25––
Using the Fast Ethernet Network Interface
The 10/100 Ethernet is a network protocol, defined by the IEEE 802.3 standard, which
includes a 10 Mb/s Ethernet and a 100 Mb/s Ethernet. The XUP Virtex-II Pro
Development System has been designed to support Internet connectivity using an
Ethernet connection.
62www.xilinx.comXUP Virtex-II Pro Development System
UG069 (v1.0) March 8, 2005
Using the Fast Ethernet Network Interface
The Ethernet network interface is made up of three distinct components: the Media Access
Controller (MAC) contained in the FPGA, a physical layer transceiver (PHY), and the
Ethernet coupling magnetics.
The LXT972A (U12) is an IEEE 802.3-compliant Fast Ethernet physical layer (PHY)
transceiver that supports both 100BASE-TX and 10BASE-T operation. It provides the
standard Media Independent Interface (MII) for easy attachment to 10/100 (MACs). The
LXT972A supports full-duplex operation at 10 Mb/s and 100 Mb/s. The operational mode
can be set using auto-negotiation, parallel detection, or manual control.
The LXT972A performs all functions of the physical coding sublayer (PCS), the physical
media attachment (PMA) sublayer, and the physical media dependent (PMD) sublayer for
100BASE-TX connections.
The LXT972A reads its three configuration pins on power up to check for forced operation
settings. If it is not configured for forced operation at 10 Mb/s or 100 Mb/s, the device uses
auto-negotiation/parallel detection to automatically determine line operating conditions.
If the PHY on the other end of the link supports auto-negotiation, the LXT972A autonegotiates with it, using fast link pulse (FLP) bursts. If the other PHY does not support
auto-negotiation, the LXT972A automatically detects the presence of either link pulses
(10BASE-T) or idle symbols (100BASE-TX) and sets its operating mode accordingly.
The LXT972A configuration pins are set to allow for auto-negotiation, 10 Mb/s or
100 Mb/s, full-duplex or half-duplex operation. These settings can be overridden by
setting control bits in the Media Independent Interface (MII) registers.
R
The slew rate of the transmitter outputs is controlled by the two slew control inputs. It is
recommended that the slowest slew rate be set by driving both of the slew inputs with a
logical 1.
Three LEDs are available to provide visual status information about the Ethernet link
connection. If a link has been established, the LINK UP LED is turned on. If the link is a
100 Mb/s link, then the SPEED LED also turns on. The RX_DATA LED blinks, indicating
that packets are being received. Setting control bits in the MII registers can alter the
function of the three LEDs.
The LX972A provides the interface to the physical media; the MAC resides in the FPGA
and is available as an IP core.
The 10/100 Ethernet requires transformer coupling between the PHY and the RJ-45
connector to provide electrical protection to the system. The magnetics used on the XUP
Virtex-II Pro Development System are integrated into the RJ45 connector (J10) from the
FastJack™ series of connectors from Halo Electronics, Inc. The HFJ11-2450 provides a
significant real estate reduction over non-integrated solutions. Tab le 2- 18 identifies the
connections between the FPGA and the PHY.
The type of network cable that is used with the XUP Virtex-II Pro Development System
depends on how the system is connected to the network. If the XUP Virtex-II Pro
Development System is connected directly to a host computer, then a cross-over Ethernet
cable is required. However, if the system is connected to the network through a hub or
router, then a normal straight-through Ethernet cable is required.
XUP Virtex-II Pro Development Systemwww.xilinx.com63
UG069 (v1.0) March 8, 2005
R
Chapter 2: Using the System
Figure 2-19 provides a block diagram of the Ethernet interface.
The XUP Virtex-II Pro Development System includes a Dallas Semiconductor DS2401P
Silicon Serial Number (U13). This device provides a unique identity for each circuit board
which can be determined with a minimal electronic interface. The DS2401P consists of a
factory laser programmed, 64-bit ROM that includes a unique 48-bit serial number, an 8-bit
CRC, and an 8-bit family device code. Data is transferred serially via the 1-Wire protocol,
which requires only a single data lead and a ground return. Power for reading the device
is derived from the data line with no requirement for an additional power supply. The
unique 48-bit serial number should not be used as the MAC address for the Ethernet
interface, because this number has not been registered as a valid Ethernet MAC address.
The XUP Virtex-II Pro Development System printed circuit board includes a label that
contains the board serial number, obtained from the DS2401P Silicon Serial Number, as
well as a valid Ethernet MAC address that has been registered with the IEEE. Xilinx
maintains a cross reference list matching the board serial number with the assigned
Ethernet MAC address on the XUP Virtex-II Pro Development System support Web page.
Xilinx provides the IP for the 1-Wire interface and application note XAPP198
Synthesizable
FPGA Interface for Retrieving ROM Number from 1-Wire Devices describes this interface.
Table 2-19:10/100 ETHERNET Connections
SignalDirectionFPGA PinI/O TypeDriveSlew
TX_DATA[0]OJ7LVTTL8 mASLOW
TX_DATA[1]OJ8LVTTL8 mASLOW
TX_DATA[2]OC1LVTTL8 mASLOW
TX_DATA[3]OC2LVTTL8 mASLOW
TX_ERROROH2LVTTL8 mASLOW
64www.xilinx.comXUP Virtex-II Pro Development System
UG069 (v1.0) March 8, 2005
Using System ACE Controllers for Non-Volatile Storage
Using System ACE Controllers for Non-Volatile Storage
In addition to programming the FPGA and storing bitstreams, the System ACE controller
can be used for general-purpose non-volatile storage. Each System ACE controller
provides an MPU interface to allow a microprocessor to access the attached CompactFlash
or IBM Microdrive, allowing this storage media to be used as a file system.
The MPU interface provides a useful means of monitoring the status of and controlling the
System ACE controller, as well as CompactFlash card READ/WRITE data. The MPU is not
required for normal operation, but when it is used, it provides numerous capabilities. This
interface enables communication between an MPU device, a CompactFlash card, and the
FPGA target system.
The MPU interface is composed of a set of registers that provide a means for
communicating with CompactFlash control logic, configuration control logic, and other
resources in the System ACE controller. This interface can be used to read the identity of a
CompactFlash device and read/write sectors from or to a CompactFlash device.
The MPU interface can also be used to control configuration flow. It enables monitoring of
the configuration status and error conditions. The MPU interface can be used to delay
XUP Virtex-II Pro Development Systemwww.xilinx.com65
UG069 (v1.0) March 8, 2005
R
Chapter 2: Using the System
configuration, start configuration, select the source of configuration, control the bitstream
revision, and reset the device.
For the System ACE controller to be properly synchronized with the MPU, the clocks must
be synchronized. The clock traces on the XUP Virtex-II Pro Development System that drive
the System ACE controller and the MPU interface sections of are matched in length to
maintain the required timing relationship.
The System ACE controller has very specific requirements for the way the file system is
created on the CompactFlash device. The FAT file system processing code cannot handle
more than one ROOT directory sector, 512 bytes, or 16 32-bit file/directory entries. If the
ROOT directory has more than 16 file/directory entries (including deleted entries), the
System ACE controller does not function properly. In addition, the System ACE controller
cannot handle CompactFlash devices whose FAT file system is set up with 1 cluster = 1
sector = 512 bytes.
The CompactFlash device must be formatted so that 1 cluster > 512 bytes, and the boot
parameter block must be setup with only 1 reserved sector. It is typical of newer operating
systems to format CompactFlash devices with more that 1 reserved sector.
The workaround for these System ACE controller requirements is to format the card with
a utility such as mkdosfs found at http://www.mager.org/mkdosfs/
The following command line produces the correct format on drive X: with a volume name
of XLXN_XUP.
For more information on the System ACE MPU interface, consult the System ACE
CompactFlash Solution (DS080
) data sheet.
Tab le 2 -2 0 outlines the MPU interface connections between the FPGA and the System ACE
controller.
Table 2-20:System ACE Connections
SignalDirection
System ACE
Pin
FPGA PinI/O TypeDrive
CF_MPA[0]O70AF21LVCMOS258 mA
CF_MPA[1]O69AG21LVCMOS258 mA
CF_MPA[2]O68AC19LVCMOS258 mA
CF_MPA[3]O67AD19LVCMOS258 mA
CF_MPA[4]O45AE22LVCMOS258 mA
CF_MPA[5]O44AE21LVCMOS258 mA
CF_MPA[6]O46AH22LVCMOS258 mA
CF_MPD[0]I/O66AE15LVCMOS258 mA
CF_MPD[1]I/O65AD15LVCMOS258 mA
CF_MPD[2]I/O63AG14LVCMOS258 mA
66www.xilinx.comXUP Virtex-II Pro Development System
UG069 (v1.0) March 8, 2005
Using the Multi-Gigabit Transceivers
Table 2-20:System ACE Connections (Continued)
R
SignalDirection
System ACE
Pin
FPGA PinI/O TypeDrive
CF_MPD[3]I/O62AF14LVCMOS258 mA
CF_MPD[4]I/O61AE14LVCMOS258 mA
CF_MPD[5]I/O60AD14LVCMOS258 mA
CF_MPD[6]I/O59AC15LVCMOS258 mA
CF_MPD[7]I/O58AB15LVCMOS258 mA
CF_MPD[8]I/O56AJ9LVCMOS258 mA
CF_MPD[9]I/O53AH9LVCMOS258 mA
CF_MPD[10]I/O52AE10LVCMOS258 mA
CF_MPD[11]I/O51AE9LVCMOS258 mA
CF_MPD[12]I/O50AD12LVCMOS258 mA
CF_MPD[13]I/O49AC12LVCMOS258 mA
CF_MPD[14]I/O48AG10LVCMOS258 mA
CF_MPD[15]I/O47AF10LVCMOS258 mA
CF_MP_CE_ZO42AB16LVCMOS258 mA
CF_MP_OE_ZO77AD17LVCMOS258 mA
CF_MP_WE_ZO76AC16LVCMOS258 mA
CF_MPIRQI41AD16LVCMOS25-
CF_MPBRDYI39AE16LVCMOS25-
Using the Multi-Gigabit Transceivers
The embedded RocketIO™ multi-gigabit transceiver core is based on Mindspeed’s
SkyRail™ technology. Eight transceiver cores are available in each of the FPGAs that can be
used on the XUP Virtex-II Pro Development System.
The transceiver core is designed to operate at any baud rate in the range of 622 Mb/s to
3.125 Gb/s per channel. Only four of the available eight channels are used on the XUP
Virtex-II Pro Development System. Three channels are equipped with low-costs Serial
Advanced Technology Attachment (SATA) connectors and the fourth channel terminates
at user-supplied Sub-Miniature A (SMA) connectors. The SATA channels are split into two
interface formats, two HOST ports (J16, J18), and a TARGET port (J17). The TARGET port
interchanges the transmit and receive differential pairs to allow two XUP Virtex-II Pro
Development Systems to be connected as a simple network, or multiple XUP Virtex-II Pro
Development Systems to be connected in a ring. The SATA specification requires an out-ofband signalling state that is to be used when the channel is idle. This capability is not
directly provided by the MGTs. Two resistors, an FET transistor, and two AC coupling
capacitors along with special idle state control signals add the out-of-band IDLE state
signaling capability to the MTGs. Additional off-board hardware can be required to
properly interface to generic SATA disk drives.
XUP Virtex-II Pro Development Systemwww.xilinx.com67
UG069 (v1.0) March 8, 2005
R
Chapter 2: Using the System
The fourth MGT channel pair terminates on user_supplied SMA connectors (J19-22) and
can be driven by a user_supplied differential clock input pair, EXTERNAL_CLOCK_P and
EXTERNAL_CLOCK_N provided on SMA connectors (J23-24). This EXTERNAL_CLOCK
can be used to clock the SATA ports if non-standard signaling rates are required. The MGT
connections are shown in Tab le 2 -2 0.
For the user to take advantage of the fourth MGT channel, four SMA connectors must be
installed at J19-J22. These SMA connectors can be purchased from Digikey under the part
number A24691-ND. Figure 2-20 identifies the location of the external differential clock
inputs.
Figure 2-20:SMA-based MGT Connections
There are eight clock inputs into each RocketIO™ transceiver instantiation. REFCLK and
BREFCLK are reference clocks generated from an external source and presented to the
FPGA as differential inputs. The reference clocks connect to the REFCLK or BREFCLK
ports on the RocketIO MGT. While only one of these reference clocks is needed to drive the
MGT, BREFCLK or BREFCLK2 must be used for serial speeds of 2.5 Gb/s or greater.
At speeds of 2.5 Gb/s or greater, REFCLK configuration introduces more than the
maximum allowable jitter to the RocketIO transceiver. For these higher speeds, BREFCLK
configuration is required. The BREFCLK configuration uses dedicated routing resources
that reduce jitter. BREFCLK enters the FPGA through a dedicated clock input buffer.
BREFCLK can connect to the BREFCLK inputs of the MGT and the CLKIN input of a DCM
for creation of user clocks.
The SATA data rate is less than 2.5 Gb/s so the 75 MHz clocks could have been supplied in
the REFCLK inputs, but for consistency the BREFCLK and BREFCLK2 clock inputs are
used for the on-board and user-supplied MGT clocks as shown in Ta ble 2 -2 1.
Table 2-21:SATA and MGT Signals
SignalMGT LocationPAD NameI/O PinNotes
SATA_PORT0_TXNMGT_X0Y1TXNPAD4A27HOST
SATA_PORT0_TXPMGT_X0Y1TXPPAD4A26–
SATA_PORT0_RXNMGT_X0Y1RXNPAD4A24–
SATA_PORT0_RXPMGT_X0Y1RXPPAD4A25–
68www.xilinx.comXUP Virtex-II Pro Development System
UG069 (v1.0) March 8, 2005
Using the Multi-Gigabit Transceivers
Table 2-21:SATA and MGT Signals (Continued)
SignalMGT LocationPAD NameI/O PinNotes
SATA_PORT0_IDLE––B15–
SATA_PORT1_TXNMGT_X1Y1TXNPAD6A20TARGET
SATA_PORT1_TXPMGT_X1Y1TXPPAD6A19–
SATA_PORT1_RXNMGT_X1Y1RXNPAD6A17–
SATA_PORT1_RXPMGT_X1Y1RXPPAD6A18–
SATA_PORT1_IDLE––AK3–
SATA_PORT2_TXNMGT_X2Y1TXNPAD7A14HOST
SATA_PORT2_TXPMGT_X2Y1TXPPAD7A13–
SATA_PORT2_RXNMGT_X2Y1RXNPAD7A11–
SATA_PORT2_RXPMGT_X2Y1RXPPAD7A12–
SATA_PORT2_IDLE––C15–
R
MGT_TXNMGT_X3Y1TXNPAD9A7USER
MGT_TXPMGT_X3Y1TXPPAD9A6–
MGT_RXNMGT_X3Y1RXNPAD9A4–
MGT_RXPMGT_X3Y1RXPPAD9A5–
MGT_CLK_N––G16BREFCLK
MGT_CLK_P––F16–
EXTERNAL_CLOCK_N––F15BREFCLK2
EXTERNAL_CLOCK_P––G15–
The RocketIO MGTs utilize differential signaling between the transmit and receive data
ports to minimize the effects of common mode noise and signal crosstalk. With the use of
high-speed serial transceivers, the interconnect media causes degradation of the signal at
the receiver. Effects such as inter-symbol interference (ISI) or data dependent jitter are
produced. This loss can be large enough to degrade the eye pattern opening at the receiver
beyond that which results in reliable data transmission. The RocketIO MGTs allow the user
to set the initial differential voltage swing and signal pre-emphasis to negate a portion of
the signal degradation to increase the reliability of the data transmission.
In pre-emphasis, the initial differential voltage swing is boosted to create a stronger rising
or falling waveform. This method compensates for high frequency loss in the transmission
media that would otherwise limit the magnitude of the received waveform.
The initial differential voltage swing and signal pre-emphasis are set by two user-defined
RocketIO transceiver attributes. The TX_DIFF_CTRL attribute sets the voltage difference
between the differential lines, and the TX_PREEMPHASIS attribute sets the output driver
pre-emphasis.
Xilinx recommends setting the TX_DIF_CTRL attribute to 600 (600 mV) and the
TXPREEMPHASIS attribute to 2 (25%) when SATA cables of 1.0 or less meters in length are
used to connect the MGT host to the MGT target. Typical eye diagrams for 1.5 Gb/s data
XUP Virtex-II Pro Development Systemwww.xilinx.com69
UG069 (v1.0) March 8, 2005
R
Chapter 2: Using the System
transmission using 0.5 meter and 1.0 meter SATA cables are shown in Figure 2-21.and
Figure 2-22.
Figure 2-21: 1.5 Gb/s Serial Data Transmission over 0.5 meter of SATA Cable
Figure 2-22: 1.5 Gb/s Serial Data Transmission over 1.0 meter of SATA Cable
70www.xilinx.comXUP Virtex-II Pro Development System
UG069 (v1.0) March 8, 2005
R
Appendix A
Configuring the FPGA from the
Embedded USB Configuration Port
The XUP Virtex-II Pro Development System contains an embedded version of the Platform
Cable USB for the purpose of configuration and programming the Virtex-II Pro FPGA and
the Platform FLASH PROM using an off-the-shelf high-speed USB A-B cable.
Configuration and programming are supported by iMPACT (v6.3.01i or later) download
software using Boundary Scan (IEEE 1149.1/IEEE 1532) mode. Target clock speeds are
selectable from 750 kHz to 24 MHz.
The host computer must contain a USB host controller with one or more USB ports. The
controller can reside on the mother board or can be added using an expansion card or
PCMCIA/CARDBUS adapter.
The host operating system must be either Windows 2000 (SP4 or later) or Windows XP (SP1
or later). IMPACT v6.3.01I and ChipScope Pro are not supported by earlier versions of
Windows.
The embedded Platform Cable USB interface is designed to take full advantage of the
bandwidth of USB 2.0 ports. It is also backward compatible with USB 1.1 ports. The
interface is self-powered and consumes no power from the host hub. It is enumerated as a
high-speed device on USB 2.0 hubs or a full-speed device on USB 1.1 hubs.
A proprietary Windows device driver is required to use the embedded Platform Cable
USB. All Foundation ISE software releases and service packs beginning with version
6.3.01i incorporate this device driver. Windows does not recognize the embedded Platform
Cable USB until the appropriate Foundation ISE or ChipScope Pro installation has been
completed.
The embedded 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 application code is successfully transmitted. All necessary firmware
files are included with every Foundation ISE software installation CD. Revised firmware
can be periodically distributed in subsequent software releases.
The embedded Platform Cable USB can be attached and removed from the host computer
without the need to power-down or reboot the host computer. When the embedded
Platform Cable is detected by the operating system, a “Programming Cables” folder is
displayed if the System Properties -> Hardware -> Device Manager dialog box is selected.
A “Xilinx Platform Cable USB” entry resides in this folder as shown in Figure A-1.
XUP Virtex-II Pro Development Systemwww.xilinx.com71
UG069 (v1.0) March 8, 20051-800-255-7778
R
Appendix A: Configuring the FPGA from the Embedded USB Configuration Port
Figure A-1:Device Manager Cable Entry
There is no difference between the embedded Platform Cable USB implementation and the
standalone Platform Cable USB hardware. The host computer operating system and
iMPACT reports the attached cable as the standalone version.
The embedded Platform Cable USB can be designated as the “active” configuration cable
by selecting “Output -> Cable Setup” from the iMPACT tool bar as shown in Figure A-2.
Figure A-2:iMPACT Cable Selection Drop-Down Menu
72www.xilinx.comXUP Virtex-II Pro Development System
1-800-255-7778UG069 (v1.0) March 8, 2005
When the Cable Communications Setup dialog box is displayed, the Communications
Mode radio button must be set to Platform Cable USB as shown in Figure A-3. If no USB
host is available, then select Parallel IV, attach a PC4 cable to J27.
Figure A-3: iMPACT Cable Communication Setup Dialog
R
Regardless of the native communications speed of the host USB port, target devices can be
clocked at any of six different frequencies by making the appropriate selection in the TCK
Speed/Baud Rate drop-down list.
The default clock rate of 6 MHz is selected by iMPACT, because all Xilinx devices are
guaranteed to be programmed at that rate. The basic XUP Virtex-II Pro Development
System contains a Platform FLASH PROM and a Virtex-II Pro FPGA. This combination of
devices does not support the maximum JTAG TCK clock frequency. This means that the
TCK Speed/Baud Rate could be set to 12 MHz. If expansion circuit boards that contain
programmable devices are added to the basic system, the user must ensure that the JTAG
clock frequency does not exceed the capability of the additional devices.
XUP Virtex-II Pro Development Systemwww.xilinx.com73
UG069 (v1.0) March 8, 20051-800-255-7778
R
Appendix A: Configuring the FPGA from the Embedded USB Configuration Port
After the programming cable type and speed has been selected, the JTAG chain must be
defined. Right click in the iMPACT window and select “Initialize Chain” from the dropdown menu shown in Figure A-4.
Figure A-4: Initializing the JTAG Chain
A status bar on the bottom edge of the iMPACT GUI provides useful information about the
operating conditions of the software and the attached cable. If the host port is USB 1.1,
Platform Cable USB connects at full-speed, and the status bar shows “usb-fs.” If the host
port is USB 2.0, Platform Cable USB connects at high-speed and the status bar shows “usbhs.” The active JTAG TCK speed is shown in the right-hand corner of the status bar.
Figure A-4, shows a Platform Cable USB connected at high-speed, using a Boundary-Scan
Configuration Mode with a JTAG TCK of 12 MHz.
If there are no configurable expansion boards attached to the basic system, the Initialize
Chain command should identify three devices in the chain: the Platform FLASH PROM
(XCF32P), followed by the System ACE controller (XCCACE), and followed by the FPGA
(XC2VP30). Any programmable devices on expansion boards follow the FPGA in the
configuration chain. A properly identified JTAG configuration chain for the basic system is
shown in Figure A-5.
74www.xilinx.comXUP Virtex-II Pro Development System
Right click on each of the devices in the chain and select “Assign New Configuration File”
from the drop-down menu (see Figure A-6). The Platform FLASH PROM and the System
ACE controller should be set to BYPASS, and the desired configuration file for the FPGA
should be specified as shown in Figure A-7.
R
Figure A-6: Assigning Configuration Files to Devices in the JTAG Chain
XUP Virtex-II Pro Development Systemwww.xilinx.com75
UG069 (v1.0) March 8, 20051-800-255-7778
R
Appendix A: Configuring the FPGA from the Embedded USB Configuration Port
Figure A-7: Assigning a Configuration File to the FPGA
Any additional files required by the design can specified at this time. Right click on the
Virtex-II Pro FPGA and select “Program” to program the device as shown in Figure A-8.
Figure A-8: Programming the FPGA
76www.xilinx.comXUP Virtex-II Pro Development System
1-800-255-7778UG069 (v1.0) March 8, 2005
R
Appendix B
Programming the Platform FLASH
PROM User Area
The XUP Virtex-II Pro Development System contains an XCF32P Platform FLASH PROM
that is used to contain a known “Golden” configuration and a separate “User”
configuration. These two FPGA configurations are supported by the design revisioning
capabilities of the Platform FLASH PROMs. The “Golden” configuration is stored in
Revision 0 and is write/erase protected, and the “User” configuration is stored in
Revision 1.
Programming the XCF32P Platform FLASH PROM is supported by iMPACT (v6.3.01i or
later) download software using Boundary Scan (IEEE 1149.1 /IEEE 1532) mode from either
the embedded Platform Cable USB (J8) or the PC4 cable connection (J27).
The.bit file created by the Xilinx implementation tools must be converted to an.MKS file
before it can be programmed into the Platform FLASH PROM.
1.Start iMPACT and select Prepare Configuration Files as shown in Figure B-1.
XUP Virtex-II Pro Development Systemwww.xilinx.com77
UG069 (v1.0) March 8, 20051-800-255-7778
R
Appendix B: Programming the Platform FLASH PROM User Area
2.Click on Next and select PROM File in the Prepare Configuration Files option menu
shown in Figure B-2.
Figure B-2: Selecting PROM File
3.Click on Next and then select Xilinx PROM with Design Revisioning Enabled using the
MCS PROM File Format.
4.Give the PROM File a name of your choice in the location of your choice as shown in
Figure B-3.
Note:
hardware does not support this option.
Do NOT select Compress Data, because the XUP Virtex-II Pro Development System
78www.xilinx.comXUP Virtex-II Pro Development System
1-800-255-7778UG069 (v1.0) March 8, 2005
R
Figure B-3: Selecting a PROM with Design Revisioning Enabled
5.Click on Next to bring up the option screen where the type of PROM is specified.
6.Select the XCF32P PROM from the drop down men. Click on the “Add” button and
specify “2” from the Number of Revisions drop down menu as shown in Figure B-4.
Figure B-4: Selecting an XCF32P PROM with Two Revisions
XUP Virtex-II Pro Development Systemwww.xilinx.com79
UG069 (v1.0) March 8, 20051-800-255-7778
R
Appendix B: Programming the Platform FLASH PROM User Area
7.Click on Next twice to bring up the Add Device File screen shown in Figure B-5.
Figure B-5: Adding a Device File
8.Click on Add File and navigate to your design directory and select the.bit file for your
design as shown in Figure B-6.
9.Click on Open and answer No when prompted to add another design file to
Revision 0.
Figure B-6:Adding the Design File to Revision 0
80www.xilinx.comXUP Virtex-II Pro Development System
1-800-255-7778UG069 (v1.0) March 8, 2005
10. Note that Revision 0 is highlighted in green; this is where the “Golden” configuration
will be placed in the PROM. By selecting your design file for Revision 0, you are just
reserving space in the PROM for the “Golden” configuration. Your design file will not
overwrite the “Golden” configuration because it is write/erase protected.
If the design file was created with the Startup Clock set to JTAG, iMPACT will issue a
warning that the Startup Clock will be changed to CCLK in the bitstream programmed
into the PROM. This warning is shown in Figure B-7 and can be safely ignored.
Figure B-7: iMPACT Startup Clock Warning
11. Once you answer No when prompted to add another design file to Revision 0, the
green revision highlight will move to Revision 1. You will be prompted to add your
design file to Revision 1 as shown in Figure B-8.
R
Figure B-8:Adding the Design File to Revision 1
12. Click on Open and answer No when prompted to add another design file to
Revision 1. Click on Finish to start the generation of the MCS file as shown in
Figure B-9.
XUP Virtex-II Pro Development Systemwww.xilinx.com81
UG069 (v1.0) March 8, 20051-800-255-7778
R
Appendix B: Programming the Platform FLASH PROM User Area
Figure B-9: Generating the MCS File
13. When prompted to compress the file, respond No, because the XUP Virtex-II Pro
Development System hardware does not support this option.
14. After iMPACT successfully creates the MCS file, select Configuration Mode from the
Mode menu as shown in Figure B-10.
Figure B-10: Switching to Configuration Mode
15. Make sure that the XUP Virtex-II Pro Development System is powered up and that
either a USB cable or a PC4 cable connects the board to the PC that is running the
iMPACT software.
16. Select the Initialize Chain command shown in Figure B-11.
82www.xilinx.comXUP Virtex-II Pro Development System
1-800-255-7778UG069 (v1.0) March 8, 2005
Figure B-11:Initializing the JTAG Chain
The iMPACT software then interrogates the system and reports that there are at least
three devices in the JTAG chain. The first device is the XCF32P PROM; the second
device is the System ACE controller; and the third device is the Virtex-II Pro FPGA.
Any additional devices shown in the JTAG chain will reside on optional expansion
boards.
17. Select the MCS file that you created earlier as the configuration file for the XCF32P
PROM and click Open, as shown inFigure B-12.
R
Figure B-12: Assigning the MCS File to the PROM
18. Select BYPASS as the configuration files for the System ACE controller and the
Virtex-II Pro FPGA.
XUP Virtex-II Pro Development Systemwww.xilinx.com83
UG069 (v1.0) March 8, 20051-800-255-7778
R
Appendix B: Programming the Platform FLASH PROM User Area
19. Right mouse click on the icon for the XCF32P PROM and select Program from the drop
down menu as shown in Figure B-13.
Figure B-13: Programming the PROM
20. The iMPACT software responds with a form that allows the user to specify which
design revisions are to be programmed and the programming options for the various
revisions. De-select Design Revision Rev 0 and all of the options for Design Revision
Rev 0 to minimize the programming time. Any options that you set for Design
Revision Rev 0 are ignored, because Design Revision Rev 0 has been previously
Erase/Write protected.
21. Select Design Revision Rev 1, and set the Erase (ER) bit to erase any previous “User”
design. Make sure that the Write Protect (WP) bit is not set.
22. Verify that the Operating Mode is set to Slave and the I/O Configuration is set to
Parallel Mode as shown in Figure B-14.
84www.xilinx.comXUP Virtex-II Pro Development System
1-800-255-7778UG069 (v1.0) March 8, 2005
R
Figure B-14: PROM Programming Options
23. Click on OK to begin programming the PROM. The iMPACT transcript window shows
the sequence of operations that took place and looks similar to Figure B-15.
XUP Virtex-II Pro Development Systemwww.xilinx.com85
UG069 (v1.0) March 8, 20051-800-255-7778
R
Appendix B: Programming the Platform FLASH PROM User Area
24. To load the newly programmed PROM configuration file into the Virtex-II Pro FPGA,
verify that the “CONFIG SOURCE” switch is set to enable high-speed SelectMap bytewide configuration from the on-board Platform Flash configuration PROM, and that
the “PROM VERSION” switch is set to enable the “User” configuration. If the switches
are set properly, only the green “PROM” LED (D19) is illuminated.
25. Press the “RESET\RELOAD” push button until the red “RELOAD” turns on. Release
the push button and the new “User” configuration is transferred to the FPGA.
86www.xilinx.comXUP Virtex-II Pro Development System
1-800-255-7778UG069 (v1.0) March 8, 2005
R
Restoring the Golden FPGA
Configuration
The XUP Virtex-II Pro Development System contains an XCF32P Platform FLASH PROM
that is used to contain a known Golden configuration and a separate User configuration.
These two FPGA configurations are supported by the design revisioning capabilities of the
Platform FLASH PROMs. The Golden configuration is stored in Revision 0 and is
write/erase protected, and the User configuration is stored in Revision 1.
Programming of the XCF32P Platform FLASH PROM is supported by iMPACT (v6.3.01i or
later) download software using Boundary Scan (IEEE 1149.1 /IEEE 1532) mode from either
the embedded Platform Cable USB (J8) or the PC4 cable connection (J27).
Appendix C
The latest Golden configuration file can be obtained from the XUP Virtex-II Pro
Development System support Web site at: http://www.xilinx.com/univ/xup2vp.html
This configuration file is used to verify the proper operation of the complete system.
1.Download the XUP_V2Pro_BIST.zip file and extract the files to a directory of your
choice. The ZIP file contains two files:
♦XUP_V2Pro_BIST.mcs, the data file that will be loaded into the PROM, and
♦XUP_V2Pro_BIST.cfi, a file that describes the design revision structure in the
PROM.
2.Make sure that the XUP Virtex-II Pro Development System is powered up and that
either a USB cable or a PC4 cable connects the board to the PC that is running the
iMPACT software.
.
Xilinx University Program Virtex-II Pro Development Systemwww.xilinx.com87
UG069 (v1.0) March 8, 20051-800-255-7778
R
Appendix C: Restoring the Golden FPGA Configuration
3.Start up iMPACT and select Configure Devices as shown in Figure C-1.
4.Clock on Next and select the Boundary Scan Mode from the option menu shown in
Figure C-2.
88www.xilinx.comXilinx University Program Virtex-II Pro Development
System
1-800-255-7778UG069 (v1.0) March 8, 2005
R
Figure C-2: Selecting Boundary Scan Mode
Xilinx University Program Virtex-II Pro Development Systemwww.xilinx.com89
UG069 (v1.0) March 8, 20051-800-255-7778
R
Appendix C: Restoring the Golden FPGA Configuration
5.Click on Next and then select Automatically connect to the cable and identify the
Boundary Scan as shown in Figure C-3.
Figure C-3: Boundary Scan Mode Selection: Automatically Connect to the Cable
and Identify the JTAG Chain
6.Click on Finish and the iMPACT software then interrogates the system and reports that
there are at least three devices in the JTAG chain. The first device is the XCF32P PROM,
the second device is the System ACE controller, and the third device is the Virtex-II Pro
FPGA. Any additional devices shown in the JTAG chain reside on optional expansion
boards.
7.Navigate to the directory where you saved the XUP_V2Pro_BIST.mcs file. Select this
file as the Configuration file for the XCF32P PROM, the first device in the JTAG chain
identified by iMPACT as shown in Figure C-4. Click on the Open button.
90www.xilinx.comXilinx University Program Virtex-II Pro Development
System
1-800-255-7778UG069 (v1.0) March 8, 2005
R
Figure C-4: Assigning New PROM Configuration File
8.Select BYPASS as the configuration files for the System ACE controller and the VirtexII Pro FPGA.
9.Right mouse click on the icon for the XCF32P PROM and select Erase from the drop
down menu as shown in Figure C-5. When the erase options screen appears, select All
Revisions and then click OK.
Xilinx University Program Virtex-II Pro Development Systemwww.xilinx.com91
UG069 (v1.0) March 8, 20051-800-255-7778
R
Appendix C: Restoring the Golden FPGA Configuration
Figure C-5: Erasing the Existing PROM Contents
The iMPACT software then erases the complete contents of the PROM, including old
versions of the Golden and User designs. The transcript window should look similar to
Figure C-6.
Figure C-6: Transcript Window for the Erase Command
10. Right mouse click on the icon for the XCF32P PROM and select Program from the drop
down menu as shown in Figure C-7.
92www.xilinx.comXilinx University Program Virtex-II Pro Development
System
1-800-255-7778UG069 (v1.0) March 8, 2005
R
Figure C-7: Selecting the Program Command
11. The iMPACT software responds with a form that allows the user to specify which
design revisions are to be programmed and the programming options for the various
revisions. Select Design Revision Rev 0 and set the Write Protect (WP) bit to prevent
the user from overwriting the Golden configuration. Verify that the Operating Mode is
set to Slave and the I/O Configuration is set to Parallel Mode as shown in Figure C-8.
Xilinx University Program Virtex-II Pro Development Systemwww.xilinx.com93
UG069 (v1.0) March 8, 20051-800-255-7778
R
Appendix C: Restoring the Golden FPGA Configuration
Figure C-8: PROM Programming Options
12. Click on OK to begin programming the PROM. The iMPACT transcript window shows
the sequence of operations that took place and looks similar to Figure C-9.
94www.xilinx.comXilinx University Program Virtex-II Pro Development
System
13. To load the newly programmed PROM configuration file into the Virtex-II Pro FPGA,
verify that the CONFIG SOURCE switch is set to enable high speed SelectMap byte
wide configuration from the on-board Platform Flash configuration PROM and that
the PROM VERSION switch is set to enable the Golden configuration. If the switches
are set properly, the green PROM CONFIG LED (D19) and the amber GOLDEN
GONFIG LED (D14) are illuminated.
14. Press the RESET\RELOAD push button until the red RELOAD turns on. Upon
releasing the push button, the new Golden configuration is transferred to the FPGA.
R
Xilinx University Program Virtex-II Pro Development Systemwww.xilinx.com95
UG069 (v1.0) March 8, 20051-800-255-7778
R
Appendix C: Restoring the Golden FPGA Configuration
96www.xilinx.comXilinx University Program Virtex-II Pro Development
System
1-800-255-7778UG069 (v1.0) March 8, 2005
R
Appendix D
Using the Golden FPGA Configuration
for System Self-Test
A special design has been placed in the Platform FLASH PROM to provide a Built-in SelfTest (BIST) boot/configuration that tests critical board features and reports on board health
and status. Figure D-1 shows BIST block diagram.
Audio Tones &
Push Buttons
Clock
Generator
PPC 1
VGA
Keyboard
PS2
LEDs &
DIP Switches
Generator
GPIO
Char. &
Test
Pattern
II C
HARDWARE
PROC PERIPH
CNTRL
Silicon
Ser Number
Key
HARD IP
OPB BUS
AC 97
CNTRL
Por t Test
External
ETHERNET
MAC
PPC 0
BRAM
128 Kb
Bridge
PLB
BUS
SYSACE
DDR SDRAM
CONTROL
CONTRL
Figure D-1: XUP Virtex-II Pro Development System BIST Block Diagram
PLB AT
LITE
LITE
UART
UART
MGT
MGT
MGT
UG069_20_010605
Appendix C, “Restoring the Golden FPGA Configuration,” of this document covers the
details of restoring the BIST design if it has been erased accidentally. This feature puts the
board through several tests to verify the board is fully functional in a stand-alone
environment. Other tests to verify system-level functionality can be supported via
XUP Virtex-II Pro Development Systemwww.xilinx.com97
UG069 (v1.0) March 8, 20051-800-255-7778
R
Compact Flash or download, but the “Golden Boot” has been designed to verify that the
board is not damaged due to user abuse. This mode allows the user to verify that the board
itself is not the root cause of a design failing to function properly.
The BIST is a combination of pure hardware and processor centric tests combined into one
FPGA design.
The “Golden Boot” design covers the following elements of the system:
1.Clock presence
2.Push buttons, DIP switches, and LEDs
3.Audio CODEC and power amplifier
4.RS-232 serial ports and PS/2 ports
5.SVGA output
6.10/100 Ethernet and Silicon Serial Number
7.Expansion ports
8.MGTs
9.System ACE processor interface
10. DDR SDRAM module and Serial Presence Detect PROM
Appendix D: Using the Golden FPGA Configuration for System Self-Test
The BIST consists of two different test strategies, a series of processor centric tests and pure
hardware non-processor centric tests. The pure hardware tests are used to verify the most
basic functions of the system and to provide a platform on which the processor centric tests
can build.
Hardware-Based Tests
These tests should be run in the order listed, because each test design can require a positive
result from a previous test.
Power Supply and RESET Test
This test verifies the correct operation of the on-board power supplies and system RESET
generation circuitry.
Additional Hardware Required
•5V external power supply
•Multimeter
•Shorting Jumper Block
Test Procedure
1.Verify that three Shorting Jumper Blocks are installed in JP1, JP2, and JP3
2.Plug in the external 5V power supply, and turn on the board by sliding SW11 up
towards the “ON” label.
3.Connect the negative lead of the multimeter to J31 and the positive lead to J30. The
meter should read between 2.375V and 2.625V, and LED D17 “2.5V OK” should be on.
4.Connect the negative lead of the multimeter to J33 and the positive lead to J32. The
meter should read between 3.135V and 3.465V, and LED D18 “3.3V OK” should be on.
98www.xilinx.comXUP Virtex-II Pro Development System
1-800-255-7778UG069 (v1.0) March 8, 2005
Hardware-Based Tests
Clock, Push Button, DIP Switch, LED, and Audio Amp Test
R
5.Connect the negative lead of the multimeter to J35 and the positive lead to J34. The
meter should read between 1.425V and 1.575V, and LED D19 “1.5V OK” should be on.
6.Install the Shorting Jumper Block on JP2, LED D17 “2.5V OK” should be off, and D6
“RELOAD PS ERROR” should be on. Remove the Shorting Jumper Block.
7.Install the Shorting Jumper Block on JP6, LED D19 “1.5V OK” should be off, and D6
“RELOAD PS ERROR” should be on. Remove the Shorting Jumper Block.
8.Turn the circuit board over.
9.Connect the negative lead of the multimeter to the negative side of C433 and the
positive lead to the positive side of C433. The meter should read between 2.375V and
2.625V, verifying the correct voltage for the MGT termination.
10. Connect the negative lead of the multimeter to the negative side of C428 and the
positive lead to the positive side of C428. The meter should read between 2.375V and
2.625V, verifying the correct voltage for the MGT power supply.
11. Turn the circuit board component side up.
This test verifies the presence of the various clocks, push buttons, DIP switches, audio
amplifier, and the beep-tone passthrough capability of the audio CODEC. The four user
LEDs are used to verify the operation of the clocks and to display the status of the user DIP
switches. Pressing each of the push buttons results in a different tone from the headphones.
Additional Hardware Required
•5V external power supply
•Headphones
Test Procedure
1.Set the “CONFIG SOURCE/PROM VERSION” DIP switch SW9 with both of the
switches up or closed.
2.Plug in the external 5V power supply, and turn on the board by sliding SW11 up
towards the “ON” label. LEDs D14 “GOLDEN CONFIG”, D19 “PROM CONFIG,” and
D4 “DONE” should be on.
3.Observe the status of the four user LEDs: D7-10. LED 3, LED 2, and LED1 should flash
at different rates, and LED 0 should be on steady indicating that the DCMs in the
FPGA are locked to the clock signals.
♦A flashing LED 3 indicates that the 100 MHz system clock is present.
♦A flashing LED 2 indicates that the 75 MHz MGT clock is present.
♦A flashing LED 1 indicates that the 32 MHz System ACE clock is present.
♦A steady-on LED 0 indicates that the DCMs are locked.
4.After about 5 seconds, the LEDs should shop flashing and their function changes to
indicate the status of the USER INPUT DIP switch SW7. If a switch is down or open,
the corresponding LED will be off, if the switch is up or closed the LED will be on.
♦LED 3 shows the status of USER INPUT switch 3.
♦LED 2 shows the status of USER INPUT switch 2.
♦LED 1 shows the status of USER INPUT switch 1.
♦LED 0 shows the status of USER INPUT switch 0.
XUP Virtex-II Pro Development Systemwww.xilinx.com99
UG069 (v1.0) March 8, 20051-800-255-7778
R
5.Briefly (less than 2 seconds), press the “RESET/RELOAD” push button SW1. This
should result in the LEDs displaying the clock status again for 5 seconds.
6.Connect the headphones to the upper jack of J14 “AMP OUT.”
Warning:
LOUD.
7.Press each one of the push buttons, SW2-6. A different tone will be produced as each
push button is pressed.
Appendix D: Using the Golden FPGA Configuration for System Self-Test
Do not put the headphones on your ears, because the tones generated will be
SVGA Gray Scale Test
This test verifies the operation of the video DAC by creating a gray scale ramp that drives
each of the red, green, and blue channels with the same signal. Any color present indicates
the failure of one or more channel outputs. Any data bus errors will show up as
discontinuities in the ramp. There should be 1.5 ramps visible on the display.
Additional Hardware Required
•5V external power supply
•SVGA display with cable capable of showing a 640 x 480 at 60 Hz image
Test Procedure
1.Set the “CONFIG SOURCE/PROM VERSION” DIP switch SW9 with both of the
switches up or closed.
2.Plug in the external 5V power supply and turn on the board by sliding SW11 up
towards the “ON” label. LEDs D14 “GOLDEN CONFIG,” D19 “PROM CONFIG,” and
D4 “DONE” should be on.
3.Connect the SVGA display to the SVGA output connector J13. A gray scale ramp
should be seen on the bottom of display.
SVGA Color Output Test
This test verifies the operation of the video DAC by creating a color bar pattern starting
with 100% white followed by 75% color bars. Between each of the color bars, there should
be a 2-pixel black stripe. This test makes sure that all color channels can be driven
individually and in-groups.
Additional Hardware Required
•5V external power supply
•SVGA display with cable capable of showing a 640 x 480 at 60 Hz image
Test Procedure
1.Set the “CONFIG SOURCE/PROM VERSION” DIP switch SW9 with both of the
switches up or closed.
2.Plug in the external 5V power supply, and turn on the board by sliding SW11 up
towards the “ON” label. LEDs D14 “GOLDEN CONFIG,” D19 “PROM CONFIG,” and
D4 “DONE” should be on.
3.Connect the SVGA display to the SVGA output connector J13. Seven distinct color bars
should be visible in the middle of the display with a black stripe between each color.
100www.xilinx.comXUP Virtex-II Pro Development System
1-800-255-7778UG069 (v1.0) March 8, 2005
Loading...
+ 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.