Activity

Hi Adam,
WRT randomness in dispatching each channel, that is what I am currently working on. I added it to AxiStream in a Beta form in an earlier OSVVM release – it has changed some on the Dev branch. I will be adding it to Axi4 VC next. Each channel will be independent, so a write data should randomly happen prior to write address, as will…[Read more]

Vivado 2022.2 simulator states to supports VHDL-2008. While this is meant to mean full support, there certainly are still many issues present. The focus was probably to support language features already supported in synthesis.

I personally tested support for VHDL-2008 fixed point number libraries, which require generic packages.

Vivado 2023.1…[Read more]

Hi Jamie,
The working library (denoted as work in VHDL) is the library into which you are currently compiling. Hence, the OSVVM packages use the name work to reference items (use work.TranscriptPkg.all).

Currently VHDL context clauses do not allow the usage of the library work. Hence, you see the usage of OSVVM there.

Diving a little…[Read more]

The OsvvmCOntext.vhd file in version 2023.04 seems out of sync with this post. It is still requiring a compile of these packages to “osvvm” when other packages include “use work.*.all” statements.
context OsvvmContext is
library OSVVM ;

use OSVVM.OsvvmScriptSettingsPkg.all ;
use OSVVM.NamePkg.all ;
use OSVVM.NameStorePkg.all ;
use…[Read more]