Other Parts Discussed in Thread: LMX2581, , CODELOADER, USB2ANY, LMX2592, LMX2594, LMX2572, LMX2582
Hello,
I have a question about the time it takes to change frequency on the LMX2581E. This is a similar concept to the lock time but slightly different as I will explain below.
I have been measuring this by triggering off the Latch Enable signal and measuring the time for Lock Detect to go high. As I measure this I view the clock, Latch Enable, and Lock Detect on the oscilloscope. This works well for cases where only one register needs to be changed but not for when two or more registers need changed.
Device;LMX2581
Evaluation board: LMX2581EVM in original configuration with internal VCO.
Software; Codeloader program version 4.20.02, Part file version 2014-11-09
Reference; 47.5MHz
Windows 7 SP1 64 bit
Connected with USB2ANY
I notice for some frequency changes that two registers need to be programmed. For example if I change PLL_NUM even just by one number, this changes registers 0 and 1 as there are bits of PLL_NUM in both registers. When viewing the CLK signal for these changes, I notice the delay between the programming of the two registers to be about 20ms. This blows out the time taken for the frequency to change to above 20ms.
In cases where only one register needs to be programmed, the time between programming and actual frequency shift is closer to 150uS as mentioned in the datasheet p7 under VCO Calibration Time.
I set up a sequence in TICs Pro burst mode to program the registers 0 and 1 straight after one another with no delay in between and I still got the same delay of around 20ms when I looked at the clock signal on the oscilloscope.
Is there any way to reduce this time between programming registers?
Many thanks
Helen