• 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
  • Reinice
    Reinice over 13 years ago

    Hi Andrew,

    I 'am trying your abMapAndWire.ils

    I want to migrate this instance to the new process:               pnp5(old process)                       pnp(new process)

    Instance Name is                                                                         "Q1"                                          "Q0"

    Instance Orientation is                                                                 "MY"                                          "R0"

    Instance Terminal Name is                                                             "C"                                           "C"

    Pin Name is                                                                             "IO|P__2"                                       "3"

    Instance Terminal Name is                                                             "E"                                           "B"

    Pin Name is                                                                             "IO|P__1"                                       "2"

    Instance Terminal Name is                                                             "B"                                           "E"

    Pin Name is                                                                              "IO|P__0"                                      "1"

    But I'am having an error on (abMapAndWireLoadConfig "config.file")
     

    Here is the content of my config.file

    (
      nil
      xSnapSpacing 0.0625   ; defaults to 0.0625
      ySnapSpacing 0.0625   ; defaults to 0.0625
      fontHeight 0.0625     ; defaults to xSnapSpacing
      addWireLabels t       ; if it should add labels for wire stubs left by
                            ; inherited connections
      map
      (
       (nil
        ; lib/cell/view to be converted, from and to.
        ; all to setting default to the from settings, and the
        ; fromView defaults to "symbol".
        fromLib "TSMC90G1033"
        fromCell "pnp5"
        fromView "symbol_xform"
        toLib "tsmcN40"
        toCell "pnp"
        toView "symbol"
        ; if any pin names need mapping, do that here. Otherwise
        ; can omit
        pinMap (("IO|P__2" "3") ("IO|P__1" "2") ("IO|P__0" "1"))
        ; Which pins should not be wired, but should replace with a
        ; netSet on the instance
        ;pinToNetSet (("B" "nbulk"))
        ; which pin should be considered the origin - in other words,
        ; stay where it is. It does not have to be the origin of the symbol
        pinOrigin "IO|P__0"
        ; this is the orientation you need to give to the new symbol
        ; to rotate it to the same orientation as the old symbol
        orient "MY"
        )
       )
      )
     

    *Error* Could not find mapped pin 1 on tsmcN40/pnp/symbol

    and when I comment pinMap (("IO|P__2" "3") ("IO|P__1" "2") ("IO|P__0" "1")), here is the error:

    *Error* Could not find mapped pin 1 on tsmcN40/pnp/symbol

    What would be the correct input for my config.file?

    Is it needed that pin names of an instance must be the same for old process and new process so that errors such as above will not show?

    Hope you can help me on this. Thanks in advance.

    Thanks and Regards,

    Reinice

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Reinice
    Reinice over 13 years ago

    Hi Andrew,

    I 'am trying your abMapAndWire.ils

    I want to migrate this instance to the new process:               pnp5(old process)                       pnp(new process)

    Instance Name is                                                                         "Q1"                                          "Q0"

    Instance Orientation is                                                                 "MY"                                          "R0"

    Instance Terminal Name is                                                             "C"                                           "C"

    Pin Name is                                                                             "IO|P__2"                                       "3"

    Instance Terminal Name is                                                             "E"                                           "B"

    Pin Name is                                                                             "IO|P__1"                                       "2"

    Instance Terminal Name is                                                             "B"                                           "E"

    Pin Name is                                                                              "IO|P__0"                                      "1"

    But I'am having an error on (abMapAndWireLoadConfig "config.file")
     

    Here is the content of my config.file

    (
      nil
      xSnapSpacing 0.0625   ; defaults to 0.0625
      ySnapSpacing 0.0625   ; defaults to 0.0625
      fontHeight 0.0625     ; defaults to xSnapSpacing
      addWireLabels t       ; if it should add labels for wire stubs left by
                            ; inherited connections
      map
      (
       (nil
        ; lib/cell/view to be converted, from and to.
        ; all to setting default to the from settings, and the
        ; fromView defaults to "symbol".
        fromLib "TSMC90G1033"
        fromCell "pnp5"
        fromView "symbol_xform"
        toLib "tsmcN40"
        toCell "pnp"
        toView "symbol"
        ; if any pin names need mapping, do that here. Otherwise
        ; can omit
        pinMap (("IO|P__2" "3") ("IO|P__1" "2") ("IO|P__0" "1"))
        ; Which pins should not be wired, but should replace with a
        ; netSet on the instance
        ;pinToNetSet (("B" "nbulk"))
        ; which pin should be considered the origin - in other words,
        ; stay where it is. It does not have to be the origin of the symbol
        pinOrigin "IO|P__0"
        ; this is the orientation you need to give to the new symbol
        ; to rotate it to the same orientation as the old symbol
        orient "MY"
        )
       )
      )
     

    *Error* Could not find mapped pin 1 on tsmcN40/pnp/symbol

    and when I comment pinMap (("IO|P__2" "3") ("IO|P__1" "2") ("IO|P__0" "1")), here is the error:

    *Error* Could not find mapped pin 1 on tsmcN40/pnp/symbol

    What would be the correct input for my config.file?

    Is it needed that pin names of an instance must be the same for old process and new process so that errors such as above will not show?

    Hope you can help me on this. Thanks in advance.

    Thanks and Regards,

    Reinice

    • 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