HDMI Debugging - 1.0 English

1. Make sure that the HDMI cable is properly inserted.
2. Ensure that the correct GTREFCLK input pins are connected according to Customizing and Generating the Core.
3. Ensure that cable detect and HPD pins are properly connected with the correct active level setting in the HDMI TX or RX subsystem GUI.
4. Try connecting with a different cable.

1. Check the RCS register and ensure the clock selections are done correctly.
2. Check the GT initialization sequence after configuration.

   For example, GTH GTTXRESET should be held HIGH until PLL_LOCK is asserted. Failing to do so might cause the PLL and GT to get stuck. See the UltraScale Architecture GTH Transceivers User Guide (UG576) or UltraScale Architecture GTY Transceivers User Guide (UG578) for more information.

3. Ensure the GTREFCLK is present and is driving the PLL.
4. Try toggling the PLL_GT_RESET bits of TXI or RXI registers.
5. Ensure that the HDMI PHY Controller driver and IP versions are from the same Vivado build.

This indicates that the HDMI design received a video carrying a TMDS Clock that is below the PLL thresholds and there is no NI-DRU in the HDMI PHY Controller instance to receive it.

The DRU must be enabled from the HDMI PHY Controller GUI to be able to receive resolutions below the PLL threshold. The DRU must be supplemented with a corresponding GT clock based on the requirements listed in HDMI PHY Controller HDMI Reference Clock Requirements (link below).

This happens when the clock detector module identifies a mismatch between the actual and required DRU REFCLK frequency. This can be due to two reasons:

• The DRU clock frequency is outside ±10 kHz tolerance of the required frequency.
• When the DRU Ref lock Selection is the same as the RX or TX Ref Clock Selection, disabling the RX or TX Ref Clock Selection can also disable the DRU Ref Clock, which reports the DRU clock frequency as equal to 1 Hz.