• 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. Skill command to create the cell view?

Stats

  • Locked Locked
  • Replies 11
  • Subscribers 143
  • Views 23286
  • 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

Skill command to create the cell view?

niteshtripathi
niteshtripathi over 8 years ago

Hi everyone,

Using skill i have successfully created a library. Now i want to create the cell view so that further and i can add instances to create the schematics. What is the command to create the cell view. Thanks.

  • Cancel
  • Andrew Beckett
    Andrew Beckett over 8 years ago

    Clearly you didn't do much searching or looking for examples, because this information should be pretty easy to find.

    All you need to do is:

    cv=dbOpenCellViewByType(libName cellName viewName "schematic" "a") ; fifth arg could be "a" or "w"

    The mode is either "a" (append/edit) or "w". For a new view, it doesn't matter - but for an existing view, "w" will overwrite, whereas "a" will start from what's there already. The fourth argument is the viewType (not the view name).

    Hopefully that will be enough for you to find the right part of the documentation, and some examples (e.g. on these forums).

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • niteshtripathi
    niteshtripathi over 8 years ago
    Hi Andrew,

    Thanks for your king reply. I have got the solution.
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • niteshtripathi
    niteshtripathi over 8 years ago
    Hi Andrew,

    Now i want to attach a tech library to my own created library. The solution which i have got is :

    techBindTechFile(ddGetObj("myLib") "newTechLib" "tech.db" t)

    Is this the correct way?

    I will be grateful for your suggestion and feedback.
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 8 years ago

    Yes, that would work.

    A slightly more portable way (which would work in IC5141 and IC61X/ICADV12.X) would be to use:

    techBindTechFile(ddGetObj("myLib") "theTechLib" techGetDefaultTechName()) ; may want to add t as fourth argument

    The techGetDefaultTechName will return the correct database filename in CDB or OA. Unlikely to change in future, but might as well future-proof your code.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • niteshtripathi
    niteshtripathi over 8 years ago
    Thanks a ton Andrew.
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • niteshtripathi
    niteshtripathi over 8 years ago

    Hi Andrew,

    I have created a instance after creating a library and cell view using the following code :

    library_name = "test_lib"
    lib_id = dbCreateLib(library_name)
    cell_name = "test_cell_1"
    cv=dbOpenCellViewByType(lib_id cell_name "schematic" "schematic" "w")
    techBindTechFile(ddGetObj(library_name) "tsmcN65" techGetDefaultTechName() t)
    masterId=dbOpenCellViewByType("tsmcN65" "nch" "symbol")
    dbCreateInst(cv masterId "M0" list(0,0) "R0" 1)

    now I want to change the properties of that instance such as length and width and I am able to do that using following :

    inst=dbFindAnyInstByName(cv "M0")

    schReplaceProperty( inst_temp "l"  "len" )

    schReplaceProperty( inst_temp "w"  "len" )

    But the problem is that toltal_width and other parameters are not changing according to the above changed parameters.

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

    That's because these are (probably) set by a CDF callback, and CDF callbacks are normally only called by form interactions, not database interactions.

    Search on support.cadence.com for CCSinvokeCdfCallbacks or on these forums (using the search in the top right corner) for abInvokeCdfCallbacks - you should find a function to call the callbacks procedurally.

    BTW, you don't really need to use schReplaceProperty - you can use dbReplaceProp or even just use inst~>w=len. You could also avoid using inst=dbFindAnyInstByName by just using the return value of dbCreateInst in the first place (this will be the instance id of the newly created instance).

    Regards,

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • niteshtripathi
    niteshtripathi over 8 years ago
    Hi Andrew,

    Thanks for your prompt reply.

    Basically when we edit any parameter in the property editor, we get this on ciw "schObjPropForm->l->value="70n" , from where I can have look on this code which is executed.
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 8 years ago

    I'm not entirely sure what you're asking here. When you are interacting with the edit properties form, it will both change the property on the instance (at the database level) and then look at the callback attribute of the CDF parameter "l" for the cell that you're editing an instance of. abInvokeCdfCallbacks/CCSinvokeCdfCallbacks is a simplified interface to allow you to call those callbacks (by finding the function in the CDF, setting up the CDF appropriately and then calling the function). I suggest you use that rather than reinvent the wheel.

    Regards,

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • niteshtripathi
    niteshtripathi over 8 years ago
    Hi Andrew,

    Here is detail what have i done/ trying to do :

    I have made a test bench for nMOS/pMOS characterization. Now I want to update the length and width by the variable suppose "len" and "wid". According to this variable ,remaining parameters should be updates such total width etc.

    I want to write a universal code which should work even if i change the tech library.

    Thanks & Regards,

    Nitesh
    • 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