Stats

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

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

  • eklikeroomys
    Halo Alex, I followed your advice and I successfully placed and routed a design. I have a new problem, when I try to save the design into the library, it gives the following error: 'M2_M1' is defined as a fixed via in design and parameterized via (oaStdViaDef) in the OpenAccess technology database. One of the via definitions must be changed. Using the OpenAccess information as the only source of technology removes the need to manually keep the two definitions in sync. Where can I fix this error?
  • eklikeroomys
    Alex, please ignore my previous post, I have decided to use the OA database in Encounter to place and route my design. This is nice, since I do not need to specify any LEF files. I complete the design up to the point where it needs to be routed, when I start the router it requests a LEF file? Must I now specify a LEF file for the router, or should I configure the router in another way, or is there another routing tool that I should use? (By the way, Im using nanoRoute)
  • Alex Soyer

    It seems you have in your techfile a via which in std_via section and in custom_via section of the tehcfhfile and which has teh same name which is incorrect they shoould have a different name, you need to correct your techfile.

    Thanks,

    Alex

  • Alex Soyer

    Which version of Encounter do you use ?

    Thanks,

    Alex

  • eklikeroomys
    Good Morning Alex, When I click on help--->About Encounter, it says SoC Encounter RTL to GDSII System Version 8.1. Is this correct? Thank you, Chris
  • eklikeroomys
    Good Morning Alex,When I click on help--->About Encounter, it says SoC Encounter RTL to GDSII System Version 8.1 Is this correct? Thank you,Chris
  • Alex Soyer

    Hello,

     Could you please try to run thss command in encounter before loading you design:

    setOaxMode -nativeLef false

    Thanks,

    Alex

  • eklikeroomys
    The command works, thank you! The design is routing!
  • eklikeroomys
    Halo Alex, The design routed successfully! Now, when I save the design as OA, Encounter gives the following error: *ERROR: (SOCOAX-683): Unable to find oaModTerm q. Can not create Connection Data for this oaModTerm. However, the saving process does seem to complete, and when I open the design in Virtuoso, it seems to be fine. Do you see any reason for concern? Thanks, Chris
  • Alex Soyer

    The message is related to saving the logical hierarchy into the layout view. Because when you save in OA form Encounter you store both physical and logical information in same view.

    I will check and get back to you but your physical view is certainly fine.

    Thanks,

    Alex

     

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.