• 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 SKILL
  3. problem with viewing schematic

Stats

  • Locked Locked
  • Replies 4
  • Subscribers 143
  • Views 14640
  • 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

problem with viewing schematic

Aritra
Aritra over 14 years ago
Hi ,

 I am using IC 6.1.3 . I am facing some problem with viewing the schematic. When I am making some layers in the LSW visible only, the schematic is not visible. Say I am making visible only metal1 . At this time if I open the schematic it will not show anything.

But If I make all layer visible then I can view the schematic fine. Is it possible to make the schematic view independent of the schematic ?

 I also have all set all layer valid form LSW. May I need to change some layer to non-valid?
  • Cancel
  • skillUser
    skillUser over 14 years ago

     Hi Aritra,

    The schematic and layout tools use the same sort of method for setting up display properties - a display.drf file specifies the display resources (line styles, "stipples" or pattern fills, colours used) by setting up "packets" for display.  Typically a schematic library does not have a technology and so it uses the default cdsDefTechLib for specifying its "technology" and this is what associates layer-purpose pairs with display packets. Again, typically for schematics the system layer-purposes and their associated display packets are defined, but it is entirely possible that your schematic comes from a library with its own technology, and this technology could be overriding the default setup for the packets used by the schematic LPPs.  For the LSW, if a layer is valid it is shown in the LSW, if it is not valid it is not shown - from the LSW you can then control the visibility and selectability of an LPP.  Again, typically the LSW is not needed for the schematic layers, they are system layers with visibility and appropriate selectability set by default.

    So I gave some background to help you understand where the problem might lie, I would suspect the schematic library has some (schematic) system layers being overridden. Perhaps, for example, the schematic LPPs are using the same packets as some of the layout packets, and when these are changed it impacts the schematic also?  Or perhaps there is a display.drf file that modifies the appearance of the schematic packets, so that the LPPs are not being displayed correctly?

    I hope that this helps you.

    Regards,

    Lawrence.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Aritra
    Aritra over 14 years ago

    Thanks  Lawrence,

                                I am tring to resolve this problem by including the schematic LPP visible to my bindkeys associated with setting the desired layes visible. Now I am having another issue related to it. I can not find the LPP of the schematic.

    If I am selecting the schematic instance and do css()~>?? it does not contain the LPP associated. Or it may be some other place which I am unable to find. So how to get the schematics LPP now?

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • dmay
    dmay over 14 years ago

    This is the bindkey we use. It basically makes all of the system layers visible.

     foreach( l setof(lyr techGetTechFile(geGetEditCellView())~>lps  (lyr~>number >= 207) ) l~>visible = t) hiRedraw()

    Derek

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • vuong
    vuong over 11 years ago

    This is helpful. Thanks a lot.

    • 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