Jim Lewis

icon indicating a website link http://synthworks.com/ icon indicating an email [email protected]

icon company SynthWorks / OSVVM icon location Tigard, OR icon location VHDL Verification Specialist, OSVVM author, VHDL Trainer (including on OSVVM), IEEE VHDL WG Chair, Yoga Teacher

Results 203 comments of Jim Lewis

WaitForTransaction on AXIS Receiver returns after 1 delta - either add a warning or wait until an actual transaction occurs.

You will find this pattern in my classes and presentations: ```vhdl architecture Test of Tb is signal SB : OSVVM.scoreboardPkg_slv.ScoreboardIDType ; begin InitProc : process begin SB

WaitForTransaction on AXIS Receiver returns after 1 delta - either add a warning or wait until an actual transaction occurs.

There is no difference between a FIFO and a Scoreboard. If you are checking TDest, TID, and TUser, then there is that. TUser can be in the FIFO if it...

WaitForTransaction on AXIS Receiver returns after 1 delta - either add a warning or wait until an actual transaction occurs.

I have thought about all data handling being done by the FIFO. That would allow Tx to push directly to the RRec.BurstFifo and then do a check operation against it....

Write data before address is lost

I found it. Currently if the delay is 0, in the procedure DoAxiReadyHandshake, there is a sequence of code that ```vhdl if Valid = '1' then -- Proper handling if...

AXI4-Lite build.pro using build command instead of include

Thank you. It is fixed on the dev branch. @Paebbels I searched with both VSCode and NotePad++ and only found that one. If you find others, please let me know.

Using Named Association with AlertIf Gives "Ambiguous Subprogram" Error

I did a push on the Dev branch to address this. I think all I needed to do is the change the name of the first parameter of the first...

Using Named Association with AlertIf Gives "Ambiguous Subprogram" Error

If you get a chance to try the update on Dev, let me know.

Using Named Association with AlertIf Gives "Ambiguous Subprogram" Error

Update that fixes this released with 2024.09. Please re-open if you still have issues

Add coverage vendor API for NVC.

@nickg Is the package nvc.cover_pkg in NVC 1.14.1 or 1.15.0? Are these released? My version reports to be NVC-1.14-devel. If you have an exact release number that nvc.cover_pkg will be...

Add coverage vendor API for NVC.

Thanks @nickg that is what I needed to know. OSVVM compile scripts know the version of the tool and can conditionally build the appropriate files for 1.15 (assuming that is...