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

  • Anand,

    Maybe there isn't a parameter to control the metal width of the source/drain metal. Why do  you think there is one?

    I cannot see how calling those two lines of code can cause the error:

    *Error* procedure: too few arguments (at least 2 expected, 1 given) - (abInvokeInstCdfCallbacks(instance \@key debug(nil) order callInitProc(nil) ... ))

    That can only happen when the procedure function is called (i.e. when the procedure is being defined), which wouldn't be happening when you just invoke abInvokeInstCdfCallbacks. So what you're saying doesn't make sense, I'm afraid - I cannot see how that would be possible.

    Regards,

    Andrew.

Reply

  • Anand,

    Maybe there isn't a parameter to control the metal width of the source/drain metal. Why do  you think there is one?

    I cannot see how calling those two lines of code can cause the error:

    *Error* procedure: too few arguments (at least 2 expected, 1 given) - (abInvokeInstCdfCallbacks(instance \@key debug(nil) order callInitProc(nil) ... ))

    That can only happen when the procedure function is called (i.e. when the procedure is being defined), which wouldn't be happening when you just invoke abInvokeInstCdfCallbacks. So what you're saying doesn't make sense, I'm afraid - I cannot see how that would be possible.

    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.