• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Custom IC Design
  3. PSS analysis: using variable for beat frequency

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 125
  • Views 16287
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

PSS analysis: using variable for beat frequency

frasheed
frasheed over 9 years ago

Hello,

I have a ring oscillator design and I am running PSS and pnoise analysis using ADE L. For calculating the phase noise and jitter I want the PSS beat frequency to be calculated from my oscillator output i.e. I don't want to manually enter any numerical value for beat frequency. I tried to calculate the frequency by running transient simulation and then adding that variable in beat frequency option in pss analysis but it gives me error that it is not valid variable or expression. Can anyone give me hint how to this ? I am using ADE 6.1.6.500.10

Thanks

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 9 years ago

    When simulating an oscillator in PSS, you need to check the box labelled "oscillator" and then tell it where the output of the oscillator is (this should be the nodes where the fundamental can be found - so if you have an oscillator followed by a divider, it should be the output of the divider).

    You have to give an estimate of the oscillation frequency to give the simulator a clue, but it doesn't have to be very accurate. PSS will solve for the actual oscillation frequency and so there is no need to be terribly accurate here - the chances are that you wouldn't have been able to enter it accurately enough anyway.

    So there is no need to try to calculate it yourself, unless you're trying to come up with a better estimate - but calculating it from a transient simulation is pretty pointless. It would only be if you have a very wide range of frequencies and can estimate it from one of the variables (e.g. a control word) for the design that it would be worthwhile.

    Note: Do not use the "oscillator" mode unless it is a free running oscillator. I've seen people use this when they have a driven circuit and they can't be bothered to work out the beat frequency. Well, this will mean that the simulator is trying to solve an unknown which is not unknown, and will lead to an ill-conditioned matrix and probably convergence difficulties...

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • frasheed
    frasheed over 9 years ago

    Hey Andrew, Thanks for the detailed answer :). Yes, the oscillator is free running but I do have an extra circuitry through which I can input different combinations to trim my oscillator output and that is why I want to calculate the the oscillator frequency first and then I want to use it in pss to calculate the phase noise and jitter. There can be 8 different combination for the extra circuitry and then 8 different trimmed frequencies of the oscillator so I guess the I should use calculated frequency from the oscillator output rather the estimated value. What would be your suggestion for this scenario ?

    EDIT: I also found a nice explanation regarding the beat frequency in another thread
    http://community.cadence.com/cadence_technology_forums/f/38/t/2661

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 9 years ago

    PSS should find the oscillator frequency anyway - it's only really to help the algorithm find the frequency more efficiently. So if you have control variables used to set which mode it's in, you can adjust your estimate. It shouldn't be absolutely required though.

    The phase noise and jitter should then be measured relative to whatever frequency it finds.

    So I'm not sure you have to do anything...

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • 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.

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

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