• 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. Transfer Layout from Encounter SOC to Virtuoso PROBLEM ...

Stats

  • Locked Locked
  • Replies 4
  • Subscribers 92
  • Views 13680
  • 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

Transfer Layout from Encounter SOC to Virtuoso PROBLEM !!!

AlhassanFattin
AlhassanFattin over 15 years ago

Dear all
i have a problem, i have requested to fabricate a chip with mosis, and i had IBM 0.13 DM cmrf8sf Kit, and i designed my system using encounter SOC as a place and route tool, the problem is that i want to export to mosis the GDS file, BUT the file that i got from mosis was a mapping file for Cadence (Virtuoso) not for SOCe !!!!
so i tried many things to transfer my design from encounter to virtuoso but in vain !!!
i tried the following
1- i tried to save the layout as an OpenAccess from encounter and then reopen it directly from virtouso, the problem in that virtuoso dont see the layers properly and said that layer purpose pair is missing !!!! i really dont know how to add my technology files properly to make the virtuoso open my design properly !!

2- then i tried to export the design as a DEF file, but really i dont know how to open it from virtuoso as i triend just to CIW->File->Import-> DEFin and tried to fill in the wanted spaces, but i got the errors that the virtuoso cant find the V1_H and V1_V in the refrence library !!!

can anyone help in that ?? and if someone has any detailed way of how to transfer my design to virtuoso i would be really thankful.
Thanks in advance

  • Cancel
  • Alex Soyer
    Alex Soyer over 15 years ago

    Hi 

    Concerning point number 2: could you try to run oa2dfII on your library in order to make it updated to see all the shape on different layers ?

     Thanks,

    Alex

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Alex Soyer
    Alex Soyer over 15 years ago

     Hi,

    An other suggestion.

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

    Dear Alex

    Iam really thankful for your quick and really informative reply, the oa2dfII way really worked and the layers really appeared, thanks very much :)

    i now try to send the design to the FAB and iam waiting for it's reply, i will keep you informed

    but there is just a thing that i dont understand, when i now open the design in virtuoso, the layers that appear are the metal layers and the vias, and the design looks really nice, BUT when i export the design to GDS file and reimport it again in virtuso, the design seems corrupted again, for example layer M5 routing dissapeard !!!!

    can you tell anything about this problem ??

    thanks really again for your reply

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Alex Soyer
    Alex Soyer over 15 years ago

    Hello,

    Happy to heard this good news.

    Now that you have added new layers in term of display in your techfile you need as well to have your mapfile (OA2stream) to understand those layers.

    Did you use the same mapfile to export and import the GDS ?

    Did you imported the GDS into the same library ?

    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