Stats

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

     Hi Kari,

    So there is no mapping table between GDS2 layer type and Encounter layer type? such as NET in encounter should be drawing in DFII, SPNET in encounter should be drawing in DFII as well?

    Also, after I create mapping file for encounter, the only way to confirm it's right is by checking the layout shown in DFII is same as layout shown in encounter? it sounds too dangerous if the layout is big and complex.

    In addition, I tried to export gds2 from encounter to DFII, then calibre DRC shows text label error, it seems related to NAME layer in encounter mapping file, how to match the layer data type for this?

    Thanks a lot!

    James

Reply
  • coffeelox

     Hi Kari,

    So there is no mapping table between GDS2 layer type and Encounter layer type? such as NET in encounter should be drawing in DFII, SPNET in encounter should be drawing in DFII as well?

    Also, after I create mapping file for encounter, the only way to confirm it's right is by checking the layout shown in DFII is same as layout shown in encounter? it sounds too dangerous if the layout is big and complex.

    In addition, I tried to export gds2 from encounter to DFII, then calibre DRC shows text label error, it seems related to NAME layer in encounter mapping file, how to match the layer data type for this?

    Thanks a lot!

    James

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.