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.
Part Number: LMK04828
We have a board with two FPGAs and four LMK04828s. Each FPGA programs two of the LMK04828s. However, each of the four LMK04828s share the same oscillator reference which is fanned out using a low jitter LVDS buffer. The two LMK04828s programmed by the first FPGA appear to have acceptable phase noise performance compared to the baseline taken using the evaluation board. However, the other two LMK04828s connected to the second FPGA have terrible phase noise under 100k offset and the charge pump output pin appears to have a sawtooth-like waveform. The first two LMK04828s are identical in schematic design to the second set of LMK04828s and their layouts are very similar, but not 100% the same. I do not understand what could possibly be going on with the second set connected to FPGA 2. They are like this on all boards so its not just a one-off issue. I am including screenshots of the eval board basline which has about 287fs of jitter, an output of one of the second LMK04828 on the first FPGA & its CPout value, and an output of the second LMK04828 on the second FPGA & its CPout value. Also included screenshots of part of the schematic showing the output used to connect to the E5052A. This output has 240 ohm bias resistors since the output is LVPECL. Also shown is a schematic showing the clock reference and fanout buffer.
We are glad that we were able to resolve this issue, and will now proceed to close this thread.
If you have further questions related to this thread, you may click "Ask a related question" below. The newly created question will be automatically linked to this question.
In reply to Dean Banerjee:
1. The board is already powered on for minutes before we even program the FPGAs so the LDO would already be stable (we are manually programming FPGAs with Vivado at this point). 2. Have not tried a double write, however we are in the process of reading back register values to verify that everything written to the LMK matches what is read back. So far its good. The programming speed of the SPI clock is around 2.5MHz.
3. i should also note that the two LMKs that are not working correctly do report that PLL2 is locked (be reading the register value) which is odd because with that much variation on CPout and the phase nose on the output, I do not see how it could be locked.
In reply to kevin priest:
This VCO requires calibration, which is internal to the device and triggered by the action of programming the 0x168 register to any value. This calibration searches through a large number of frequency bands and determines the correct frequency band and amplitude; this is all internal to the device. For this calibration to be valid, the internal LDOs of the device need to be stable and PLL1 needs to be locked. Although the supply is stable, I don't know if the default power on reset state for all internal LDOS is powered up or not; it's not the case for many of our other devices. The other thing would be if the VCO calibration runs before PLL1 is locked. In this case, it could calibrate to the wrong frequency band and get stuck there. Note that when you read the regsiters back, you get the same results whether the calibration is successful or not.
To test this theory, wait at least 10 ms and then program register 0x168 one more time to the same value to re-activate the VCO calibration for the PLLs with the problem. If this fixes your problem, then points to the timing of the writing to the device. If not, it's something else.
if we write 0x0F into 0x168 nothing happens. At least nothing we can detect on the signal source analyzer. If we write 0x00 to 0x168 we get a different profile (shown below), however the output clock is about 297MHz and PLL2 is not locked. If we then write 0x0F back to 0x168 at this point, the PLL locks and the phase noise plot goes back to looking all distorted again. We noticed DAC LOCKED register is always low - but do not know what this means. I also probed all of the voltage pins on the IC and did not see a difference between the two LMKs that work and the two that do not. The only difference seen on the pins is the jitter on the clock outputs and the the CPout behavior. What could the issue be? If the thermal pad was not soldered down properly could this be the case? Or noise coupled into a particular pin?
Do I understand that you have more than one board with 4x LMK04828s. On each board the LMK04828s in the specific position of... I'll call them #1, #2, #3, or #4 each have the same behavior between boards?
Based on your charge pump voltages not being railed, I expect the locking and calibration to be OK.
The charge pump sawtooth looks as if there is some large leakage pulling the charge pump high or low. If you tri-state the PLL2 charge pump, are you able to confirm this net is high impedance or if there is some impedance pulling to ground or Vcc? For this test, set PLL2_CP_TRI = 1. This is located in register R361, bit 1.
* Granted, your schematic looks legit for your PLL2 loop filter.
What is the frequency of your PLL2 phase detector? Looking at the charge pump waveform, it seems the period is about 570 us resulting in ~1754 Hz PDF rate?
It seems both plots you shared, the good and the bad both have spurs at this ~1.7 kHz frequency... although I don't see that in the EVM case. In the 'good' case the spurs are small. In the 'bad' case the spurs are totally destroying your phase noise.
> Could you share your programming with me? Or at least the PLL2_R, PLL2_REF_2X_EN, PLL2_N, and PLL2_P values for starters? With your 20 MHz reference, I would expect you have PLL2_R = 1 and optionally the doubler enabled for a 40 MHz PDF frequency.
> One more thing, what is the state of pin 6, SYNC/SYSREF_REQ? Is it quite? Noise can couple from that pin to VCO0, and to a lessor extent VCO1.
Dean BanerjeeWe noticed DAC LOCKED register is always low - but do not know what this means.
When PLL1 is being used an TRACKING is being used for Holdover, DAC LOCKED means the proper holdover voltage which will be applied by a DAC will be minimized based on the current PLL1 Vtune. Not applicable to your issue.
To design your own Clock Tree solution, visit WEBENCH Clock ArchitectMore information Clock and Timing System products: http://www.ti.com/clock-and-timing/overview.html
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.