How to compile Xilinx Timing-Simulation library SIMPRIM unde

[uvbaz]

Hallo Everyone,

By the Post-PAR Simulation under NC-Sim, i need to compile the Xilinx
Library SIMPRIM, the Solution of Xilinx Homepage are here:

http://www.google.com/url?sa=D&q=http://www.xilinx.com/xlnx/xil_ans_display.jsp%3FiLanguageID%3D1%26iCountryID%3D1%26getPagePath%3D5474

but i do not want to use solution 2, because of others reasons, a
pre-compiled libraries are not possible.

And i do not want to use solution 1 too, because i want to do the
simulation with ncvlog+ncelab+ncsim step by step.


Now the problem is: How can i do this

ncverilog -y $XILINX/verilog/src/simprims $XILINX/verilog/src/glbl.v
+libext+.v <testfixture>.v <design>.v

with ncvlog+ncelab+ncsim?? I know it must be in cds.lib, hdl.var and
so, but how?


Thanks!!!

 

[uvbaz]

right URL:

http://www.xilinx.com/xlnx/xil_ans_display.jsp?iLanguageID=1&iCountryID=1&getPagePath=5474

 

If we still provide ncprep as part of the installation, you could use
that. You give it the same kind of command line you would give
ncverilog, and it generates everything you need to run an equivalent
ncvlog+ncelab+ncsim execution. There is a RUN_NC script that will run
all 3 steps, and argument files containing all the arguments needed by
each tool, to be included by the -f option of each tool. These can be
modified as desired. Any -y options will have been expanded into the
actual files that need to be compiled by ncvlog.

 

[uvbaz]

Thanks for your answer, Sharp

I have tried NCPREP yesterday. NCPREP is so clever, that it includes
only the files that <testfixture>.v <design>.v needed, from the
library SIMPRIM.

But how can i do this manual???

Thanks again
Cheng



sharp@cadence.com schrieb:

If we still provide ncprep as part of the installation, you could use
that. You give it the same kind of command line you would give
ncverilog, and it generates everything you need to run an equivalent
ncvlog+ncelab+ncsim execution. There is a RUN_NC script that will run
all 3 steps, and argument files containing all the arguments needed by
each tool, to be included by the -f option of each tool. These can be
modified as desired. Any -y options will have been expanded into the
actual files that need to be compiled by ncvlog.

 

uvbaz wrote:

I have tried NCPREP yesterday. NCPREP is so clever, that it includes
only the files that <testfixture>.v <design>.v needed, from the
library SIMPRIM.

But how can i do this manual???

I think that the more typical use-model would be to compile everything
in the SIMPRIM library with ncvlog. Then compile your design with
ncvlog, and elaborate your top-level module(s) with ncelab. It should
use only the modules from the library that were actually used by your
design.

Typically, I think you would compile a library like SIMPRIM into a
separate design library from your design. But that probably involves
doing things with your cds.lib and hdl.var file that I don't know
anything about. Sorry I can't be more helpful.

 

[uvbaz]

hallo, Sharp,

Yes, i think i should use the way you said.

Thanks a lot

Cheng

sharp@cadence.com schrieb:

uvbaz wrote:

I have tried NCPREP yesterday. NCPREP is so clever, that it includes
only the files that <testfixture>.v <design>.v needed, from the
library SIMPRIM.

But how can i do this manual???

I think that the more typical use-model would be to compile everything
in the SIMPRIM library with ncvlog. Then compile your design with
ncvlog, and elaborate your top-level module(s) with ncelab. It should
use only the modules from the library that were actually used by your
design.

Typically, I think you would compile a library like SIMPRIM into a
separate design library from your design. But that probably involves
doing things with your cds.lib and hdl.var file that I don't know
anything about. Sorry I can't be more helpful.