Skip to content

2026.01

Latest
Latest

Choose a tag to compare

View all tags
@github-actions github-actions released this 01 Mar 07:13
2026.01
6244364

Release notes for 2026.01

CoSim

  • Adds CoSimPCIe Verification Component - Thanks to Simon Southwell

MIT

  • Added DoDirectiveTransactions (AddressBus and Stream) to implement common directive transactions
  • Added VHDL-2019 interface capability to AddressBus.
  • Support for interfaces in Stream deferred to later revision due to vendor support issues in many simulators.

AXI4 Full VC

  • Added VHDL-2019 interfaces
  • Architectures are now separate from the entity in Axi4Manager_a.vhd, Axi4Subordinate_a.vhd, and Axi4Memory_a.vhd
  • If you need to update architectures, only update the 2019 architecture (in src) and enable TCL variable OsvvmDevDeriveArchitectures "true" in OsvvmSettingsLocal.tcl

ScoreboardGenericPkg

  • Updated FindAndFlush and FindAndDelete s.t. if the item is found, it reports as a PASSED and otherwise as FAILED

TestCase Reports

  • Opening VHDL Test Case File in vscode, in OsvvmSettingsLocal.tcl set:
    variable VhdlFileViewerPrefix "vscode://file/" ;
    • Default, view in browser
    • Assumption, test case file is the one compiled just before simulate
  • For VHDL-2019 simulators, integrate VHDL Assert counts into test pass/fail and Alert reporting (AlertLogPkg)

Language Support Package

  • Added Constant: TOOL_USES_32_BIT_INTEGERS

Updated build error handling

  • By default OSVVM catches all errors and ending with a Tcl error is off.
  • This is desirable as when running CI, you want all test cases that can run to run.
  • When running CI, use the JUnit test reporter to generate pass/fail messages
  • Add the following tcl variables to your OsvvmSettingsLocal.tcl to adjust TCL error signaling:
    • FailOnBuildErrors - Signal a tcl error if an error was signaled during a build. Default is false.
    • FailOnReportErrors -Signal a tcl error if an error was signaled during reporting. Default is false.
    • FailOnTestCaseErrors - Signal a tcl error any test case fails during a build. Default is false.
    • AnalyzeErrorStopCount - if 0, do not signal Analyze errors, otherwise, signal analyze error (and stop) when AnalyzeErrorStopCount errors occur. Default is 0.*
    • SimulateErrorStopCount - if 0, do not signal Simulate errors, otherwise, signal simulate error (and stop) when SimulateErrorStopCount errors occur. Default is 0*
  • If you have errors in any part of the OSVVM process, adjust the following TCL variables
    • TclDebug - When true and an OSVVM API command fails, print Tcl's $::errorInfo when an error occurs. Default false.
    • ReportDebug - When true and OSVVM reporting fails, print Tcl's $::errorInfo when an error occurs. Default false.

Note

SetInteractiveMode will change both AnalyzeErrorCount and SimulateErrorCount to 1 and Debug to true (which the same impact as TclDebug).

Build Reporting

  • If TestSuite has 0, 0, 0 => status is EMPTY
  • If compile before fails, do not start the test case.
  • Simulate error handling
    • IF compile before fails, do not start. Use error message as message to YAML to display
    • If simulate fails, use error message to YAML to display.
  • If analyze fails before simulate, test case will FAIL and report Analyze Failed

Compile Lists as TOML and CSV List

  • CreateDryRunDict - Instead of running analyze and simulate, collect file list and simulate list as dictionaries.
  • CreateAnalyzeListCsv - Run in DryRun and produce a inorder CSV list of files
  • CreateVhdlLsToml - Run in DryRun and produce VHDL LS Toml files.

SPI

  • Updated SPI test suite so that it is passing again

Scripts

  • Added VHDL-2019 feature controls. These are set automatically in the VendorScripts_***.tcl file.
  • SetVHDLVersion 2019 automatically done for tools that support it.
    • Turn off by doing SetVHDLVersion 2008 in your OsvvmSettingsLocal.tcl

Report Stuff

Assets 6
Loading