• 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 Digital Implementation system tool - layout i...

Stats

  • Locked Locked
  • Replies 5
  • Subscribers 91
  • Views 1835
  • 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 Digital Implementation system tool - layout issue

hon cheong
hon cheong over 15 years ago

I have two questions regarding the encounter Digital Implementation system tool.

1. Using the digital implementation system tool, after doing floorplanning, place and route, the layout view for the standard cells are in abstract form. how can I view the layout view of those standard cells?
(I have include .lib and .lef files in the digital implementation system tool prior to synthesis).

2.If I want to import the layout to virtuoso from encounter digital implementation tool, I first save the synthesis result in DEF file format. In the DEF In dialog box, I am required to fill in "used Ref Library Names".
While I am using IBM process and found the .lef and .lib files in the "ARM_IBM_130nm8RF_4.0 " folder, I am unable to find any other DFII library that contains all the standard cells. Is that supposed to have one library that contains all the layout views of the standard cells?

Thank you.

Regards,
Hon Cheong

  • Cancel
Parents
  • Kari
    Kari over 15 years ago

     If you want the true layout of the std cells, you need either the GDS or an already-created DFII library. But if you want to see the same data you see in Encounter (abstracts vs full layouts) in Virtuoso, you can do that. You would read the std cell LEF into Virtuoso and you'll have abstract views (instead of layout views) in the library. Then you can read in the DEF and it should pick up the std cell abstracts. Consult the Virtuoso documentation for more information about reading in LEF and DEF.

    But you can't run a true DRC (and LVS) unless you have the full layout. So I'm assuming that if MOSIS is merging your final GDS, then they will also have to run signoff DRC and LVS and report back to you any errors they find. This loop can be time-consuming. Get the data as clean as you can in Encounter by running Verify Connectivity, Verify Geometry, and Verify Process Antenna.

    As for the parasitic extraction, is that for timing or something else? You can extract RCs in Encounter.

    Hope this helps,

    - Kari

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

     If you want the true layout of the std cells, you need either the GDS or an already-created DFII library. But if you want to see the same data you see in Encounter (abstracts vs full layouts) in Virtuoso, you can do that. You would read the std cell LEF into Virtuoso and you'll have abstract views (instead of layout views) in the library. Then you can read in the DEF and it should pick up the std cell abstracts. Consult the Virtuoso documentation for more information about reading in LEF and DEF.

    But you can't run a true DRC (and LVS) unless you have the full layout. So I'm assuming that if MOSIS is merging your final GDS, then they will also have to run signoff DRC and LVS and report back to you any errors they find. This loop can be time-consuming. Get the data as clean as you can in Encounter by running Verify Connectivity, Verify Geometry, and Verify Process Antenna.

    As for the parasitic extraction, is that for timing or something else? You can extract RCs in Encounter.

    Hope this helps,

    - Kari

    • 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