OSVVM on GitHub, OSVVM Training in Germany, and other OSVVM Training Datess
OSVVM on GitHub
OSVVM is now on GitHub. You can find releases there. I will be putting bug patches there first before formally releasing them on OSVVM.org. Long term I also plan on putting tool specific branches as needed (such as for Cadence).
OSVVM Training in Germany
In conjunction with PLC2, we will be offering OSVVM training in Germany. See the matrix below for the first two dates in Freiburg, Germany.
OSVVM Training Dates
VHDL Testbenches and Verification – OSVVM+ Boot Camp
Learn the latest VHDL verification techniques including transaction level modeling (tlm), self-checking, scoreboards, memory modeling, functional coverage, directed, algorithmic, constrained random, and intelligent testbench test generation. Create a VHDL testbench environment that is competitive with other verification languages, such as SystemVerilog or ‘e’. Our techniques work on VHDL simulators without additional licenses and are accessible to RTL engineers.
|February 29 – March 4||Freiburg, Germany||Enroll with PLC2|
|March 28 – April 1 and April 11-15||online class||Enroll with SynthWorks||April 25-29||Stockholm, Sweden||Enroll with FirstEDA|
|May 9-13||Freiburg, Germany||Enroll with PLC2|
|May 23-27 and June 13-17||online class||Enroll with SynthWorks|
|July 25-29 and August 8-12||online class||Enroll with SynthWorks|
|September 12-16||Bracknell, UK||Enroll with FirstEDA|
Leave a Reply
You must be logged in to post a comment.
I’m looking forward to the training with PLC2 in may, which I will attend to.
I have also done some local modifications of the OSVVMs github repository (Alert report in XML format), which maybe are interesting for others too. We use XML to read the report into tools which generate simulation summaries from various sources like Modelsim coverage reports and so on.
I am also looking forward to the class.
We also have others interested in having writebin formsts of JSON and CSV. Hence, I think we will need to work all three formats into the whole library.
Other OSVVM methods have options that are set locally in a package/protected type as well as globally in the OsvvmGlobalPkg. I thinking this needs to be continued, and in addition, I think we may need to consider having the OsvvmGlobalPkg settings be able to be initialized from a settings file (something like osvvm.ini).