Jim Lewis
-
Jim Lewis wrote a new post 2 years, 1 month ago
Don’t miss your chance to express what verification approach you use for FPGAs (OSVVM)
This is the first public survey I have seen. Others have been done by random selection and invitation only.
Survey is here
-
Jim Lewis wrote a new post 2 years, 1 month ago
On GitHub Issues, I had the following question, “With OSVVM scripting (.pro), is there a way to specify testbench generics, waveform files, and length of time to run a simulation.”
So lets take a look at these. […]
-
Jim Lewis started the topic Questa-Intel & Reports in the forum OSVVM 2 years, 2 months ago
Recently due to some issue reports, I had a look at Questa-Intel 2021.02. When I ran it, it would not create proper OSVVM log and html log messages – much of the information was missing.
The first thing I noticed is that it started up with two windows instead of just the GUI:
So I consulted with a friend of mine to see if he knew what the…[Read more]
-
Jim Lewis started the topic OSVVM, Questa – Fails to Compile OSVVM in the forum OSVVM 2 years, 2 months ago
In the Questa – Intel 2022.0X version, the osvvm library was removed, but the library mapping for osvvm still remains in the ini file at /questa_fse/modelsim.ini. This unfortunately prevents OSVVM from compiling.
The only way I have found to fix it is to comment out the mapping in the ini file. To do this, simply put a ‘;’ as the first…[Read more]
-
Jim Lewis started the topic OSVVM & Questa – Calls to PushBurstRandom in the forum OSVVM 2 years, 2 months ago
For Questa 2021.02, there is an issue with it being able to simulate calls to PushBurstRandom and CheckBurstRandom with an integer FirstWord value:
procedure PushBurstRandom ([Read more]
constant Fifo : in ScoreboardIdType ;
constant FirstWord : in integer ;
constant Count : in integer ;
constant FifoWidth : in… -
Jim Lewis replied to the topic OSVVM and Cadence Xcelium in the forum OSVVM 2 years, 2 months ago
Hi Steve,
Checking out the current version is on my todo list. The Xcelium team has our full regression suite so I would expect it all to be working at this point.I don’t think I introduced anything in the more current release that would cause Xcelium to stop working. But again, I hopefully will have a moment to test soon.
Best Regards,
Jim -
Jim Lewis replied to the topic .gitmodules File in the forum OSVVM 2 years, 2 months ago
Hi Ryan,
Thanks. It will be updated no later than the 2022.10 release.Best Regards,
Jim -
Jim Lewis replied to the topic Synopsys VCS-MX in the forum OSVVM 2 years, 2 months ago
Hi Antonio,
I should be able to look into it shortly too. Also if it is a TCL error, you may need to update your TCL version.Cheers,
Jim -
Jim Lewis wrote a new post 2 years, 3 months ago
Summary of recent changes in OSVVM:
Scripts updated for better signaling to continuous integration (CI) tools
MemoryPkg updated to remove 31 bit limitation and support storage policies.
Reports keep […]
-
Ha, very nice.
In my current system test bench of a AXI-QDMA Interface I model memory using my own dictionary implementation. First I used plain `std_logic_vector`, but it became slower & slower with increasing writes to new addresses in the dict. Then I’ve remembered that integers are “faster” than values with 9-state logic. So I’ve done something similar to your MemoryPkg, using an `integer_vector(0 to 1)` to store 64-bit wide `std_logic_vector` values, and also using integers for the address in the dictionary.
I’ve looked into an older version of your MemoryPkg before, which was limited to 31 bit – which was the reason for my own memory implementation. Now that this restriction is gone, it’s maybe finally time to try OSVVMs MemoryPkg.
Greetings,
Torsten
-
-
Jim Lewis replied to the topic Standard messaging feature in OSVVM? in the forum OSVVM 2 years, 3 months ago
See OSVVM’s AlertLogPkg for today’s answer to this question
-
Jim Lewis replied to the topic 31 bit maximum data width for memory package in the forum OSVVM 2 years, 4 months ago
Hi Michael,
New version is release as 2022.08. MemoryPkg is now a generic package.Instance MemoryPkg (and MemoryPkg_X) support any number of bits. If there is an X or U in a bit in the data word, only that bit will read back as an X or U (respectively).
Instance MemoryPkg_NoX supports any number of bits. All meta values (UXZW-) are…[Read more]
-
Jim Lewis replied to the topic New to OSVVM / problem running the example in the forum OSVVM 2 years, 4 months ago
Hi Phil,
I just installed 2020.3 Microsemi edition. I have a Libero Silver 1 Yr DiskID NL License. It runs the demo fine.With some of the older OSVVM versions a space in the path was problematic, however, that was addressed in a previous release.
Best Regards,
Jim -
Jim Lewis replied to the topic Expected failures in custom VC based on AddressBusRecType in the forum OSVVM 2 years, 4 months ago
Hi Per,
As you have noted, unlike StreamRecType, AddressBusRecType does not have a params field.What I do in the Axi4Manager VC is use SetModelOptions to set an WB_ERR expected and a WB_RTY expected – sometimes coded together, sometimes coded separately. The AXI4 response codes that need to be checked are BRESP and RRESP. The way we check…[Read more]
-
Jim Lewis replied to the topic New to OSVVM / problem running the example in the forum OSVVM 2 years, 4 months ago
Hi Phil,
Which OSVVM release are you running? What does the output say?Can you email me a copy of the sim/log/ModelSim-2020.3/OsvvmLibraries_RunDemoTests.log and the OsvvmRun.yml. My email is jim at SynthWorks.com
Best Regards,
Jim -
Jim Lewis replied to the topic 31 bit maximum data width for memory package in the forum OSVVM 2 years, 4 months ago
Hi Michael,
Testing a solution on the dev branch of OSVVM. I am thinking it will be ready shortly – I am thinking Monday.Best Regards,
Jim -
Jim Lewis replied to the topic 31 bit maximum data width for memory package in the forum OSVVM 2 years, 4 months ago
Hi Michael,
For Axi4Memory subordinate, I made the memory byte wide and wrote each byte separately. That made handling byte enables easy. However, it does not make reading a memory file easy.I have plans to rewrite the storage aspect so it can be more flexible in both sizes and policies. Currently the policy is if there is an X, make all…[Read more]
-
Jim Lewis started the topic 2022.06a is Released in the forum OSVVM 2 years, 4 months ago
2022.06a was just released. It addresses an issue when creating the HTML based log file. The variable TestCaseName was a local to Log2Html when it needed to be a variable.
-
Jim Lewis wrote a new post 2 years, 5 months ago
Summary of Changes in 2022.06
Scripting: At build completion, print single-line, text-based build summary
Scripting: Improved Error Handling. (continuing from 2022.05)
Scripting: Updated HTML log […]
-
Jim Lewis started the topic failed: wrong # args: should be "Simulate2Html … in the forum OSVVM 2 years, 5 months ago
Just a quick note. Another user was running a test case and ended up
with the following message:# ** Error: simulate For tcl errorInfo, puts $::osvvm::SimulateErrorInfo
# ** Error: simulate 'TbDpRam_BasicReadWrite ' failed: wrong # args: should be "Simulate2Html TestCaseName TestSuiteName"There are actually two errors here.
1) The TCL…[Read more] -
Jim Lewis replied to the topic SpaceWire VC in the forum OSVVM 2 years, 5 months ago
Hi Michael,
I looked at this a little bit in the past.The approach to modeling here requires thinking about the interface side (the handlers), the internal control side (for initialization and other tasks), and the transaction side (here TX and RX). I think in TestCtrl, transactions for TX and RX still need to be able to be dispatched…[Read more]
- Load More