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.

DS90UB935-Q1: Clock output anomaly

Part Number: DS90UB935-Q1
Other Parts Discussed in Thread: DS90UB934-Q1

Hello,

I am inputting a 40 MHz (crystal) clock to the serializer (CLKIN), and need to get 20 MHz out (CLK_OUT) for the sensor. 

To achieve this, I set CLK_DIV to 4, M to 1, and N to 14. 

I based my register values off the equation provided in the datasheet: CLK_OUT = FC x [M / (HS_CLK_DIV x N)], where FC should equal 28 x CLK_IN  (for the DVP RAW10 mode).
Thus CLK_OUT = 28 * [1 / (4*14)] * CLK_IN = 1/2 CLK_IN.

I've ran a series of tests using different reister values, and. I've concluded that the error lies in the FC constant, which is always 16.8x (CLK_IN) rather than 28x. I can't find any registers on the serializer that sets this beyond the mode setting, which is strapped. The FC constant should be based on the number of bits per transaction (28), so I'm not sure if the error lies in the sensor, serializer, or deserializer

For instance, I've set: HS_CLK_DIV = 4, M = 4, N = 28, so that CLK_OUT = CLK_IN, expecting 40 MHz out. Instead I am getting 24 MHz out. The only thing that factor be causing this discrepancy is the FC multiplier, which is 16.8 rather than 28 (28/16.8 = 5/3).

If anyone has insight into the reason why the forward channel data rate is always 3/5ths the rate it should be, I would really appreciate your help.

I am using the serializer in conjunction with DS90UB934 deserializer in DVP (backwards compatable) mode.

Thanks,

Sam

 

  • Hello Sam,

    have you followed this document?

    http://www.ti.com/lit/an/snla270a/snla270a.pdf

    As you can see in page 6, the required value of CLK_DIV for this mode should be = 1.

    Remember also in DVP mode the CSI-2 throughput must exactly match the output throughput: in RAW10: CSI-2 Throughput = CLKIN × 20

  • Hello Hamzeh,

    Thank you for your timely response.

    I should clarify that by saying "I set CLK_DIV to 4, M to 1, and N to 14", I was referring to HS_CLK_DIV as CLK_DIV. I just checked and confirmed that CLKIN_DIV is indeed 1, as per the datasheet. 


    As for the CSI-2 throughput, the bit rate should be 800 Mb/s, which is 20x the 40 MHz serializer reference clock. 

    Edited to add a test result: I've noticed that the PCLK output on the deserializer is stuck at 24.5 MHz, no matter what the timing settings are on the serializer. (When the serializer is unplugged or powered down the PCLK line on the deserializer end is low.) Whereas the serializer datasheet claims that downstream PCLKs will be equal to twice the sensor's reference clock, that is not the case for my system at the moment. Does this imply that the SerDes connection is faulty?

    What other factors could affect the forward channel data rate? Page 21 of the DS90UB935-Q1 asserts that the FC data rate is f x 28, but I am still getting f x 16.8 for all cases. Could the error trace back to deserializer settings, or is it isolated to the serializer? 


    Thanks ,

    Sam

  • Hamzeh,

    Upon closer review of the "Backwards Compatibility Modes" document you reference above, I've realized that Table 2 (Strap Configuration Mode Select) states backward compatibility only works for Coax cable. My system has been designed for STP cable.

    Is there any way to use the DS90UB935-Q1 serializer with the DS90UB934-Q1 deserializer in STP RAW10 mode?

    Please do let me know if you have a solution or if you can confirm that this will not work.

    Edited to add a test result: I decided to go ahead and alter my board for Coax mode functionality (cutting the DOUT- line and terminating both ends to ground w/ RC network as per the data sheet). Conclusion: nothing changed in terms of clocking; the aforementioned issue persists. Nonetheless, the system is now configured for DVP RAW10 over Coax. Any further advice would be much appreciated.

    Thanks,

    Sam

  • Here are the results of my measurements on various clocking schemes. The FC value is calculated based on the aforementioned equation, all others were either inputted or measured.

    So to clarify, the two questions at hand are:

    1) Why is the forward channel data rate so consistently misbehaving?
    2) Is it possible to operate the 935/934 link in DVP (backwards compatible) mode over STP cable?

  • Hello Samuel,

    I believe you have some incorrect settings on your system. It can be hardware or register settings. Hence please send me both schematics + register dumps from both devices.

  • Hamzeh,

    I've attached the SerDes register dump and schematics for the circuits that use the SerDes components. I can send you the full schematics via direct message when you add me.

    Please do let me know if you spot any errors or need further information. I am looking forward to hearing back from you.

    Best regards,
    Sam Shafer

    3884.Eureka SerDes reg dump.pdf

    1881.Eureka SerDes reg dump.xlsx

  • Hello Sam,

    Here is the schematics review feedback. I will check the register dumps and come back to you.

    934:
    - At CMLOUTs you do have a short circuit. Please connect via 100nF capacitors as per d/s figure 25.
    - On the pins 3, 20, 34, you are missing the 10nF capacitors. (See d/s figure 25)
    - On pin 17, a 1uF capacitor is missing before connecting VDD18 to IDx and MODE. (See d/s figure 25)
    ==================

    935:
    - on PDB pin you need 10Kohm instead of the 12.1Kohm (See d/s figure 18)
    - PDB pin must be connected to the main 1V8 not to VDDPLL (See d/s figure 18)
    - Mode pin must be connected to the main 1V8 not to VDDD (See d/s figure 18)

  • Update:

    After a few hours of error tracking in the software, I have identified the source of the error and resolved it.

    Register 0x14 on the Serializer (REMOTE_BIST_CTRL) was set to force a FC error. Once unset, the clock issue resolved .

    I am still wondering about the ability to use STP cables in DVP mode. Is this possible? Please let me know. Thanks.

    Regards,

    Sam

  • Hello Sam,

    good news. Thanks for sharing.

    Yes, you should be able to use Coax as well STP.