Quote:


Couple of qs: did you import your verilog netlist into cadence using verilogIn? and tried to close that schematic?

or did you try to close opened netlist i.e. verilog code?

Although,  ncvlog suggests verilog code...but then...

Rajdeep

Hi Jsun,

There might be a problem accessing the data in your file system mybe ...
In order to check your file system is all fine and running, please the following command:
Code:

nchelp  -lockcheck lockcheckFile 

If successful, the above should return:
File locking PASSED

If the above is OK, then you need to check your library for locking by running the following command:
Code:

ncpack -nocopyright –status mylibrary 

This would tell you the Read/Add flags status

You can unlock library by running:
Code:

ncpack -nocopyright –unlock mylibrary 

You can find more information about the unpack utility in the following PDF:
$IUSHOME/doc/ncvlog/ncvlog.pdf
I would advise running the:
Code:

cdnshelp -hierarchy $CDSHOME/doc 

I’m assuming your files are entirely managed in UNIX.

Hope these comments are useful. Please post further details otherwise

Cheers,
Riad.

Hi Jsun,

There is definitely something wrong in your system.
Secondly, your IUS verion is old, very old. I don't know whether this particular version is faulty but I would higly recommend moving toward latest IUS82 versions.

Anyway, I have done a bit of search and have managed to find as similar problem from the cdnshelp. It is actually in the VHDL KPNS doc ($IUSHOME/doc/ncvhdlKPNS/ncvhdlKPNS.html#1061304). It says the following (just a snippet, get the remaining from the doc):
Code:

[b]Description[/b]: In design environments where multiple systems are used and disks are shared over a network, there is the possibility that an incorrectly configured server will cause problems for the locking mechanism used by the NC tools.
A locking mechanism is used to ensure file integrity when multiple processes need to read/write from/to a common file. When the locking mechanism fails to gain a lock, the DLNOLK error is generated.

b]Solution[/b]: The server in question must be set up to support NFS locks. It is likely that the network is not set up correctly. To help troubleshoot this problem, the following utilities may be helpful.
 

My advice from now on is:
1. get yourself the new IUS82.
2. If still things don't work, although with the right network and file system, then you better get in touch with Cadence Customer Support.

That's all what I can say for no I'm afraid

Cheers,
Riad.