OSVVM Presentation in Copenhagen IDA is hosting an OSVVM presentation on 9 November 2015 from 18:30 til 20:30. For details see: http://ida.dk/event/316127 OSVVM and Error Reporting DVCon Europe in Munich, Germany. See: DVCon-Europe Program OSVVM World Tour Training Dates VHDL Testbenches and Verification – OSVVM+ Boot Camp Learn the latest VHDL verification techniques including transaction l... »
Webinar OSVVM for VHDL Testbenches. Thursday June 25, 2015 Open Source VHDL Verification Methodology (OSVVM) is a comprehensive, advanced VHDL verification methodology. Like UVM, OSVVM is a library of free, open-source code (packages). OSVVM uses this library to implement functional coverage, constrained random tests, and Intelligent Coverage random tests with a conciseness, simplicity and capabil... »
Coming to DAC? I will be hosting an OSVVM birds of feather (BOF) / community meeting. The meeting is intended to provide the opportunity to learn more and discus future directions of OSVVM. It is on Tuesday evening June 9 from 7 pm to 8:30 pm in Room 300 »
OSVVM 2015.03 is a minor release that updates only AlertLogPkg. All other packages remain unchanged. In AlertLogPkg, added AlertIfEqual, AlertIfNotEqual, and AlertIfDiff (file). Added ReadLogEnables to initialize LogEnables from a file. Added ReportNonZeroAlerts. Added PathTail to extract an instance name from MyEntity’PathName. Added ReportLogEnables and GetAlertLogName. See AlertLogPkg_Use... »
OSVVM 2015.01 is a major release that introduces AlertLogPkg. AlertLogPkg adds Alert and verbosity control procedures that are a powerful replacement for assert statements. All OSVVM packages have replaced asserts with alerts. VHDL assert statements have a limited form of an alert and verbosity control. Through a simulator, you can set an assertion level that will stop a simulation. Through a simu... »
I have just posted release 2014.07a. There are no new features in this release. It fixes memory leaks. The first (and biggest) issue is in the deallocate procedure in CoveragePkg for CovPType. The Name of each coverage bin is never deallocated when deallocate is called. If you called deallocate during your testing process, the space allocated for the bin names was never given back. Hence, if you a... »
Release 2014.07 has been posted on the downloads pages. Its main target is interfacing with requirements tools. Added names to bins (via AddBins and AddCross). It is intended that the name match a requirement name. When using WriteBin or WriteCovHoles, if a bin name is set, it will print. For details, see Setting Bin Names in the Reporting Coverage section of the CoveragePkg Users Guide. Enhanced ... »
Over the summer I have been working on the next set of revisions for OSVVM. One of the new features allows a name to be specified for each bin. The name is specified in calls to AddBins and AddCross. If a name is present, calls to WriteBin will print it. One motivation for a bin name is to correlate a requirement with it being tested (PASSED) or not tested (FAILED). Hence the output of WriteBin is... »
Webinar Thursday June 26, 2014 OSVVM provides functional coverage and randomization utilities that layer on top of your transaction level modeling (tlm) based VHDL testbench. Using these you can create either basic Constrained Random tests or more advanced Intelligent Coverage based Random tests. This simplified approach allows you to utilize advanced randomization techniques when you need them an... »