• 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. Help: SOC Encounter DEFout and Virtuoso DEFin

Stats

  • Locked Locked
  • Replies 10
  • Subscribers 91
  • Views 15511
  • 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
Ruri over 14 years ago

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!

  • Cancel
  • Kari
    Kari over 14 years ago

     Hi,

     Using a DEF is not a typical way to get your design from Encounter to Virtuoso. I always use Encounter's streamOut command to transfer gds. You could also use OA I believe. Check the Encounter user guide for either one of these methods. It may take some setup, but you'll get much better results.

     - Kari

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Ruri
    Ruri over 14 years ago

    Thank you very much for your reply, Kari.

    Since I only have the standard cell library without the abstract view, will that affact the StreamIn?

     Another question is that the Cadence available to me at this moment is IC5141, is OA still an option?

     Thanks!

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Kari
    Kari over 14 years ago

     I don't think you need the abstract view. They layout is what's important, and that's all I ever use.

     I don't have any experience with OA, but as far as I know, it was available in 5141.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Scrivner
    Scrivner over 14 years ago

     Hi Ruri,

     

    I use DEF to import digital blocks to be placed in mixed-signal designs in Virtuoso. The via information should be defined in the techfile of the library that you are importing the design into (or in the techfile that the library is attached to). The warnings you see means that the techfile needs to have the via definitions added.

     

    You can still import the design without having abstract views. In the import DEF form (File->Import->DEF), there is a field called "Component Master Views". Put "layout" in this field and it will use the layout views when importing instead of abstract views. 

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Ruri
    Ruri over 14 years ago

    Thanks, Kari and Scrivner.

    Kari - I will try the GDS streamOut from Encounter later, since I do not have the streamOut map file at this moment ...

     Scrivner - I checked the library and tech file you mentioned, they do not have the Via information, as you said. But the via information from Encounter is so weird - the names are like VIA12_1CUT_H ... VIA23_1CUT_FAT_C ... really don't know where to find libs having such definitions ... could you please give me a hint?

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Ruri
    Ruri over 14 years ago

    Hi Scrivner,

     I just tried to add "layout" in the field of "Component Master Views," and it did show the standard cell layout in the Virtuoso this time, but all the standard cells are somehow misplaced and overlapped ... The log file has the warning of:

    \w *WARNING* Cellview (XXXX layout) has no cell boundary!

    ......

     

    BTW, I still got no vias ...

     

    Thank you,

    Ruri  

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Scrivner
    Scrivner over 14 years ago

    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.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Ruri
    Ruri over 14 years ago

    Hi Scrivner,

    Thank you very much for your detailed explaination.

    I just did the streamOut and streamIn, and succeeded so far. I got another question - how to proceed with the LVS with Assura or Calibre? given I only have the functional view by importing (Verilog In) the structural verilog file from SOC Encounter? shouldn't I need the schematic view to proceed with the LVS?

     Thank you again,

    Ruri

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Kari
    Kari over 14 years ago

     LVS is Layout Vs Schematic. You'll be comparint the GDS (layout) to the schematic (verilog netlist).

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Ruri
    Ruri over 14 years ago
    Thank you, Kari. Don't know what you're trying to say, but I solved the problem. It took me some time to correctly import the verilog netlist with power and ground pins, so that I can proceed the LVS with general analog flow. Thanks, Ruri
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

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