• 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. Encounter does not stream out all cells into a GDS

Stats

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

Encounter does not stream out all cells into a GDS

archive
archive over 17 years ago

Hello all, I used First Encounter v4.1 for place and route, and using following command, a GDS format of the design was made: streamOut ~/WiMax576_0.7.gds -mapFile ~/gds2_cmos90.map -libName WiMax576 -structureName decoder576 -stripes 1 -units 1000 -mode ALL now, in Cadence Virtuoso, all standard cells are appearing like red boxes, and Calibre-DRC stops reading the GDS by following error: ERROR: Cell FILLERCELL32 is referenced but not defined. *** Calibre finished with Exit Code: 4 *** Can someone help me please to resolve the error? Thanks, Ali


Originally posted in cdnusers.org by Naderi
  • Cancel
  • archive
    archive over 17 years ago

    I believe you need to use streamOut's "-merge" option and supply it with the gds file(s) that describe the contents of the standard cells.


    Originally posted in cdnusers.org by BobD
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 17 years ago

    Hi Bob,

    Those GDS files may not be available. The standard cells are introduced to the Encounter by LEF and lib files.

    Do you think i need to import the LEF and lib files into the cadence too?

    if yes, isn't it something redundant that occupies a lot disk space?, because their library is already defined and available in the cds.lib.

    Ali


    Originally posted in cdnusers.org by Naderi
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 17 years ago

    Hi Ali,

    If the GDS files aren't available, then within Virtuoso the contents of the standard cells should be defined within a Virtuoso library in you cds.lib path. It sounds like that is the situation you have now, but you're seeing "red boxes". Are they empty? Or if you hit "shift-f" in Virtuoso do their contents become visible?

    For Calibre-DRC, if the gds of the standard cells aren't available, you might want to try streamOut's "-outputMacros" option that will stream out the contents of the standard cells as defined in the LEF abstracts rather than what is within the gds.

    -Bob


    Originally posted in cdnusers.org by BobD
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 17 years ago

    Thanks Bob,

    hitting "shift-f" showed markers with crossed diameters. therefore, the cell were not created in the layout.
    I recreated the GDS by using -outputMacros, then it solved the error and now GDS includes the standard cells when imported to the cadence.
    If you don't mind, i would like to ask another question.
    What is difference between merging the GDS files and using -outputMacros when streaming out the design from Encounter?
    Also, what shortcut key does the reverse of "shift-f"?

    Thanks again,
    Ali


    Originally posted in cdnusers.org by Naderi
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 17 years ago

    -outputMacros uses the LEF abstract geometries for the standard cells which usually includes only pins and blockages to reduce the size of the data set as compared to gds which contains full detail of the standard cells. The risk you run when running geometric verification with LEF abstracts instead of gds is that the LEF abstract doesn't capture some detailed nuance that the gds contains and a violation can sneak through. The purpose of creating abstracts is to simplify the implementation tool's job so it doesn't have to consider every little geometry.

    In Virtuoso, I believe the reverse of "shift-f" is "ctrl-f".

    Hope this helps,
    Bob


    Originally posted in cdnusers.org by BobD
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 17 years ago

    Ali,

    I would not recommend running physical verification (DRC/LVS/etc.) on a gds that uses the LEF data instead of GDS data. You are likely to get a lot of violations that you would not see with the full layout. The whole purpose of streaming in to Virtuoso is to pick up the cell layouts. If you don't see them in the Library Manager of Virtuoso, that's the problem. If you do see them but they are not getting included in your design when you stream in the FE gds, then it's likely a problem with the stream in setup. I'm not sure what your design flow is, but hopefully this helps.

    - Kari


    Originally posted in cdnusers.org by Kari
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 17 years ago

    Hi Kari,

    I am running Encounter using LEF and lib files of cmos90nm technology. The library of cmos90nm is defined and available in the library manager of Virtuoso (layout/symbole/abstract/...). When i finished the place&route, i exported the design into a GDS file. When the GDS file was imported in to the Cadence, PIPO.log showed some warrning as follow:

    CellView Rectangles Polygons Paths Ellipses Labels Instances Arrays Dots
    ******************************************************************
    decoder576/layout 1642 0 2389153 0 2 3171777 0 0
    (BFLVTX2/layout) -- (referenced, but not defined, no data created).
    (CTBUFLVTX6_0/layout) -- (referenced, but not defined, no data created).
    (CTBUFLVTX12_0/layout) -- (referenced, but not defined, no data created).
    .
    .

    so, Bob told that the GDS of standard-cell library should be merged into my design when streaming out the design from Encounter. But i am not given such GDS files. mayby CMC ot STM doesn't support it.

    Is there any method to generat the required GDS files?
    Or do I have any mistake in using tools?

    Thanks,
    Ali


    Originally posted in cdnusers.org by Naderi
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 17 years ago

    Ali,

    How do you stream in to Virtuoso?

    If you use the GUI, then make sure you click on the Options, and turn on Retain Reference Library (No Merge). I know it sounds counter-intuitive, but give it a shot.

    If you use a set of keys and the command line (pipo strmin si_keys), then make sure refLib in si_keys is set to t.

    Let us know how it works - there is another thing we can try if it doesn't.

    - Kari


    Originally posted in cdnusers.org by Kari
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • archive
    archive over 17 years ago

    Kari,

    Perfect, I think it worked by turning "Retain Reference Lib" on. No other warrning.
    Now, I see the red boxes in the layout, which include the layout of std-cells (using "shift-f").

    Thank you very much indeed,
    Ali


    Originally posted in cdnusers.org by Naderi
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • akari
    akari over 15 years ago
    Dear Kari I already turn on the Retain Reference Library (No Merge) option. But I still can't found some layer, for example the layer for power ring, etc. Can you give me some advice? PS: on the stream out map file, all the metal layer already determined.
    • 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