• 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 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
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
Parents
  • 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
Reply
  • 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
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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information