• 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. Config View for a cell

Stats

  • Locked Locked
  • Replies 7
  • Subscribers 127
  • Views 19507
  • 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

Config View for a cell

sohaibafridi
sohaibafridi over 13 years ago

In a post it was mentioned how to do a post layout simulation:

a. First create your layout
b. Run Assura or PVS LVS on the layout
c. Run QRC to generate an extracted view
d. Create a schematic test-bench for the cell
e. Create a config view for the test-bench and set the view for the cell to the extracted view
f. Run ADE-L using the config view

 Please could you elaborate a bit on config view. How to create it and what is its purpose?

  • Cancel
Parents
  • Quek
    Quek over 13 years ago

    Hi Sohaib

    Many thanks for posting the new thread. This would allow us to have more focus on your question and to give you the best answer. : )  Thank you also for referencing the original post. I think you have made a very excellent post.

    A config view allows you to use different views for different cells during netlisting. When ADE netlist a schematic directly, every instance has to be netlisted according to the viewList and stopList values which have been specified. When netlisting through a config view, users can set different views for different instances. E.g. a schematic contains 3 cells A, B and C. In the config view, we can set cellA to use verilog view, cellB to use schematic view and cellC to use an extracted view. This gives great flexibility in doing simulations.

    Here is how you can create a config view:
    a. In library mananger, go to "File->New->CellView"
    b. Select "config" type. The application will be automatically set to "Hierarchy Editor"
    c. A "New Configuration" form appears. Set the "View" to schematic and press "Use Template" button
    d. A form appears. Select "Spectre" template and press OK twice to close both forms.
    e. The config view creation is completed. You can now use it to set different views for the different cells.

    Hope that this clears up your doubt.

    Best regards
    Quek

    • Noname.gif
    • View
    • Hide
    • Cancel
    • Vote Up +1 Vote Down
    • Cancel
Reply
  • Quek
    Quek over 13 years ago

    Hi Sohaib

    Many thanks for posting the new thread. This would allow us to have more focus on your question and to give you the best answer. : )  Thank you also for referencing the original post. I think you have made a very excellent post.

    A config view allows you to use different views for different cells during netlisting. When ADE netlist a schematic directly, every instance has to be netlisted according to the viewList and stopList values which have been specified. When netlisting through a config view, users can set different views for different instances. E.g. a schematic contains 3 cells A, B and C. In the config view, we can set cellA to use verilog view, cellB to use schematic view and cellC to use an extracted view. This gives great flexibility in doing simulations.

    Here is how you can create a config view:
    a. In library mananger, go to "File->New->CellView"
    b. Select "config" type. The application will be automatically set to "Hierarchy Editor"
    c. A "New Configuration" form appears. Set the "View" to schematic and press "Use Template" button
    d. A form appears. Select "Spectre" template and press OK twice to close both forms.
    e. The config view creation is completed. You can now use it to set different views for the different cells.

    Hope that this clears up your doubt.

    Best regards
    Quek

    • Noname.gif
    • View
    • Hide
    • Cancel
    • Vote Up +1 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