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