• 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. Functional Verification
  3. Not able to Invoke XRUN

Stats

  • Locked Locked
  • Replies 12
  • Subscribers 65
  • Views 14239
  • 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

Not able to Invoke XRUN

adtdeep
adtdeep over 1 year ago

Hi,

I had installed XCELIUM in my personal computer, license manager is installed in my college server. i have set all the paths and env variables for using this tool but when i invoke xrun command its showing "xrun: command not found."

Regards,

Deepak B

  • Cancel
Parents
  • StephenH
    StephenH over 1 year ago

    Deepak, perhaps you could share the settings you used for your PATH variable? It's hard to debug without any details.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • jgonzo
    jgonzo over 1 year ago in reply to StephenH

    Hello Stephen,

    I have a same problem with XCELIUM with IC_6.1.8.270_RHELx86 on AMD machine.

    in .bashrc linked XCELIUM with this command

    source /eda/cadence/2021-22/scripts/XCELIUM2209.sh

    which is doing:

    export CDS_XCELIUM=/eda/cadence/2021-22/RHELx86/XCELIUM2209
    export PATH="${PATH}:${CDS_XCELIUM}/bin:${CDS_XCELIUM}/tools/bin:${CDS_XCELIUM}/tools/cdsgcc/gcc/bin"
    alias help_cds_xcelium='$CDS_XCELIUM/tools/cdnshelp/bin/cdnshelp &'
    # xrun, simvision, xmvhdl, xmvlog, xmsc, xmelab, xmsim, xmls, xmhelp, xfr, xmxlimport

    when I try in folder /eda/cadence/2021-22/RHELx86/XCELIUM2209/tools.lnx86/bin
    checkSysConf XCELIUM2209

    I get

    This operating system version '8.0WS' is not supported

    If you believe you are running a supported OS then check that
    the OS version directory exists in the data directory:
    /eda/cadence/2022-23/RHELx86/IC_6.1.8.270/share/patchData/Linux/x86_64

    I have ksh installed together with all recommended patches (https://support.cadence.com/apex/ArticleAttachmentPortal?pageName=ArticleContent&id=a1Od000000051rO&pageURL=COSComputingPlatforms&oMenu=DocumentViewer%20Computing%20Platforms)

    for ssl I have:

    yum list installed | grep ssl
    apr-util-openssl.x86_64                            1.6.1-6.el8                                                 @rhel-8-for-x86_64-appstream-rpms
    compat-openssl10.x86_64                            1:1.0.2o-4.el8_6                                            @rhel-8-for-x86_64-appstream-rpms
    openssl.x86_64                                     1:1.1.1k-7.el8_6                                            @rhel-8-for-x86_64-baseos-rpms   
    openssl-devel.x86_64                               1:1.1.1k-7.el8_6                                            @rhel-8-for-x86_64-baseos-rpms   
    openssl-libs.x86_64                                1:1.1.1k-7.el8_6                                            @rhel-8-for-x86_64-baseos-rpms   
    openssl-pkcs11.x86_64                              0.4.10-2.el8                                                @anaconda                        
    xmlsec1-openssl.x86_64 

    Could it be connected with the fact it is a AMD? With intel processors with same RHEL8 installation XCELIUM is running.

    Thank you

    Best regards

    Josef

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • StephenH
    StephenH over 1 year ago in reply to jgonzo

    Josef, you've made the same mistake as Deepak. You have invoked the IC 6.1.8 version of checkSysConf, which is very old and isn't aware of RHEL8 (notice the screen output tells you it's picking the definition file from /eda/cadence/2022-23/RHELx86/IC_6.1.8.270/share/patchData/Linux/x86_64.

    This is most likely to be caused by you adding Xcelium to the end of your PATH instead of the start - this means that the binaries in the Xcelium install will only be picked up if there's no same-named binary elsewhere int he PATH. I would usually add new programs to the start of the PATH to ensure they are picked up in preference to any other tools.

    If you run the Xcelium copy of checkSysConf, it should be happy with that OS version.

    As regards the choice of Intel or AMD CPU, Xcelium should not be sensitive to this difference, both vendors should be fine.

    • Cancel
    • Vote Up +1 Vote Down
    • Cancel
  • jgonzo
    jgonzo over 1 year ago in reply to StephenH

    Thank you, I wasnt aware of that. I was missing motif package which is not written in https://support.cadence.com/apex/ArticleAttachmentPortal?pageName=ArticleContent&id=a1Od000000051rO&pageURL=COSComputingPlatforms&oMenu=DocumentViewer%20Computing%20Platforms

    so now checkSysConf PASS

    Should I paste here the full results?

    but I am still getting

    xrun -version
    bash: /eda/cadence/2021-22/RHELx86/XCELIUM2209/tools/bin/xrun: No such file or directory

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • jgonzo
    jgonzo over 1 year ago in reply to StephenH

    Thank you, I wasnt aware of that. I was missing motif package which is not written in https://support.cadence.com/apex/ArticleAttachmentPortal?pageName=ArticleContent&id=a1Od000000051rO&pageURL=COSComputingPlatforms&oMenu=DocumentViewer%20Computing%20Platforms

    so now checkSysConf PASS

    Should I paste here the full results?

    but I am still getting

    xrun -version
    bash: /eda/cadence/2021-22/RHELx86/XCELIUM2209/tools/bin/xrun: No such file or directory

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
  • StephenH
    StephenH over 1 year ago in reply to jgonzo

    I don't know what would cause that error. The /eda/cadence/2021-22/RHELx86/XCELIUM2209/tools/bin/xrun file is a symbolic link to a compiled ELF binary, if you do "ls -l /eda/cadence/2021-22/RHELx86/XCELIUM2209/tools/bin/xrun" it should point at "../inca/bin/xrun".

    Make sure that /eda/cadence/2021-22/RHELx86/XCELIUM2209/tools/inca/bin/xrun exists and is executable.

    • Cancel
    • Vote Up +1 Vote Down
    • Cancel
  • jgonzo
    jgonzo over 1 year ago in reply to StephenH

    Yes, files exist, I should have rights and files are executable.

    I am getting:

    lrwxrwxrwx. 1 user user 16 Feb  1  2023 /eda/cadence/2021-22/RHELx86/XCELIUM2209/tools/bin/xrun -> ../inca/bin/xrun

    if I check folder /eda/cadence/2021-22/RHELx86/XCELIUM2209/tools/inca/bin

    I get:

    -rwxrwx---. 1 user user 20731556 Jan 23  2023 xrun

    • 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