Brad Adam

I was not familiar with that VHDL-2008 capability but this did solve it for me!

Was able to alias the buried signal and then use force in to drive it from the testcase giving me more control over the specific time that the signal changed during testing.

Thanks Jim.

Hey,

This is awesome news, I really appreciate the continued updates to these libraries.

Regarding clock jitter, looking into the code in ClockRstPkg.vhd I’m not sure I fully understand what is happening with the supplied coverage ID. Has there been a documentation update which details this new function?

I would expect a jitter clock to…[Read more]

I did “global aldec”, all lower case.

The error message was referencing an all uppercase $ALDEC but “global aldec” fixed this issue. I noticed the same thing with “puts $aldec” vs “puts $ALDEC” as you describe.

No, there is no $aldec used in the $PATH_TO_SIM_DIR on my machine, that just points to the project directory on my C:/ drive.

Thanks,
Brad

Hey,

I totally agree. This is part of what was so confusing to me. I could see that when using $aldec and running the test the variable would be properly expanded as you show, however, a bit further into the run, when attempting to load the aldec_matlab_cosim.dll the path would still show an unexpanded variable $ALDEC in the path.

I actually…[Read more]

Hey, Jim!

So I’ve been working with Aldec as well on this and we’ve tracked down the root cause of OSVVMs failure to correctly call the $ALDEC variable.

Turns out that we needed to add “global aldec” to the VendorScripts_RivieraPro.tcl within the vendor_simulate process.

I don’t think there is a way to add images on these forms to show you…[Read more]

Okay, that was helpful and after comparing the logs I’m reasonably confident that I am supplying the needed switches to the SetExtendedSimulateOptions.

At this point the remaining failure when using RunTest seems to be in the load libraries steps, specifically the libraries from Aldec. In the below console output, systf.dll and…[Read more]

Hey, I appreciate the insight and I actually worked my way to this action after noticing that the simulate command called vsim. I guess one more question to make sure I’m understanding these scripts correctly.

Currently, I know the following script will allow my to run my test and see the results:

SetCoverageSimulateEnable true

analyze…[Read more]

Actually, I found the RunTest code in OsvvmProjectScripts.tcl, and the best way to add additional options for this would be following Example_LocalScriptsDefaults.tcl I assume?

Okay, this is very helpful information and from this I believe the answer to what I am trying to do is probably no.

Looking at TestStandAlone.vhd assume there is a generate statement that decides if xMiiPhy gets created or not.


phy_gen : if C_PHY_GEN_TRUE = 1 generate

xMiiPhy_1 : xMiiPhy
generic map (
MII_INTERFACE =>…[Read more]

Hey,

glbl is a verilog file referenced by an IP from a third party vendor.

Is it possible to set a generic for a file that is analyzed before simulation? Looking at the script users guide I would think that SetExtendedAnalyzeOptions is meant to accomplish this but I could be using the command incorrectly. Is it possible to use…[Read more]

I appreciate the insight, Jim. Was approaching this from the wrong angle.

Yes, writing to a memory that supports word addressing is the more accurate way of saying this. I would like to ignore WSTRB but the issue seems to be occurring at the manager side, not the subordinate side.

As in the comment above if I do the following:

write(trans_rec, x”0001?, x”DEADBEEF”); –WSTRB = 1110

The AXIBUS data line shows t…[Read more]

Hey,

So this is an atypical use case for sure.

Usually I use the Axi4Lite VC as ‘normal’ and if, for instance, I was sending 32-bit data to some addresses I would do:
write(trans_rec, x”0000″, x”DEADBEEF”);
write(trans_rec, x”0004″, x”DEADBEEF”);
write(trans_rec, x”0008″, x”DEADBEEF”);
Where the base address is increasing…[Read more]

Just found what I think is the answer in the AXI4_VC_user_guide on table 9.3.2 which lists WSTRB as non-configurable.

So I guess my question becomes, is this still accurate and if so, is there a known way to work around this in OSVVM?

Thank you for this update, I’ll check it out in future testing.