Post Go back to editing

AD9106, no SPI/startup after clock update

Hello,

I am designing a high speed circuit based on the AD9106 DAC, controlled by a small Arduino board.

Basically I got everything up and running a while back using a LT6904 adjustable clock source. This solution as single-ended and only worked up to ~25MHz, so I upgraded it to a differential clock using an AD8138 amplifier. This released the full potential of the LT-clock, 65MHz.

Only problem was the noise created on the 3.3V supply (and the fact that I would like to increase clock >100MHz).

To improve the circuit further I changed the clock source to a LMK61A2-125 (125MHz, LVDS output, very low jitter).

Unfortunately there was no output on the DAC after the change, nor can I communicate with it over SPI (which also used to work, of course). I have tried writing my old setup to the DAC as well as reading data from the internal registers, but nothing seems to work.

The clock IC is connected as shown in the attached picture, from the AD9106 datasheet, with a 100R resistor across the output (I tried on both sides of the coupling-caps, as shown in the LMK61A2 evaluation board documentation), and i can measure the clock signal on the inputs.

I measure this using two single-ended probes (but the circuits does not work even without the probes), and see ~550mV DC offset on each clock input, with a ~400mVpp clock signal on top of it.

Now, the AD9106 datasheet specifies a DC level of 900mV, but this is internally biased and since the circuit worked before I have to assume this is not the cause(?)

(To put it simply; it will be a major task to change back to the LT6904 circuit - one that I wish to avoid if possible).

Anyway, those are the symptoms, not unlike what a guy in here had experienced (ez.analog.com/thread/67752), but changing the clock source and decreasing VCC to 1.8V is not an option for me... But then again; the DAC should be able to run at 3.3V with differential clock, right?

Sorry for the long post, please feel free to ask any questions I have have no been clear enough :-)

Regards,

David Larsen.