• 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 code to add instance

Stats

  • Locked Locked
  • Replies 8
  • Subscribers 144
  • Views 22520
  • 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 code to add instance

Yassin
Yassin over 16 years ago

Hi,

I want a skill code to add an instance in a schematic sheet.

I tried the following code but it hasn't worked

procedure(
abc(component)
schHiCreateInst("tsmcN90" component "symbol" "I0" 1 1)
mouseAddPt()
0:0
)

then i call this function using:
abc("nch")

I am new to skill so i expect that there are much better ways to do that.

by the way, what does Hi stands for in the word schHiCreateInst??

Regards,
Yassin

  • Cancel
Parents
  • dmay
    dmay over 16 years ago

    The "hi" refers to "Human Interface". These are the commands you find when you are interactively working in Composer or Virtuoso. For doing the same thing in Skill code, you want to look for commands without the "hi".

    You should be able to use schCreateInst or dbCreateInst. To be honest, I'm not sure what the difference is between the two.

    procedure(abc(component)
        ;First you need to get the master id of the cell you want to place
        mstr=dbOpenCellViewByType("tsmcN90" component "symbol"  "schematicSymbol" "r")
        schCreateInst(geGetEditCellView() mstr "I0" 0:0 "R0" 1)
    )

    Note the following usage info for schCreateInst. If you set the instance name to be nil instead of I0, then Cadence will automatically name the instance uniquely.

    schCreateInst(
    d_cvId
    d_masterId
    t_instanceName
    l_origin
    t_orient
    [ n_magnification ]
    )
    => d_inst | nil

    Creates an instance of the given master cellview in the specified cellview at the given location with the given orientation. You can specify the magnification to set for the instance. Although not fully supported, you can use this property to scale the appearance of an instance.

    Derek

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • dmay
    dmay over 16 years ago

    The "hi" refers to "Human Interface". These are the commands you find when you are interactively working in Composer or Virtuoso. For doing the same thing in Skill code, you want to look for commands without the "hi".

    You should be able to use schCreateInst or dbCreateInst. To be honest, I'm not sure what the difference is between the two.

    procedure(abc(component)
        ;First you need to get the master id of the cell you want to place
        mstr=dbOpenCellViewByType("tsmcN90" component "symbol"  "schematicSymbol" "r")
        schCreateInst(geGetEditCellView() mstr "I0" 0:0 "R0" 1)
    )

    Note the following usage info for schCreateInst. If you set the instance name to be nil instead of I0, then Cadence will automatically name the instance uniquely.

    schCreateInst(
    d_cvId
    d_masterId
    t_instanceName
    l_origin
    t_orient
    [ n_magnification ]
    )
    => d_inst | nil

    Creates an instance of the given master cellview in the specified cellview at the given location with the given orientation. You can specify the magnification to set for the instance. Although not fully supported, you can use this property to scale the appearance of an instance.

    Derek

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
  • Nhumai
    Nhumai over 7 years ago in reply to dmay

    Hi Derek,

    what if I would like to create a master schematic which contain all other instance of all the cells in 1 lib. 

    how can I modify your code ? I am a beginner to skill 

    thanks 

    Nhumai 

    • 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