Not able to Invoke XRUN

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

Hi Stephen,

The below is the env and path variable i have set in cshrc file and sourced it:

setenv LM_LICENSE_FILE 5280@internal_ip

setenv CDS_LIC_FILE 5280@internal_ip

setenv XCELIUMHOME /home/install/XCELIUM2209

set path = ( $XCELIUMHOME/tools.lnx86/dfII/bin $XCELIUMHOME/share/bin $XCELIUMHOME/bin $XCELIUMHOME/tools/bin $XCELIUMHOME/tools/dfII/bin $XCELIUMHOME/tools.lnx86/bin $XCELIUMHOME/tools.lnx86/dfII/bin $path)

Regards,

Deepak B

Normally I would only add $XCELIUM_HOME/tools.lnx86/bin to the path or PATH variable, the rest of those entires you quoted should not be required.

It's possible that your personal machine doesn't have a compatible OS, or is missing some key components of the OS. For example I often see that users don't have "ksh" installed, and there are some commands within Xcelium that require ksh.

You can try running the command "checkSysConf XCELIUM2209" which should report a bunch on checks to see if your OS has the required components installed. Check and fix any "FAIL" messages. Eventually you need to see a message similar to this before Xcelium will work:

Normal exit. This workstation (foo) status is: PASS

Host foo has a Cadence supported Linux configuration.

Hi,

i got the below response when i ran the command,

[deepak.mee23@server install]$ checkSysConf XCELIUM2209

=======================================================================

[Copyright 2002-2022] Cadence Design Systems, Inc. All rights reserved.

This  program and online  documentation  may not be copied, modified,

re-published, uploaded,  executed, or  distributed in any way, in any

medium, whether in whole or in part, without prior written permission

from Cadence Design Systems, Inc.

=======================================================================

============== checkSysConf:  Version 3.51 ====================

Configuration checks failed on this workstation (server), status is: FAIL

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:

/home/install/IC618/share/patchData/Linux/x86_64

Exiting checkSysConf ... Good-bye

iam currently using RHEL8 and the college lab system which was already working also is throwing the same response but iam able to invoke the xrun command there.

Regards,

Deepak B

It looks like you're running checkSysConf from a different tool install path (/home/install/IC618/).

Xcelium version 22.09 does support RHEL 8, and thus the right checkSysConf should accept that as a valid platform. The IC618 tool doesn't appear to support RHEL8 (according to the info on https://downloads.cadence.com/ESDWeb/Welcome.eo) so that might explain your results.

Whilst debugging issues I would recommend that you run checkSysConf from the Xcelium install path.

Hi Stephen,

Right now i checked by running checkSysConf from the Xcelium install path and iam getting the status as "PASS" and a message "Host localhost.localdomain has a cadence supported linux configuration"
but still when i run xrun command iam getting command not found.

Regards,

Deepak B

Hi,

Thanks after installing libssl it worked.

Regards,

Deepak B

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

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.

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