• 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. How to open OpenAccess design in Virtuoso ??

Stats

  • Locked Locked
  • Replies 48
  • Subscribers 94
  • Views 41540
  • 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

How to open OpenAccess design in Virtuoso ??

AlhassanFattin
AlhassanFattin over 15 years ago

Dear All

i have a layout for a design made in Encounter Soc and i want to transfer it to Virtuoso using OpenAccess, can anyone help me to know after i save the design as OA in soc how to open it in Virtuoso, and what are the technology libraries that are needed to be added to the design or imported in virtuoso to make it see the design properly, as i have tried to open that design DIRECTLY in virtuoso (without adding any Technology files or anything) and the design open but nearly there is no metal layers or vias in the design !!! and there is a warning that Layer Purpose Pairs are not found !!!

can anyone help me in how to properly setup my virtuoso so as to open my OpenAccess design ??

Thanks in advance

  • Cancel
  • Alex Soyer
    Alex Soyer over 14 years ago

    Could you pelase confirm the rules are defined in your LEFDefaultRouteSpec constraint group ?

    EDI stands for Encounter Digital Implementation.

    Thanks,

    Alex

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • eklikeroomys
    eklikeroomys over 14 years ago
    Alex, I ran verify-->Geometry, with many error results, how do I fix this?
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • eklikeroomys
    eklikeroomys over 14 years ago
    I confirm that the minimum spacings for via and metal layers are defined in the LefDefaultRouteSpec constraint group.
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Alex Soyer
    Alex Soyer over 14 years ago

    You should check after Nanoroute which should report the problem but I suspect a problem in your techfile.

    Please check the warning when you start Encounter and when you Import/restore the design.

    Could you check if you have a .oalefxxxxx directory or file which contains the LEF whic is going to be used by Nanoroute?

    You could check as well the warning before Nanoroute and the violations reported by Nanoroute after the routing.

    Thanks,

    Alex

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • eklikeroomys
    eklikeroomys over 14 years ago
    Halo Alex, I have fixed the errors and the design is now correct with no errors. I need your help with one more thing, I want to use an OA netlist instead of a Verilog netlist for my design. I ran the setOaxMode command, but when I use an OA netlist instead of a Verilog netlist, I get the following errors: **ERROR: (SOCLF-116): Pitch of layer 'MET1' is 0. **ERROR: (SOCLF-3): Error found when processing LEF file. I dont know why this happens, since the library containing the OA netlist is attached to the correct reference library. (I am using an OA schematic as a netlist, is this correct?) Thank you, Chris
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Alex Soyer
    Alex Soyer over 14 years ago

    Chris,

    Please make sure in the OA reference library teh first library contains the technology information (the design lib if attached or reference to the baseTech library).

    In order to debug the problem you could look at the .oalefxxxx file generated in your working directory.

    Thanks,

    Alex

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • eklikeroomys
    eklikeroomys over 14 years ago
    Thank you Alex, may I ask where can I find the commands for Encounter, like the setOaxMode command? Are they all in the help files?
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Alex Soyer
    Alex Soyer over 14 years ago

    Chris,

     Yes it is, please look at the "Encounter Text Command Reference".

    Around page 180.

    Thanks,
    Alex

    • 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