English
Language : 

DS077 Datasheet, PDF (27/108 Pages) Xilinx, Inc – Product Availability
R
DATA[7:0]
CCLK
WRITE
BUSY
Spartan-IIE FPGA Family: Functional Description
M1 M2
M0
M1 M2
M0
Spartan-IIE
Spartan-IIE
CS(0)
D0:D7
CCLK
WRITE
BUSY
CS
CS(1)
D0:D7
CCLK
WRITE
BUSY
CS
DONE
INIT
PROGRAM
PROGRAM
DONE
INIT
GND
PROGRAM
DONE
INIT
GND
Figure 20: Slave Parallel Configuration Circuit Diagram
DS077-2_06_110102
Multiple Spartan-IIE FPGAs can be configured using the
Slave Parallel mode, and be made to start-up simulta-
neously. To configure multiple devices in this way, wire the
individual CCLK, Data, WRITE, and BUSY pins of all the
devices in parallel. The individual devices are loaded sepa-
rately by asserting the CS pin of each device in turn and
writing the appropriate data. Sync-to-DONE start-up timing
is used to ensure that the start-up sequence does not begin
until all the FPGAs have been loaded. See Start-up,
page 23.
Write
When using the Slave Parallel Mode, write operations send
packets of byte-wide configuration data into the FPGA.
Figure 21, page 28 shows a flowchart of the write sequence
used to load data into the Spartan-IIE FPGA. This is an
expansion of the "Load Configuration Data Frames" block in
Figure 16, page 23.
The timing for Slave Parallel mode is shown in Figure 26,
page 50.
For the present example, the user holds WRITE and CS
Low throughout the sequence of write operations. Note that
when CS is asserted on successive CCLKs, WRITE must
remain either asserted or deasserted. Otherwise an abort
will be initiated, as in the next section.
1. Drive data onto D0-D7. Note that to avoid contention,
the data source should not be enabled while CS is Low
and WRITE is High. Similarly, while WRITE is High, no
more than one device’s CS should be asserted.
2. On the rising edge of CCLK: If BUSY is Low, the data is
accepted on this clock. If BUSY is High (from a previous
write), the data is not accepted. Acceptance will instead
occur on the first clock after BUSY goes Low, and the
data must be held until this happens.
3. Repeat steps 1 and 2 until all the data has been sent.
4. Deassert CS and WRITE.
DS077-2 (v2.3) June 18, 2008
www.xilinx.com
27
Product Specification