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.

DS90UB953-Q1: DS90UB953-Q1/DS90UB954-Q1

Part Number: DS90UB953-Q1

Hello,

I'm struggling to configure a DS90UB953 serializer with a DS90UB954 deserializer in RAW10 mode.

My input timing configuration is:

Pixel Clock: 88MHz

Active area: 1280x720

Horizontal blanking: 500

Vertical blakning: 100

CLOCKIN(reference clock) = 50MHz

The connection between the transceiver is coaxial mode(single ended, 50Ohm).

I would like to know exactly what register are need to be configured to have both the transmitter and the receiver succesfully comunicate in RAW10 mode (only one port, port 0).

Also an example with different timing would be helpful.

Thanks

Best Regards,

Fabio

  • Hi Fabio,

    Are you using a camera with DVP interface or CSI interface? What about the processor...is it DVP or CSI?

    953 supports CSI input and 954 supports CSI output. It doesn't make sense to use 953-954 for RAW10 mode operation since both devices uses CSI interface.

    Best,

    Jiashow

  • Hello Jiashow,

    I'm using both (serializer/deserializer) the CSI interface but I need to configure it in RAW10 mode.

    Is this mode not working or there is some issue?

    I see in the specification/datasheet that is clearly a possible way of transmission.

    Thanks

    Best Regards,

    Fabio

  • Hi Fabio,

    Do you mean your CSI format is RAW10? If so, just configure the device in CSI-2 Synchrnous mode (Refer to the Typical Application diagrams in the datasheet).

    On the software portion, write to the following registers:

    # Set up Port0
    board.WriteI2C(UB954, 0x4C, 0x01)

    # Set up Back Channel Config (0x58)
    board.WriteI2C(UB954,0x58,0x5E)

    # Set up SER ID (this should be automatically loaded)
    #board.WriteI2C(UB954,0x5B,UB953ID)
    # Set up SER Alias ID (pick an alias ID for your serializer)
    board.WriteI2C(UB954,0x5C,UB953)
    # Set up Slave/Camera ID (use the real I2C address of your camera)
    board.WriteI2C(UB954,0x5D,sensorID)
    # Set up Slave/Camera Alias ID (pick an alias ID for your camera)
    board.WriteI2C(UB954,0x65,sensorAlias)

    Communicate to your serializer and camera using the alias IDs.

    Best,

    Jiashow

  • Hi Jiashow,

    I'm using a DS90UB953 serializer in DVP Bacward compatibility mode RAW10 transmitting to a DS90UB954 deserializer in DVP Backward compatibility mode RAW 10 too.

    Both the CSI interfaces of the chipset are managed by uC, not real cameras.

    I would like to know if this configuration(both the chipsets in backward compatibility mode RAW 10) is allowed by transceivers or not?

    In case, could you please send me an example configuration with both registers chipsets?

    Thanks

    Regards,

  • Hello,

    please could you confirm it is possible to have both, the DS90UB953 serializer in DVP Bacward compatibility mode RAW10 and the DS90UB954 deserializer in DVP Backward compatibility mode RAW 10 too?

    Is a script to configure pattern generator in this mode available?

    In the datasheet of the DS90UB953-q1 pag 59 Table 114. PGEN_CSI_DI (Address 0x03) is specified:

    "This field controls the value sent in the CSI-2 packet for the Data Type. The default
    value (0x24) indicates RGB888."

    Where I can find the value for RAW 10 mode and the other allowed non-default value?

    Thanks

    Best Regards,

    Fabio

  • Hello,

    I need to configure both the DS90UB953 serializer in DVP Bacward compatibility mode RAW10 and a DS90UB954 deserializer in DVP Backward compatibility mode RAW 10 too.

    Is this configuration allowed?

    Is a script to configure pattern generator in this mode available?

    Thanks

    Regards,

  • Hi Fabio,

    Since 953 input is CSI and 954 output is CSI input, to the SerDes, there's no backwards compatibility needed. You cannot configure both 953 and 954 in backwards compatibility mode. If uC is outputting CSI data, there's no need to configure the 953/954 in backwards compatibility mode since to the SerDes, they are receiving CSI data. The reason why you would want to configure for backwards compatibility mode is when you have a 953 connected to a 914/934 (DVP deserializers) or a 954 connected to a 913/935 (DVP serializers).

    Best,

    Jiashow

  • Hello Jiashow,

    What you say indeed correct, but let me try to explain better the reasons behind my colleague's request.

    Our company is a manufacturer of test equipment, and we feature among our products several camera simulators based on TI chips, and we have quite a strong experience with them.

    In this specific application the display is featuring a 954 deserializer,  this board is made by our customer and we have no control at all over it.

    We verified that the 954 mentioned above is configured to pair with a 913, it locks and the video stream is present.

    Now we need to generate video to the same display with a 953, but keep in mind that we cannot change the 954 configuration at all, since it's beyond our control.

    So the question is, how can we configure the 953 chip for the test aformentioned,? And... is this possible at all?

    Thanks,

    Marco

  • Hello Jiashow,

    we need to know how to configure a 953 to behave exactly like a 913.

    Best Regards,

    Fabio

  • Hi Fabio and Marco,

    Thanks for clarifying this. Unfortunately, there's no way to configure 953 and 954 in backwards compatibility mode. But it might be possible to configure 953/954 without changing the hardware.

    Are you able to change the software configuration of the 954? With a 953 and a 954, you have to be running at either synchronous mode or asynchronous mode. If running at 4G is too high, it's possible to run the 953/954 at a lower rate if need be .

    A couple of questions:

    • What's the reference clock frequency of the 954?
    • What are the AC coupling cap values the 954 is using? If the 954 is using 100nF for RIN+ and 47nF for RIN-, then the 954 devices can function properly with a 953 and a 913.
    • Are you using PoC? If PoC is being used, it gets trickier, because you need to make sure the PoC filter is able to filter out the forward channel and back channel frequencies. Perhaps it's possible to run this at a lower line rate.

    Best,

    Jiashow