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.

LMX2594: LMX2594 Lock Time Issue in Full Assist Mode

Part Number: LMX2594


Good afternoon,

we are using 4 LMX2594 PLLs in our project and we are facing issues about lock times.

In particular we have the following PLL output frequencies plan [in MHz] to guarantee:

3000
3200
3400
3440
3500
3800
3920
4420
4480
4600
4720
4740
4760
4780
4800

We are using the FULL ASSIST mode and the following loop filter:

The following frequencies changes show lock time in the order of 200us - 400us

  • Start Frequency : from 4420 MHz to 4800 MHz -> Stop Frequency: 3920MHz
  • Start Frequency: 4600 -> Stop Frequency: 3000 MHz, 3400 MHz
  • Start Frequency: 4480 MHz -> Stop Frequency: 3000 MHz, 3200 MHz, 3400 MHz
  • Start Frequency: 4420 MHz -> Stop Frequency: 3000 MHz, 3200 MHz, 3400 MHz
  • Start Frequency: 4600 MHz -> Stop Frequency: 3440 MHz
  • Start Frequency: 4480 -> Stop Frequency: 4420 MHz, 3440 MHz

Even using the loop filter coming from PLLatinum tool does not reduce lock times.

We are measuring the lock time enabling a counter after the last PLL SPI writing and freezing it when MUXout pin (set as lock detect) goes to logic 1.

What we should check in order to improve the lock times?

Thanks for the support

  • Hello Michele, 
    Would you have any equipment capable of measuring frequency vs time such as PNA? If you do, I recommend measuring lock time by locking the device to one frequency than changing output frequencies and measuring the amount of time it takes to reach your threshold for the output.

    What is your SPI write speed? 
    To make sure I understand, you're measuring Lock time as follows: 

    Besides this, did you design your loop filter using PLLatinumSim? You can also estimate lock time here for you configurations.

    One more thing, the cap closest to the pin should be at least 3.3nF due to degradation concerns. 

    Regards, 

    Vicente 

  • Hello Vicente,

    Thanks for your reply.

    1) Yes we have a Network Analyzer but we need to measure the lock time from firmware so it is not feasable using a PNA. I think we can assume that monitoring MUXout pin for lock detect is reliable for our needs. Is it that correct? What we notice also is that MUXout pin is not stable initally but it stabilizes after some period of time (see attacched picture). Is it a normal behaviour?

    2) SPI speed is 40MHz. Do it affect lock time?

    3) We also use an input Fosc of 20MHz. It also affect lock time?

    4) Yes, we measure lock time as described in your picture.

    5) We also tried to use PLLatinum tool in order to design our loop filter and estimate lock time but we didn't see any improvement for that particular frequencies.

    6) Do you mean that the Cap closest to the Vtune pin should be at least 3.3nF?

  • Hi Michele, 
    1. For me personally, using a Phase noise analyzer is more feasible. As I mentioned it's far easier to lock the device and then change output frequencies and measuring the time it takes to settle to your required threshold. You can also monitor MUXOUT or even Vtune trigged by the last programming action (R0) 

    When you report MUXOUT being not being stable, has the device been programmed and VCO calibrated? If so the behavior your describe is odd but if you're referring immediately after power up before the device locks - then behavior is normal. 

    2. Max SPI writes speed is 75 MHz - though 40 MHz is pretty fast I wouldn't expect significant improvement. 

    3. OSCIN frequency will affect lock time. 

    5. Yes for a 20 MHz input- I won't expect much improvement given frequency is low. Please try 100 MHz input if possible. 

    Regards, 

    Vicente