• 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 41353
  • 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 15 years ago

     Hello,

     I think it is better not to duplicate your post.

    Anyway here after is my reponse to your first post:

    I assume you have started Encounter with a LEF techno.

    If this is the case then :

    1.create a new library which should be 'reference' the technology library

    2.import the LEF with technology info on this new library, it should create all missing vias and layers

    3.save your design from Encounter in this new library

    Please keep me posted,

    Alex

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • eklikeroomys
    eklikeroomys over 14 years ago
    Halo Alex,
    I have a problem similar to the one you responded to here,
    The steps you give here are a bit unclear, could you please elaborate?

    I have saved my SoC Encounter oa design, but when I import it into Virtuoso Layout XL, it references its abstract cellviews from another library that it has created, and uses some techfile that Encounter has generated. This techfile is not correct, it uses incorrect layers, doesnt show vias or nets.

    I then deleted the techfile and attached the correct one using CIW ---> Tools ---> Technology File Manager. Next, I used Library Manager ---> Edit ---> Rename to ensure that instances are referenced from the correct library. Now, when I open the layout view of the design, the instances are correct, but the routing layers are all wrong, and I cant see any vias. Can you please help me I am quite new to Cadence and EDA.
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Alex Soyer
    Alex Soyer over 14 years ago

    Hello,

    Could you please tell me if you have started your design with LEF or with OA tech library?

    • If you have started with LEF then in that case you would have to make sure your technology library is compatible with your LEF file (same layer name, etc...).
      • Compatibility OK
        1. create a new library which refenrence your base tech library then import this LEF into this new library you will probably see couple of warnings reporting conflicts in term of rules definition but they copuld be ignored.
        2. Save the OA view from Encounter in this new library
      • Compatibility NOT OK
        1. Resolve the compatibility issue by modifying the techlef very carefully according to the techfile
        2. then follow the previous step when "Compatibility OK".
    • If you have started from OA tech in that case you just need to into OA in an existing library.

    Thanks,

    Alex

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • eklikeroomys
    eklikeroomys over 14 years ago
    Halo, I generated a LEF file using Cadence Abstract Generator, then used this LEF file in Encounter. How do I reference the tech library into a new library? And can I just copy and paste (import) the LEF into the new library?
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • eklikeroomys
    eklikeroomys over 14 years ago
    Halo Alex, I managed to reference the tech library into a new library that I have created, but Im not sure how to import a LEF file into the library? As far as I know the LEF is only used for P&R purposes?
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • eklikeroomys
    eklikeroomys over 14 years ago
    Halo Alex,

    Please ignore the two earlier posts, as I have managed to figure it out. I have created a new library, referenced the technology library and imported the LEF file, but when I try to save my design into the new library, I get the following error:  Unable to convert FE layer name MET1 to OA. I get this error for all metal layers. I cant see that anything is wrong with my technology or LEF files?
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Alex Soyer
    Alex Soyer over 14 years ago

    Based on te message from Encounter it seems you have a disconnect between the OA technology and the LEF technology like layer names as mentionend in my previous email.

    Coudl you please confirm that you have implemented your design using a LEF?

    You need to dump out the technology from the OA tech lib: CIW -> Tools -> Technology File Manager -> Dump and choose the tech lib then specify the file name.

    Edit the dumped ASCII file and compare the layer name which have to be the same.

    You need to modify your LEF layer name to match tech ASCII file.

    Then you could import the LEF on the referenced library and then save to OA form Encounter.

    Thanks,
    Alex

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • eklikeroomys
    eklikeroomys over 14 years ago
    Good Morning Alex,

    Yes, I am implementing my design in Encounter using a LEF. I generated this LEF using Cadence Abstract Generator. How can I make Cadence Abstract Generator include all layers into the LEF file? I have found that it only includes some of the layers. This causes Encounter to generate technology file with incorrect layer numbers, which causes the layout to have incorrect routing layers in Virtuoso.
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Alex Soyer
    Alex Soyer over 14 years ago

    Good Morning!!

    Abstract Generator generates a LEF with the technology information according to what you have in your Virtuoso techfile.

    If you LEF is wrong it means your techfile is probably not correct as well.

    I would advise you to export a LEF ouyt of your techfile with only the technology information using CIW ->  File -> Export -> LEF in the form specify the library and click 'output technology information only' then you will get a technology lef that could be used in Encounter.

    Please remove the technology section of the LEF exported out of Abstract Generator and load both LEF (tech and macro ones) into Encounter then re-run your flow and try agian to save to OA.

    You could as well directly start with OA technology library with Encounter instead of using LEF.

    In Design Import form click on OA

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • eklikeroomys
    eklikeroomys over 14 years ago
    This makes a lot of sense, thank you!
    • 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