• 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. Back annotation of design parameters in the schematic (SKILL...

Stats

  • Locked Locked
  • Replies 8
  • Subscribers 145
  • Views 16599
  • 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

Back annotation of design parameters in the schematic (SKILL code).

Atul Dwivedi
Atul Dwivedi over 12 years ago

Hi there,

I am in want of a simple procedure to set the componet values (eg. w,l of MOS; capacitance value of a cap) in the schematic from a file. The input file may contain the desired component value in the required format.  

Please tell me if this is possible. If yes, please suggest the appropriate APIs to do the same and what all formatted information should the input file store.

Thanks in advance.

Regards,

Atul 

  • Cancel
  • NiallDuncan
    NiallDuncan over 12 years ago

    If the ID of your capacitor is "instId" and if you have the schematic open then you can modify its parameters using the code below. Then you just need to read in the values from a file which should be straight forward.

    ;; Select the instance
    geDeselectAll()
    geSelectObject( instId )

    ;; Call the "Edit Object Properties" dialog
    ;; Using this method ensures that callbacks are maintained
    schHiObjectProperty()

    ;; Update the instance properties
    schObjPropForm->w->value = "2u"
    schObjPropForm->l->value = "0.5u"

    ;; Close the form
    hiFormDone(schObjPropForm)

    ;; Unselect the instance
    geDeselectAll()

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • skillUser
    skillUser over 12 years ago

    Hi Atul,

    You may wish to look at this code from the support site. When changing instance parameters through SKILL, the CDF callbacks would not be invoked, so you will also most likely need the following solution code also: How to invoke CDF callbacks procedurally through SKILL

    Then the only piece missing for you is to have a file of an appropriate format and read it in using SKILL - let us know if you need help with that part.

    Regards,

    Lawrence.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Atul Dwivedi
    Atul Dwivedi over 12 years ago

    Thank you both of you!

    Lawrence, a special thanks for providing those links. I am yet to deeply understand these codes. But before that I just want to confirm that are these compatible with a hierarchy of cellViews? For eg. I have one topLevel and three instances of another CellView (and further nesting is possible). We can assume the name of the subcircuit instance in the topLevel (and at all levels) is available in the input file. Is the code capable of handling this level of complexity. If not, then can you please further suggest me how do I go about it?

    Thanks and Regards,

    Atul 

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • NiallDuncan
    NiallDuncan over 12 years ago

    Atul,

     

    If you provide the library and cellview name in your file, then you can open each cellview in append mode using:

    cellId = dbOpenCellViewByType("myLibrary" "myCellView" "schematic" "schematic" "a")

    To get a particular instance you use:

    instId = dbGetInstanceByName(cellId, "myInstanceName")

    Do some modifications. And when you are complete you would save the changes and close the cell

     dbSave(cellId)

    dbClose(cellId)

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • skillUser
    skillUser over 12 years ago

     Hi Atul,

    To be clear, the code for changing instance parameters works at the current level only, so you would need to do something like what Niall is suggesting. The callback-invoking code is called per-cellview also, but you can call it for all cellviews in a library, for example, so you can perform all the parameter updates first and then you could force all the callbacks for everything afterwards.

    To expand through the hierarchy, you could control it from the top-level using the names found in the file, and you would need to intelligently handle how to push down more than one level if needed.  An alternative approach is to expand everything in the hierarchy (assuming that you need to change something at all levels, for example).  In this case you might find code similar to that found in this solution helpful, it contains an example of a recursive function for expanding or traversing all cells in the hierarchy.

    Good luck with the coding!

    Lawrence.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Atul Dwivedi
    Atul Dwivedi over 12 years ago

    Dear Niall, thanks a lot for such a simple solution. I had been hunting around for such an easy solution, but never found it. If you don't mind, can you please elaborate on how you guys know about so many APIs? I mean the Cadence Finder is there and so is the community, what else?

    Lawrence, I must thank you for the efforts. My problem is solved by above method, hence would not go for any approach requiring recursion (although that was indeed my last resort!).  

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 12 years ago

    Atul,

    The cdsFinder is only a quick reference - I'd advise taking a look at the documentation in more detail (cdnshelp in IC61X releases). There are manuals in there for various SKILL API, in much more depth than the cdsFinder - which is intended really only as a reminder. There are whole manuals for SKILL language, User Interface functions, Design Framework/Virtuoso, Schematic, Virtuoso Layout Suite, etc, etc.

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Atul Dwivedi
    Atul Dwivedi over 12 years ago

    Andrew,

     'cdnshelp' is indeed a wonderful tool. I am sure this will help me a lot in my work. Thanks a lot for voluntering and helping me out!

    Regards,

    Atul 

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

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