• 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. Custom IC Design
  3. LVS Problem running Fedora 19

Stats

  • Locked Locked
  • Replies 14
  • Subscribers 126
  • Views 16661
  • 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

LVS Problem running Fedora 19

ziikzak
ziikzak over 11 years ago

It seems that all the installation and configuration process using 
Installscape are finished without problem, since my schematic simulation and DRC run very well, but I encounter an error message like the following when I try to work on LVS.

 

virtuoso:   ERROR: The command /tools/cadence/IC610/share/oa/bin/ 
sysname returned an error status: 
                            unknown 
virtuoso:    INFO: Note that OpenAccess (OA) requires running the 
Configure phase. 
virtuoso:          See the "OpenAccess Installation and Configuration 
Guide" before 
virtuoso:          you complete the configuration step. This manual is 
included with 
virtuoso:          the Cadence product documentation. 

Thanks in advance you guys 

  • Cancel
  • Quek
    Quek over 11 years ago

    Hi ziikzak

    Would you please confirm the following?
    a. Are you able to start Virtuoso without any errors/warnings in CDS.log file?
    b. What is the version of Virtuoso? (virtuoso -W)
    c. Are you running Diva, Assura, Calibre or ... for DRC/LVS?
    d. Are there any warnings about OA installation when running DRC?

    It looks like a re-installation of IC61 package might be the easiest solution.

    Best regards
    Quek

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 11 years ago

    Also, do you have $OA_HOME set? Type "env | grep OA" in your terminal window. What does "ls -l <ICinstDir>/share/oa" show?

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • ziikzak
    ziikzak over 11 years ago

    Hi Querk,  

    a. I did not see any error message in CDS.log

    b. my version is IC 6.1.5

    c. I run Assura for DRC/LVS

    d. No, running DRC is always easy  

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Quek
    Quek over 11 years ago

    Hi ziikzak

    Thanks for the info. As suggested by Andrew, would you also please check the following?

    terminal>env | grep OA_HOME

    Is OA_HOME variable set? If it is set, please unset it and retry LVS.

    Best regards
    Quek

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • ziikzak
    ziikzak over 11 years ago

     Yes, I did, and my terminal window did not show any thing. 

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Quek
    Quek over 11 years ago

    Hi ziikzak

    Would you please try the following?

    a. Open Assura LVS form
    b. Press the "View rsf" file button and save the file as "lvs.rsf"
    c. Execute LVS in a terminal window

    terminal>assura lvs.rsf

    Do you still see the same OA error?

    Best regards
    Quek

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • ziikzak
    ziikzak over 11 years ago

    Hi, 

    I mean when i run env|OA_HOME, i did not see any respone. 

     ziikzak

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Quek
    Quek over 11 years ago
    Hi ziikzak

    Thanks for the clarification. It means that OA_HOME has not been set. Would you please try "assura lvs.rsf"?

    Best regards
    Quek
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 11 years ago

    Note that Fedora 19 is absolutely not a supported OS, and my guess is that you may be hitting an issue we saw where OA cannot identify the platform properly. First try using absolutely the latest IC and ASSURA versions (latest hotfixes of both, for the IC616 version) and if it still doesn't work you'll probably need to move to a supported OS (eg RHEL 6).

    Regards,

    Andrew 

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • ziikzak
    ziikzak over 11 years ago
    yes, I tried.
    here is the error message popup

    Summary Report: inv.sum
     RSF           : inv.rsf
     Library Name  : Lib1
     Cell Name     : INVERTER
     View Name     : layout
     Rules File    : /home/huy/Documents/IBM_PDK/cmrf8sf/V1.8.0.0DM/Assura/LVS/extract41.rul
     Options       : -exec1 -LVS
     Work Directory: /home/huy/Documents/INDIVIDUAL/LVS/LVS
     Operating Mode: Legacy Mode is Off


    Starting dfIIToVdb...
    avlck:   ERROR: The command /apps/cadence/ASSURA615/share/oa/bin/sysname returned an error status:
                                unknown
    avlck:    INFO: Note that OpenAccess (OA) requires running the Configure phase.
    avlck:          See the &quot;OpenAccess Installation and Configuration Guide&quot; before
    avlck:          you complete the configuration step. This manual is included with
    avlck:          the Cadence product documentation.
    Virtuoso Framework License (111) was checked out successfully. Total checkout time was 1.14s.
    @(#)$CDS: dfIIToVdb_64 version av4.1:Production:dfII6.1.5-64b:IC6.1.5-64b.500.17 08/06/2013 19:10 (sjfql419) $
    sub-version 4.1_USR4, integ signature 2013-08-06-1301

    run on localhost.localdomain from /apps/cadence/ASSURA615/tools.lnx86/assura/bin/64bit/dfIIToVdb on Mon Feb 17 00:00:27 2014

    *WARNING* CellView &quot;Lib1/INVERTER/layout&quot; does not exist in /apps/cadence/ASSURA615/share/cdssetup/cds.lib.


    *****  dfIIToVdb terminated abnormally  *****

    *WARNING* Translation abnormally terminated!

    *WARNING* aveng exit with bad status
    *WARNING* Status 256
    *WARNING* Assura execution terminated


    *****  aveng fork terminated abnormally  *****
    • 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