Stats

  • Locked Locked
  • Replies 10
  • Subscribers 126
  • Views 16437
  • 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

CDF issues

Arafat01

Hey,

I have a Library with several cells.

Some of these cells have different ports in the symbols and different ports in the CDF port list.

So when I perform a CDL out the portlist is diff from CDF port list.

The LVS is not clean because of this.

These symbols where not freshly created when a modification was made to the schematic but were just modified dueto this CDF did not get updated.

Is there any possible way to update the CDF portlist directly from the existing symbols.

Thank You

Parents

  • Whilst Frank's pointer to the solution is a good answer and a pointer I would have provided if he'd not beaten me to it (!), I am rather surprised that the CDL netlist you get is incorrect.

    If it is a hierarchical block, the CDF termOrder will be used, unless it's incorrect... in other words, if there are additional terminals or terminals missing. If that happens, it should revert to the built-in order based on the terminals that are actually in the schematic. I've tried this, and this is indeed the case.

    The one exception is (of course) if you've configured it to stop at the cell - in which case the only information it can use is the CDF because there is no corresponding schematic to switch into - so in that case the termOrder has to be used in order to be consistent with any external files.

    If you have a hierarchical netlist where the non-stopping cells are mis-netlisted due to errors in the CDF, this needs to be reported to Cadence Customer Support (of course, if you're using some old version, you may want to check with a recent version first, but I'm not aware of any such issues for a long time now - perhaps you can give the version number you're using from Help->About in the CIW?)

    Regards

    Andrew.

Reply

  • Whilst Frank's pointer to the solution is a good answer and a pointer I would have provided if he'd not beaten me to it (!), I am rather surprised that the CDL netlist you get is incorrect.

    If it is a hierarchical block, the CDF termOrder will be used, unless it's incorrect... in other words, if there are additional terminals or terminals missing. If that happens, it should revert to the built-in order based on the terminals that are actually in the schematic. I've tried this, and this is indeed the case.

    The one exception is (of course) if you've configured it to stop at the cell - in which case the only information it can use is the CDF because there is no corresponding schematic to switch into - so in that case the termOrder has to be used in order to be consistent with any external files.

    If you have a hierarchical netlist where the non-stopping cells are mis-netlisted due to errors in the CDF, this needs to be reported to Cadence Customer Support (of course, if you're using some old version, you may want to check with a recent version first, but I'm not aware of any such issues for a long time now - perhaps you can give the version number you're using from Help->About in the CIW?)

    Regards

    Andrew.

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.