2. Support
  3. AR# 69427: HDMI Transmitter (TX) Subsystem v2.0 (Rev. 5) - Why do I sometimes see DDC Transaction failures when the HDMI Sink requests clock stretching?

AR# 69427

HDMI Transmitter (TX) Subsystem v2.0 (Rev. 5) - Why do I sometimes see DDC Transaction failures when the HDMI Sink requests clock stretching?

Description

Why do I sometimes see DDC Transaction failures when the HDMI Sink requests clock stretching?

Solution

This is a known issue which occurs due to the way in which the DDC (I2C) clock stretching is implemented.

The HDMI Transmitter Subsystem has a timeout mechanism, which will time out if the slave holds the SCL low for more than 100ms (@100mhz CPU interface clock).

Once the timeout occurs, the state machine will go back to an idle state.

Therefore, after the slave release the SCL, it will start from an idle state which is then followed by the start condition etc., instead of resuming from the current state.

This can cause DDC transactions to fail.

This issue is resolved in the HDMI Transmitter Subsystem v3.0 in Vivado 2017.3 and later versions.

Linked Answer Records

Master Answer Records

Answer Number Answer Title Version Found Version Resolved
65911 HDMI 1.4/2.0 Transmitter (TX) Subsystem - Release Notes and Known Issues for the Vivado 2015.4 tool and later versions N/A N/A
AR# 69427
Date 03/27/2018
Status Active
Type General Article
IP