The following gure shows a conguraon of the HDMI TX where both HDCP 1.4 and 2.3 are
enabled. With both HDCP protocols enabled, the HDMI Subsystem congures itself in the
cascade topology where the HDCP 1.4 and HDCP 2.3 are connected back-to-back. The HDCP
Egress interface of the HDMI transmier sends unencrypted audiovisual data, which is encrypted
by the acve HDCP block and sent back into the HDMI transmier over the HDCP Ingress
interface for transmission over the link. The HDMI TX Subsystem ensures that only one of the
HDCP protocols is acve at any given me and the other is passive by calling the relevant HDMI
1.4/2.0 TX Subsystem API funcons.
Figure 5: HDCP 1.4 and HDCP 2.3 over HDMI Transmitter
HDCP 2.3
Transmitter
(Active)
HDCP 1.4
Transmitter
(Passive)
Video
(AXI4-Stream or Native)
AXI4-Stream Audio
TMDS Link
HDCP Egress
(Unencrypted)
HDMI TX Core
HDCP Ingress
(Encrypted)
HDMI TX Subsystem
X16558-121020
For more details on HDCP, see the HDCP 1.x Product Guide (PG224) and the HDCP 2.2 LogiCORE
IP Product Guide (PG249).
IMPORTANT!
HDMI IP supports HDCP 2.3; however, all logs are shown as 2.2 which will be xed in a
future release.
AUX Packets
For HDMI, all data island packets consist of a 4-byte packet header and a 32 bytes of packet
contents. The packet header, represented in the following gure, contains 24 data bits (3 bytes)
and 8 bits (1 byte) of BCH ECC parity.
Figure 6: Packet Header
Chapter 3: Product Specification
PG235 (v3.2) October 19, 2022 www.xilinx.com
HDMI 1.4/2.0 TX Subsystem 16
Send Feedback
剩余146页未读，继续阅读
