• 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. Hierarchy Editor - How to use library list

Stats

  • Locked Locked
  • Replies 6
  • Subscribers 125
  • Views 8853
  • 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

Hierarchy Editor - How to use library list

Atul Dubey
Atul Dubey over 10 years ago

Hello,

I was trying to understand how library list (GUI field above switch view and stop view list) works in hierarchy editor. I did few experiment but could not understand its usage. I always needs to define a library to the cds.lib file and hierarchy editor can use that to find the cells used in the design schematic.

Can someone please explain it through an example how library list is used in hierarchy editor?

I understood from a previous post that it is used for finding cells for textual views live verilog view, But i could not make it work because for a verilog view to compile properly in virtuoso user needs to have the library in cds.lib ( no matter you have it in library list or not).

  • Cancel
Parents
  • ShawnLogan
    ShawnLogan over 10 years ago

    Dear Atul,

    > I am still trying to figure it out how library list is used in
    > hierarchy editor in case of textual views (for example : reference
    > verilog ),

    I am probably not understanding your question - so I must, initially, apologize if I am not help to answer your question! However, the library list indicates those libraries from your cds.lib which the hierarchy edit will search for the name of the cells in your design. If you do not include a library in your list that contains one or more of the cells in your design, the hierarchy editor will indicate that the cell is not found. This will prevent you from creating a netlist of the design. There is no difference in its use if the cell has a "textual" view or a schematic/extracted view. The default view to be used is specified by the order of the views you select and the placement of the stop view in that list. 

    I have attached an example of the hierarchy editor where I have circled the library list at the top and how two verily cells are instantiated. Note each cell is from a library in the library list. Their verilog views were selected as the verilog view in the "View List" appears before the "Stop List" view (spectre in this case).

    I hope this helps.

    Shawn

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • ShawnLogan
    ShawnLogan over 10 years ago

    Dear Atul,

    > I am still trying to figure it out how library list is used in
    > hierarchy editor in case of textual views (for example : reference
    > verilog ),

    I am probably not understanding your question - so I must, initially, apologize if I am not help to answer your question! However, the library list indicates those libraries from your cds.lib which the hierarchy edit will search for the name of the cells in your design. If you do not include a library in your list that contains one or more of the cells in your design, the hierarchy editor will indicate that the cell is not found. This will prevent you from creating a netlist of the design. There is no difference in its use if the cell has a "textual" view or a schematic/extracted view. The default view to be used is specified by the order of the views you select and the placement of the stop view in that list. 

    I have attached an example of the hierarchy editor where I have circled the library list at the top and how two verily cells are instantiated. Note each cell is from a library in the library list. Their verilog views were selected as the verilog view in the "View List" appears before the "Stop List" view (spectre in this case).

    I hope this helps.

    Shawn

    • 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