Presentation on theme: "HDMI Test Tools September 2008"— Presentation transcript:
1 HDMI Test Tools September 2008 Quantum Data, Inc.HDMI Test ToolsSeptember 2008
2 Quantum Data HDMI Support CEA 861-D/VESA Format LibrariesCreation of “Complex” Test images/test sequencesHDCP TestsCEC TestsEDID TestsAnalyzer FunctionsFunctional Tests
3 882E Test Instrument User-friendly front panel. Ethernet with built-in browserRS-232 serial connectionBuilt-n functional and compliance tests
4 Navigating the 882EThe 882E product supports access to all test functions through the following:Front Panel Interface“Tools” > “Reports”“Tools” > “Analyzer”“Content” > “Image File”Built in web page, accessed by Internet Explorer or any other web browser
5 Format Libraries CEA-861-D Format Libraries VESA Format Libraries Programmable Custom Formats
6 Image LibrariesC++ SDK for creating complex images and complex test sequences (Script Runner)..bmp files can be stored.Animated test images.Image Files & Function TestsImage support for up to 12 bbp/channel at 4:4:4 video sampling rate (HDMI 1.3b).
7 HDMI Test Equipment 881E Video Test Generator Use case is factory assembly line.882E Video Test GeneratorUse case is development laboratory/sinks.882E AnalyzerUse case is development laboratory/sinks & sources.881/882E Generator882E Analyzer
8 HDMI Functional Testing Definition:Functional Testing occurs after the build has been delivered to a testing environment. Functions are tested by feeding them input and examining the output for validity. An important attribute of functional testing is that there are external specifications to which the tester may compare testing results. In essence, the tester is validating that the program meets the business requirements. Thus, this testing represents one of the easiest assessments to conduct.- University of Minnesota, Dept. of Engineering Glossary, September 2007
9 HDMI Functional Testing The test goal of functional testing is to verify that a DUT with can support declared capabilities.A test of function is typically, but not exclusively, part of the product manufacturing process.
10 HDMI Functional Testing Test ImagesImage ShiftFormat LibraryHDCP TestEDID Data TestLip Sync and LipSyncB Test8 Channel Audio Tests (LPCM, Dolby Digital, Dolby Digital +)DV Swing TestRead and Report InfoframesPixel Repetition TestActive Format Descriptor TestMunsell Color TestDynamic “Deep Color” 12 bbp TestCombined HDCP/CEC TestCEC TestCEC “Ping” TestFormat Rx TestTMDS Analyzer High Level functional tester
11 HDMI Functional Testing Static Test Images (Patterns) provide subjective quality assessment and basic functional test.Animated Test Images can provide subjective assessments of motion artifact in displays.
12 HDMI Functional Testing The “Image Shift” Utility allows any standard image from the built-in image library OR custom images (created with SDK or downloaded .bmp files) to be put into motion.Speed is regulated by line, pixel and field. Direction is regulated with X/Y axis controls.
13 HDMI Functional Testing Format Libraries generate standard timings based on accepted, industry standard specifications.VESA 1.0, Revision 11CEA 861-DSTANAG Class A,B,CCustom formats can can beused to simulate required timingsfor unique application displays.
14 HDMI Functional Testing “HDCPProd” image runs a functional test on HDCP authentication with Sink devices. Results are “pass/fail”.
15 HDMI Functional Testing EDID Data image provides a functional verification that EDID is properly programmed.This is visible on the DUT (Sink) and can be used as a manufacturing test.
16 HDMI Functional Testing Lipsync testing is a subjective test to determine relative synchronization of audio/video in a sink device.Time interval is sec/audio event for progressive formats. Maximum synchronization is sec/audio event when scaled.Time interval is sec/audio event for interlaced formats. Maximum synchronization is sec/audio event when scaled.
17 HDMI Functional Testing LipSyncB Test image is a flashing full-white square 1/8th of major active axisOnly appears in first field of interlaced formatsAudio burst (2 to 3 cycles of sine positioned relative to center of flashing square plus or minus 500 ms
18 HDMI Functional Testing Lipsync handling of source/repeater devices can be tested. Based on current operational specifications of HDMI 1.3b, sinks report audio and video latency in their EDID. An Rx can simulate a sink and send the same data to a source repeater and measure the delay to see if it corresponds to the EDID latency factors.
19 HDMI Functional Testing Audio tests provide functional testing of HDMI audio frequency and amplitude. Eight channels of LPCM (linear PCM) audio can be tested individual, in pairs and all at once, simulating function of 5.1 Audio.
20 HDMI Functional Testing HDMI supports compressed audio. Dolby Digital and Dolby Digital+ are generated as sound clips and can verify that Sink or repeater devices are decoding these formats properly. Subject evaluation of sound quality is also possible.
21 HDMI Functional Testing TMDS digital video swing is changed between 90 mVp-p to 1620 mVp-p. The DV_Swing test is used to evaluate a displays ability to adjust to changes in digital video amplitude and to look for degradation indicated by the image.
22 HDMI Functional Testing Verification of HDMI Infoframe Data.Infoframes can be transmitted as well as received.Data is parsed into human readable textInfoframe data can be changed by adjusting functions in both the DUT and tester to determine proper interaction (See Debug Testing).Tx InfoframeRx Infoframe
23 HDMI Functional Testing Special progressive scan gaming formats use pixel replication (“PixelRep” Image) to display different H res based on a fixed V res. The Pixel Replication Test will test each of ten modes, duplicating pixels form 0 to 10x. Performance of the display is subjectively judged looking for gaps in the drawing.
24 HDMI Functional Testing The “AFDTest” (Active Format Descriptor) image will test monitor display function based on matching aspect ratio with allowed “aperture” (see examples).
25 HDMI Functional Testing Munsell color is universal color that applies to any visual surface. A color is fully specified by listing the three numbers for hue, value, and chroma. For instance, a fairly saturated purple of medium lightness would be 5P 5/10 with 5P meaning the color in the middle of the purple hue band, 5/ meaning medium lightness, and a chroma of 10
26 HDMI Functional Testing In colorimetry, the Munsell color system is a color space that specifies colors based on three color dimensions, hue, value and chroma. Several color order systems place colors into a three dimensional color solid of one form or another, but Munsell Color separates hue, value, and chroma into perceptually uniform and independent dimensions, and was the first to systematically illustrate the colors in three dimensional space. The Munsell system, and particularly the later renotations, is based on rigorous measurements of human subjects’ visual responses to color, putting it on a firm experimental scientific basis.
27 HDMI Functional Testing Deep color testing is done with a combination of dynamic test images that will exercise a displays ability to resolve from 4 to 12 bpp depth.Ramp12 ImageRamp Dif
28 HDMI Functional TestsA combined HDCP and CEC Test Image have been created to speed up manufacturing process by adding two tests together. Both tests are run on the DUT (Sink) for the purposes of verifying CEC and HDCP function.
29 HDMI Functional Testing CEC “Ping” verifies that CEC lines are open between two devicesCEC Production Tests gives “Pass/Fail” indication based on requesting and receiving Vendor ID and Physical Address from the DUT
30 HDMI Functional Testing Format Measurements can be done on the Rx port of the 882 Analyzer productImmediate reporting can be viewed on the LCD of the 882 as source device modes are tested.HTML reports with this data can also be generated.Not only verifying the format (mode) but can interprete color depth of “deep color” source devices.
31 HDMI Functional Testing ViewPix Test – Reads and reports RGB values from sourcePix-Err Test – Compares subsequent frames of data for changes in PixelsCable Test – Tests cables by connecting Tx to Rx and using Pseudo Random Noise image.Timing Test – Measures format timingLipSync Test – Tests sources ability to react to Sink latency as described in the EDID
32 HDMI Debug TestingDefinition:“Debugging” is a methodical process of finding and reducing the number of bugs, or defects, in a computer program or a piece of electronic hardware thus making it behave as expected. Debugging tends to be harder when various subsystems are tightly coupled, as changes in one may cause bugs to emerge in another.-Wikipedia “Debug”, August 18, 2008
33 HDMI Debug TestingThe test goal of Debug testing is to exercise the product design to understand and correct implementation errors.A test of function is typically, but not exclusively, part of the product design process and may incorporate tests that would be used later as part of compliance or interoperability testing.
34 HDMI Debug Testing Command Line Control EDID Editor CEC ITE (Interactive Test Environment)SAM+ (Signal Analyzer Module)
35 HDMI Debug Testing Command Line interface can be established: Using access through the “homepage” available on the web interface.Using “Hyperterm” and connecting directly to the RS-232 serial I/OAs a “Telenet” session connecting to the ethernet port.
36 HDMI Debug TestingCommand line interface provides lowest level control of a test device/function:Example: CPTX:OESS <Value>This causes the test equipment to use long reads during authentication where the value corresponding to the following:1 = encryption enable pulse is positioned at the beginning of the vsync pulse.4 = encryption enable pulse is positioned at the middle of the vsync pulse.5 = encryption enable pulse is positioned at the end of the vsync pulse.CPTX:OESS 1 = encryption enable is at the beginning of vsync.
37 HDMI Debug Testing Example: HPPW <Value> This hot plug pulse width command is used to set the hot plug assertion pulse width in milliseconds. The range is 100 to 4000 ms:HPPW 175 = sets the hot plug assertion pulse width to 175 ms.
38 HDMI Debug TestingEDID editing and applying specific EDID changes provides a way to study how changes will effect Sink, Sources and RepeatersEDID editting can be:Applied to the Rx of an analyzer to emulate a sink.Re-applied to a Sink DUT to determine interactions.
39 HDMI Debug TestingEDID Editor allows for EDID emulation in testing source devices.Create or extract an EDID file and load it on one of two 882E inputs.Four block EDID are programmable.Block 0Block 1Block 2Block 3
40 HDMI Debug Testing EDID functions can be incremented and reapplied. Overall function and individual functions of products can be tested.Entries can be made in “human readable” terms which does not require hexadecimal code.Files are saved and stored in .xml with conversion to text possible.
41 HDMI Debug TestingCEC ITE provides tools for “debugging” CEC protocols.Bit TimingBus ArbitrationCorrupted BitsTest for correct messageacknowledgement.Allows “Op Codes” tobe sent on pull downmenus and looks atsend and receiveresponse.
42 HDMI Debug TestingAnalyzing formats generated by a source/repeater and being able to append measures allow comparision of known good format to one requiring some debugging.SAM+ (Signal Analyzer Module) receives HDMI video and breaks it down, compares it to our built-in library and can recalculate the report and express it in the language of HDMI Compliance Test Specification – simulating an ATC test.
43 HDMI Debug TestingA primary consideration in debug testing is to stress a design to test limits.The ability to understand code/hardware interaction in a DUT is built into test proceduresResults of debugging may be determined by the ultimate goal of meeting business case requirements all the way to Compliance testing
44 HDMI Debug TestingNOTE: Because many functions of HDMI are destined for compliance testing, many of compliance tests may also be used for debugging purposes.Example: CEC function may not even be possible until basic electrical function of the CEC bus is operable.The CEC ComplianceTest, Section 7 couldbe used to test viabilityof the bus.
45 HDMI Compliance Testing Definition:Conformance testing, also known as Compliance testing, is a methodology used in engineering to ensure that a product, process, computer program or system meets a defined set of standards. These standards are commonly defined by large, independent entities such as the Institute of Electrical and Electronic Engineers (IEEE), the World Wide Web Consortium (W3C) or the European Telecommunications Standards Institute (ETSI).- SeachSoftwareQuality, 15 February, 2007
46 HDMI Compliance Testing The test goal of compliance testing is to verify that a DUT meets the technical requirements of a specific set of written standards.A test of compliance is typically to determine acceptance of minimum standards required for commercial acceptance of a product. Typically there are two levels of compliance testing:Laboratory TestingSelf-Certification
47 HDMI Compliance Testing HDMI Specifications:HDMI Specification 1.1HDMI Specification 1.2HDMI Specification 1.2aHDMI Specification 1.3HDMI Specification 1.3aHDMI Compliance Testing Specifications:Compliance Test Specification 1.1Compliance Test Specification 1.2aCompliance Test Specification 1.3aCompliance Test Specification 1.3bCompliance Test Specification 1.3b1Compliance Test Specification 1.3c
49 HDMI Compliance Testing EDID Compliance Test corresponds to the following Compliance Test Sections:Test ID 7.1 EDID Related Behavior (Source)Test ID 8.1 EDID Readability (Sink)Test ID 8.2 EDID VESA Structure (Sink)Test ID 8.3 CEA Timing Extension Structure (Sink)Test ID D Format Support Requirements (Sink)Test ID 8.18 Format Support Requirements (Sink)Test ID 8.19 Pixel Encoding Requirements (Sink)Test ID 8.20 Video Format Timing (Sink)
50 HDMI Compliance Testing EDID Compliance Test requires that a CDF (Capabilities Declaration Form) be completed to base-line the test.Tests declare in a CDF both mandatory and optional features based on what the product supports.
51 HDMI Compliance Testing The EDID Compliance test parses the EDID data into human readable text. The EDID blocks are shown for reference and the specific product data is provided for reporting purposes.
52 HDMI Compliance Testing Sink Device EDID Compliance Reports are generated as an HTML file and include Product Information, CDF, EDID blocks and “pass/fail” test results.Sink Device EDID Compliance Test Results are broken down by:Test IDTest Step“Pass/Fail” results by test stepTest Section Summary “Pass/Fail”
53 HDMI Compliance Testing Test ID 7.1 EDID Related Behavior:EDID Emulators on an Rx port provide EDID for testing source behavior.EDID Emulators can be programmed with up to four blocks of EDID data.Block 0Block 1Block 2Block 3
54 HDMI Compliance TestCEC Compliance Test corresponds to the following Compliance Test Sections:Test ID 7-1,7-2 Electrical TestsTest ID 8.1,8.2 Signaling and Bit TimingTest ID 9.1 thru 9.7 Frame CommunicationTest ID 10.1 Device Installation and AddressingTest ID 11.1 FeaturesTest ID 12-1,12-2,12-3 Invalid Message Tests
55 HDMI Compliance Testing CEC Compliance Test provides TPA (Test Point Adaptors) for Quiescent and Dynamic Electrical Testing.TME (Test Management Environment) Software performs the test functions and reporting.
56 HDMI Compliance Testing The CEC test requires device selection, identification of the product and inputting CDF (Compliance Declaration Form) data.
57 HDMI Compliance Testing The CEC TME is automated and takes the operator threw appropriate test IDs, based on the type of product and features declared.Each test sections begins by providing interconnection diagrams and recommended test equipment.All tests call out CEC Test ID numbers for clear reference to the HDMI Compliance Test Specification.
58 HDMI Compliance Testing Each test section describes the test goal and provides instruction to the operator regarding performance of the test.
59 HDMI Compliance Testing At the conclusion of each test section, results are reported. Summary “pass/fail” is reported as well as specific test sections are given “pass/fail” in detailed reporting.
60 HDMI Compliance Testing CEC Compliance reports are delivered as the testing progresses.Written tests can be requested. The files are HTML files which call out each Compliance Test Section.Sections that pass are given a “Pass” status. “Fails” are reported in detail at the step level.
61 HDMI Compliance TestThe HDCP Compliance Test corresponds to the following HDCP Compliance Test Sections 1.3:Tests of a Source device1A-01 through 1A-09 (downstream with Rx)1B-01 through 1B-06 (downstream with Repeater)Tests of a Sink device2C-01 through 2C-04 (upstream with Tx)Tests of a Repeater device3A-01 through 3A-05 (downstream with Rx)3B-01 through 3B-05 (downsteram with Repeater)3C-I-01 through 3C-I-07 (upstream with Tx, between Tx and Rx)3C-II-01 through 3C-II-09 (upstream with Tx, between Tx and Repeater)
62 HDMI Compliance Testing Product is NOW APPROVED by DCP.Additional changes in the test, addition of the EST and SRM disk have increased test coverage of the HDCP Compliance Test.Certification by DCP identifies the Quantum Data HDCP CT as identical to that being used in the Authorized Test Centers.
63 HDMI Compliance Testing Preparation for testing HDCP requires setting the PCP (Product Capability Parameter):DUT Type Source, Sink, RepeaterSource Max KSVSource Authentication ControlSource Out Only Repeater Yes/NoSink 1.1 Features Supported Yes/NoSink 1.1 Audio Supported Yes/NoRepeater 1.1 Features Supported Yes/NoRepeater Audio Support Yes/NoRepeater HPD Pulse Yes/NoRepeater Max KSVRepeater Out OnlyRep Yes/No
64 HDMI Compliance Testing Enhanced HDCP Compliance Test – Includes EST (Encryption Status Tester) and SRM disk for testing for key revocation.
66 HDMI Compliance Testing HDCP Compliance Test provides a “Summary” of of the test sectionsTest can be run in “Batch Mode” or with command line, individual tests can be run separately.All tests report results matched to the Test ID.Test results are reported with “Pass”, “Fail” and “Warning”
67 HDMI Interoperability Testing Definition:The ability of two or more systems to exchange information and to use the information that has been exchanged.-IEEE Standard Computer Dictionary, 1990
68 HDMI Interoperability Testing The test goal of interoperability testing is to understand product interactions and develop develop systems that operate together seamlessly.A test of interoperability is part of the design process, but may also be needed to analyze specific product system installations in the field.
70 HDMI Interoperability Testing Interoperabilty Testing is accomplished when a product can emulate multilple system configurations and view the results.Many test functions already illustrated in this seminar can be used for studying interoperability:EDID ReportsFormat ReportingInfoframe Data,HDCP TestsCEC Tests
71 ACA Testing Capability The Auxillary Channel Analyzer (ACA) passively sniffs on the I2C bus and CEC bus of the HMDI interconnection. This allows exposure of all Auxillary Channel trafficEmulator to DUTDUT to DUT
72 HDMI Interoperability Testing ACA provides analysis of DDC and CEC bus traffic.HDCP, EDID, HPD and CEC events are logged and time stampedDetail (lower left) and data (lower right) can also be viewed.
73 HDMI Interoperability “Every possibility you add to an interface increases your likelihood of failure”-B.J. Fogg, Stanford University“It is much, much harder to achieve simplicity in interaction design.”-Tim Plowman, University of California, Berkeley
74 HDMI Interoperatbility The complexity of the HDMI transmitter and receiver interface provides fertile ground for interoperability problems.The simpler the end-user operation is, the more complex the internal structures and automation required.Since the days of “HiFi”, consumer electronic products are typically required to interoperate. The “component mentality” of consumers requires that interoperability be addressed at all levels.
75 HDMI Interoperability Interoperability Test Environments:Internal Testing (Debug, Interop, Function)Compliance Testing (both Internal/external)Plugtests (External)Beta Testing (“Adhoc Partner Testing”)Field Experience.Testing locations can be presented as:In the LaboratoryIn the Field (i.e. under common use)
76 Laboratory TestingJoseph Lias, President of Simplay Labs LLC suggests that compliance testing speeds up identification of interoperability issues.Compliance Testing and Interoperability Testing are not the same:Compliance Testing will examine a specific product against a specification. While many interoperability problems may be generally addressed in compliance testing, it is NOT the primary concern.Interoperability testing will examine a product interaction with other related devices. Laboratory methods are not clearly defined
77 Laboratory TestingRunning compliance tests will resolve some high level interoperability problemsExample:CEC Test ID Test Objective is “To ensure that the DUT responds correctly to a <Request Active Source> message when it is the current active source”.The Required Test Method for Test ID is to “Broadcast a <Request Active Source> Message”.The Pass Criteria for Test ID is that “The DUT responds to the <Request Active Source> message by broadcasting an <Active Source> message”.With the correct equipment… you have tested one instant of potential interoperability.
78 Laboratory TestingAdditional test methods for Laboratory Interoperability Testing:Standard: a collection of “Golden” devices that utilize the HDMI interface and might be combined in a system with the DUT.A Test device that can simulate or emulate other devices that might be used in a system with the DUT.A Test device that can view the data transactions that occur between different HDMI DUTs in a system.
79 Laboratory Testing Emulation can be accomplished by using tools like: EDID EditorFormat EditorCEC ITE (Debugging Tool)Command line set ups (through the Web Interface OR the “Settings” button on the front panel)Immediate interactions can be observed in DUT performance and some functions will generate an internal report that describes the interactions.
80 Laboratory Testing“Golden Test” devices or a collection of available consumer electronic devices provide a valid method for understanding interoperability potential.Being able to emulate product is also a reasonable approach. Assuming that the emulation device has been put through rigorous testing and has the flexibility to truly simulate product states that may suggest interoperability.A device to observe and report auxillary channel traffic that promotes interoperability is needed.
81 Laboratory TestingUse of the Auxillary Channel Analyzer (ACA) to study HDCP, HPD and EDID and CEC interactions in the Laboratory
82 Laboratory TestingUsing a “passive sniffer” allows to study interactions between different system DUTs and product emulation isn’t required.
83 Field Testing“Adhoc Field Testing” can provide ways to test interoperability with selected clients, locations or productsPlugtests provide organized ways to combine multiple, unrelated manufactured products for systematic testing.Portable test devices that can be used in the consumers home or office to take a “snap shot” or log observed interoperability problems.
84 Field TestingHT-180 “Hand Shake Tester” is a portable product that can test product in a “real world” application.The HT-180 can observe DDC bus transactions and display data as:Reason codes on the LCDTrace files captured with a notebook computer which are in the same format as the laboratory tool
85 Field Testing Idenfifies 5V, Current and Hot Plug Issues Identifies EDID problems.Localizes HDCP handshake problems
86 Field Testing EDID Failures Checks if EDID port was not acknowledged Checks if EDID port access was attempted by sourceVerifies that EDID header and checksums are validChecks if EDID read was triggered by hot plug detection
87 Field Testing Hot Plug Failures Checks hot plug for < 100ms deassertionVerifies that hot plug downstream assertion is passed to upstreamChecks if hot plug detection assertion upstream was not the result of downstream problemMeasures +5v signals for voltage and current draw on a source
88 Field Testing HDCP Failures Checks for invalid Aksv from sourceVerifies that source write of An occurs prior to write of AksvVerifies that source read of Bcaps occurs prior to read of R0’Verifies that source write of Aksv occurs prior to read of R0’Checks for invalid Bksv from sinkChecks if Ri’ is read without second phase of authentication (in case of repeater)Checks if HDCP reauthentication was triggered by hot plug detectionChecks if HDCP port is not acknowledgedChecks for excessive HDCP re-authentication attempts by sourceVerifies that source attempted to access sink HDCP portChecks if the READY bit is not set as a result of any of the following failure conditions:Repeater did not attempt to read Bksv downstream receiverSource did not begin reauthentication after five secondsInvalid Bksv
89 Field TestingHT-180 can be inserted into a system and can passively observe DDC data traffic between an HDMI source, sink and repeater.
90 Field TestingHT-180 supports “Trace File” formats collected through an ACA. This is the identical format to the laboratory ACA and captures the same type of data (although does not currently support CEC)
91 Field Testing NO_ERROR 0x00, EDID_HEADER_BAD 0x01, EDID_CHECKSUM_BAD EDID_NOT_READ0x03,EDID_READ_INCOMPLETE0x04,EDID_READ_DURING_HPD_LOW0x05,EDID_READ_NACKED_HPD_HI0x06,LARGE_EDID_WITHOUT_EDDC0x07,EDID_NOT_READ_AFTER_HPD0x08,EDID_CROSSED_256_BYTES0x09,AKSV_BAD0x10,BKSV_BAD0x11,FACSIMILE_AKSV0x12,FACSIMILE_BKSV0x13,HDCP_NOT_ATTEMPTED0x14,HDCP_READ_DURING_HPD_LOW0x15,HDCP_NACKED_HPD_HI0x16,AKSV_WRITTEN_BEFORE_AN0x17,
92 Field Testing AKSV_WRITTEN_WRONG_ORDER 0x18, AKSV_SENT_MULT_TIMES HDCP_WENT_BEYOND_LENGTH0x1A,KSV_FIFO_READ_INCOMPLETE0x20,KSV_FIFO_READ_NOT_5_MULT0x21,KSV_FIFO_HAD_BAD_KSV0x22,KSV_FIFO_HAD_FACSIM_BKSV0x23,KSV_FIFO_WITHOUT_BSTATUS0x24,KSV_FIFO_READ_TOO_LONG0x25,KSV_FIFO_MISSING_BKSV0x26,KSV_FIFO_WITH_NO_DEVS0x27,KSV_FIFO_WITH_NO_READY0x28,R0_READ_WITHIN_100MS0x30,R0_READ_BEFORE_BCAPS0x31,R0_READ_WITHOUT_AKSV0x32,R0_READ_BEFORE_BKSV0x33,RI_MISMATCH_CAUSE_REAUTH0x34,R0_MISMATCH_CAUSE_REAUTH0x35,
93 Field Testing SOURCE_USES_SHORT_READS 0x36, BCAPS_RESERVED_BITS_SET BCAPS_NOT_READY_IN_TIME0x41,NO_REAUTH_AFTER_NO_READY0x42,DS_FAIL_WITH_NO_HPD0x43,BCAPS_NOT_POLLED0x44,BCAPS_READY_CAUSE_REAUTH0x45,BSTATUS_HAD_MAX_DEVS_EX0x50,BSTATUS_HAD_MAX_CASC_EX0x51,BSTATUS_RESERVED_SET0x52,BSTATUS_NOT_HDMI_MODE0x53,BSTATUS_HDMI_NO_BCAPS0x54,BSTATUS_DEVS_0_WITH_DEV0x55,BSTATUS_DEV_CNT_0_PROB0x56,BSTATUS_MAX_STAT_NO_PASS0x57,AINFO_1_1_SET_NO_BCAPS0x60,AINFO_RESERVED_SET0x61,AINFO_AFTER_AKSV0x62,
94 Current Reason Code Listings V_PRIME_WITH_NO_BSTATUS0x64,V_PRIME_WITH_NO_READY0x65,DOWNSTREAM_AUTH_NOT_UP0x67,DOWNSTREAM_REAUTH_NOT_UP0x68,REAUTH_CONSTANT0x69,SOURCE_STOPS_POLLING_RI0x6A,DDC_MISSING_STOPS0x6C,DDC_MISSING_STARTS0x6D,HPD_TOO_SHORT0x70,HPD_NEVER_GOES_HIGH0x71,HPD_NOT_PASSED_THROUGH0x72,HPD_NOT_HIGH_AFTER_5_SEC0x73,NO_REAUTH_AFTER_HPD0x74,AUTH_CONTINUES_AFTER_HPD0x75,VOLTAGE_TOO_LOW0x78,VOLTAGE_TOO_HIGH0x79,CURRENT_PULL_TOO_HIGH0x7A
95 HDMI TestingTo provide an understanding of the various levels of testing required for HDMI products and illustrate test methods.To explain the HDMI HDCP compliance test specification in terms of test goals, “shoulds” and “shalls”.To explain HDMI HDCP Interoperability testing useful in both laboratory and field environments.
96 HDMI Testing Thank you for your participation today! You may have questions, so please feel free to contact us:Visit our website atCall us at: