• 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. Digital Implementation
  3. Encounter DEF file export

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
rayz over 16 years ago

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

  • Cancel
Parents
  • coffeelox
    coffeelox over 15 years ago

     Hi Kari,

     I am trying to export GDS file from encounter into DFII. I have cds2gds.map and gds2cds.map, they are pretty similar, which one should I use? also, I found the map files are not acceptable by encounter while doing export. From the document, it seems encounter's layer mapping file has the different format than the DFII mapping layer format.

     THis is from encounter,

    METAL1    NET           1        0
    METAL1    SPNET         999      0
    METAL1    PIN           1000     0
    METAL1    LEFPIN        2000     0
    METAL1    FILL          3000     0
    METAL1    VIA           4000     0
    METAL1    VIAFILL       5000     0
    METAL1    LEFOBS        10000    0
    NAME      METAL1/NET    20000    0

     And this is from DFII,

    #Cadence layer    Cadence layer    Stream layer    Stream data
    #name             purpose          number          type
    #
    metal             drawing          13,10,18        0-63
    poly              drawing          40              0

    so I could not do export and import correctly, any suggestions?

    THanks a lot!

     
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • coffeelox
    coffeelox over 15 years ago

     Hi Kari,

     I am trying to export GDS file from encounter into DFII. I have cds2gds.map and gds2cds.map, they are pretty similar, which one should I use? also, I found the map files are not acceptable by encounter while doing export. From the document, it seems encounter's layer mapping file has the different format than the DFII mapping layer format.

     THis is from encounter,

    METAL1    NET           1        0
    METAL1    SPNET         999      0
    METAL1    PIN           1000     0
    METAL1    LEFPIN        2000     0
    METAL1    FILL          3000     0
    METAL1    VIA           4000     0
    METAL1    VIAFILL       5000     0
    METAL1    LEFOBS        10000    0
    NAME      METAL1/NET    20000    0

     And this is from DFII,

    #Cadence layer    Cadence layer    Stream layer    Stream data
    #name             purpose          number          type
    #
    metal             drawing          13,10,18        0-63
    poly              drawing          40              0

    so I could not do export and import correctly, any suggestions?

    THanks a lot!

     
    • 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