• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Custom IC SKILL
  3. Changing Pcell parameters with a skill script

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 144
  • Views 14467
  • 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

Changing Pcell parameters with a skill script

menime54
menime54 over 14 years ago

Hi All,

I am trying to change the parameter of a pcell using a skill script.  I can change bolean parameters using:

 instance~>parameterName = nil

inst~>sourceFirst = nil

 If I try to write to a cyclic parameter the properites form changes, but the pcell is not affected.  And it eventually errors out when I manually try to change the properties form.

inst~>lastContactParam = "no contact"

I have found a way around it in my script.  I open the properties form and change the parameter on the form and apply the change, but this option takes a very long time to complete when I run my script over a large number of transistors

 leHiEditProp() geiPlSetPropValue("editorNum0" "parameter" "lastContactParam" "cyclic" 0) geiPlInvokePlistAction("editorNum0" "apply")

Is there a way to bypass the properties form to write to a cyclic field??

Thank you,

Stephanie

  • Cancel
Parents
  • StefanSL
    StefanSL over 14 years ago

     Hi Stephanie,

    didn't hear about cyclic fields for PCells,
    is your cell really a "pure" Pcell or are there CDFs defined that behave similar to
    pcell-parameters but are defined separately?

    Perhaps you could try to inspect your cell by using the CDF-editor,

    CIW - Tools - CDF - Edit

    But, that's not the difference, you can manipulate CDF-parameters the same
    way as pcell-parameters.

    --> One possibility might be: the name of the parameter and the prompt in the
    properties form must not be necessarily the same as they are for PCells,
    so possibly you are trying to manipulate a non-existing Parameter by using an incorrect name?

    You should first check this by using the CDF-editor or by running cdfDump against
    your cell:
    cdfDump("LIB" "filename_to_dump_to" ?cellName "YOURCELL" ?level 'user ?edit t)

    hope this helps, have a nice weekend

    Stefan

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • StefanSL
    StefanSL over 14 years ago

     Hi Stephanie,

    didn't hear about cyclic fields for PCells,
    is your cell really a "pure" Pcell or are there CDFs defined that behave similar to
    pcell-parameters but are defined separately?

    Perhaps you could try to inspect your cell by using the CDF-editor,

    CIW - Tools - CDF - Edit

    But, that's not the difference, you can manipulate CDF-parameters the same
    way as pcell-parameters.

    --> One possibility might be: the name of the parameter and the prompt in the
    properties form must not be necessarily the same as they are for PCells,
    so possibly you are trying to manipulate a non-existing Parameter by using an incorrect name?

    You should first check this by using the CDF-editor or by running cdfDump against
    your cell:
    cdfDump("LIB" "filename_to_dump_to" ?cellName "YOURCELL" ?level 'user ?edit t)

    hope this helps, have a nice weekend

    Stefan

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information