• 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 solve the LVS error :"unable to descend into any...

Stats

  • Locked Locked
  • Replies 9
  • Subscribers 125
  • Views 8296
  • 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 solve the LVS error :"unable to descend into any of the views defined in the view list"

Justing
Justing over 6 years ago

I am using 130nm process,adding my own devices,DRC is passed,but LVS got an error below:

ERROR(OSSHNL-116): unable to descend into any of the views defined in the view list: ”auCdl schematic” for instance. I3 in cell CELLPMAMTJ . Either add one of these views to : library Cell: p33 or modify the view list to contain an existing view. 

Anyone who had the same problem or know how to sovle it, please help !!!

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 6 years ago

    It's International post-in-the-wrong-forum day today (the second I've had to deal with in a few minutes - I'm sure there will be more). Posting in the "Feedback, Suggestions, and Questions" isn't going to get you anywhere, since that is a forum intended for issues with the forum system itself, not for technical questions.

    The error gives quite a few clues. Presumably you're trying to create a CDL netlist using the auCdl netlister. So, look in the schematic for CELLPMAMTJ and find instance I3. Note down (use Edit Properties) what the library, cell and view name of the instance (presumably the view name is "symbol") and then in the library manager look at that lib/cell. What views are available? It's telling  you that there is not an auCdl nor a schematic view for this cell, and so it doesn't know what to descend into for that component.

    If you show me what is there (please post the info), I might be able to give you a suggestion...

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Justing
    Justing over 6 years ago in reply to Andrew Beckett

    Thanks for your patience and reply. Actually there are both "schematic“ and ”symbol“ view available.  What should I do now?  Thanks !

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 6 years ago in reply to Justing

    You're showing cellPMAMTJ, whereas I was asking about whatever instance I3 is within cellPMAMTJ which is what the error message is about. It doesn't surprise me that there's a schematic for cellPMAMTJ because it wouldn't have got as far as complaining about instance I3 otherwise...

    So please check what I3 is an instance of, and show the views available for whatever that lib/cell is for that instance.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Justing
    Justing over 6 years ago in reply to Andrew Beckett

    Hi Andrew,

    Thanks for your patience. I've checked I3 instance and as you said, it only has the veriloga and symbol view. So how cam I add an auCdl  view for it ?

    Regards,

    Justing.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Justing
    Justing over 6 years ago in reply to Andrew Beckett

    I have added a config view follow the cadence guide about "creating a config view for auCdl ", but it still doesn't works.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • RiadKaced
    RiadKaced over 6 years ago in reply to Justing

    Hi Justing,

    In order to be able to run LVS, you need an auCDL stop view on your primitives. The view itself can be just a copy of the symbol. However, you would need all the CDF information for your CDL netlister, including netlist procedure, terminal mappings ...etc. Generally speaking, your foundry is supposed to provide all of this in their primitive library as part of their PDK. I would highly recommend speaking with your foundry partners for more information. 

    Riad.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 6 years ago in reply to Justing

    I guess it rather depends on what this instance is supposed to be. Currently it contains a behavioural model - does it correspond to a physical component (i.e. is it a primitive part of a design kit representing a transistor, resistor, capacitor etc)? It's not just a matter of creating a config - you normally need to provide a stopping view (auCdl) and the corresponding CDF to say how to netlist it, but then you'd also need your LVS rules to also know what to do with that device. Or maybe there's supposed to be a schematic for this cell? I would contact whoever created cellPMAMTJ and/or whoever created the component I3 that you're using to determine what the right way forward is.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Justing
    Justing over 6 years ago in reply to Andrew Beckett

    Ok, I got it. That means the device is not complete, right ?

    This is a new device of our own lab design. And it acturally correspond to a resistor. Now we will work on it to complete the device. Thanks for your reply !!

    Regards,

    Justing.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Justing
    Justing over 6 years ago in reply to RiadKaced

    Hi Riad,

    Now we will work on what you have said to complete this device. 

    Thanks !

    Justing

    • 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