Post Go back to editing

Restrictions on jumps between different frequencies using manually programmed VCO calibrations settings

Thread Summary

The user is experiencing occasional lock failures with the ADF4368 synthesizer when using manually programmed VCO calibration to jump between frequencies, particularly from 6.0 GHz to 12.2 GHz. The issue can be resolved by toggling the PD_ALL bit or the MUTE_NCLK bit, but this adds an extra 120 us of delay. The support engineer suggests optimizing the register write sequence and confirms that the lock loss is related to a meta-stability issue in the N counter. The user will test these suggestions and verify if they can reduce the delay.
AI Generated Content
Category: Hardware
Product Number: ADF4368

We are using the manually programmed VCO calibration to jump quickly between various frequencies (about 10 or so frequencies spanning the full range of VCO cores).  We dwell on each frequency for about 10ms.

We have found that occasionally the ADF4368 will not lock when a new frequency setting is applied.  It is a bit unpredictable when this will occur.  When it does occur, subsequent frequency changes using the manually programmed VCO calibration will continue to fail. Something appears to be locked up.  To clear the lock up, we have to either program a new frequency with automatic VCO calibration enabled or cause a brief power down of the IC by asserting the PD_ALL bit and then de-asserting it.

As a workaround, we are now always doing a brief power down of the IC after the last step of a frequency change using  manually programmed VCO calibration (the last step being to write register 0x10).  But this then causes about another 150us of delay to the frequency change.  While, this is still much faster than using the automatic VCO calibration, but we'd like to avoid this additional delay.

  • Are there some restrictions regarding jumps between frequencies using the manually programmed VCO calibration procedure?  (i.e. is it okay to jump from a frequency using a different VCO core?). 
  • Is there any other way (faster) to clear a lockup without the use of the PD_ALL bit?

Thread Notes

Parents
  • Thanks for all the points to help speed the process.  We are incorporating most of those already.  We'll try to optimize our code as much as practical.

    The MUTE_CLK toggle is working stably under all our test conditions. So, I'll mark that post as the answer to this thread.

Reply
  • Thanks for all the points to help speed the process.  We are incorporating most of those already.  We'll try to optimize our code as much as practical.

    The MUTE_CLK toggle is working stably under all our test conditions. So, I'll mark that post as the answer to this thread.

Children
No Data