Stats

  • Locked Locked
  • Replies 2
  • Subscribers 126
  • Views 14045
  • 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

Attach Spectre Assertions to a Schematic

MarkSummers

I am looking for a way to attach spectre assertions to a schematic.  This way the assertions will stay with the schematic as it used in multiple designs.  Does anyone know the best/recommended way to do this.  Thanks

Parents

  • Another possibility is to create a component which netlists as an instance of a spectre "assert". This should be straightforward enough - you'll want a symbol with no pins, and then in the CDF you'll want all the parameters of "spectre -h assert" that you're likely to want. I would't set "parseAsCEL" to yes on anything. List all the parameters in the instParameters in the spectre simInfo in the CDF, and specify the component name as "assert".

    Then when you instantiate an instance of assert, you can give (for example) dev="M4" and since it will be netlisted in the same subckt as M4, it will refer to it...

    Because of this, you may not necessarily want to provide all the options - for example, those which allow vectors to be given (such as subs, values, anal_types) would almost certainly require you to write a custom netlisting procedure.

    Regards,

    Andrew.

     

Reply

  • Another possibility is to create a component which netlists as an instance of a spectre "assert". This should be straightforward enough - you'll want a symbol with no pins, and then in the CDF you'll want all the parameters of "spectre -h assert" that you're likely to want. I would't set "parseAsCEL" to yes on anything. List all the parameters in the instParameters in the spectre simInfo in the CDF, and specify the component name as "assert".

    Then when you instantiate an instance of assert, you can give (for example) dev="M4" and since it will be netlisted in the same subckt as M4, it will refer to it...

    Because of this, you may not necessarily want to provide all the options - for example, those which allow vectors to be given (such as subs, values, anal_types) would almost certainly require you to write a custom netlisting procedure.

    Regards,

    Andrew.

     

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.