Stats

  • Locked Locked
  • Replies 4
  • Subscribers 125
  • Views 14028
  • 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

Symbolics and Translation to IC61

armthy

 Hello,

I have noticed that during IC51 to IC61 translation, some of the symbolic/symbolic arrays are unbound in IC61.

On further investigation, I have realized that this is due to incorrect usage of symbolics in IC51.  Instead of using Create->Contact the Symbolics have been added as an Instance. Since I have seen legacy designs that have this usage all over the hierarchy, I am wondering if any forum members has a template of skill code that can go thru a layout hierarchy and replace symbolic instances with the equivalent contacts.

I can run such a code in IC51, correct the layout hierarchy and then run the translation to IC61.

Appreciate any help on this.

Thanks!

  •  On a related note. Has any of you faced this issue and if so how have you gotten around it?

    If I query the symbolic instance which parameter should tell me that it is a symbolic placed as an instance? To do a replace this is key as I need to differentiate from other instances. Any ideas?

    Thanks!

  •  I'd be surprised if this was to do with it being placed as an instance in IC5141, since there's not really a difference between an instance and a via in IC5141 - it's the same object in the database.

    Probably best to contact customer support. Then we can take a look at your data and figure out what's going wrong.

    Andrew.

  •  Hi Andrew,

     Thanks for your reply. If you place a instance array of a via in IC51 the objType is mosaicInst. This will not translate correctly to IC61. It will be unbound. If you use the "Create->Contact" and create a contact array, this will get translated correctly to IC61 as the vias will be now mapped to the one coming from the techfile via definition.

    Normal 0 false false false EN-US X-NONE X-NONE /* Style Definitions */ table.MsoNormalTable {mso-style-name:"Table Normal"; mso-tstyle-rowband-size:0; mso-tstyle-colband-size:0; mso-style-noshow:yes; mso-style-priority:99; mso-style-parent:""; mso-padding-alt:0in 5.4pt 0in 5.4pt; mso-para-margin:0in; mso-para-margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-ascii-font-family:Calibri; mso-ascii-theme-font:minor-latin; mso-hansi-font-family:Calibri; mso-hansi-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman"; mso-bidi-theme-font:minor-bidi;} I was able to create code for this purpose as follows.

    if((cvt~>viewName == "symbolic" && cvt~>objType == "mosaicInst" && cvt~>w) then 

                    coordT=(xCoord(lowerLeft(cvt~>mosaic~>bBox))+xCoord(upperRight(cvt~>mosaic~>bBox)))/2.0:(yCoord(lowerLeft(cvt~>mosaic~>bBox))+yCoord(upperRight(cvt~>mosaic~>bBox)))/2.0                               

                    leCreateContact(cvID cvt~>cellName coordT car(cvt~>mosaic~>tileArray) cvt~>w cvt~>l cvt~>mosaic~>rows cvt~>mosaic~>columns cvt~>mosaic~>uX cvt~>mosaic~>uY  "center" "center")

                    dbDeleteObject(cvt~>mosaic)

                    ) ;if

  • OK, that makes sense. I was assuming the symbolic had been placed in IC5141 with the right parameters for rows and columns, rather than being placed as a mosaic.

    Andrew.

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.