Stats

  • Locked Locked
  • Replies 2
  • Subscribers 142
  • Views 1161
  • 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

Change the FetType using skill

FormerMember
FormerMember

Hi, 

I wanted to change the Fet type of a mos instance from egnfet to lvtnfet (or any other type).

Currently I am using this snippet for a cell view with only one instance.

cv=gegetWindowCellView()
x=cv~>instances
schReplaceProperty(list(x)  "fetType"  "lvtnfet")

after executing this snippet 

when I type 
x~>fetType 

it displays "lvtnfet".

But when I generate the CDL, the fetType is still displayed as "egnfet".

I am able to change every other cdf parameter using the above snippet and it is also displayed in CDL correctly except fetType.

Please tell a solution for the problem.

Regards
Utkarsh

  • Without knowing the details of your PDK, it's hard to know whether what you are doing makes sense (well, I'm sure it doesn't make sense because it didn't work!). For a start, I have no idea whether "fetType" is actually a CDF parameter for the devices in your library, and even if it is, whether it affects simulation or CDL netlists.

    Sometimes you would need to change a parameter and then call the CDF callbacks; other times you would need to change the master (i.e. change the instance to be another device) and then call the callbacks. Sometimes that won't work either because some of the CDF parameters may have storeDefault=yes in the CDF and consequently keep an old model name or old property value from the previous instance.

    My suggestion would be to contact customer support so that an application engineer can look at this with you.

    Regards,

    Andrew.

  • FormerMember
    FormerMember in reply to Andrew Beckett

    Hi Andrew

    Yes its a cdf parameter.
    I would look forward to contact an Application Engineer. Thanks.

    Regards
    Utkarsh

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.