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.

LMK04610: Periodic Unlocking of PLL1 on startup.

Part Number: LMK04610

Hello,

I have run into some unexpected behavior with the PLL1 DLD on the LMK04610. It appears that the device indicated PLL1 lock shortly after startup as expected, but then indicates unlock periodically for  up to a couple minutes. When observed on an oscilloscope the lock signal can bee seen to start with an unlock period of around 600Hz and then slowly decrease in frequency. This increase in time between unlock events eventually leads to a stable PLL1 lock detect output indicating the PLL is locked. I have not seen it unlock again after the lock detect signal goes stable. I have included an example scope screen shot below in Figure1.

I have attempted to adjust to the PLL1 tuning thinking it was ringing, but adjustment of the PPL1 proportional gain has little to no effect until the extremes where it causes the PLL to become unstable. Adjusting PLL1 integrator gain does reduce the time to a stable lock signal, but maxing out the PLL1_INTG parameter only reduces the stable lock time to around 5 seconds.

Figure1: Unlock signal shortly after startup (Pink) and correspond VCXO voltage (Orange)

In another effort I adjusted the DLD lock count. Lowering the lock count did not effect the stable lock time, but increasing the lock count to above 0x080000 had a substantial impact on the lock detect signal. I made a table showing the tested values and rough time to a stable lock detect signal below. This seems counter intuitive and makes me believe there is something about the DLD that I am mis-understanding or have incorrectly configured.

Lock Cycle Count Approximate Lock Stable Time
0x000400 10 seconds
0x004000 10 seconds
0x020000 10 seconds
0x040000 10 seconds
0x080000 2 seconds
0x200000 < 1 second

As a starting point I have included the TICS Pro file used as the base configuration for my testing and here are my system specs

VCXO: Crystek CVHD-950

Ref Oscillator: Abracon AOCJY2 

Ref Frequency: 100MHz

VCXO Frequency: 125MHz

VCXO Gain: +3.125kHz/V 

If anyone else has seen this lock detect signal behavior or can provide some advice on how to fix, or further trouble shoot, this behavior It would be extremely helpful. 

101747_TI_Example_250MHz_1_4.zip

  • Looks like PLL1 locking process was interrupted when a reference is not stable at power up.
    Monitor status pins with "HOLDOVER_EN" and "PLL1 LOCK Detect" , to see if PLL1 entered holdover status repeatedly.
    It can explain why larger lock count can achieve a shorter lock time , because locking process is not be interrupted.
  • I looked at the status output set as HOLDOVER_EN and it appears that holdover is not active during the majority of the PLL1 lock time. I have attached a screenshot of the PLL1 lockdetect and Holdover status waveforms. I also tested a register set with Holdover disabled and the periodic unlock behavior is the same.

    Yellow is the holdover status and blue is the PLL1 lock detect signal. It appears after about 150ms the holdover is de-asserted and does not re-assert. The solid blue region is where the PLL1 lock detect is doing the periodic toggle as described in my original post.

  • It is strange.
    1, Could you monitor VCXO output frequency when PLL1 LD in toggling? It can tell us what behavior in loop control.
    2, Another method to reduce lock time is to adopt a larger phase detect frequency. In GUI, there are examples with 1.288MHz PDF and corresponding loop filter settings.
    3, I checked Ref Oscillator: Abracon AOCJY2 is an OCXO, so the reference should be good enough. I think your tests had been past OCXO stability time.

    BR,
    Shawn
  • Shawn,

    1.) I monitored the VCXO output frequency using a spectrum analyzer and saw a gradual increase to ~125MHz from power on until the lock detect indicated a stable lock. The power up frequency was typically a couple Khz below the 125MHz VCXO freq. I saw corresponding behavior when monitoring the VCXO control voltage, which gradually increased to a stable value of 2.1v.

    2.) I tested a pll1 configuration with a 1.25MHz PFD and It did decrease the lock time to 0.75sec ( lock indicated by the DLD). The DLD output was still indicating the periodic unlock events as described previously just with a faster decay to stable lock indication. I have attached a screenshot of the DLD signal to clarify.

    3.) The system is usually running for half an hour or more before my testing so the OCXO should be stable.

    Do you expect there to be some locking and unlocking indicated by the DLD during startup? Also, it seems to me the behavior is likely tied to the DLD itself not the actual PLL loop given the stable increase of the VCXO freq/control voltage, but a more experienced opinion on this would be appreciated.

    From my understanding increasing the PFD frequency will also increase phase noise passed from the OCXO, is this just a trade off that needs to be made between phase noise and lock time?

    Thanks for the help,

    Seth Kreitinger

  • Hi Seth,
    My colleague will continue to look into your case. Thanks for your patience.

    BR,
    Shawn
  • Hi Seth,

    Something wrong in E2E make no response in E2E. Let me clarify the Digital lock detect signal.

    It is expected in PLL locking.

    As datasheet showed, phase error should be less than a specified window size (ε) for continuous enough times (PLLx Lock Count), one time violation would reset count. If the violation happened after locked, digital lock status will change from lock to unlock.

    In PLL locking, feedback clock phase is tuned to close to reference clock phase, it can have some frequency ringing around target frequency. In PLL locking, because frequency had not been locked, phase relationship on PFD (phase frequency detector) is moving.Ahead, close, behind will periodically happen until PLL locked. When we set a small PLLx lock count, we can saw obvious periodic lock and unlock on digital lock detect status.

    For why large PLLx Lock Count can make a fast lock, I had not thought of the whole flow, but Figure 40 can give some clues.

    Datasheet also shows "Digital Lock Detect Frequency Accuracy", which also related with above figure.

    Hope we can find the cause soon. let us know your thought. I had looped my colleagues in E2E system for more discussion.

    Thanks.

    Best Regards,

    Shawn

  • Hello Seth,

    I apologize for the delay. I wanted to check and see what your status is on this topic.

    Looking at your info about the lock stable time decreasing as you increase lock detector counter, it seems there is some predefined event at about 0.1 Hz which is causing an unlock... or phase error > epsilon which is kicking it out of lock. When you program the high count time, it simply takes longer for the DLD to assert, but the reset time is the same.

    Are there other system processes you could stop on your PCB to see if they are causing some interference?

    Are you able to try a different reference vs the OSCin into CLKin? Could there be a momentary phase glitch on the reference source?

    73,
    Timothy