Design with DS90UB962-Q1 and DS90UB953A-Q1

Hi Alexey,

The NO_FPD_CLK bit is set when the clock fails to meet a certain threshold frequency. You can configure that threshold frequency in the FREQ_DET_CTL Register (Address 0x77) bits 3:0. Check to make sure the threshold is lower than your clock frequency. At this point, I unable to determine if there is a hardware issue or not.

Thank you,

Carrie

Hi Carrie,

Thank you for reply.

As you advise I tried to configure threshold frequency with setting in FREQ_DET_CTL Register bits 3:0 different values (0x01-0x0f). But that had no effect.

Regards, 

Alexey

Hi Alexey,

Check Register 0x4D to verify lock (LOCK_STS bit) first.

If LOCK_STS isn’t enabled, verify that the MODE input strap pin (Pin 45) is configured correctly. You can do this by checking your circuit with the datasheet or by reading bits 1 and 0 (FPD3_MODE) of the PORT_CONFIG register (address 0x6D). Also verify that the back channel is configured correctly for your modes of operation (BCC_CONFIG register address 0x58).

Once you try this, send me a snapshot of all of your registers so I can take a close look at the values they contain.

Thank you,

Carrie

Hi Carrie,

I select channel 0:
    i2cset -y 1 0x3c 0x4c 0x01

And see LOCK_STS==0:
    i2cget -y 1 0x3c 0x4d
    0x00

My camera data output format is RAW12H, as described in it's datasheet. MODE input strap pin is configured as said in Datasheet DS90UB962-Q1, Table 2, Mode No 6, i.e. RAW12 HF.
I check the configuration:
    i2cget -y 1 0x3c 0x6d
    0x7e
So, I see RAW12 High Frequency Mode is actually selected.

I confirm back channel enabled and it's frequency is selected properly for my case - 2.5 Mbps.
    i2cget -y 1 0x3c 0x58
    0x18

Then I get dump of registers:
    i2cdump -y 1 0x3c
    No size specified (using byte-data access)
         0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f 0123456789abcdef
    00: 78 00 1e 40 d0 01 00 fe 1c 10 7a 7a 0f b9 00 ff x.?@??.???zz??..
    10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 04 02 ..............??
    20: f0 03 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ??..............
    30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
    40: 00 a9 71 01 00 00 20 00 00 00 00 12 01 00 02 00 .?q?.. ....??.?.
    50: 00 00 00 00 00 00 00 00 18 00 00 00 00 00 00 00 ........?.......
    60: 00 00 00 00 00 00 00 00 00 00 00 00 00 7e 88 88 .............~??
    70: 2b 2c e4 00 00 00 00 c5 00 01 00 00 20 00 00 00 +,?....?.?.. ...
    80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
    90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
    a0: 00 00 00 00 00 1b 00 00 00 00 00 00 00 00 00 00 .....?..........
    b0: 1c 3a 14 08 25 00 18 00 ee 33 83 74 80 00 00 00 ?:??%.?.?3?t?...
    c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
    d0: 00 43 94 27 60 f2 00 03 00 00 00 00 00 00 00 00 .C?'`?.?........
    e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
    f0: 5f 55 42 39 36 30 00 00 00 00 00 00 00 00 00 00 _UB960..........

Thank you,

Alexey

Hi Alexey,

The values programmed into the 960 registers look fine. What clocking mode are you using?

I’d like to take a look at a register dump from your serializer, to verify that valid data is being supplied to the link.

Are you using custom hardware or an EVM? If the hardware is custom, are you able to send me the schematic?

Thank you,

Carrie

Hi Carrie,

It is not clear for me how to check the clocking mode, could you advise me please? To get a register dump from the serializer is not a simple task for me, because it is not easy to connect wires to my camera i2c bus. Perhaps it would be possible a bit later. I'm using custom hardware, the schematic is  big enough and complicated and I think it would be better if I answer your questions about possible issues of it.

By the way I got eye diagrams on CMLOUT and they look good, so my camera is working. Then I connected another camera with serializer 933 and saw NO_FPD3_CLK==0 and FREQ_STABLE==1, so the schematic seems to be correct.

Thank you,

Alexey

Hello Alexey,

If you have an EVM, you can check the clocking mode by looking at the MODE bits of the MODE_SEL register of the 953. You can read the 953 register remotely using I2C communication over the backchannel.  

You can check the values of a register on the 953A from the 962 EVM using the scripting tab. Use the board.WriteI2C(SerId, reg, data) and board.ReadI2C(SerId, reg) to read and write values. To access the 962, use the EVM Serial ID 0x7A. To access the serializer, you can read register 0x5B of the 962 for the I2C address and then the read/write I2C commands will allow you to access registers remotely. In your case, you’d use board.ReadI2C(0x7A, 0x5B) to get the Serial ID of the serializer (ser_id) and then use board.ReadI2C(ser_id, 0x03) to get the value of the MODE_SEL register.

You could also look at your schematic to view the strapping of the mode pin of the serializer. As long as you aren’t remotely modifying the MODE_SEL register of the serializer, the mode will be whatever it is strapped to. See Table 8 in the 953 data sheet for strapping configurations.

Regards,

Carrie