Errors While Generating Simulation Reports

[Jake]

Hello,

I have recently been running into some issues with my latest OSVVM simulations. I am using OSVVM version 2024.07 and the Siemens Questa version 2025.1_1 simulator.

I am looking to moving to the most recent version of OSVVM as soon as possible, but sadly the aforementioned version of Questa doesn’t support all the VHDL2019 features that OSVVM leverages.

As for the errors that I am seeing. My simulations seem to run fine, and all my affirmations are passing. I notice this log message after each simulation runs:

“ReportError: Simulate2Html failed. See previous messages for details”

After doing some digging into the Tcl API, it seems like this message is being printed in the CallbackOnError_AfterSimulateReports procedure call in the simulate procedure that is defined in Scripts/OsvvmScriptsCore.tcl.

After adding some debugging puts commands to see the errors, I think I’ve found my problem. The ReportErrMsg and LocalReportErrorInfo messages indicate that the “file rename -force $AlertYamlSourceFile $AlertYamlFile” command in the SimulateDoneMoveTestCaseFiles procedure is failing because some of the generics of my testbench module contain directory paths. This causes the files to not be renamed properly. I see errors similar to the following:

error renaming "file_test_alerts.yml" to "reports/file_regressions/file_test_IFILENAME_<path to file>_OFILENAME_<path to additoinal file>_DEBUG_EN_false_alerts.yml": no such file or directory
    while executing
"file rename -force $AlertYamlSourceFile $AlertYamlFile"
    (procedure "SimulateDoneMoveTestCaseFiles" line 35)
    invoked from within
"SimulateDoneMoveTestCaseFiles "
    (procedure "AfterSimulateReports" line 3)
    invoked from within
"AfterSimulateReports"
ReportError: Simulate2Html failed.  See previous messages for details
Build Start time  11:24:30 MDT Tue Apr 29 2025
Build Finish time 11:25:40, Elapsed time: 0:01:10
Build: sim_RunAllFileTests PASSED,  Passed: 1,  Failed: 0,  Skipped: 0,  Analyze Errors: 0,  Simulate Errors: 0
#  exit -f
# End time: 11:25:48 on Apr 29,2025, Elapsed time: 0:01:16
# Errors: 0, Warnings: 0

I’ve looked through the documentation and don’t see anything that might change this behavior.

Do you have any insight for me on how I could correct this issue?

Thanks in advance for the help! I’ve really enjoyed the excellent features and functionality that OSVVM has provided me.

-Jake Talbot

[Jim Lewis]

Hi Jake,
> I am using OSVVM version 2024.07 and the Siemens Questa version 2025.1_1 simulator.
>
> I am looking to moving to the most recent version of OSVVM as soon as possible, but sadly the aforementioned
> version of Questa doesn’t support all the VHDL2019 features that OSVVM leverages.

This mainly controls whether to use the RandomPkg2019 or not. RandomPkg2019 was tested in 2024.2 and 2024.3 and it passed all of our regression tests. Not sure what happened to make them think it is not working. Questa has had a history of having issues with impure functions – including the protected type version of RandomPkg.

If you comment out the lines in OsvvmLibraries/Scripts/VeendorScripts_siemens.tcl, that sets 2019 everything will be fine:
# if {[expr [string compare $ToolVersion “2024.2”] >= 0]} {
# SetVHDLVersion 2019
# }

This will be commented out in the next release or updated for 2025.2 (if it is supported there).

With respect to the generic naming, the files had to be renamed to incorporate the generics to ensure unique naming for each results file (in the event the test case is run with multiple different generics). That said, this was not an anticipated use model. Obviously a fix is needed. Brainstorming just a little, all ‘/’, ‘\’, and ‘:’ in a name can be replaced by ‘_’. Does this sound like it will work?

[Jake]

Thanks Jim for the quick response! I really appreciate it.

As far as VHDL2019 support in Questa version 2025.1_1, I ran the regression tests using OSVVM version and get a slew of errors similar to the following when RandomPkg2019.vhd is compiled:

# ** Error: ../OsvvmLibraries/osvvm/RandomPkg2019.vhd(122): (vcom-1440) Language feature Class VARIABLE parameter “RV” of mode OUT or INOUT for FUNCTION is not supported yet.

It is very interesting to me that this worked in previous versions of this particular simulator. I’ll have to reach out to my FAE or sales rep for more details on this. I’ll try your suggestion of commenting out the lines in VendorScripts_siemens.tcl and re-run some tests.

As far as your suggestion goes for file renaming and my current predicament, I think your proposed solution will work just fine.

Thanks again,
Jake
I’ll try commenting out the

[Jim Lewis]

Hi Jake,
The fixes for both of these issues are now on the OSVVM Dev branch. If you are allowed to fetch OSVVM from GitHub you can get the dev branch by doing:

git clone --recursive --branch dev https://github.com/osvvm/OsvvmLibraries

Otherwise let me know and I can push it to main and do a release to osvvm.org.

Jim

[Jake]

Thanks Jim!

Unfortunately I am unable to fetch from GitHub. I would very much appreciate a release to osvvm.org.

I did try to comment out the lines you mentioned in VendorScripts_siemens.tcl and re-ran the built in regressions. Everything worked fine. I will start the process of adopting the newest release as soon as it is posted to osvvm.org

Thanks again for the help and the rapid responses!

-Jake

[Jim Lewis]

I have released these updates as part of 2025.4

[Jake]

Thank you!

I’ll get them integrated and report back.

-Jake

[Jake]

I have migrated to 2025.4, and things are working well for me so far. Thanks Jim!

-Jake

[Author]

Posts