• 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. Edit assert in Checks/Asserts assistant

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 125
  • Views 1168
  • 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

Edit assert in Checks/Asserts assistant

amac
amac 10 months ago

Hello,

is it possible to use the Checks/Asserts assistant to edit a regular assert?

In this old post Andrew seems to have done so but there is no procedure:

https://community.cadence.com/cadence_technology_forums/f/custom-ic-design/56883/using-time-of-an-assert-event-in-ade-assembler-s-output-expressions/1388751

 

BR

  • Cancel
  • Andrew Beckett
    Andrew Beckett 10 months ago

    You can add asserts as "Device Checks" through the Checks/Asserts assistant, and that gives you the ability to edit all the fields of an assert. Note that you can only edit asserts added this way, not those added through an include file. The exclamation mark here is a "Device Check":

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • amac
    amac 10 months ago in reply to Andrew Beckett

    Thank you, this info was somehow not well explained (or not very prominent) in the guides.

    Anyways, a strange effect is that the assert is called MyLibrary\/MyCell\/assertName in the netlist so in case it's needed, for example I used it as info time through @(assert), it has to be called that way instead of simply assertName

    BR

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett 10 months ago in reply to amac
    amac said:
    the assert is called MyLibrary\/MyCell\/assertName in the netlist

    This is done to ensure that checks defined in different cellViews don't clash with each other - otherwise they might have the same name. It's a bit inconvenient if you are referring to them via the @ syntax, but it's a necessary evil, unfortunately!

    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