• 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. Blogs
  2. Analog/Custom Design
  3. Analog Behavioral Modeling - What Language Do You Speak…
archive
archive
Blog Activity
Options
  • Subscribe by email
  • More
  • Cancel
CDNS - RequestDemo

Have a question? Need more information?

Contact Us
mixed-signal simulators
MMSIM
analog
Mixed-Signal
Block-level simulation
AMS simulation
Circuit Design
mixed signal
Custom IC Design
Custim IC Design
Cusstom IC Design

Analog Behavioral Modeling - What Language Do You Speak?

2 Mar 2010 • 2 minute read

An increasing number of mixed-signal design teams are contemplating adding analog behavioral modeling to their repertoire in order to achieve reasonable simulation speeds.  Utilizing analog behavioral models can yield simulation performance improvements that can make full chip verification a reality.  This approach can be several magnitudes faster than transistor-level; however, the actual performance improvement is greatly dependent on the level of detail in the model, as well as, the language of choice.  Analog behavioral models are generally written in one of the languages below:

 

Verilog-AMS – A derivative of Verilog, it includes analog and mixed-signal extensions in order to define the behavior of analog and mixed-signal systems, providing both continuous-time and event-driven modeling

 

Wreal – An extension of the Verilog-AMS modeling language allowing analog block operation as a real data flow model

 

Verilog-A – An extension of Verilog to describe analog and non-electrical behavior as a continuous-time subset

 

VHDL-AMS (IEEE1076.1) – similar in concept to Verilog-AMS, providing analog and mixed-signal extensions in order to define the behavior of analog and mixed-signal systems

 

One of the biggest challenges in the creation of analog behavioral models is; whose job is it?  The analog designer is the most familiar with the circuit performance and specific behaviors, however, many analog designers typically are not programmers and familiar with the languages mentioned above.  The digital designer, who also tends to be the full chip verification engineer, is most familiar with programming languages, but lacks the analog specific circuit knowledge.  Therefore, a blend of both skill sets is required or a conscience effort for both designers to work together.  One must continually make the tradeoff of effort versus benefit when deciding to create an analog behavioral model.  Some of the questions that come to mind are: Can I re-use it?  How long will it take me to create a high quality model?  What performance gains can I expect?

 

Finally, as you consider adding analog behavioral modeling to your design repertoire; consider your modeling goals and language.  A performance model needs to capture specific circuit behavior and can affect your effort versus benefit equation, while a functional model requires you to only capture the 1st order effects that are needed to verify the circuit functionality.  Model On!

 

Greg Curtis

 


CDNS - RequestDemo

Try Cadence Software for your next design!

Free Trials

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

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