Jim Lewis

Being the second simulator to go through this activity, I would expect you to find some rough edges that need updated. OSVVM CoveragePkg should not know anything about the types...

I commented in #933, but I also found that neither imported XML as defined by the UCIS standard. As a result, OSVVM creates a YAML file and then converts it...

> I ran into the issue @JimLewis mentioned (it needed to be integer type). I changed it in the CoveragePkg locally, but that would make it incompatible with Aldec. Isn't...

@nickg When you suggested a procedure for setting the value, are you thinking that an impure function cannot return an access type? On p 20 for IEEE 1076-2008, I see:...

@nickg @Blebowski I should be able to make some updates that will facilitate this shortly. I am hoping before Monday.

@Blebowski I just updated the API for Coverage. I renamed the package to CoverageVendorApiPkg and created a CoverageVendorApiPkg_NVC.vhd for you to modify. I updated the osvvm.pro file so that it...

Are you looking to set the seeds to something particular or just set them all to something different? The call to NewID calls InitSeed and gives each coverage model a...

Have you seen SetRandomSalt? It is intended for that application. In your top-level testbench, do: ```vhdl entity TestHarness is generic (DATE_STRING : string := "") ; end entity TestHarness ;...

I should note, I am ok with having a wrapper function. The question is, what are its parameters: - Does it accept either 3 string or 3 integer values? -...

@Paebbels - almost endless memory. The package produces warnings at 34 bits of address and supports up to 40 bits of address (hard limit internally). Note some simulators will crash...