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
  • Scrivner

    I don't understand why people prefer to use GDSII over DEF. I find DEF a much better way to import the data into DFII. When importing with DEF, all of the objects retain properties such as cell names on instances and net names on routes. This is very helpful if anything ever needs to be debugged in  LVS or if you are investigating ECOs, etc. If you use GDSII, all of that data gets lost.

Reply
  • Scrivner

    I don't understand why people prefer to use GDSII over DEF. I find DEF a much better way to import the data into DFII. When importing with DEF, all of the objects retain properties such as cell names on instances and net names on routes. This is very helpful if anything ever needs to be debugged in  LVS or if you are investigating ECOs, etc. If you use GDSII, all of that data gets lost.

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.