MAX9263/MAX9264
HDCP Gigabit Multimedia Serial
Link Serializer/Deserializer
46
then reads the deserializer KSV (BKSV) and writes it to
the serializer. The FC begins checking BKSV against the
revocation list. Using the cipher, the serializer and dese-
rializer calculate a 16-bit response value, R0 and R0’,
respectively. The GMSL amendment for HDCP reduces
the 100ms minimum wait time allowed for the receiver
to generate R0’ (specified in HDCP rev 1.3) to 128 pixel
clock cycles in the GMSL amendment.
There are two response value comparison modes: inter-
nal comparison and FC comparison. Set EN_INT_COMP = 1
to select internal comparison mode. Set EN_INT_COMP
= 0 to select FC comparison mode. In internal compari-
son mode, the FC reads the deserializer response R0’
and writes it to the serializer. The serializer compares
R0’ to its internally generated response value R0, and
sets R0_RI_MATCHED. In FC comparison mode, the FC
reads and compares the R0/R0’ values from the serial-
izer/deserializer.
During response value generation and comparison, the
host FC checks for a valid BKSV (having 20 1’s and 20
0’s, which is also reported in BKSV_INVALID) and checks
BKSV against the revocation list. If BKSV is not on the list,
and the response values match, the host authenticates
the link. If the response values do not match, the FC
resamples the response values (as described in HDCP
rev 1.3 Appendix C). If resampling fails, the FC restarts
authentication by setting the RESET_HDCP bit in the
serializer. If BKSV appears on the revocation list, the
host cannot transmit data that requires protection. The
host knows when the link is authenticated and decides
when to output data requiring protection. The FC per-
forms a link integrity check every 128 frames or every 2
seconds Q0.5 seconds. The serializer/deserializer gener-
ate response values every 128 frames. These values are
compared internally (internal comparison mode) or can
be compared in the host FC.
In addition, the serializer/deserializer provide response
values for the enhanced link verification. Enchanced
link verification is an optional method of link verification
for faster detection of loss of synchronization. For this
option, the serializer and deserializer generate 8-bit
enhanced link verification response values, PJ and PJ’,
every 16 frames. The host must detect three consecutive
PJ/PJ’ mismatches before resampling.
Encryption Enable
The GMSL link transfers either encrypted or nonen-
crypted data. To encrypt data, the host FC sets the
encryption enable (ENCRYPTION_ENABLE) bit in
both the serializer and deserializer. The FC must set
ENCRYPTION_ENABLE in the same VSYNC cycle in
both the serializer and deserializer (no internal VSYNC
falling edges between the two writes). The same timing
applies when clearing ENCRYPTION_ENABLE to disable
encryption.
Note: ENCRYPTION_ENABLE enables/disables encryp-
tion on the GMSL irrespective of the content. To comply
with HDCP, the FC must not allow content requiring
encryption to cross the GMSL unencrypted. See the
Force Video/Force Audio Data section.
The FC must complete the authentication process before
enabling encryption. In addition, encryption must be
disabled before starting a new authentication session.
VSYNC Detection
If the FC cannot detect the VSYNC falling edge, it can
use the serializer’s VSYNC_DET register bit. The host
FC first writes 0 to the VSYNC_DET bit. The serializer
then sets VSYNC_DET = 1 once it detects an internal
VSYNC falling edge (which may correspond to an exter-
nal VSYNC rising edge if INVVSYNC of the serializer is
set). The FC continuously reads VSYNC_DET and waits
for the next internal VSYNC falling edge before setting
ENCRYPTION_ENABLE. Poll VSYNC_DET fast enough
to allow time to set ENCRYPTION_ENABLE in both the
serializer/deserializer within the same VSYNC cycle.
Synchronization of Encryption
The video vertical sync (VSYNC) synchronizes the start
of encryption. Once encryption has started, the GMSL
generates a new encryption key for each frame and each
line, with the internal falling edge of VSYNC and HSYNC.
Rekeying is transparent to data and does not disrupt the
encryption of video or audio data.
Repeater Support
The serializer/deserializer have features to build an
HDCP repeater. An HDCP repeater receives and
decrypts HDCP content and then encrypts and transmits
on one or more downstream links. A repeater can also
use decrypted HDCP content (for example to display
on a screen). To support HDCP repeater authentication
protocol, the deserializer has a REPEATER register bit.
This register bit must be set to 1 by a FC (most likely on
repeater module). Both the serializer and deserializer use
SHA-1 hash value calculation over the assembled KSV
lists. HDCP GMSL links support a maximum 15 receivers
(total number including the ones in repeater modules). If
the total number of downstream receivers exceeds 14,
the FC must set the MAX_DEVS_EXCEEDED register bit
when it assembles the KSV list.