• 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. how to activate/deactivate a component during a simulat...

Stats

  • Locked Locked
  • Replies 4
  • Subscribers 126
  • Views 5695
  • 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

how to activate/deactivate a component during a simulation

wighou
wighou over 15 years ago

 Hi,

Is it possible to activate/deactivate a component during a simulation ? This very usefull function doesn't seem to exist in the schematic editor.

Regards

  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 13 years ago

    Yawei,

    You presumably edited the post after initially appending, because it only mentioned IC613 when I first read it, but now you say you're using IC614 (the version you gave is only a partial version number, as it should have an additional subnumber on the end to say which subversion you're using). Why you're reading documentation from a different version than the one you're using, I'm not sure, but never mind. This is not documented in the schematic documentation - but if you search in cdnshelp for nlIgnore, you'll find it.

    I tried with the "spectre" netlister in ADE in IC613 Base, 6.1.3.500.19, IC614 Base, 6.1.4.500.13 and it worked in all. This is not surprising, because it was implemented in an IC612 hotfix, according to CCR 263562.

    It does not however work with the AMS cell-based netlister ("ams") in ADE. This is covered in existing CCR 107333. That netlister is very different from standard ADE netlisters, so doesn't follow the same infrastructure. However, it also wasn't working in the AMS-OSS netlister either (from some tests that I did some time ago, also mentioned in the same CCR) - maybe it has been fixed in the meantime, as I've not re-tested that part recently.

    You could use the bind-to-open capability in the hierarchy editor to achieve the same effect though - so maybe you could use that. Or get a duplicate CCR filed with explanation as to your need,

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 13 years ago

    Yawei,

    You presumably edited the post after initially appending, because it only mentioned IC613 when I first read it, but now you say you're using IC614 (the version you gave is only a partial version number, as it should have an additional subnumber on the end to say which subversion you're using). Why you're reading documentation from a different version than the one you're using, I'm not sure, but never mind. This is not documented in the schematic documentation - but if you search in cdnshelp for nlIgnore, you'll find it.

    I tried with the "spectre" netlister in ADE in IC613 Base, 6.1.3.500.19, IC614 Base, 6.1.4.500.13 and it worked in all. This is not surprising, because it was implemented in an IC612 hotfix, according to CCR 263562.

    It does not however work with the AMS cell-based netlister ("ams") in ADE. This is covered in existing CCR 107333. That netlister is very different from standard ADE netlisters, so doesn't follow the same infrastructure. However, it also wasn't working in the AMS-OSS netlister either (from some tests that I did some time ago, also mentioned in the same CCR) - maybe it has been fixed in the meantime, as I've not re-tested that part recently.

    You could use the bind-to-open capability in the hierarchy editor to achieve the same effect though - so maybe you could use that. Or get a duplicate CCR filed with explanation as to your need,

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
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.

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

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