Stats

  • Locked Locked
  • Replies 3
  • Subscribers 64
  • Views 2432
  • 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

[AMS][xrun: Command not found]

IssacW

dear all,
 

A new warning regarding "Xcelium" occurs after our Linux env. update, as shown in the next thread. so I believe this should be something related to the environment variable setup.
 

also shown in the same picture, the path of "xrun" has been clearly identified by cadence so is there any explanation about this discontinuity, or any further setup to help cadence evoke "xrun"?


look forward to your opinions. many thanks.

Parents
Reply
Children
  • Andrew Beckett
    in reply to IssacW

    What is the content of /etc/os-release ?

    My guess is that you are running an OS that only supports 64-bit executables. So perhaps try running "xrun -64 -version" and see if that works. If it does, you could use:

    setenv CDS_AUTO_64BIT ALL

    or

    export CDS_AUTO_64BIT=ALL

    (depending on your shell) and then:

    xrun -version

    should work.

    Andrew

  • IssacW
    in reply to Andrew Beckett

    hi Andrew,

    that it is! now it works by referring to the "xrun" under folder "64bit".
    I'm the first one working in AMS flow in our group so have got a ways to go in understanding Xcelium. anyway thanks. 

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.