• 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
  • Kari
    Kari over 15 years ago

     Hi,

    It may have been better to start a new thread with this question, coffeelox - since you're looking to streamOut of Encounter and not DEFin to DFII, as the original poster was. Anyway, I'll take a stab at it...

    Yes, the format of the layer map file for Encounter's streamOut is completely different from a DFII gds map file. It's usually a lot shorter, since Encounter only deals with metal layers. You may need to create the Encounter gds map file if it was not part of the tech data delivered by the foundry. The DFII gds map file is usually part of the deliverables from the foundry. I don't know what the difference is between the two you have (cds2gds and gds2cds).

    It looks like you've already found the format for the Encounter map file in the User Guide. Also take a look at the streamOut command in the Text Command Reference. You'll want to specify the map file in this command. You will get a gds2 file that you can read into DFII.

    When you read the Encounter GDS file into DFII, you'll need to use the DFII gds map file.

    I'm not sure if this completely answers your question, but I hope it helps.

    - Kari

     

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

     Hi,

    It may have been better to start a new thread with this question, coffeelox - since you're looking to streamOut of Encounter and not DEFin to DFII, as the original poster was. Anyway, I'll take a stab at it...

    Yes, the format of the layer map file for Encounter's streamOut is completely different from a DFII gds map file. It's usually a lot shorter, since Encounter only deals with metal layers. You may need to create the Encounter gds map file if it was not part of the tech data delivered by the foundry. The DFII gds map file is usually part of the deliverables from the foundry. I don't know what the difference is between the two you have (cds2gds and gds2cds).

    It looks like you've already found the format for the Encounter map file in the User Guide. Also take a look at the streamOut command in the Text Command Reference. You'll want to specify the map file in this command. You will get a gds2 file that you can read into DFII.

    When you read the Encounter GDS file into DFII, you'll need to use the DFII gds map file.

    I'm not sure if this completely answers your question, but I hope it helps.

    - Kari

     

    • 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