github-mirrors/cve2
1
0
Fork 0
mirror of https://github.com/openhwgroup/cve2.git synced 2025-04-22 21:17:59 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions

Value passed to UVM set_timeout is calculated as 1000000000 basing on 1ns/1ps timescale.

Browse source 
But if you are using precompiled UVM it may be compiled with other timescale depending on compilation option used when it was compiled or tools default timescale value (uvm does not set timescale int the code).
In this case for us precompiled UVM timescale is 1ps/1ps - so UVM gets 1000000000 in set timeout but interprets it as ps. As a result timeout is 1000 times smaller that you expect. That is why we are getting timeouts.
It is hard to find perfect solution. One of them is to recompile the UVM with -timescale 1ns/ps (or whatever you will use for your design).
This commit is contained in:
Dawid Zimonczyk 2020-07-09 10:57:56 +02:00 • committed by Rupert Swarbrick
parent 14f85d3ee3
commit 1dfddee5e6
1 changed files with 3 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

4
dv/uvm/data/riviera/riviera.hjson
View file

@ -11,7 +11,8 @@
build_opts: ["-sv",
"-timescale 1ns/1ps",
"-uvmver 1.2",
"+incdir+\"{ALDEC_PATH}/vlib/uvm-1.2/src\"",
"\"{ALDEC_PATH}/vlib/uvm-1.2/src/uvm_pkg.sv\"",
"-f {sv_flist}"]
run_opts: ["-sv_seed={seed}",
@ -20,6 +21,7 @@
"-lib {sv_flist_gen_dir}/work",
"+UVM_TESTNAME={uvm_test}",
"+UVM_TEST_SEQ={uvm_test_seq}",
"-sv_lib \"{ALDEC_PATH}/bin/uvm_1_2_dpi\""
"-do {tool_srcs_dir}/riviera_run.do"]
// Coverage related.