• 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. Regarding Smoothness in transient analysis

Stats

  • Locked Locked
  • Replies 6
  • Subscribers 125
  • Views 15478
  • 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

Regarding Smoothness in transient analysis

RFStuff
RFStuff over 11 years ago

 Dear All,

I created a verilogA module.

What it basically does is as below:-

It is a simple sine wave generator. 

I stored the sine wave  time & amplitude in a text file for one period of the sine wave.

The verilog A code reads the file and generates the sine wave for the entire transient simulation time.

But the problem is:-

If I am not using the strobeperiod, the curve is NOT smooth at all.

But when I use stobeperiod=1ps then it becomes smooth.

I was thinking that the  transient simulation will be evaluated at each time point stored in the file.

Can anybody please tell why this is happening.

Kind Regards,

  • Cancel
  • skillUser
    skillUser over 11 years ago

    Hi RFStuff,

    The simulator will only place timesteps that are sufficient to resolve the equations, not necessarily enough that the sine wave looks like a sine wave.  One way to help the simulator take more timesteps is to use the bound_step() function - this should be a little nicer to the simulator (than strobeperiod) as it still has flexibility on the time points, but now they are limited to a maximum time between steps. Work out how many samples/points you wantper cycle and work out the max timestep from there.

    I hope that this helps.

    Regards,

    Lawrence.

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

    Also, a simple sine wave generator would use the sin() function in the language rather than generating a piece-wise waveform from an external file. It's hard to give a precise answer (Lawrence is correct, of course) without seeing your code - it depends how you're doing it...

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • RFStuff
    RFStuff over 11 years ago

     Thanks a lot Lawrence & Andrew.

    I have never come across the bound_step() function. 

    What it is actually ? Is it a OCEAN function . I searched in OCEAN document but couldn't find this one.

    Can you please explain how it actually work or point me to the doc or link where I can know about this function.

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

    $bound_step is a function in the VerilogA language.  It's covered in the language reference manual (both those we ship with the software, plus the official Accellera LRM).

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • RFStuff
    RFStuff over 11 years ago

     I actually read through the document.

    1:-

    What I understood is:- bound_step( ) enforces the maximum timestep( that is the upper limit of the time gap between two points) in the verilogA module.

    But the actual step can still be lesser than the specified bound_step() value depending upon what the simulator needs to solve the equations. Please tell whether I am correct.

    2:-

    Actually, I need to create a Oscillator marcomodel. I want to add noise and other stuff to it. So I stored only one period of the actual ring-oscillator in a file and teh verilogA module uses it to produce the full waveform.

     

    Kind Regards,

     

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

    Yes, $bound_step tells the simulator that the next timestep should be no more than the specified delta time from the current timestep. The simulator is free to take shorter timesteps if it needs to though to maintain accuracy.

    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