Home
  • Products
  • Solutions
  • Support
  • Company
  • Products
  • Solutions
  • Support
  • Company
Community Forums Custom IC Design Observing PLL Phase Noise with hbnoise

Stats

  • Replies 3
  • Subscribers 127
  • Views 240
  • Members are here 0

Observing PLL Phase Noise with hbnoise

illaoi
illaoi 12 days ago

Consider an integer-N type-2 PLL with reference of 50 MHz and output frequency of 2400 MHz (N=48) with no behavioral model for any of the blocks (VCO, PFD, CP, Divider,...), all designed with PDK.

Usually selecting Oscillator and selecting oscillator nets with estimation of frequency works fine in analyses, however I personally have had issues to obtain the phase noise of the output of the PLL.

I believe in either pss or hb, since you have a reference clock, checking oscillator box would stop the simulation since it argues that you have a periodic signal (reference) which is inevitable in PLL simulation. 

Therefore, it makes sense not to choose oscillator, but to choose the harmonic, in the case I mentioned the 50 MHz, and either have >=48 number of harmonics are maybe 2 tone in hb analysis and then hbnoise to obtain phase noise. Please keep in mind that VCO control voltage will have an input reference leak that would create spurs around 2.4 GHz with 50 MHz spacing.

I have tried both of them but in all cases, the simulation never converged (of course, I mean hb, or pss, when no oscillator has been selected), thus can anyone comment on if I took any steps wrong or any better way that I can do to obtain phase noise?

