Jim Lewis

Hi Jake,
This is something that one of the Siemens AEs has talked to me about and has worked on. I will have to see if he has something ready to submit for OSVVM. The plan is that Visualizer will simply use a separate VendorScripts_Visualizer.tcl. With that it should be fairly easy to do whatever visualizer needs done as all the hooks are…[Read more]

Hi Brad,
I have had on my todo list to come back to look at this example in further detail – I have just had a very busy year end for 2023.

Since I don’t have a copy of your testbench, we have only been able to talk in generalities. However, I think I see the issue in your statement here:

> When analyzing that TB file, since the generic has…[Read more]

Hi Lukas,
Do you have the output of LinkLibraryDirectory? If it is working ok, it should be something like the following:

LinkLibraryDirectory C:/tools/VHDL_LIBS/QuestaSim-2022.01
# set CurrentSimulationDirectory C:/tools/sim/questa
# vmap defaultlib C:/tools/VHDL_LIBS/QuestaSim-2022.01/defaultlib
# vmap osvvm…[Read more]

If you look at the OSVVM *.pro compile scripts you will note there are a number of places where we do not compile certain things – because of a bug in a particular tool.

Note these ports are not OPEN. Instead they have a null range, which is a valid range. Please submit a bug against Xcelium for this issue.

Hi Rishi,
The issue with 10.5b looks like a bug in that version of the tool. I don’t test with versions that old.

Best Regards,
Jim

Hi Rishi,
The issue with 2022.4 (quarter or release in 2022 not sure) / 2022.10 (10 probably is month) that says:

# ** Error: vhdl_src/std/standard.vhd: (vcom-1576) expecting IDENTIFIER or BODY.

Is a tool install issue. OSVVM does not analyze (compile) the standard package.

Best Regards,
Jim

Hi Adam,
If C_PHY_GEN_TRUE is a top level generic, OSVVM will allow you to specify it for either simulate or RunTest. As long as your simulator supports that, it should work just fine. Generate is resolved at elaboration time – which is the first step of simulation.

Have you tried something like this and it failed to work?

Jim

In OsvvmLibraries/Ethernet/TestStandAlone/TestStandAlone.pro, I set the generics for the top level test by doing:

simulate Tb_xMii1 [generic MII_INTERFACE RGMII] [generic MII_BPS BPS_1G]

Here Tb_xMii1 is the name of the configuration for the testharness (named TbStandAlone).

So if you have not already, add top level generics to the…[Read more]

Have you tried:

simulate DUT_test glbl -L unisim [generic C_EXAMPLE_PARAM 1]

What library is glbl in? If it were VHDL and glbl is in the unisim library, the glbl would be referenced as unisim.glbl.

If all of your simulations nee glbl and unisim library, you can do

SetExtendedSimulateOptions "-L unisim"
SetSecondSimulationTopLevel…[Read more]

Did you read: https://osvvm.org/archives/2280

One of the examples is precompiling OsvvmLibraries and then linking to them. Let me know if that answers your questions.

Hi Jorge,
I just came across this again. This issue was addressed in release 2022.08. MemoryPkg now supports data words of any width. A couple of different implementations of MemoryPkg are provided via generic instances). The instance MemoryPkg (and MemoryPkg_X) stores data and X/U’s. The instance MemoryPkg_NoX stores only data and X’s are…[Read more]

Hi Joseph,
A pro file is tcl plus a procedure abstraction layer that replaces the calls to vlib, vmap, vcom, vlog, and vsim with library, LinkLibrary, analyze, analyze, and simulate (respectively).

Sounds like your do file is fairly complicated. Not sure if you can successfully transition it or not. However, here is how to try to do…[Read more]

Hi Joseph,
The coverage controls work in a coordinated fashion with the OSVVM scripts that analyze and simulate the design. How about posting your do file – or a representative piece of it and I can suggest how to update it to use the OSVVM script API instead – it is actually quite a bit simpler than using the vendor commands directly.

For…[Read more]