• 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. Device checking output in Spectre

Stats

  • Locked Locked
  • Replies 0
  • Subscribers 125
  • Views 14393
  • 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

Device checking output in Spectre

nicola91it
nicola91it over 6 years ago

Hi all,

I've got a model file .scs where I've set all rules for checking the maximum voltage across each terminal of my transistors. For example, each line is like the following:

Assert_name assert sub=my_sub mod=my_mod expr=my_expr message=my_message level=warning 

Then, in ADEL I include this file in model libraries and device checking is performed when I run simualtions. To output the results, I've found

Simulatiion->options->analog->check,

where I set dochecklimit=yes, and I specify the file where I want the report to be saved in checklimitdest. 

Next are my questions:

- When I open the output file, it just displays different violations reporting the instance and the type of violation. Is It possible to have a more readable report that lists, for example, instance, violation, intant of time when violation occured, duration, and magnitude of violation? 

-in some technoligies I've noticed that the simulator displays warning messages in the CIW because it simply reads some maximum ratings in the model files of transistors (so, a file containing different asserts is not needed here). May I know how Spectre knows how to output these warning without any assert?

Hope it's all clear (unfortuantely, cannot report technolgies that are bring used).

Thank you in advance. 

Nicola 

  • 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