Xilinx Virtex-5 RocketIO GTP User Manual page 177

R
Table 7-33: Channel Bonding Attributes (Continued)
Attribute
CHAN_BOND_LEVEL_0
CHAN_BOND_LEVEL_1
CHAN_BOND_MODE_0
CHAN_BOND_MODE_1
CHAN_BOND_SEQ_1_1_0
CHAN_BOND_SEQ_1_1_1
CHAN_BOND_SEQ_1_2_0
CHAN_BOND_SEQ_1_2_1
CHAN_BOND_SEQ_1_3_0
CHAN_BOND_SEQ_1_3_1
CHAN_BOND_SEQ_1_4_0
CHAN_BOND_SEQ_1_4_1
CHAN_BOND_SEQ_1_ENABLE_0
CHAN_BOND_SEQ_1_ENABLE_1
CHAN_BOND_SEQ_2_1_0
CHAN_BOND_SEQ_2_1_1
CHAN_BOND_SEQ_2_2_0
CHAN_BOND_SEQ_2_2_1
CHAN_BOND_SEQ_2_3_0
CHAN_BOND_SEQ_2_3_1
CHAN_BOND_SEQ_2_4_0
CHAN_BOND_SEQ_2_4_1
CHAN_BOND_SEQ_2_ENABLE_0
CHAN_BOND_SEQ_2_ENABLE_1
CHAN_BOND_SEQ_2_USE_0
CHAN_BOND_SEQ_2_USE_1
Virtex-5 RocketIO GTP Transceiver User Guide
UG196 (v1.3) May 25, 2007
CHAN_BOND_LEVEL indicates the amount of internal pipelining used for the
elastic buffer control signals. A higher value permits more daisy-chaining of
RXCHBONDO and RXCHBONDI to ease placement and routing constraints.
To minimize required latency through the elastic buffer, CHAN_BOND_LEVEL
in the master should be set to the smallest value possible for the required
amount of daisy-chaining. See the
learn how to set the channel bonding level.
Defines the channel bonding mode of operation for this transceiver.
OFF: No channel bonding.
MASTER: This transceiver is master for channel bonding. Its RXCHBONDO
port directly drives RXCHBONDI ports on one or more SLAVE transceivers.
SLAVE: This transceiver is a slave for channel bonding. Its RXCHBONDI
port is directly driven by the RXCHBONDO port of another SLAVE or
MASTER transceiver. If its CHAN_BOND_LEVEL setting is greater than 0,
its RXCHBONDO port may directly drive RXCHBONDI ports on one or
more other SLAVE transceivers.
The CHAN_BOND_SEQ_1 attributes are used in conjunction with
CHAN_BOND_SEQ_1_ENABLE to define channel bonding sequence 1.
Each subsequence is 10 bits long. The rules for setting the subsequences depend
on INTDATAWIDTH and RX_DECODE_SEQ_MATCH. See the
section to learn how to set channel bonding subsequences.
Not all subsequences need to be used. CHAN_BOND_SEQ_LEN determines
how much of the sequence is used for a match. If CHAN_BOND_SEQ_LEN =
1, only CHAN_BOND_SEQ_1_1 is used.
CHAN_BOND_SEQ_1_ENABLE can be used to make parts of the sequence
don't care. If CHAN_BOND_SEQ_1_ENABLE[k] is 0,
CHAN_BOND_SEQ_1_k is a don't-care subsequence and is always a match.
The CHAN_BOND_SEQ_2 attributes are used in conjunction with
CHAN_BOND_SEQ_2_ENABLE to define the second channel bonding
sequence. When CHAN_BOND_SEQ_2_USE is TRUE, the second sequence is
used as an alternate sequence to trigger channel bonding.
Each subsequence is 10 bits long. The rules for setting the subsequence depend
on INTDATAWIDTH and RX_DECODE_SEQ_MATCH. See the
section to learn how to set channel bonding sequences.
Not all subsequences need to be used. CHAN_BOND_SEQ_LEN determines
how many of the subsequences are used for a match. If
CHAN_BOND_SEQ_LEN = 1, only CHAN_BOND_SEQ_2_1 is used.
CHAN_BOND_SEQ_2_ENABLE can be used to make parts of the sequence
don't care. If CHAN_BOND_SEQ_2_ENABLE[k] is 0,
CHAN_BOND_SEQ_2_k is a don't care subsequence and is always a match.
Determines if the second channel bonding sequence is to be used.
TRUE: Channel bonding can be triggered by channel bonding sequence 1 or
2.
FALSE: Channel bonding is only triggered by sequence 1.
www.xilinx.com
Configurable Channel Bonding (Lane Deskew)
Description
"Description" section for channel bonding to
"Description"
"Description"
177