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.

DS90UB960-Q1: ALP remote serializer error

Part Number: DS90UB960-Q1
Other Parts Discussed in Thread: ALP, USB2ANY, , DS90UB953-Q1, , TDA4VM

Hi TI Team,

I use USB2ANY tool to connect DS90UB960-Q1 custom board to test the signal receiving quality of FPD-LINK. The camera I use is DS90UB953-Q1, the resolution is 1920*1080, but the remote serializer in the ALP information shows DS90UB913 and the resolution is not correct. I don’t know if it’s caused by LAYOUT trace or a software setting error. How to solve the problem? ,

Thanks

  • Hi Geralt,

    Thanks for reaching out. 

    The horizontal resolution being displayed on ALP is correct. This is because the horizontal resolution in ALP is being displayed in bytes, and the YUV422 8-bit data format has 2 bytes per pixel. As a result, the number of bytes in the horizontal resolution would be 1920*2 = 3840 bytes, which matches the value being displayed in ALP.

    In regards to ALP showing the incorrect serializer being connected, this can be fixed by using either of the following methods:

    -Clicking on the "Scan Connected Devices" option, and double clicking on the I2C target address of the serializer that you want to connect to.

    -Opening the scripting tab in ALP, and running the following command: "board.devaddr = serializer_I2C_target_address"

    Regards,

    Kenneth

  • Hi Kenneth,

    I tried using both methods but couldn't read the camera serializer model number,
    - Click the "Scan for connected devices" option, only the deserializer address 0x7a appears, and the serializer model number cannot be obtained even if you click it.
    - Open the script tab in ALP and run the following command: "board.devaddr = 0x30", also can't get the correct serializer model number,
    Is there any other way to solve this problem?

    Thanks

  • Hi Geralt,

    Thanks for providing an update.

    You previously mentioned that the DS90UB960-Q1 that you are using is on a board that you designed. Is the DS90UB953-Q1 that you are using also on a board that you designed, or is it on a TI EVM (the DS90UB960-Q1EVM)?

    Additionally, I will reach out to other members of the team to see if there is anything else that can be done to resolve this issue. I will provide an update by next Monday at the latest. 

    Regards,

    Kenneth

  • Hi Geralt,

    Thank you for your patience. 

    I spoke with other members of the team, and have gained some understanding for why this may be happening. 

    ALP may be showing that a different serializer is connected because the back channel is operating at a data rate that is not supported by the mode that the serializer is currently set to operate in. From the screenshot that you have provided, it looks like the back channel is currently operating at a data rate of 50 Mbps. For the DS90UB960-Q1, use register 0x58 to set the back channel data rate to 10 Mbps, and see if that changes the connected serializer shown by ALP. If changing the back channel data rate to 10 Mbps doesn't resolve this issue, please let me know.

    Regards,

    Kenneth

  • Hi Geralt,

    I would also like to mention that in order for the connected serializer to update in ALP, you may also have to click on the "Scan Connected Devices" button again after the back channel data rate is changed to 10 Mbps. As previously mentioned, if changing the back channel data rate does not resolve this issue, please let me know. 

    Regards, 

    Kenneth

  • Hi Kenneth,

    I tried to change the back channel data rate to 10 Mbps, but it still doesn't solve the problem,

    I tried to use another different model camera serializer which is DS90UB913, it is able to display correctly,


    In addition, we don't have TI EVM (DS90UB960-Q1 & DS90UB953 EVM), so we can't compare if it's an ALP setting problem or a problem with the camera or our custom board.

    It seems that the back channel is valid, but why the serializer will display incorrectly, is there anything that needs to be reconfirmed?

    Best regards

  • Hi Kenneth,

    I tried to change the value of the register 0x0C and found that the model of the serializer can be detected correctly. Is this setting correct? If I want to use BIST mode for testing, can it run normally?

    Best regards

  • Hi Geralt,

    To determine if the device settings are correct, I'll need some more information about the configuration of both devices. Therefore, I have the following questions:

    What I2C port of the DS90UB960-Q1 is the USB2ANY connected to? If the I2C port connected to the USB2ANY wasn't mapped to the correct RX ports, then that could explain why changing the settings of register 0x0C fixed this issue.

    Additionally, could you provide some more information about the configuration of the mode pin for each device? What is the mode pin configuration for the DS90UB960-Q1? What is the mode pin configuration for the DS90UB953-Q1?

    Regards,

    Kenneth

  • Hi Kenneth

    USB2ANY is connected to DS90UB960-Q1 I2C_2(Pin 7,8), because I2C(Pin 11,12) has been connected TDA4VM uses, DS90UB960-Q1 mode pin default RX MODE is RAW12HF, but I think that is not important, because TDA4VM will change the setting to be correct according to the use of CAMERA, and I don’t know what the mode pin configuration of DS90UB953-Q1 is, Because the CAMERA we use is an outsourced finished product, is there any other way for me to confirm the mode pin?

    Best regards

  • Hi Geralt,

    Thanks for providing additional details about your test setup. 

    USB2ANY is connected to DS90UB960-Q1 I2C_2(Pin 7,8), because I2C(Pin 11,12) has been connected TDA4VM uses,

    It looks like ALP was unable to recognize the device initially because the I2C port that was connected to the USB2ANY was not mapped to the RX ports that were connected to the serializer. As shown by your previous screenshot, it looks like this issue has now been corrected, since the I2C port connected to the USB2ANY device is now mapped to the RX ports connected to the serializers. The USB2ANY should now be able to communicate successfully with both the serializer and deserializer, since ALP is now identifying the correct serializer connection. 

    is there any other way for me to confirm the mode pin?

    The mode of the serializer can be determined by reading the value of bits 2:0 in Register 0x03 of the DS90UB953-Q1. 

    Regards,

    Kenneth