Stats

  • Locked Locked
  • Replies 4
  • Subscribers 66
  • Views 17938
  • 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

ncelab and ncvlog version error conflict

mhkvy4

I am trying to follow a tutorial on how to use NClaunch interface to compile and elaborate verilog files.  There seems to be a version conflict when I get to the elaborate step. Here is the error I get:

ncvlog_cg: *F,NBADVR: The version of the Calling tool "TOOL: ncelab(64) 10.20-s076" does not match the version of the Called tool "TOOL: ncvlog_cg(64) 08.20-s015".

When I type in ncvlog and ncelab from the terminal, the versions appear to be same 64 bit ones, 08.20-s015.

Is there any way I can change the version ncelab called by nclaunch. 

Also when I try to use ncelab on my stimulus file from the command line, I get the following error:

Unable to find a unit named 'stimulus.v' in the libraries.

I am beginner to using ncverilog and nclaunch so any help would be appreciated. 

Thanks

Parents

  • This is a very strange error that one would normally never expect to see :-)

    I wonder if someone has messed with the tool installation...

    What is your PATH variable set to? Please share it here.

    Have you set CDS_INST_DIR (a common mistake, users should NOT set this as it's a tool internal variable)?

    Please also share your exact ncverilog command.

    As a point of reference, you should aim to use a newer Incisive release, the 10.20 stream moved out of support a very long time ago, we're on 15.10 now, and 14.10 is the oldest supported release today.

    Also, if you're new to the tool and creating a new flow, I would strongly recommend to use the "irun" front-end, as this is the preferred compile/elab/run tool that replaces the older ncverilog/ncvlog/ncelab/ncsim commands.

Reply

  • This is a very strange error that one would normally never expect to see :-)

    I wonder if someone has messed with the tool installation...

    What is your PATH variable set to? Please share it here.

    Have you set CDS_INST_DIR (a common mistake, users should NOT set this as it's a tool internal variable)?

    Please also share your exact ncverilog command.

    As a point of reference, you should aim to use a newer Incisive release, the 10.20 stream moved out of support a very long time ago, we're on 15.10 now, and 14.10 is the oldest supported release today.

    Also, if you're new to the tool and creating a new flow, I would strongly recommend to use the "irun" front-end, as this is the preferred compile/elab/run tool that replaces the older ncverilog/ncvlog/ncelab/ncsim commands.

Children
No Data

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.