Stats

  • Locked Locked
  • Replies 13
  • Subscribers 95
  • Views 21553
  • 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

Encounter DEF file export

rayz

I am trying to export my layout from Encounter to Cadence DFII ennvironment using DEF format.  Apparently the DEF file generated by Encounter does not contain all the VIA definitions or Virtuoso has problem reading them since when the design is imported in Virtuoso some of the VIAs are missing and I see warniong message that VIA definitions are missing. Do you have any experince dealing with this issue.

Thanks

Parents
  • Kari

    Hi James,

    You wouldn't so much modify the DFII map file to get the Encounter map file, as you would create the Encounter map file from scratch and just use the GDS layer and datatype numbers from the DFII map file. The Encounter map file only needs the layers that are defined in your LEF file, usually just the metal and via layers. These usually correspond to the "drawing" purpose in the DFII map file. But you may also have metal fill (as an example), which may or may not be a different purpose or even a different layer altogether. I've seen DFII techfiles that define these things several different ways, so it really depends on your technology.

    The Encounter User Guide has a chapter called "Importing and Exporting Designs" - read the section near the end about the map file format. Take a stab at creating it, stream the GDS into DFII, and see if everything is there like it should be. If not, you may have to go back and add some things. 

    Here's a quick example for just a couple of layers that may help: (the colums are: lef layer name, Encounter object type, GDS layer #, GDS datatype #)

    M1              NET             31              0
    M1              SPNET           31              0
    M1              FILL            31              1
    M1              PIN             31              0
    VIA1            VIA             51              0
    M2              NET             32              0
    M2              SPNET           32              0
    M2              FILL            32              1
    M2              PIN             32              0

    - Kari

Reply
  • Kari

    Hi James,

    You wouldn't so much modify the DFII map file to get the Encounter map file, as you would create the Encounter map file from scratch and just use the GDS layer and datatype numbers from the DFII map file. The Encounter map file only needs the layers that are defined in your LEF file, usually just the metal and via layers. These usually correspond to the "drawing" purpose in the DFII map file. But you may also have metal fill (as an example), which may or may not be a different purpose or even a different layer altogether. I've seen DFII techfiles that define these things several different ways, so it really depends on your technology.

    The Encounter User Guide has a chapter called "Importing and Exporting Designs" - read the section near the end about the map file format. Take a stab at creating it, stream the GDS into DFII, and see if everything is there like it should be. If not, you may have to go back and add some things. 

    Here's a quick example for just a couple of layers that may help: (the colums are: lef layer name, Encounter object type, GDS layer #, GDS datatype #)

    M1              NET             31              0
    M1              SPNET           31              0
    M1              FILL            31              1
    M1              PIN             31              0
    VIA1            VIA             51              0
    M2              NET             32              0
    M2              SPNET           32              0
    M2              FILL            32              1
    M2              PIN             32              0

    - Kari

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.