LarsAsplund on vunit_event
Added string decoration functio… Make check result function an a… Added event mechanism. and 12 more (compare)
eine on master
readme: update shield syntax (b… (compare)
Hello. I'm getting a "Subprogram check_equal is ambiguous" error, followed by an enormous wall of text when trying to compare an slv popped from a queue_t with a string literal.
check_equal(pop_std_ulogic_vector(tx_queue), x"CA", "Check byte 1");
Any suggestions on this? I see that the tb_queue in the VUnit GitHub repo uses assert statements for this instead. Why is that, and are there any downsides?
for a student project about verification I wanted to do some tests of a DUT using vunit. My goal is to perform the results of the stimulation with a testbench with the measurement results of a LogicAnalyser of the same system. For this I am looking for a way to generate some kind of result table with the corresponding states and timings of my variables when testing with vunit. Does anyone have an idea ?
I hope I have formulated my problem halfway clearly. I am still completely new in the area of HDL and testing, should I say something wrong please excuse me :)
Translated with www.DeepL.com/Translator (free version)
@vruizescribano The "bound check failure" is coming from ghdl, not vunit. Usually means some math operation you're doing is overflowing.
You are right. It looks like I am having an issue with GHDL because even a simple std_logic_vector is giving me a metadata value. This code was run using Modelsim previously without having any issue. I had big expectation with GHDL but Modelsim makes things easier. I will give a second try to GHDL if someone points out what it could be, otherwise I will switch back to Modelsim after Xmas time. Thanks!
SystemExitwhich does work. Use case is for prototyping the design I have a software model of it and want to swap out software functions with running a vunit sim as a "function" with returned data. Ideally for me it would just take the place of the
post_runand return the
Results as it does now.
Compiling into vunit_lib: ............\Users\vpallichadath\AppData\Roaming\Python\Python310\site-packages\vunit\vhdl\string_ops\src\string_ops.vhd failed
=== Command used: ===
"C:\Program Files (x86)\Ghdl\bin\ghdl" -a --workdir=C:\Projects\vunit\vunit-master\examples\vhdl\user_guide\vunit_out\ghdl\libraries\vunit_lib --work=vunit_lib --std=08 -PC:\Projects\vunit\vunit-master\examples\vhdl\user_guide\vunit_out\ghdl\libraries\vunit_lib -PC:\Projects\vunit\vunit-master\examples\vhdl\user_guide\vunit_out\ghdl\libraries\lib C:\Users\vpallichadath\AppData\Roaming\Python\Python310\site-packages\vunit\vhdl\string_ops\src\string_ops.vhd
=== Command output: ===
C:\Program Files (x86)\Ghdl\bin\ghdl.exe:command-line: cannot find "std" library