• 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 Design
  3. usim_trim to change block parameter multiplicity (m)

Stats

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

usim_trim to change block parameter multiplicity (m)

KOTB
KOTB over 7 years ago

Hello,

To change a parameter in transistor, capacitance or resistor without touching the netlist, we can use for example :usim_trim instance=x1.x2.cap5 value=3f

What if I want to change the multiplicity factor " m" of an instance x1.x2.x3 from 1 to 4 for example ? It must exist a command :  usim_trim instance=x1.x2.x3 m=4  ?

Thanks,

Regards,

kotb

  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 7 years ago

    usim_trim can only be used with a small set of parameters, as documented.

    You could just use an alter instead:

    trim1 alter dev=m1 param=m value=4

    (the first word is a unique name to distinguish it from any other alter statements).

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • KOTB
    KOTB over 7 years ago in reply to Andrew Beckett

    Thanks Andrew,

    it is still not clear for me what is the dev=m1

    let's say my instance in netlist is :

    XSEG\<7\>  (sl\<0\>  bl\<0\> 0 vdd)  SEG_RC1X 

    I want to add a multiplicity parameter of m=4 without touching the netlist. can I use the alter option directly OR the instance in netlist must already have a parameter m:

    (XSEG\<7\> (sl\<0\>  bl\<0\> 0 vdd) SEG_RC1X  m=m1) ?

    trim1 alter param=m1 value=4

    Thanks,

    Regards,

    Kotb

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 7 years ago in reply to KOTB

    Yes, this still works. You do need to put:

    trim1 alter dev=XSEG\<7\> param=m value=4

    The dev is the instance name. You can change the m-factor on a hierarchical instance, and will then apply m to everything within it (multiplying any existing m-factors on those lower level blocks by the m-factor on the instance).

    You can add:

    outPar info what=output where=file

    into the netlist, and then you can see the m-factor on each of the lower level effective parameters (it will write a file called netlistSuffix.info.output into the working dir with the information for the output parameters of each device).

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 7 years ago in reply to Andrew Beckett

    Sorry, forgot to say that this can be done even if the instance does not already have m on it.

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • KOTB
    KOTB over 7 years ago in reply to Andrew Beckett

    Thanks Andrew, 

    I used this command line  :trim1 alter dev=X8SEG\<0\>.XSEG\<7\> param=m value=4

    and I have this ERROR:

    `trim1': Sweeping the parameters of a subcircuit instance (`XSEG<7>') is currently not supported by `dev' parameter. Please use `sub' parameter instead.

    So, I replaced 'dev' by 'sub', as said in the ERROR and now it works with no problem.

    Thanks again, I am really grateful for your continuous support and smart solutions.

    Regards,

    kotb

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • KOTB
    KOTB over 7 years ago in reply to Andrew Beckett

    Thanks Andrew, 

    I used this command line  :trim1 alter dev=X8SEG\<0\>.XSEG\<7\> param=m value=4

    and I have this ERROR:

    `trim1': Sweeping the parameters of a subcircuit instance (`XSEG<7>') is currently not supported by `dev' parameter. Please use `sub' parameter instead.

    So, I replaced 'dev' by 'sub', as said in the ERROR and now it works with no problem.

    Thanks again, I am really grateful for your continuous support and smart solutions.

    Regards,

    kotb

    • 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