Stats

  • Locked Locked
  • Replies 3
  • Subscribers 125
  • Views 14598
  • 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

MOS area and perimeter are not calculated from parametrized w and l

joliveros

Hi all..

In my design I'm using nmos4 and pmos4 active devices from AMS DKIT 3.70 PRIMLIB library. As shown in the figure, when I try to edit their properties in Virtuoso Schematic, their area and perimeter fields are recalculated for w and l values (and are not editable for that reason). So, there is no problem when I assign numerical values to w and l, but when I parametrize those variables (to do parametric analysis with the Analog Environment or to pass symbols parameters down through design hierarchy with "pPar") the area and perimeter values are miscalculated. In fact, they are not recalculated, and the last calculated numerical values remain fixed regardless the actual value the parameters take. I guess this is really no a Cadence issue, but a DKIT one. However, I need to get around this inconvenient and I don't know how to do that.

Thanks in advance for your help.

Parents

  •  Hi Andrew,

    I modified the "Base" CDF (because I had write access) of the transitors as you suggested and that worked fine for the issue.

    However, it's not clear to me where these modifications are saved. I read CDF documentation and now I know there are 3 CDF types: Base, User and Effective. If I edit Effective CDF, those changes are lost when I close the cadence session, User and Base (having write access) CDF are effectively saved though.The place where they are saved (or how to save and recall them) is what I am missing. Previous issue is important to me because I am planning to move from dkit AMS 3.70 (with IC51.41) to 4.00 (with IC6.10), and I want to keep my previous work (assuming that AMS 4.00 still has the callbacks problem related to your sourcelink solution).

    Can I really keep my previous CDF modifications when moving to next dkit version? I think that now I have to move the previous Base CDF modifications to User CDFs (and discover how to save and reuse them) in order to be able to applying them to the new version dkit User CDFs, is that correct?

    What else do I need to take into account to do this Cadence and Dkit moving?

    How do I convert my CDBs to the new OpenAccess platfform?

    Thanks in advance !!

Reply

  •  Hi Andrew,

    I modified the "Base" CDF (because I had write access) of the transitors as you suggested and that worked fine for the issue.

    However, it's not clear to me where these modifications are saved. I read CDF documentation and now I know there are 3 CDF types: Base, User and Effective. If I edit Effective CDF, those changes are lost when I close the cadence session, User and Base (having write access) CDF are effectively saved though.The place where they are saved (or how to save and recall them) is what I am missing. Previous issue is important to me because I am planning to move from dkit AMS 3.70 (with IC51.41) to 4.00 (with IC6.10), and I want to keep my previous work (assuming that AMS 4.00 still has the callbacks problem related to your sourcelink solution).

    Can I really keep my previous CDF modifications when moving to next dkit version? I think that now I have to move the previous Base CDF modifications to User CDFs (and discover how to save and reuse them) in order to be able to applying them to the new version dkit User CDFs, is that correct?

    What else do I need to take into account to do this Cadence and Dkit moving?

    How do I convert my CDBs to the new OpenAccess platfform?

    Thanks in advance !!

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.