• 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. Convergence Issue with verilogA model

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 125
  • Views 16166
  • 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

Convergence Issue with verilogA model

Flyyn Rider
Flyyn Rider over 11 years ago
 Hi, (some weird text appers below and i dont know what that is, my post starts with : I am sim......)

I am simulating 12 bit segmented SAR ADC with comparator in Verilog A. I have read several posts on achieving convergence like relaxing tolerances/specifying cmim etc. In a 12 bit ADC my LSB is around 250uV and I can’t afford to relax the tolerances further from their default values.

Problem:

Anyway the problem is not with my foundry model circuit instances, nothing wrong with the circuit netlist. I face convergence problems at the output of Verilog A comparator model. And I need to know how to fix the comparator code to avoid convergence issues. When I replace Verilog A comparator with transistor based design, no convergence problems are flagged.

But I have to run MC simulations and I don’t want to include the spread of comparator in my ADC accuracy plots for now, so it is crucial that I use Verilog model for comparator.

Although issues are flagged (error requirement were not satisfied because of convergence difficulties), for nominal run I don’t get convergence problem. But during MC simulations when a 200th simulation fails to converge, it translates to enormous wastage of time.

I have attached pdf presentation containing snapshots of my problem.

Fig 1 shows the entire circuit schematics

Fig 2 shows the comparator block and the node where convergence issue is reported

Fig 3 shows the Verilog code for comparator

Fig 4 and 5 show the snapshots of output log files which I have commented

So the problem is with the Verilog code of comparator. Can we change the Verilog code to achieve convergence? If yes then what should I change? If no then what should I do?
reporting convergence problem.pdf
  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 11 years ago

    It may not definitely be the VerilogA model, but I would suggest changing the code to something like:

    real compOut=0;
    @cross(V(sigin)-V(sigref),0);
    if (V(sigin)<V(sigref) compOut=sigout_low;
    else compOut=sigout_high;
    V(sigout)<+transition(compOut,0,1n);

    Set an appropriate delay and transition on your output transition. Currently you have instantaneous change, which is not good for convergence. Also, I'm using @cross here to ensure that it solves for the crossing point - without this it won't accurately get the decision point (that may not matter to you).

    Note I didn't test the code above, so there may be typos...

    Andrew.

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

    It may not definitely be the VerilogA model, but I would suggest changing the code to something like:

    real compOut=0;
    @cross(V(sigin)-V(sigref),0);
    if (V(sigin)<V(sigref) compOut=sigout_low;
    else compOut=sigout_high;
    V(sigout)<+transition(compOut,0,1n);

    Set an appropriate delay and transition on your output transition. Currently you have instantaneous change, which is not good for convergence. Also, I'm using @cross here to ensure that it solves for the crossing point - without this it won't accurately get the decision point (that may not matter to you).

    Note I didn't test the code above, so there may be typos...

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
No Data

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