Activity

Meant to say one warning in the previous message.

I got it to compile now with one error.


Warning-[AGGRNULLRANGE] Null range
../osvvm/RandomPkg.vhd, 109
RANDOMPKG

Modified my build script

mkdir -p worklib
vhdlan -full64 -vhdl08 -verbose…[Read more]

I get the following syntax error when using VCS 2020.03-SP1:

Error-[IEEEVHDLSYNTAXERR] Syntax error
../osvvm/ScoreboardPkg_int.vhd, 53
analysis-PreParsing

generic map (
^
Syntax error detected during VHDL parsing.

I have a script with the following:

mkdir -p worklib
vhdlan -full64 -vhdl08 -verbose -nc…[Read more]

Hi Tim,
> Is OSVVM supported by the latest Synopsys VCS-MX?
It is my understanding that it is, however, I have not done any testing with it – yet. Hopefully toward the end of the year, that will be changing.

> I didn’t notice any scripts in the OsvvmLibaries/Scripts repository.
It is on my todo list. Does VCS-MX have a tcl interface or do y…[Read more]

#2 Did you run the testbench examples before modifying them? The test TbAxi4_MemoryBurst (which runs when you do build ../OsvvmLibraries/AXI4/Axi4/testbench) does bursts. The first burst in the test is 3 32 bit words – IE 12 bytes and the address is word aligned.

What is 1 wider? Did you mean 64 bits? AXI data supports a power of 2…[Read more]

#1 I use “run all” to run my tests. std.env.stop will stop the test. However, stop works much like a breakpoint, so the simulation can be continued. I am ok with this.

If you wanted to prohibit the testbench from running further after it stops, use std.env.finish instead. It also allows an integer parameter, so you can call it…[Read more]