• 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. VerilogA vs. built-in device models

Stats

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

VerilogA vs. built-in device models

samer1
samer1 over 8 years ago

Hello, 

I've been using verilog-A to model devices for quite sometime and I wanted to ask what differences are there between the user define model (written in verilogA) and a built-in mosfet model, for example, from the simulator's perspective. 

For example, I have a kit with its specific devices and their models are written in .scs file. Those files simply include the parameters passed to the model equations, I assume, that are hard coded in the simulator. On the other hand, when I write the verilogA code I define both the equations and the model parameters. 

Does the simulator interpret both models the same way in terms of the numerical algorithms used (Newton-Raphson, ..etc)?

Does the simulator process the verilogA equations directly or there is some intermediate step to translate the verilogA code to another form then start solving the equations? (something like a synthesizer in digital). The reason why I am asking this question is that I read some articles about verilogA and they recommended not to overuse the verilogA functions such as ddt , for instance, to ensure proper convergence. So, it sounds to me like there is some intermediate interpretation step done by the simulator before solving the equations. 

Thanks

  • Cancel
Parents
  • samer1
    samer1 over 8 years ago
    Got it.
    Thanks Andrew
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • samer1
    samer1 over 8 years ago
    Got it.
    Thanks 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