• 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. spectre assert

Stats

  • Replies 2
  • Subscribers 125
  • Views 613
  • Members are here 0

spectre assert

Joe Mellon
Joe Mellon 1 month ago

Hi, can anyone tell me how to exclude subckts in spectre assert statement? Just like "xsubckt=..." in checklimit statement or any other...

Thanks,

Joe

  • Sign in to reply
  • Cancel
  • Andrew Beckett
    Andrew Beckett 1 month ago

    Joe,

    I'm not sure this is possible. There is (in theory) this:

    mycl checklimit asserts=[testassert] param=skip_dev_inside_subckt value=[inv1]

    but I can't get it to work. I think the skip_dev_inside_subckt (see "spectre -h assert") only makes a difference for certain types of assert.

    I suggest you contact customer support so that a fuller investigation can be made and an enhancement filed if needed.

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • Joe Mellon
    Joe Mellon 1 month ago in reply to Andrew Beckett

    Hi Andrew,
    Sorry for the late reply - I was away on vacation and just got back.

    Quick update:
    1, Tried "param=skip_dev_inside_subckt value=[inv1]" in my case - Didn't behave as expected.
    2, Dug deeper into the "skip_..." options mentioned, and finaly found a workaround in the "Spectre Circuit Simulator Reference" manual: "checklimit_skip_insts=[...]"
    3, Added an option line in my netlist:
    myclopt options checklimit_skip_insts=[inv1]
    It works perfectly now, exactly as needed. Hope this helps others facing similar issues!

    Really appreciate you taking the time!
    Cheers,
    Joe

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • 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