CY7B9234-270JXCT Cypress Semiconductor Corp, CY7B9234-270JXCT Datasheet - Page 24

• Manufacturer Part Number: CY7B9234-270JXCT
• Description: IC TRANSMITTER HOTLINK 28-PLCC
• Manufacturer: Cypress Semiconductor Corp
• Series: HOTlink™r
• Type: Transmitter and Receiverr

Specifications of CY7B9234-270JXCT

• Package / Case: 28-PLCC
• Protocol: Fibre Channel
• Voltage - Supply: 4.5 V ~ 5.5 V
• Mounting Type: Surface Mount
• Product: PHY
• Supply Voltage (min): 4.5 V
• Supply Current: 0.085 A
• Maximum Operating Temperature: + 70 C
• Minimum Operating Temperature: 0 C
• Mounting Style: SMD/SMT
• Number Of Channels: 1
• Lead Free Status / RoHS Status: Lead free / RoHS Compliant
• Number Of Drivers/receivers: -
• Lead Free Status / RoHS Status: Lead free / RoHS Compliant, Lead free / RoHS Compliant

Use of the Tables for Generating Transmission
Characters
The appropriate entry in the table shall be found for the Valid
Data byte or the Special Character byte for which a Transmission
Character is to be generated (encoded). The current value of the
Transmitter’s running disparity shall be used to select the Trans-
mission Character from its corresponding column. For each
Transmission Character transmitted, a new value of the running
disparity shall be calculated. This new value shall be used as the
Transmitter’s current running disparity for the next Valid Data
byte or Special Character byte to be encoded and transmitted.
Table 1 shows naming notations and examples of valid transmission
characters.
Use of the Tables for Checking the Validity of Received
Transmission Characters
The column corresponding to the current value of the Receiver’s
running disparity shall be searched for the received Trans-
mission Character. If the received Transmission Character is
found in the proper column, then the Transmission Character is
valid and the associated Data byte or Special Character code is
determined (decoded). If the received Transmission Character is
not found in that column, then the Transmission Character is
invalid. This is called a code violation. Independent of the Trans-
mission Character’s validity, the received Transmission
Character shall be used to calculate a new value of running
disparity. The new value shall be used as the Receiver’s current
running disparity for the next received Transmission Character.
Table 2. Code Violations Resulting from Prior Errors
Valid Data Characters (SC/D = LOW)
Document #: 38-02014 Rev. *B
3. Otherwise, running disparity at the end of the sub-block is the
Transmitted data character
Transmitted bit stream
Bit stream after error
Decoded data character
Name
D0.0
D1.0
D2.0
D3.0
D4.0
D5.0
D6.0
D7.0
D8.0
same as at the beginning of the sub-block.
Data
Byte
HGF
000
000
000
000
000
000
000
000
000
Bits
EDCBA
00000
00001
00010
00011
00100
00101
00110
00111
01000
100111
011101
101101
110001
110101
101001
011001
111000
111001
abcdei
Current RD−
RD
−
−
−
−
101010 1001
0100
0100
0100
1011
0100
1011
1011
1011
0100
101010 1011
fghj
Character
D21.1
D21.0
011000
100010
010010
110001
001010
101001
011001
000111
000110
abcdei
Current RD+
RD
−
−
+
+
1011
1011
1011
0100
1011
0100
0100
0100
1011
fghj
Table 1. Valid Transmission Characters
Detection of a code violation does not necessarily show that the
Transmission Character in which the code violation was detected
is in error. Code violations may result from a prior error that
altered the running disparity of the bit stream which did not result
in a detectable error at the Transmission Character in which the
error occurred. Table 2 shows an example of this behavior.
010101 0101
010101 0101
Byte Name
Character
D30.7
D31.7
D10.2
D10.2
D0.0
D1.0
D2.0
D5.2
.
.
.
.
000
000
000
010
111
111
765
RD
−
−
+
+
D
.
.
.
.
IN
Data
or Q
00000
00001
00010
00101
11110
11111
43210
Code Violation
OUT
111010 1010
111010 1010
Character
.
.
.
.
D23.5
CY7B9234
CY7B9334
Hex Value
Page 24 of 36
00
01
02
45
FE
FF
.
.
.
.
RD
+
+
+
+
[+] Feedback