P.S. To get a sense of the PLL phase noise I used PhaseNoise function in the calculator but that requires so many cycles to be able to see close in phase noise.

  • Reply
  • Cancel
  • Cancel
  • ShawnLogan
    ShawnLogan 12 days ago

    Dear illaoi,

    illaoi said:
    Consider an integer-N type-2 PLL with reference of 50 MHz and output frequency of 2400 MHz (N=48) with no behavioral model for any of the blocks (VCO, PFD, CP, Divider,...), all designed with PDK.

    and

    illaoi said:
    I have tried both of them but in all cases, the simulation never converged (of course, I mean hb, or pss, when no oscillator has been selected), thus can anyone comment on if I took any steps wrong or any better way that I can do to obtain phase noise?

    The fact that the PSS portion of your simulation sequence does not converge is not surprising illaoi for several reasons.

    1. Even if your simulation converged, the divider ratio of 50 will stress the simulator and your computing resources (i.e., memory) as described in the Troubleshooting article at URL:

    https://support.cadence.com/apex/ArticleAttachmentPortal?id=a1Od000000056dyEAA&pageName=ArticleContent

    or by typing "spectre -h rfmemory".

    2. As your PLL approaches its steady-state, the input and output frequencies are not identical. This alone prevents pss convergence as it requires that all frequencies in the steady-state are synchronous. If you try to include a long tstab interval to  allow the input and output frequency to be closer in frequency, you might as well consider running a transient simulation to examine steady-state performance in lieu of waiting the same time and only then start a pss analysis.

    3. For these reasons, my understanding based on reference [1], is Cadence does not recommend using a pss/pnoise simulation to estimate PLL performance. In lieu of this, the use of a conventional transient or transient noise simulation is proposed.

    From my experiences, we relied on transient analyses to evaluated PLL parameters such as settling, stability, phase offsets, reference spurs and other parametric. Phase noise of the PLL output was evaluated using a combination of behavioral models, pss/pnoise results for the VCO, and knowledge of the large signal PLL transfer functions.

    I hope this provides some information to help you.

    Shawn 

    [1] https://community.cadence.com/cadence_technology_forums/f/rf-design/49390/pss-pnoise-simulation-for-vco-and-pll

    • Cancel
    • Up 0 Down
    • Reply
    • Cancel
  • illaoi
    illaoi 10 days ago in reply to ShawnLogan

    Shawn,

    Thanks for the reply, though let me clarify why this "In lieu of this, the use of a conventional transient or transient noise simulation is proposed." will not be practical.

    Needless to say, transient is not goanna cut it since there is no noise from noisy components, therefore it must be tran noise for phase noise estimation. 

    Consider 10 GHz oscillator that we are interested in seeing 10 MHz offset phase noise, that means, at least I need, 1/10M, 100ns of cycles, which would be 100ns/100ps, which is thousand cycles.

    That would take a very long time for the whole PLL simulation. Also, do you recommend using PhaseNoise function as I mentioned?

    • Cancel
    • Up 0 Down
    • Reply
    • Cancel
  • ShawnLogan
    ShawnLogan 10 days ago in reply to illaoi

    Dear illaoi,

    illaoi said:
    Needless to say, transient is not goanna cut it since there is no noise from noisy components, therefore it must be tran noise for phase noise estimation. 



    While you are absolutely correct that a conventional transient analysis will not provide an estimate of the phase noise of the output clock, there is merit in its use prior to performing a transient noise simulation. Why do I suggest this?

    1. If you are planning to perform a transient noise analysis to estimate output phase noise, it is necessary to assure your simulator settings and simulation time are sufficient to provide an accurate model of the steady-state behavior of the phase-locked loop. Since a conventional transient simulation will require less computing resources than a transient noise simulation, verifying the simulator settings and settling behavior of the phase-locked loop with a conventional transient simulation is more efficient. With respect to this item, please also note my comment in response to your second comment below.

    2. You may want to use the state variables from the end of your conventional transient simulation as initial conditions or nodesets for your transient noise simulation to expedite its settling time. As you know, with a high gain VCO (i.e., Kvco ~ GHz/V), knowledge of the nearly converged VCO control voltage can expedite settling to a particular frequency.

    illaoi said:

    Consider 10 GHz oscillator that we are interested in seeing 10 MHz offset phase noise, that means, at least I need, 1/10M, 100ns of cycles, which would be 100ns/100ps, which is thousand cycles.

    That would take a very long time for the whole PLL simulation.


    I totally understand your concern illaoi and have faced this same quandary! I also hesitate to add, but feel I should, that the situation you attempt to quantify is much worse.

    As I mentioned in item (1), in order for a transient noise simulation to provide accurate results, the portion of the simulation you analyze for phase noise must represent near steady-state behavior. In the example you provided, you note: "that means, at least I need, 1/10M, 100ns of cycles, which would be 100ns/100ps, which is thousand cycles. That would take a very long time for the whole PLL simulation.". In reality, if you are simulating with real components, your integration time must be on the order of the minimum time feature or less. For example, your charge-pump (I assume yo meant your PLL is actually third-order) will produce pulses that are far far less than the period of the VCO. In addition, the change in VCO frequency per cycle will be far less than its period. I have worked with cases where the charge-pump offsets are only correctly estimated when the integration time step is on the order of ps for VCO in the 10 - 30 GHz range. These simulations take days and weeks to perform as they approach steady-state behavior. As I am sure you also know, an improper estimate of the charge-pump phase offset due to simulator accuracy settings will lead to an incorrect estimate of phase-locked loop sub-harmonics and hence an incorrect phase noise estimate.

    So, in summary, yes, I fully acknowledge your comments with respect to simulating a phase-locked loop with real components (i.e., without behavioral views). This fact served as the motivation for my alternate suggestions. They are more time efficient and have proven themselves accurate in my experiences.

    illaoi said:
    Also, do you recommend using PhaseNoise function as I mentioned?

    The phaseNoise() function is for use with a pss/pnoise based analysis and can be used following a converged pss/pnoise analysis. From the ViVA or ocean reference manuals, its input datasets are one of the following:

    Signal dataset—Select the signal data set from the drop-down list. Available options: pss_fd, hb_fd, hb_mt_fi, and qpss_fi

    For a transient noise simulation, phase noise is computed from the PSD. It can be obtained from the transient noise GUI (see Figure 4) , but I must warn you, a substantial amount of knowledge or experience with its arguments and simulator settings is necessary to produce a valid estimate of phase noise. it does produce valid results - but knowledge of the simulator and PSD/phase noise parameters is very important to assure the accuracy of the estimate. I am happy to help out if that is a path you decide to try.

    I am sure my responses will put a frown on your face illaoi, but I must be honest in responding! Sorry!

    Shawn

    • Cancel
    • Up 0 Down
    • Reply
    • Cancel

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.

© 2023 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information