• 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. Custom IC Design
  3. Layout: from Encounter to Virtuoso

Stats

  • Locked Locked
  • Replies 10
  • Subscribers 127
  • Views 17786
  • 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

Layout: from Encounter to Virtuoso

konx
konx over 16 years ago

Hi! 

I'm a new user of the forums :)

This is the problem I have at the moment: 

I have a complete design in Encounter of a block called Pixel, and I want
to export it to cadence virtuoso. Reading on internet and the help,
I've seen that I have to export a GDSII file (basically, I can produce
2 file: the outputStream called pixel_output_stream and the Map file
streamOut.map).

Now, I'm trying to import these file using File --> Import --> Stream
in the CIW window of cadence.

In the Stream File field I specify the path to pixel_output_stream,
while I use the map file in the Layer tab that I can find clicking on
option (here I can upload the map file).

Obviously I specify even the tech library (cmrf8sf, Arti2009DM and
others).

then, I click Translate.

the final result is not
correct; I have this error:

ERROR (58): Failed to create the new layer purpose pair 'DIEAREA:ALL'.
It will be skipped and all the shapes on this LPP will be dropped.

I have this error 163 times, exactly the number of the Stream layer
that I can see when I upload the streamOut.map file.

The final result (in Virtuoso) is a design with correct shape and with
all the cells (flip-flop, etc...), but with no routing between cells
(but I did it in Encounter) and without supply and ground rings
(again, I did it in Encounter).

I received an answer in other forum, where they point out that the Encounter streamOut file is (more or less) like this:

E.g. of stream out file:
---------------------------------------------------------------------------

-----------------------------------------------------------------------------------
METAL1          NET                           1            0
METAL1          SPNET                      2            0
METAL1          PIN                         3              0
METAL1          LEFPIN                     4            0
METAL1          FILL                        5                0
METAL1          VIA                          6               0
METAL1          VIAFILL                    7              0
METAL1          LEFOBS                    8              0
NAME            METAL1/NET              9               0
NAME            METAL1/SPNET        10             0
NAME            METAL1/PIN              11              0
NAME            METAL1/LEFPIN         12            0
VIA12           FILL                              13            0
VIA12           VIA                              14             0
VIA12           VIAFILL                       15              0
--------------------------------------------------------------------------------------------------------------------------------------------------------------

 

Instead, the Virtuoso streamIn file is:

 E.g. of stream in file:
---------------------------------------------------------------------------

-----------------------------------------------------------------------------------
#Cadence Layer(M*foundry*)  Layer Purpose  Encounter Stream layer
Stream Datatype
   viap1                                        drawing         1,2,3                                0
   met1                                        drawing         4,5,6,7,8,9,10                   0
   met1I                                       drawing          11                                   0
   met1T                                      drawing           12,13,14,15                     0
   viam1                                       drawing         16,17,18                          0
--------------------------------------------------------------------------------------------------------------------------------------------------------------

"As you can see, some layers from Encounter were merged so they lose
functionality in Virtuoso. "

Questions: 

The last file, is a file that is provided with the technology libraries,
is something that should be generated by Encounter or Virtuoso, or is
something that I have to generate by myself following some rules? (in this case, which rules?)

Moreover: if I have these 2 map files, what file I need to specify in
XStream? If you go to CIW --> File --> Import --> Stream and click on
Option and then select tha Layout tab, here you can specify a map
file. At the moment I'm uploading the streamOut.map generated by
Encounter. Do I have to specify the other one (supposing I'll be able
to find it out)?

Sorry if these are stupid questions, but for me these are all new
things :)

 Thanks in advance for help

 Francesco.

 

 

 

 

  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett over 15 years ago

     Albert,

    I don't know. I'd have to try it to find out, and quite honestly I don't have the bandwidth today to try this (it's not something I'm that familiar with, to be honest, as it's outside my usual field of expertise). So ask at the same time you file a service request.

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett over 15 years ago

     Albert,

    I don't know. I'd have to try it to find out, and quite honestly I don't have the bandwidth today to try this (it's not something I'm that familiar with, to be honest, as it's outside my usual field of expertise). So ask at the same time you file a service request.

    Regards,

    Andrew.

    • 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