• 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. Connectivity lost while changing technology.

Stats

  • Locked Locked
  • Replies 12
  • Subscribers 145
  • Views 17599
  • 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

Connectivity lost while changing technology.

Atul Dwivedi
Atul Dwivedi over 12 years ago

Hi there,

As the subject suggests I am trying to migrate a design from one technology to another. The method adopted is by changing the master:

selectedObject=car(geGetSelSet())

masterID=dbOpenCellViewByType("newTechLibName" "newTechCellName" "symbol" "schematicSymbol") 

selectedObject~>master=masterID

This indeed changes the master and I can see the MOS of new technology appearing, but the wires connecting them are not connected now (it seems as if because of change in symbol).

A slight adjustment does the job at graphical schematic level. Is there any way to change the master and preserve the connectivity also (the w's and l's value remains same, fortunately!)

Thanks and Regards,

Atul 

  • Cancel
Parents
  • Atul Dwivedi
    Atul Dwivedi over 12 years ago

    Hi Andrew,

    The config file has the following contents:

    (

      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

                            ; 

                            ons

      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 "cmos32lp"

       ; fromCell "egnfet_b"

       ; fromView "symbol"

       ; toLib "cmos090"

       ; toCell "nsvt33"

       ; toView "symbol"

       ; ; if any pin names need mapping, do that here. Otherwise

       ; ; can omit

       ; ;pinMap (("G" "g") ("D" "d"))

       ; ; 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 "D"

       ; ; this is the orientation you need to give to the new symbol 

       ; ; to rotate it to the same orientation as the old symbol

       ; ;orient "R90"

       ; )

       ; and now for another mapping...

       ;(nil

       ; fromLib "cmos32lp"

       ; fromCell "egpfet_b"

       ; fromView "symbol"

       ; toLib "cmos090"

       ; toCell "psvt33"

       ; toView "symbol"

       ; ;pinOrigin "G"

       ; ;orient "R90"

       ; )

       (nil

        fromLib "analogLib"

        fromCell "pmos4"

        fromView "symbol"

        toLib "cmos090"

        toCell "psvt33"

        toView "symbol"

        ;pinOrigin "G"

        ;orient "R90"

        )

       (nil

        fromLib "analogLib"

        fromCell "nmos4"

        fromView "symbol"

        toLib "cmos090"

        toCell "nsvt33"

        toView "symbol"

        ;pinOrigin "G"

        ;orient "R90"

        )

       )

      ) 

     

    Regards,

    Atul 

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

    Hi Andrew,

    The config file has the following contents:

    (

      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

                            ; 

                            ons

      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 "cmos32lp"

       ; fromCell "egnfet_b"

       ; fromView "symbol"

       ; toLib "cmos090"

       ; toCell "nsvt33"

       ; toView "symbol"

       ; ; if any pin names need mapping, do that here. Otherwise

       ; ; can omit

       ; ;pinMap (("G" "g") ("D" "d"))

       ; ; 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 "D"

       ; ; this is the orientation you need to give to the new symbol 

       ; ; to rotate it to the same orientation as the old symbol

       ; ;orient "R90"

       ; )

       ; and now for another mapping...

       ;(nil

       ; fromLib "cmos32lp"

       ; fromCell "egpfet_b"

       ; fromView "symbol"

       ; toLib "cmos090"

       ; toCell "psvt33"

       ; toView "symbol"

       ; ;pinOrigin "G"

       ; ;orient "R90"

       ; )

       (nil

        fromLib "analogLib"

        fromCell "pmos4"

        fromView "symbol"

        toLib "cmos090"

        toCell "psvt33"

        toView "symbol"

        ;pinOrigin "G"

        ;orient "R90"

        )

       (nil

        fromLib "analogLib"

        fromCell "nmos4"

        fromView "symbol"

        toLib "cmos090"

        toCell "nsvt33"

        toView "symbol"

        ;pinOrigin "G"

        ;orient "R90"

        )

       )

      ) 

     

    Regards,

    Atul 

    • 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