Forum Discussion

ClaraIF's avatar
ClaraIF
Icon for New Contributor rankNew Contributor
3 months ago

Questions about the ALTPLL module in Quartus Prime 20.1 Lite

I would like to raise some issues that have arisen while using Quartus 20.1 Lite and the ALTPLL module:

  1. How does the Band Width setting affect the PLL lock mechanism? Specifically, if the configuration allows for a wider input clock frequency range, does this imply that the generated output clock could have greater variability? Or is the output frequency always guaranteed to be exactly as configured as long as the input clock remains within the selected BW range?
  2. Does the BW range affect the deactivation of the Locked signal? In other words, does having a more permissive BW range reduce the probability of Locked being deactivated?
  3. Does the selected BW range affect the Quartus compiler’s timing analysis? What output clock deviation does the timing analysis take into account when a specific BW setting is applied?
  4. I wanted to check the compilation results for the PLL with the different BW options. It compiles correctly with both “Low” and “Medium”, but when I select “High” after compilation, it gives me the results for “Medium”. No error appears in "MegaWizard Plug-In Manager"; in fact, the message ‘Able to implement the requested PLL’ appears. Could it be a problem with my PLL configuration? Or with the project configuration itself? Could you clarify how such a change would affect the compiler’s behaviour and timing analysis results? Is there official documentation on the internal operation of the PLL and how the BW affects it? I found the next ones, but I would like to know if there is more: "MAX10 Clocking and PLL User Guide" and "PLL IP Core User Guide".

Thank you,

Clara Iracheta

4 Replies

  • FvM's avatar
    FvM
    Icon for Super Contributor rankSuper Contributor
    Hi,
    PLL bandwidth settings affects dynamic behaviour, ability to track a frequency modulated or jittering clock and locking speed. It does not affect static locking and pulling frequency range as far as I'm aware.

    PLL output in locked state follows the defined frequency ratio.

    Timing analysis and compilation result doesn't depend on bandwidth setting.

  • ShengN_altera's avatar
    ShengN_altera
    Icon for Super Contributor rankSuper Contributor

    Hi,


    How does the Band Width setting affect the PLL lock mechanism?

    May check here https://www.intel.com/content/www/us/en/docs/programmable/683732/17-0/parameter-settings-89007.html

    Specifically, if the configuration allows for a wider input clock frequency range, does this imply that the generated output clock could have greater variability?

    Not exactly. The frequency ratio is still enforced.

    Or is the output frequency always guaranteed to be exactly as configured as long as the input clock remains within the selected BW range?

    Yes, the output frequency is always guaranteed to be exactly as configured, as long as the PLL is locked and the input clock frequency is within the allowable operating range (which includes the effect of the bandwidth setting and VCO range).


    Does the BW range affect the deactivation of the Locked signal? In other words, does having a more permissive BW range reduce the probability of Locked being deactivated?

    Yes. Can refer here https://www.intel.com/content/www/us/en/docs/programmable/683732/17-0/parameter-settings-89007.html also


    Does the selected BW range affect the Quartus compiler’s timing analysis? What output clock deviation does the timing analysis take into account when a specific BW setting is applied?

    Not exactly.


    but when I select “High” after compilation, it gives me the results for “Medium”.

    This is reporting bug, will report this. You can rest assured that the configuration is taking place correctly if you refer to the bandwidth range which is correct.


    Thanks,

    Regards,

    Sheng


  • ClaraIF's avatar
    ClaraIF
    Icon for New Contributor rankNew Contributor

    Hi Sheng.

    Thank you for your reply!

    The question arises because we have observed noise issues in the clock during some tests and we want to maximise the availability of the equipment without compromising security (ensuring that the time analysis is correct for the effective PLL output frequency). In other words, we want the noise/jitter to have as little effect as possible and only lose the Locked status when the output frequency is compromised.

    Which configuration is more appropriate: Low or High bandwidth?

    Thank you,

    Clara

  • ShengN_altera's avatar
    ShengN_altera
    Icon for Super Contributor rankSuper Contributor

    Hi,


    Use low BW because you care about minimal jitter.

    If that causes unacceptable Locked deassertions, increase BW only as much as needed to regain availability.


    Thanks,

    Regards,

    Sheng