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.

CDCE6214-Q1: What is the expected LVDS input common mode?

Part Number: CDCE6214-Q1
Other Parts Discussed in Thread: CDCE6214

Hi,

I *had* a circuit working fine for a few months, then all of a sudden the CDCE6214 won't lock any more to the 10MHz input clock.

The output of U11 is clean. Nice LVDS with 400mV swing on each line, centered around 1.2V.

However, despite me loading the correct (and same configuration since 3 months), now on the PRIREF input of U15 (the CDCE6214) is centered around 0V (which seems like a big problem to me).

So my question are:

* Shouldn't the CDCE6214 polarize the LVDS lines to be centered around 1.2V?

* What input common mode does the CDCE6214 expect (couldn't find the info in the datasheet).

I have changed the chip 3 times, to no avail. always the same problem: will never lock to the 10MHz input LVDS clock. Also, the CLK_OUT_P/N from U15 is flat, (according to configuration, it should be outputting 10MHz, as was the case before it stopped locking). That makes me think that the CDCE6214 is not seeing any input for some reason.

Any hints on where to look next?

I have attached my TICS pro register dump.

R85	0x00550000
R84	0x00540000
R83	0x00530000
R82	0x00520000
R81	0x00510004
R80	0x00500000
R79	0x004F0008
R78	0x004E0000
R77	0x004D0000
R76	0x004C0008
R75	0x004B0008
R74	0x004AA181
R73	0x00492000
R72	0x00480006
R71	0x00470000
R70	0x00460008
R69	0x0045A181
R68	0x00442000
R67	0x00430006
R66	0x00420006
R65	0x00410808
R64	0x0040A181
R63	0x003F0000
R62	0x003E0028
R61	0x003D0000
R60	0x003C0008
R59	0x003B2008
R58	0x003A502C
R57	0x00390000
R56	0x00380028
R55	0x0037001E
R54	0x00363400
R53	0x00350069
R52	0x00345000
R51	0x003340C0
R50	0x003207C0
R49	0x00310013
R48	0x003023C7
R47	0x002F03D0
R46	0x002E0000
R45	0x002D4F80
R44	0x002C0318
R43	0x002B0051
R42	0x002A0002
R41	0x00290000
R40	0x00280000
R39	0x00270000
R38	0x00260000
R37	0x00250000
R36	0x00240000
R35	0x00230000
R34	0x00220000
R33	0x00212710
R32	0x00200000
R31	0x001F0000
R30	0x001E00F0
R29	0x001D0000
R28	0x001C0000
R27	0x001B0004
R26	0x001A0000
R25	0x00190401
R24	0x00188026
R23	0x00170000
R22	0x00160000
R21	0x00150000
R20	0x00140000
R19	0x00130000
R18	0x00120000
R17	0x001126C4
R16	0x0010921F
R15	0x000FA037
R14	0x000E0000
R13	0x000D0000
R12	0x000C0000
R11	0x000B0000
R10	0x000A0000
R9	0x00090000
R8	0x00080000
R7	0x00070C0D
R6	0x00060000
R5	0x00050008
R4	0x000400C0
R3	0x00030000
R2	0x00020003
R1	0x00012310
R0	0x00001010

  • Hi Ibrahim,

    When the device is configured for differential input, AC-couple to the reference clock is required. Your schematic is correct. You should be able to measured some DC voltage at the Pri or Sec input pins, this DC voltage is generated internally. Now you measured zero volt, did you power it down by accident? Is the device drawing any current? Power down current is around 3mA.

  • Hello Noel,

    Thanks for the feedback.

    I have finally solved my problem. My I2C was little too fast (400KHz) and i must have had a little too much capacitance on my I2C lines. Thus, my system was at the limit of operating correctly.

    If that may help others (on top of your message), once correctly configured, the DC votlage on input LVDS lines is 1.5V (that's what i measured).

    Thanks,