• 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. RF Design
  3. problem with nodeset and ic Ringoscillator design

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 63
  • Views 13260
  • 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

problem with nodeset and ic Ringoscillator design

frasheed
frasheed over 10 years ago

Hello, 

I am simulating ring oscillator to match current and frequency values from simulation run by some other ppl. Those guys used SPF spice file and I have extracted DSPF file. After running simulation I am getting slight deviation in values, in order to tackle it , I need to see the response of active devices so I comment out all parasitic capacitors and set very low resistance to parasitic resistors that it will behave as a short. The simualtion run time was 50ns and before modifying R's and C's it was taking 24 min on average, but Now in 2 days it just passed through 3ns . When I did i set the nodeset values to certain nodes, but these nodes are not added in netlist and virtuoso gives me this error :

Ensure that the specified schematic names are valid.

/I0/I3/I0/net8 /I0/I3/I0/net31

These nodes are on the first level going down to the hierarchy (descend ). If I select any node from top level then its added to the netlist. After this I creted spectre .ic file and add these nodes there with their values, and then added this file as initial condition, even then the simulation is very very slow.

Any solution or suggestion that can help me to analyse the results only from the extracted transistors in my DSPF file.

Thanks

  • Cancel
  • ShawnLogan
    ShawnLogan over 10 years ago

    Dear frasheed,

    > I need to see the response of active devices so I comment out all parasitic capacitors and set very low resistance

    > to parasitic resistors that it will behave as a short. The simualtion run time was 50ns and before modifying R's and C's

    > it was taking 24 min on average, but Now in 2 days it just passed through 3ns .

    I am not sure, but I am thinking that when you set the resistors to very low values, you have created some very small time constants that are resulting in very small time steps. Have you examined the size of the time steps in your simulation?

    I have been faced with a very similar oscillator correlation issue. This is how I approached it:

    For the parasitic resistors, I add a scale factor as a parameter. Hence, if a parasitic resistor had a value of 10.0 ohms, I set it to the value of rscale*10.0. The value of rscale can be set to a number between 0.0 and 1.0. I then ran a series of simulations where I reduced the value of rscale from 1.0 to a low number. In this fashion, I could observe how the oscillator frequency and parameters varied as the parasitic resistances were reduced. This method also prevents the netlist from having too many small resistors.

    There is also a spectre parameter you can set to force spectre to ignore time constants below a specific value using the parasistics reduction option.

    I hope this helps!

    Shawn

    • 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