This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

DS90UH929-Q1: What HDCP CTS tool does BU use for HDCP validation?

Part Number: DS90UH929-Q1

Hello Team,

My customer will use UH929 and UH940N with HDCP 1.4.

but it is first time to use UH929/UH940N for HDCP 1.4.

so they questioned what HDCP CTS tool TI use for validation. then they can be on same page to validation this feature.

Could you pls help advise??

Thank you.

  • Hello Harry,

    TI used an external authorized test center (ATC) from DCP to qualify UH949/UH929 HDCP. The test house used a Panasonic UITA-2000 module to perform the CTS testing. 

    It is worth noting though, that the procedure is complicated compared to standard HDCP CTS testing. The reason is that technically 949/929 works as an HDCP repeater device. But standard HDCP repeater devices have an HDMI input and an HDMI output. However since 949/929 is a serializer/deserializer system with FPD output, it only has an HDMI input and no HDMI output (even on the DES side). 

    For that reason it can't be tested as a repeater using the standard CTS process. Instead, the 949/929 needs to be tested as an HDMI receiver device which requires programming some reserved settings to the device to make it advertise as a receiver instead of repeater. 

    Best Regards,

    Casey 

  • Hello Casey,

    Thanks for reply in detail.

    Instead, the 949/929 needs to be tested as an HDMI receiver device which requires programming some reserved settings to the device to make it advertise as a receiver instead of repeater. 

    You told it requires some setting to act as HDCP receiver. so what register does my customer need to configure to do this test??

    I also have our HDCP app note and on reading it but it is quite complicated ^^;;

    3835.SNLA287_HDCP.PDF

    Could you pls help to move further on this??

    Thank you.

  • Harry,

    Is the customer intending to actually run HDCP compliance testing here? If so, how will they perform it? Do they actually have compliance test HW like what I mentioned above? It is not typical for customer to run compliance testing for HDCP specifically. We can support discussion on the topic, but we are not a test house so if they need to get into the detailed test procedure it is best if they work with an ATC like we did from our side to walk through the process. We can support questions related to device capabilities and any config scripts needed to set the part into receiver mode instead of repeater mode.

    Best Regards,

    Casey  

  • Hello Casey,

    Yes, They are planing to purchase it. I informed that TI doesn't support for HDCP test procedure and you may go to test equipment to get support for it. I also told that we can support it to pass if any CTS item has issue as receiver.

    Thank you.

  • Harry,

    Ok thank you for clarifying to the customer that TI is not an ATC and does not have deep knowledge about the test procedure to support walking them through all of it. Attached is the ATC application form with capabilities we provided during our own testing for reference:

     HDCP on HDMI Test Application and Product Capability for ATC rev u.doc

    Here is the HDCP compliance setup script to be run prior to testing in order to set the device to receiver mode:

    DS90UH949-Q1 HDCP Compliance Setup.py
    """
      TI Confidential - NDA Restrictions
    
      Copyright 2020 Texas Instruments Incorporated. All rights reserved.
    
      IMPORTANT: Your use of this Software is limited to those specific rights
      granted under the terms of a software license agreement between the user who
      downloaded the software, his/her employer (which must be your employer) and
      Texas Instruments Incorporated (the "License"). You may not use this Software
      unless you agree to abide by the terms of the License. The License limits your
      use, and you acknowledge, that the Software may not be modified, copied or
      distributed unless embedded on a Texas Instruments microcontroller which is
      integrated into your product. Other than for the foregoing purpose, you may
      not use, reproduce, copy, prepare derivative works of, modify, distribute,
      perform, display or sell this Software and/or its documentation for any
      purpose.
    
      YOU FURTHER ACKNOWLEDGE AND AGREE THAT THE SOFTWARE AND DOCUMENTATION ARE
      PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED,
      INCLUDING WITHOUT LIMITATION, ANY WARRANTY OF MERCHANTABILITY, TITLE,
      NON-INFRINGEMENT AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL TEXAS
      INSTRUMENTS OR ITS LICENSORS BE LIABLE OR OBLIGATED UNDER CONTRACT,
      NEGLIGENCE, STRICT LIABILITY, CONTRIBUTION, BREACH OF WARRANTY, OR OTHER LEGAL
      EQUITABLE THEORY ANY DIRECT OR INDIRECT DAMAGES OR EXPENSES INCLUDING BUT NOT
      LIMITED TO ANY INCIDENTAL, SPECIAL, INDIRECT, PUNITIVE OR CONSEQUENTIAL
      DAMAGES, LOST PROFITS OR LOST DATA, COST OF PROCUREMENT OF SUBSTITUTE GOODS,
      TECHNOLOGY, SERVICES, OR ANY CLAIMS BY THIRD PARTIES (INCLUDING BUT NOT
      LIMITED TO ANY DEFENSE THEREOF), OR OTHER SIMILAR COSTS.
    
      Should you have any questions regarding your right to use this Software,
      contact Texas Instruments Incorporated at www.TI.com.
    
    """
    ############################
    # DS90UH949-Q1 HDCP Compliance Setup
    # Set UH949 into HDCP receiver mode instead of repeater mode to enable compliance testing 
    ############################
    
    import time
    import sys
    
    # System dependant variables - adjust according to system 
    UH949 = 0x18        # 949 I2C Address
    
    # Disable Internal HDCP Controller
    mask = int('10000000',2)
    bridgeread = board.ReadI2C(UH949,0x54,1)
    BRIDGE_CFG = bridgeread | mask
    board.WriteI2C(UH949,0x54,BRIDGE_CFG)       # Enable HDMI/HDCP External Control 
    
    # Deassert Hot-plug
    board.WriteI2C(UH949,0x48,0x01)
    board.WriteI2C(UH949,0x49,0x00)
    board.WriteI2C(UH949,0x4A,0x00)
    board.WriteI2C(UH949,0x4B,0x00)
    board.WriteI2C(UH949,0x4C,0x00)
    board.WriteI2C(UH949,0x4D,0x00)
    board.WriteI2C(UH949,0x4E,0x01)
    
    # Disable HDCP Repeater
    board.WriteI2C(UH949,0x48,0x01)
    board.WriteI2C(UH949,0x49,0x00)
    board.WriteI2C(UH949,0x4A,0x06)
    board.WriteI2C(UH949,0x4B,0x00)
    board.WriteI2C(UH949,0x4C,0x00)
    board.WriteI2C(UH949,0x4D,0x00)
    board.WriteI2C(UH949,0x4E,0x00)
    
    # Reset FPD3 TX HDCP (for both TX ports in case previously enabled)
    board.WriteI2C(UH949,0x1E,0x03)
    board.WriteI2C(UH949,0xC3,0x80)
    board.WriteI2C(UH949,0x1E,0x01)
    
    # Assert Hot-plug
    board.WriteI2C(UH949,0x48,0x01)
    board.WriteI2C(UH949,0x49,0x00)
    board.WriteI2C(UH949,0x4A,0x00)
    board.WriteI2C(UH949,0x4B,0x01)
    board.WriteI2C(UH949,0x4C,0x00)
    board.WriteI2C(UH949,0x4D,0x00)
    board.WriteI2C(UH949,0x4E,0x01)

    Best Regards,

    Casey