Closed HKLee2040 closed 6 years ago
jwise
commented
6 years ago Hmmm, now that is weird. I'm using Verilator 3.912 also and have no problem like this, and I have the same $sformatf in my RANDFUNC.vlib.
Can you make sure that the one in your path is 3.912? /usr/bin/verilator_bin --version
$sformatf got added to Verilator in 3.877.
HKLee2040
commented
6 years ago /usr/bin/verilator_bin --version ==> 3.874
After remove the 3.874 version, it can work now.
jwise
commented
6 years ago Great! Glad you got it working. I'll close this bug, but if you have further problems with this, please feel free to reopen it.
koroyuki
commented
6 years ago Dear Sir, This is my first time to write a comment here. I have the same issue with HKLee2040 of Dec.5, 2017. My Verilator version is 3.874-1. HKLee2040 wrote that "After remove the 3.874 version, it can work now." May I know the detail commands that HKLee2040 did? Thanks in advance. Tago
HKLee2040
commented
6 years ago @koroyuki Sorry, I do not remember the detail commands, it's several months ago. I think it should be something like: sudo apt-get remove verilator or sudo apt-get remove --auto-remove verilator Then install Verilator 3.912.
I did not try docker. Maybe you can try it.
BTW, I do not use verilator because it needs large DDR and my computer can't afford it.
koroyuki
commented
6 years ago Dear HKL332040 Thank you very much for your quick reply. I understand the remove step. Is the installation command that sudo apt-get install Verilator=3.912 ?
Tago
HKLee2040
commented
6 years ago @koroyuki As my remember, I download the 3.912 source code, build the code, and then make install.
koroyuki
commented
6 years ago Dear HKLee2040
Thank you very much for your suggestion again.
Before I read your suggestion above, I did "sudo apt-get remove verilator", and then
:~$ sudo apt-get install verilator
Reading package lists... Done
Building dependency tree
Reading state information... Done
verilator is already the newest version (3.874-1).
0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
So 3.912 was not obtained. Only version 3.874-1 was installed. I try tar ball method under the URL you gave me now on.
3.874-1.
koroyuki
commented
6 years ago Dear HKLee2040
I followed https://www.veripool.org/projects/verilator/wiki/Installing to build Verilator 3.916 environment. The build looked success! How can I do a sanity check next?
HKLee2040
commented
6 years ago koroyuki
commented
6 years ago Dear HKLee2040, Thank you very much for your suggestion and sorry for my slow response. According to Verilator Testbench in nvdla integration guide, I tyoed ./tools/bin/tmake -build verilator build pass was displayed. Next, I typed make run TEST_sanity0
After several ten minute run with lots of warning messages, It ended with make: *** [../../outdir/nv_full/verilator/VNV_nvdla.mk] Error 255
I wildly guess it is maybe due to out of memory. My PC has 16GB memory. I am going to configure nvdla RTL with "nv_small" as shown in Tree Build section in the integration guide. Your suggestion is very welome! koroyuki
HKLee2040
commented
6 years ago @koroyuki I can't reopen this issue. I suggest that you can open a new issue to discuss this problem.
koroyuki
commented
6 years ago Dear HKLee2040, Thank you very much for your strong support. I found my mistakes for systemc-2.3.0 path and verilator path in make execution. I am trying to build "nv_large nv_small" environment instead of "nv_full". I typed the following commands.
git clone https://github.com/nvdla.hw.git nvdla_hw cd nvdla_hw git checkout master // checkout before 2017 Nov. version make I am asked cpp path, gcc path, java path, and perl path only. I am not asked systemc path, verilator path and clang path. For "make" of "nv_full" case, the all paths above are asked. make ends with pass . However, ./tools/bin/tmake -build vmod failed. Do you have a suggestion? Best regards koroyuki
HKLee2040
commented
6 years ago @koroyuki I'm afraid that nv_small or nv_large is not ready. https://github.com/nvdla/hw/issues/94
koroyuki
commented
6 years ago Dear Heng-Kuan Lee. Thank you very much for your support. I see. I use the latest "nv_full". koroyuki
2018-03-16 15:37 GMT+08:00 Heng-Kuan Lee notifications@github.com:
@koroyuki https://github.com/koroyuki I'm afraid that nv_small or nv_large is not ready.
94 https://github.com/nvdla/hw/issues/94
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/nvdla/hw/issues/72#issuecomment-373628620, or mute the thread https://github.com/notifications/unsubscribe-auth/AdUawvankMSgoRb4JRmR_3s6JB1p9VVuks5te2ucgaJpZM4QzUjF .
koroyuki
commented
6 years ago Dear HKLee2040
I installed verilator 3.923 from veripool and make it. I followed http://nvdla.org/integration_guide.html#verilator-testbench. I still face a "failed" as shown below. Would you have a suggestion?
tago@d200:~/nvdla_hw$ ls outdir/build.log outdir/build.log
Best regards koroyuki
Verilator 3.912 clang 3.8.0 ubuntu 16.04
"Unsupported or unknown PLI call: $sformatf"
============================================== files are generated under /media/rogers/DATA/work/nvdla_org/trunk/outdir/nv_full/vmod/nvdla/top
make: Leaving directory '/media/rogers/DATA/work/nvdla_org/trunk/vmod/nvdla/top' make: Entering directory '/media/rogers/DATA/work/nvdla_org/trunk/verif/verilator' /usr/bin/verilator --cc --exe -f verilator.f --Mdir ../../outdir/nv_full/verilator/ nvdla.cpp --compiler clang --output-split 250000000 %Error: ../../outdir/nv_full/vmod/vlibs/RANDFUNC.vlib:52: Unsupported or unknown PLI call: $sformatf %Error: Exiting due to 1 error(s) %Error: See the manual and http://www.veripool.org/verilator for more assistance. %Error: Command Failed /usr/bin/verilator_bin --cc --exe -f verilator.f --Mdir ../../outdir/nv_full/verilator/ nvdla.cpp --compiler clang --output-split 250000000 make: *** [../../outdir/nv_full/verilator/VNV_nvdla.mk] Error 10 Makefile:21: recipe for target '../../outdir/nv_full/verilator/VNV_nvdla.mk' failed make: Leaving directory '/media/rogers/DATA/work/nvdla_org/trunk/verif/verilator' logfile: outdir/build.log