• 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. Cadence hierarchy editor, view to use

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 125
  • Views 15062
  • 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

Cadence hierarchy editor, view to use

gsimard
gsimard over 14 years ago

Hi,

 

I have a test bench TB in which I instanciate 2 symbols of the same device A. Within this device's schematic, there is a symbol B.

Cadence Hierarchy Editor sees two different instances of device A (say I1 and I2), but device B (say I3) is *shared* by both I1 and I2. This prevents me from specifying a different "view to use" for B in devices I1 and I2 (say schematic and extracted).

 Is there a way to have cadence generate two devices for B (say I3 and I4) ? This could solve my problem. The current release I'm using (5.10.41) does not allow me to use Occurence Bindings, which I thought could solve this issue.

 

Thank you for any advice,

Guillaume

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 14 years ago

    Guillame,

    Occurrence Bindings are indeed what  you want. These are supported in IC5141 for the AMS simulator only (because they can be handled during elaboration). In IC61X they are supported in all ADE netlisters (OSS which is the netlisting system underneath was enhanced to allow the necessary expansion of the hierarchies to allow for different hierarchical occurrences).

    So unfortunately unless you're using AMS, or using IC61, there's no solution. Other than maybe creating a copy of A's schematic, and then setting I1 to schematic, and I2 to schematic_copy. Then you can independently set the binding for the instances of B in both schematic and schematic_copy separately.

    Regards,

    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