Stats

  • Locked Locked
  • Replies 10
  • Subscribers 91
  • Views 15795
  • 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

Help: SOC Encounter DEFout and Virtuoso DEFin

Ruri

Hi,

I've been doing analog designs, and new to the digital implementation. Really really need your help, these problems have troubled me for several days!

I did the APR in SOC encounter (Ver 9.1), and the results looked OK. So I DEFout (5.5) and DEFin to the Virtuoso (Ver 5141), the VIAs and Standcells are missing, and lots of warning like this:

************************************************************************************************** 

\o Processing VIAS Section

\w *WARNING* dbOpenCellViewByType: Failed to open cellView (VIAGEN12_1 layout) from lib (tsmcN65) in 'r' mode because cellview does not exist.

\w *WARNING* dbOpenCellViewByType: Failed to open cellView (VIAGEN12_3 layout) from lib (tsmcN65) in 'r' mode because cellview does not exist.

\w *WARNING* Unable to find site master CORE.

.........

\o Processing COMPONENTS Section

\w *WARNING* Unable to find master DFCNQD1!

\w *WARNING* Unable to find master DFCNQD1. Instance TMP_REG[0] not created.

.......... 

*****************************************************************************************************************

I googled a lot, and found a post suggested that I might have left out the reference library that contains the VIA information. But what kind of reference library has the VIA information? Right now I only have a standard cell library from TSMC that contains all of the standard cells, with only schematic, symbol and layout view (NO ABSTRACT view!!).

Given I'm only having the standard cell library without abstract view, is it possible to transfer the digital layout to Virtuoso? I need to integrate both the digital and analog layout as a chip.

Really don't know what to do next ... please, help!  

Any comments, suggestions are appreciated!

Parents
  • Scrivner

    Hi Ruri,

     

    About the vias - the LEF used by Encounter defines vias. The via definitions can include what's called "generated vias" which is a sort of a bit of code that  tells Encounter how to build vias that it needs. When it builds these vias it names them with these odd names. In order to import the DEF into a Virtuoso layout, the techfile for the library you are importing must have the same via definitions that are in the LEF file. So it sounds like your techfile does not have the vias defined.

     

    The problem with overlapped cells is that there is no prBoundary layer defined in the layouts of the cells according to the warning.

     

    So it looks like import using DEF is not a good option since your cell library and techfiles are not set up to support it. It sounds like you are going to have to use GDS stream for import/export.

Reply
  • Scrivner

    Hi Ruri,

     

    About the vias - the LEF used by Encounter defines vias. The via definitions can include what's called "generated vias" which is a sort of a bit of code that  tells Encounter how to build vias that it needs. When it builds these vias it names them with these odd names. In order to import the DEF into a Virtuoso layout, the techfile for the library you are importing must have the same via definitions that are in the LEF file. So it sounds like your techfile does not have the vias defined.

     

    The problem with overlapped cells is that there is no prBoundary layer defined in the layouts of the cells according to the warning.

     

    So it looks like import using DEF is not a good option since your cell library and techfiles are not set up to support it. It sounds like you are going to have to use GDS stream for import/export.

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.