Stats

  • Locked Locked
  • Replies 11
  • Subscribers 144
  • Views 7952
  • 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

Modified parameters don't change layout pcells

egolowen

Hi,

I am writing SKILL code in order to modify the parameters of layout instances, however even though the parameter has been properly modified, the layout pcell does not change (for example, if I increase the length of an nfet the property is the correct value but the layout instance remains the same size).

 I have tried using:
  foreach(prop properties
... 
prop~>value = param_value
...
)

and:
 dbReplaceProp(inst prop~>name 'string param_value)

But neither have fixed the issue.
Is there a better may to modify these parameters so the layout itself is updated properly? I was thinking of trying to use a replay file but that may not do the trick.

Thanks,
Elizabeth

Parents
  • Hi Andrew,
    Thanks for reply.
    1. I am beginner in skill manipulation. I do not understand abInvokeCdfCallbacks or CCSinvokeCdfCallbacks procedures or how to use them.
    Could you please give me stand-alone procedure set here that can do the job?

    2. For example, dbReplaceProp(car(geGetSelSet()) car(geGetSelSet())~>w "float" 12.0u) command executes but no change is not reflected in layout.

    Or is there any other correct way to change width/length of instance in layout.

    Thanks,
    Anand
Reply
  • Hi Andrew,
    Thanks for reply.
    1. I am beginner in skill manipulation. I do not understand abInvokeCdfCallbacks or CCSinvokeCdfCallbacks procedures or how to use them.
    Could you please give me stand-alone procedure set here that can do the job?

    2. For example, dbReplaceProp(car(geGetSelSet()) car(geGetSelSet())~>w "float" 12.0u) command executes but no change is not reflected in layout.

    Or is there any other correct way to change width/length of instance in layout.

    Thanks,
    Anand
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.