In-system Debug - 3.2 English - PG235

For in-system debugging, relevant information can be verified using UART before checking the hardware signals.

1. Press i to check the system information.
2. Press z to check the event log.

   The following table shows two examples of system flow event logs.

   Table 1. System Flow Event Log

   At System Start-up

   While Changing Video Stream from UART Menu

   VPHY log ------ GT init start GT init done TX frequency event TX timer event TX MMCM reconfig done QPLL reconfig done GT TX reconfig start GT TX reconfig done TX MMCM lock QPLL lock TX reset done TX alignment done HDMI TX log ------ Initializing HDMI TX core.... Initializing VTC core.... Reset HDMI TX Subsystem.... TX cable is connected.... TX Stream is Down TX Set Stream, with TMDS (32) TX Audio Unmuted TX Stream is Up

   VPHY log ------ TX frequency event QPLL lost lock TX frequency event TX timer event TX MMCM reconfig done QPLL reconfig done GT TX reconfig start GT TX reconfig done TX MMCM lock QPLL lock TX reset done TX alignment done HDMI TX log ------ TX Set Stream, with TMDS (128) TX Stream is Down TX Audio Unmuted TX Stream is Up

   Table 2. System Flow Event Log (For Versal Pass-through Designs)

   At System Start-up

   While Changing Video Stream from UART Menu

   HDMIPHY log ------ GT init start GT init done TX frequency event TX timer event TX GPO Rising Edge Detected TX MMCM reconfig done GT TX reconfig done TX MMCM lock LCPLL lock TX reset done RX frequency event RX timer event RX DRU disable RX GPO Rising Edge Detected GT RX reconfig done RPLL lock RX reset done RPLL lost lock RPLL lock RX reset done RX MMCM reconfig done RX MMCM lock TX frequency event TX frequency event TX timer event TX GPO Rising Edge Detected TX MMCM reconfig done GT TX reconfig done LCPLL lost lock TX MMCM lock LCPLL lock TX reset done HDMI TX log ------ Initializing HDCP 1.4 core.... Initializing AXI Timer core.... Initializing HDMI TX core.... Initializing HDCP 2.3 core.... Initializing VTC core.... Reset HDMI TX Subsystem.... TX cable is connected.... TX Set Stream TX Set Stream TX Audio Unmuted TX Set Audio Channels (2) TX Stream is Up TX HDCP 2.3 authentication request TX Audio Unmuted VID Bridge Unlocked TX Stream Start TX Stream is Down TX Audio Unmuted TX Set Audio Channels (2) TX Stream is Up TX HDCP 2.3 authentication request

   HDMIPHY log ------ TX frequency event RX frequency event RX frequency event RX timer event RX DRU disable RX GPO Rising Edge Detected GT RX reconfig done RPLL lock RX reset done RX MMCM reconfig done RX MMCM lock RX frequency event RX frequency event RX timer event RX DRU disable RX GPO Rising Edge Detected GT RX reconfig done RPLL lock RX reset done RX MMCM reconfig done RX MMCM lock HDMI TX log ------ VID Bridge Unlocked TX Stream is Down TX Audio Unmuted TX Set Audio Channels (2) TX Audio Unmuted TX Set Audio Channels (2)

3. Press e to check the EDID.

   In this release, the application software reads and parses the sink EDID to determine the sink capability. However, the current application does not block you from setting certain video formats although it is not supported by the sink. Instead, a warning message is prompted to indicate the sink limitation when you type e.

   In this release, for the EDID parsing feature, three VERBOSITY levels are defined. You can set it according to your requirements. It is accessible from the video_common library, in xvidc_cea861.h.

   #define XVIDC_EDID_VERBOSITY          0

   where XVIDC_EDID_VERBOSITY is defined in the following table.

   XVIDC_EDID_VERBOSITY	Description
   0 (Default)	Read and parse the EDID No display of capability
   1	Read and parse the EDID Display of basic capability of the sink
   2	Read and parse the EDID Display of full capability of the sink

   Important: In the Example design running on MicroBlaze™ , limited BRAM resources are allocated to store the software binary. If you enable the XVIDC_EDID_VERBOSITY to a higher level, which consumes more software resources, you might need to increase the BRAM allocation. Otherwise, you might experience system instability such as UART hangs.
4. Press h to check the HDCP status.
   Note: The HDCP debug menu is not enabled by default. You can enable it by setting it in xhdmi_example.h.

   /* Enabling this will enable HDCP Debug menu */
   #define HDCP_DEBUG_MENU_EN 1

   Note: You must check the software size so that it does not exceed the allocated blockRAM.
5. It is recommended that you use the following steps while changing the video mode through the HDMI application during TX-Only mode (as a color bar or any supported video pattern available) in a pass-through topology or TX-only topology example design:
   1. Select the intended resolution from the menu (by default, the video mode color space is set to RGB, frame rate is set to 60 Hertz (except, 576p and 576i which are 50 Hertz, and the 3840x2160p (SB) which is 30 Hertz, and the color depth is set to 8 BPC)
   2. Select the intended frame rate from the menu (this will only change the frame rate on top of the video mode set in 5.a)
   3. Select the intended color space from the menu (this will only change the color space on top of the video mode set in 5.b)
   4. Select the intended color depth from the menu (this will only change the color depth on top of the video mode set in 5.c)
      Note: Color depth option should be set at the last step.