• 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. Importing encounter created GDSII file in virtuoso 6.1....

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 91
  • Views 14904
  • 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

Importing encounter created GDSII file in virtuoso 6.1.5

jagadishdn
jagadishdn over 11 years ago

I am facing an issue during import of an encounter RTL-to-GDSII 11.1 created gds2 file. I have a tsak of taking of place and routing digital logic block in encounter and importing the same into virtuoso 6.1.5 for mixed signal simulation. Following are the things i have been able to do so far.

--> I am using 90nm faraday standard  cells in umc 90nm technology. The same are imported in virtuoso library manager as symbols and been able to get a schematic view of my design.

--> For the same design I have layout with standard cells, verified geometry and connectivity. No errors and warnings seen. Using the default streamout.map file of umc, I have successfully obtained gds file of the design.

--> When I import the gds file into virtuoso 6.1.5, the Faraday standard cells donot show up. Following is the log file shown.

  ********************************************************************************
Product   : Virtuoso(R) XStream In
Program   : @(#)$CDS: strmin version 6.1.5 12/12/2012 15:27 (sjfnl003) $
          : sub-version  IC6.1.5.500.15
Started at: 21-May-2014  15:20:06
User Name : jagadishdn
Host Name : localhost.localdomain
Directory : /home/jagadishdn/umc90
CADENCE Design Systems, Inc.
********************************************************************************
Info: Cellview Rev Num:99,  Tech Rev Num:59

INFO (XSTRM-289): The automatic layer mapping is done by StreamIn. This is because either the layer mapping is not provided or the XST_AUTO_LM value is used with the -layerMap option.

Summary of Options:
        library                         t2
        strmFile                        cdac33.gds
        logFile                         strmIn.log
        topCell                         cdac33
        view                            layout
        case                            Preserve
        propSeparator                   ,
        techRefs                      faraday

WARNING (XSTRM-267): The referenced cell "OR3X1" was not found. The OpenAccess design data was created for this cell without any reference. Ensure that the referenced cell exists and library is defined in the cds.lib file.
WARNING (XSTRM-267): The referenced cell "OR2XLP" was not found. The OpenAccess design data was created for this cell without any reference. Ensure that the referenced cell exists and library is defined in the cds.lib file.
WARNING (XSTRM-267): The referenced cell "OR3B2XLP" was not found. The OpenAccess design data was created for this cell without any reference. Ensure that the referenced cell exists and library is defined in the cds.lib file.
WARNING (XSTRM-267): The referenced cell "NR3XLP" was not found. The OpenAccess design data was created for this cell without any reference. Ensure that the referenced cell exists and library is defined in the cds.lib file.
WARNING (XSTRM-267): The referenced cell "OR2B1XLP" was not found. The OpenAccess design data was created for this cell without any reference. Ensure that the referenced cell exists and library is defined in the cds.lib file.
WARNING (XSTRM-267): The referenced cell "QDFCRBX1" was not found. The OpenAccess design data was created for this cell without any reference. Ensure that the referenced cell exists and library is defined in the cds.lib file.
WARNING (XSTRM-267): The referenced cell "NR2XLP" was not found. The OpenAccess design data was created for this cell without any reference. Ensure that the referenced cell exists and library is defined in the cds.lib file.
WARNING (XSTRM-267): The referenced cell "QDFFX1" was not found. The OpenAccess design data was created for this cell without any reference. Ensure that the referenced cell exists and library is defined in the cds.lib file.
WARNING (XSTRM-267): The referenced cell "OA12X1" was not found. The OpenAccess design data was created for this cell without any reference. Ensure that the referenced cell exists and library is defined in the cds.lib file.
WARNING (XSTRM-267): The referenced cell "NR2X1" was not found. The OpenAccess design data was created for this cell without any reference. Ensure that the referenced cell exists and library is defined in the cds.lib file.
WARNING (XSTRM-267): The referenced cell "DFCRBX1" was not found. The OpenAccess design data was created for this cell without any reference. Ensure that the referenced cell exists and library is defined in the cds.lib file.
INFO (XSTRM-220): 1. Translating STRUCTURE cdac33_VIA1 as cellView t2/cdac33_VIA1/layout
INFO (XSTRM-61): Creating a new layer L7 in the technology file.
INFO (XSTRM-62): Creating a new layer:purpose pair L7:drawing in the technology file.
INFO (XSTRM-61): Creating a new layer L28 in the technology file.
INFO (XSTRM-62): Creating a new layer:purpose pair L28:drawing in the technology file.
INFO (XSTRM-61): Creating a new layer L19 in the technology file.
INFO (XSTRM-62): Creating a new layer:purpose pair L19:drawing in the technology file.
INFO (XSTRM-220): 2. Translating STRUCTURE cdac33_VIA0 as cellView t2/cdac33_VIA0/layout
INFO (XSTRM-220): 3. Translating STRUCTURE VIA34_stack_CROSS as cellView t2/VIA34_stack_CROSS/layout
INFO (XSTRM-61): Creating a new layer L49 in the technology file.
INFO (XSTRM-62): Creating a new layer:purpose pair L49:drawing in the technology file.
INFO (XSTRM-61): Creating a new layer L70 in the technology file.
INFO (XSTRM-62): Creating a new layer:purpose pair L70:drawing in the technology file.
INFO (XSTRM-61): Creating a new layer L61 in the technology file.

--> Please suggest me the way out.

 

Thanks

Jagadish D N

 

  • Cancel
Parents
  • Kari
    Kari over 11 years ago

    Do you have the layout views of the std cells in Virtuoso? That is what the EDI GDS is trying to reference.

    So you can get the layout views into Virtuoso and try again, OR you can create a merged GDS from EDI, which will pull in the std cell GDS and then you can stream the complete design into Virtuoso instead of referencing already-existing views. Check out the -merge option of the streamOut command. 

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Kari
    Kari over 11 years ago

    Do you have the layout views of the std cells in Virtuoso? That is what the EDI GDS is trying to reference.

    So you can get the layout views into Virtuoso and try again, OR you can create a merged GDS from EDI, which will pull in the std cell GDS and then you can stream the complete design into Virtuoso instead of referencing already-existing views. Check out the -merge option of the streamOut command. 

    • 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