Stats

Locked Locked
Replies 2
Subscribers 126
Views 4148
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 start XRUN (Error: No such file or directory)

MT202407295352 11 months ago

Hello,

I have the problem that I cannot start XRUN. I am doing the following steps to start the tool:

source cadence_license_server

source XCELIUM_23.03.007_RHELx86.sh

xrun

After these steps I get the following error:

bash: /eda/cadence/2023-24/RHELx86/XCELIUM_23.03.007/tools/bin/xrun: No such file or directory

I have checked all the required dependencies for the Cadence tools, but XRUN still does not work.

This is the output from running checkSysConf XCELIUM2303:

=======================================================================
[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.50 ====================

Date information gathered: Thu Sep 26 09:28:05 CEST 2024
-------------------------------------------------------
Host Name ..............: ___
Hostid .................: ___
Operating System .......: Linux / x86_64
OS Version .............: Red Hat Enterprise Linux release 8.10 (Ootpa)
Kernel Version .........: 4.18.0-553.22.1.el8_10.x86_64
Hardware Type ..........: x86_64
Memory .................: 63795 Megabyte
CPU model ..............: Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz
No. of CPUs ............: 12
Total Swap Space........: 6140 Megabyte
X Server ...............:
Patch Data file ........: /eda/cadence/2023-24/RHELx86/XCELIUM_23.03.007/share/patchData/Linux/x86_64/redhat/8.0WS/XCELIUM2303

****************   Now verifying configuration     ****************

Validating Kernel requirements...
            Minimum             Installed                   Status    Info
            --------------      -------------------------- ------    --------------------
            4.18.0-147          4.18.0-553.22.1.el8_10.x86_64PASS

Validating MEMORY requirements MegaByte ...
            Minimum   Installed Status Info
            -------   --------- ------ --------------------
            4096MB    63795MB   PASS

Validating SWAP requirements in MegaByte ...
            Minimum   Installed Status Info
            -------   --------- ------ --------------------
            0MB       6140MB    ----    None specified

Validating OS version requirement...
            Minimum     Installed   Status    Info
            ---------- ---------- ------    ----------------------------
            8.1         8.10        PASS

Validating DISPLAY requirements...
          Minimum           Installed                   Status Info
          ----------------- ---------------------       ------ ----
          --- planes        --- planes                  ---     None specified


Validating PACKAGE requirements.....17 to check
#   PACKAGE                Release    Build          Installed               Arch        Status Info
-- -------                -------    -----          ----------              ----        ------ --------------------
1   glibc                  2.28       72             2.28-251.el8_10.5       x86_64      PASS
-> 'GlibC'
2   elfutils-libelf        0.176      5              0.190-2.el8             x86_64      PASS
-> 'Libelf Library'
3   ksh                    20120801   26             20120801-254.el8        x86_64      PASS
-> 'ksh'
4   redhat-lsb-core        4.1        47             4.1-47.el8              x86_64      PASS
-> 'lsb'
5   mesa-libGL             19.1.4     3              23.1.4-3.el8_10         x86_64      PASS
-> 'Mesa libGL'
6   mesa-libGLU            9.0.0      15             9.0.0-15.el8            x86_64      PASS
-> 'Mesa libGLU'
7   motif                  2.3.4      16             2.3.4-20.el8            x86_64      PASS
-> 'Motif 2.3.4'
8   libXp                  1.0.3      3              1.0.3-3.el8             x86_64      PASS
-> 'libXp'
9   libpng                 1.6.34     5              1.6.34-5.el8            x86_64      PASS
-> 'libpng 1.6'
10 libpng12               1.2.57     5              1.2.57-5.el8            x86_64      PASS
-> 'libpng 1.2'
11 libjpeg-turbo          1.5.3      10             1.5.3-10.el8            x86_64      PASS
-> 'libjpeg'
12 expat                  2.2.5      3              2.2.5-15.el8_10         x86_64      PASS
-> 'expat XML parser'
13 glibc-devel            2.28       72             2.28-251.el8_10.5       x86_64      PASS
-> 'GlibC-devel'
14 libnsl                 2.28       72             2.28-251.el8_10.5       x86_64      PASS
-> 'libnsl'
15 readline               7.0        10             7.0-10.el8              x86_64      PASS
-> 'readline'
16 ncurses-compat-libs    6.1        7.20180224     6.1-7.20180224.el8      x86_64      PASS
-> 'ncurses'
17 compat-openssl10       1.0.2o     3              1.0.2o-4.el8_6          x86_64      PASS
-> 'OpenSSL 1.0.2o'

Normal exit. This workstation (___) status is: PASS
Host ___ has a Cadence supported Linux configuration.

Exiting checkSysConf ... Good-bye

I know that a similar post exists (community.cadence.com/.../not-able-to-invoke-xrun), but all suggested solutions do not solve my problem.

Regards,

Max

Alonso Schmidt 11 months ago

Hi Max,

The solution presented in the following article may solve this:

Running xrun/xrun -64bit, SimVision, and Specman commands gives "Command not found" and "No such file or directory" errors on RHEL 8

"To resolve this, you need to ensure that the Xcelium 64-bit binary path comes first in the search path. For example:

%setenv PATH <xcelium_install_dir>/tools/bin/64bit:<xcelium_install_dir>/tools/bin:$PATH"

Can you please try it and let me know if it helps?

Regards,

Alonso
Cancel
Vote Up 0 Vote Down

Cancel
MT202407295352 11 months ago in reply to Alonso Schmidt

Hi Alonso,

Thanks for the quick reply. The hint to run the 64 bit binary helps a lot. I am modifying the XCELIUM script as follows:

export PATH="${PATH}:${CDS_XCELIUM}/bin/64bit:${CDS_XCELIUM}/tools/bin/64bit:${CDS_XCELIUM}/tools/cdsgcc/gcc/bin"

and everything works fine.

Regards,

Max
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.