• 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. Cell is not defined error (maybe an auCdl issue)

Stats

  • Locked Locked
  • Replies 9
  • Subscribers 125
  • Views 18800
  • 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

Cell is not defined error (maybe an auCdl issue)

oldnick
oldnick over 10 years ago

I'm working on a design that has structures without schematics (CCD cells), effectively the layout and schematic are both empty as far as LVS is concerned. Anyway, I've modified the rule deck so that LVS picks up the structures and recognises each cell and that seems to work fine.

I've been trying to make a schematic symbol for the cell so that LVS sees the cell in the layout and the corresponding symbol in the schematic and can match them. Anyway, I made a symbol with the required in/out pins and did an LVS, which failed. I then copied the symbol view to create an auCdl view, which seemed to get me further through the LVS process but I ran up against this error and I'm not sure what to try next.

ERROR (NVN-13010): Cell CCD is not defined. 

Maybe there is something more to do with the auCdl, I just copied it to an auCdl view in library manager.

Any help would be great cheers.

  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 10 years ago

    I'd have to do some experiments and checking through the documentation to work through this. Whilst I have a lot of knowledge of Physical Verification in general (dating back over 25 years), I've not done that much PVS rule generation or technology setup so I'd have to do some revision and research...

    Anyway, I've spoken to the Europractice folks, and they've assured me that your issue has been assigned an owner and they will be dealing with it as soon as possible. Rather than double working (and I do this forum in my "spare" time), I'll let them deal with this .

    Kind Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 10 years ago

    I'd have to do some experiments and checking through the documentation to work through this. Whilst I have a lot of knowledge of Physical Verification in general (dating back over 25 years), I've not done that much PVS rule generation or technology setup so I'd have to do some revision and research...

    Anyway, I've spoken to the Europractice folks, and they've assured me that your issue has been assigned an owner and they will be dealing with it as soon as possible. Rather than double working (and I do this forum in my "spare" time), I'll let them deal with this .

    Kind Regards,

    Andrew.

    • 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