06 | Keysight | N5399C, N5399D HDMI Electrical Performance Validation and Compliance Software - Data Sheet
Using the HDMI EPVC Software
Device Definition
The HDMI software logically guides the user through the test
process. The graphical user interface is designed to glean test
process and device under test information from the user to
efficiently carry out the testing. (Refer to Figure 5.) The user
will know the device type (which determines the test suite) and
which specification applies (HDMI 1.4b or HDMI 2.0). Though
the specifications for HDMI 2.0 and HDMI 1.4b are different, the
selection of HDMI 2.0 will reveal both 1.4b and 2.0 tests, as seen
in Figure 8.
The device definition screen lets users enter the full functionality
of the device for the purpose of creating the test plan. A test
plan is important in order to guide the test process to test at
the specific data rates and test configurations (single-ended vs.
differential) that are required.
Figure 5. Entry screen for HDMI software.
Figure 6. Device definition screen with timings and resolutions table.
New to the Keysight HDMI validation software are the device
definition and connection setup tabs in the setup screen. As
seen in Figure 5, upon start up, these tabs are labeled with a
red status, which indicates that the user has to complete some
actions before proceeding. Also included in the setup screen are
transfer function generation and probe offset calibration. The
probe offset calibration is not new and should be run periodically
to make precision measurements, particularly when measuring
the eye at TP2. The offset calibration is for HDMI measurements
only and will result in the elimination of offsets in the differential
measurements made by the software. The transfer function
generation feature allows the user to create new filters that may
be needed when performing characterizations with different
cable models, different fixtures, equalization and skew. Generally,
the filters, or transfer functions, that are required are already
provided and the user does not have to create any.
This screen enables the standard DUT identification and test
comments, however, the new key feature is the ability to define
the timings/resolutions at which to test. You can enter these
resolutions by:
1. Using the capability declaration form (CDF)
2. Using a previously stored template
3. Using the default setup (which you can define)
4. Adding your own custom timing
5. Independently editing any of these using the check boxes
in the pixel clock tabs at the top of the bottom section
Once the resolution/timing table is defined, it can be stored as a
template or as a default state. If defined as default, it will show up
on all future application start-ups.