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: FPDlink III Splitter

Part Number: DS90UB960-Q1

Hello, TI experts.

We want to use a device that can acquire image signals losslessly in FPDlink III without affecting the ECU's image acquisition (without changing the controller's software) for video transmission debugging.

Is there such a solution?

Analog signal replicate?
Deserializer*1+Serializer*2?
Or other options?

Thank you!

  • Hi Jian Huang,

    In this case for a FPD3 system we would need to use a UB960, with two UB953 connected (one on each CSI TX port of UB960). The UB960 can be configured in replicate mode which would replicate the CSI data being sent from the camera to be sent to both the ECU as well as the other ECU / PC for monitoring.

    Please let me know if you have any questions here.

    Best,

    Thomas

  • Hi Thomas,

    Thanks for your reply .

    Does this solution require modifying the ECU driver?
    In addition, can the reverse channel still be transparently transmitted to the sensor's I2C?

    Are there any analog switches that can achieve similar functionality?

    H.J.

  • Hi H.J.

    The downstream ECU could receive the data in the same format as if the serializer was directly upstream from the ECU. There would need to be some care taken to ensure that the SOC on the ECU could still configure the upstream serializer & camera sensor.

    There is a multiplexor which we have used for FPD-Link devices, but I'm not aware of any splitter which we've used in the past.

    HD3SS3411-Q1 data sheet, product information and support | TI.com

    Best,

    Thomas

  • Hi Thomas

    Can the red control channel in the picture below enable access and configuration to the sensor?

    Does the configuration of 953_1 and 960 also need the SOC of the ECU to complete (configuration of I2C address, video stream copy, etc.)?

    H.J.

  • Hi H.J.

    Yes, if the I2C bus of the UB953 is connected to the UB960 on the blue board we could have either configuration of the upstream UB953 either by a local I2C controller on blue board or by the SOC on ECU. How this is configured would by decision to be made from system level.

    For pass through from ECU to upstream SER:

    • ECU targets device 0x30, alais 0x0A
    • 953_1 outputs transaction to 0x30 to local bus (UB953_1 and UB953_2 strap to 0x32)
    • UB960 configured to pass through transaction to 0x30 to SER (ser alias & ser addr can be set to 0x30)
    • Transaction terminates at serializer with read / write

    Please let me know if you have questions here.

    Best,

    Thomas

  • Hi Thomas

    The two methods mentioned earlier are:

    1,The SOC in the ECU configures UB960 and UB953 on the blue board, and the software of the SOC in the ECU needs to be modified;
    2,Add an MCU to the blue board to configure UB960 and UB953, but the configuration of the camera in the ECU (such as ISP control signals, diagnostics, etc.) cannot be transmitted over.
    I'm not sure if my understanding is correct.


    Do you have any suggestions for a solution that can separate the video stream without modifying the ECU software?

    H.J.

  • Hello Jian,

    Thomas is OoO today and will be back tomorrow.

  • Hi H.J.

    For solution 2 mentioned above we should be able to configure pass through for I2C transactions & other diagnostics such that they pass from the upstream camera to the downstream deserializer associated with the ECU. This should allow the split without need for updating the ECU SW.

    Best,

    Thomas