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

     Hi James,

    In general, yes - NET and SPNET would map to the drawing purpose, but PINs may also, or the DFII map may have a separate PIN purpose. Metal fill may map to drawing or some other purpose. There's just no guarantee that everyone does the same thing in their DFII map file. Like I said, I've seen some weird DFII gds maps! 

    As for confirming it's right, it's not as trial-and-error as it may have sounded. The layers and object types in Encounter are not that many - when you create your Encounter map file, you can be pretty sure you're getting everything. It's just good to verify a few things after you stream in to DFII. Also, some people output text, some don't, etc. I just want you to make sure you're getting everything you want. You don't have to pore over the entire layout! Just check a few signal routes, a few power routes, a few pins, etc. to make sure that type of data got translated correctly. Your signoff DRC and LVS would be the final test.

    I'm not sure what your Calibre text label error is. Do you mean the text is not on the layer that Calibre is expecting? You may need to check the Calibre deck with the DFII gds map to make sure that matches first. Most DFII map files have a "text" datatype, but again, it can vary. Then double check that the DFII map matches the Encounter map. Yes, the NAME lines are the ones that deal with text.

    - Kari

Reply
  • Kari

     Hi James,

    In general, yes - NET and SPNET would map to the drawing purpose, but PINs may also, or the DFII map may have a separate PIN purpose. Metal fill may map to drawing or some other purpose. There's just no guarantee that everyone does the same thing in their DFII map file. Like I said, I've seen some weird DFII gds maps! 

    As for confirming it's right, it's not as trial-and-error as it may have sounded. The layers and object types in Encounter are not that many - when you create your Encounter map file, you can be pretty sure you're getting everything. It's just good to verify a few things after you stream in to DFII. Also, some people output text, some don't, etc. I just want you to make sure you're getting everything you want. You don't have to pore over the entire layout! Just check a few signal routes, a few power routes, a few pins, etc. to make sure that type of data got translated correctly. Your signoff DRC and LVS would be the final test.

    I'm not sure what your Calibre text label error is. Do you mean the text is not on the layer that Calibre is expecting? You may need to check the Calibre deck with the DFII gds map to make sure that matches first. Most DFII map files have a "text" datatype, but again, it can vary. Then double check that the DFII map matches the Encounter map. Yes, the NAME lines are the ones that deal with text.

    - 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.