• 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. Deleting Schematic instance and instantiating another device...

Stats

  • Locked Locked
  • Replies 19
  • Subscribers 143
  • Views 25459
  • 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

Deleting Schematic instance and instantiating another device on the same origin

archive
archive over 13 years ago

Dear All,

I am looking to do the following thing using SKILL

1. Open a schematic and look for a specific instance.

2. Delete the instance.

3. Instantiate another cell at the same origin (Both the symbols match in pin locations.)

 

I am not able to identify, how I can get the origin of the original instance before deleting it. Any kind of help is much appreciated.

 

Please help!

 

Thanks,

Vijay

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

    Hi Reinice,

    First of all, I've no idea why you are using the names  "IO|P__2" etc. I'm positive they're not the names of the "pins" (actually it's the terminal name I care about - so maybe I'm using the wrong nomenclature - the term name is the one of interest).

    So the pinMap would be:

    pinMap (("B" "B") ("C" "C") ("E" "E"))

    In which case you can just leave it commented it. You show the "B" corresponding to the "E" pin in your table, but that can't be correct because that would mean the base and emitter are being swapped. Also you show the different orientation - the orientation is only needed if the transistor is a different way around.

    If you comment out the pinMap line, the error message you get is not the one you show, but instead would be:

    *Error* Could not find mapped pin IO|P__0 on tsmcN40/pnp/symbol

    That's not surprising, since the pin should be "B" - 

         pinOrigin "B"

    So given my above comment, I suspect you may want orient to be set to "R0" too - but you can experiment with that yourself.

    From your second question, you need to call the code with the database object of the cellView being migrated. If it's already open in the schematic editor, and the window is the current window, you can call:

    abMapAndWire(geGetEditCellView())

    Regards,

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 13 years ago

    Hi Reinice,

    First of all, I've no idea why you are using the names  "IO|P__2" etc. I'm positive they're not the names of the "pins" (actually it's the terminal name I care about - so maybe I'm using the wrong nomenclature - the term name is the one of interest).

    So the pinMap would be:

    pinMap (("B" "B") ("C" "C") ("E" "E"))

    In which case you can just leave it commented it. You show the "B" corresponding to the "E" pin in your table, but that can't be correct because that would mean the base and emitter are being swapped. Also you show the different orientation - the orientation is only needed if the transistor is a different way around.

    If you comment out the pinMap line, the error message you get is not the one you show, but instead would be:

    *Error* Could not find mapped pin IO|P__0 on tsmcN40/pnp/symbol

    That's not surprising, since the pin should be "B" - 

         pinOrigin "B"

    So given my above comment, I suspect you may want orient to be set to "R0" too - but you can experiment with that yourself.

    From your second question, you need to call the code with the database object of the cellView being migrated. If it's already open in the schematic editor, and the window is the current window, you can call:

    abMapAndWire(geGetEditCellView())

    Regards,

    Andrew

    • 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