Jim Lewis
-
Jim Lewis replied to the topic Pre Compiled OSVVM Libraries in the forum OSVVM 1 year, 5 months ago
Did you read: https://osvvm.org/archives/2280
One of the examples is precompiling OsvvmLibraries and then linking to them. Let me know if that answers your questions.
-
Jim Lewis wrote a new post 1 year, 5 months ago
Working with VHDL Libraries in OSVVM
Abstract Small projects may use a single library for all aspects of the project. As projects increase in size separating different chips into separate V […]
-
Jim Lewis wrote a new post 1 year, 5 months ago
OSVVM EventsUpcoming OSVVM conference/webinar and training classes: September 14 OSVVM in a NutShell, VHDL’s #1 Verification Methodology at Verification Futures C […]
-
Jim Lewis replied to the topic Limitation using MemoryPkg in the forum OSVVM 1 year, 6 months ago
Hi Jorge,
I just came across this again. This issue was addressed in release 2022.08. MemoryPkg now supports data words of any width. A couple of different implementations of MemoryPkg are provided via generic instances). The instance MemoryPkg (and MemoryPkg_X) stores data and X/U’s. The instance MemoryPkg_NoX stores only data and X’s are…[Read more] -
Jim Lewis wrote a new post 1 year, 7 months ago
Requirements Tracking with OSVVM, Part 2
OSVVM release 2023.07 updates OSVVM’s Requirement Tracking (aka Specification Tracking) capability so that HTML and CSV based merged requirements reports a […]
-
Jim Lewis wrote a new post 1 year, 7 months ago
OSVVM 2023.07 Release
Summary of 2023.07 Changes AlertLogPkg: Added WriteRequirementsYaml to write requirements for a test case into a YAML file ReportPkg: In […]
-
Jim Lewis replied to the topic Learning OSVVM with AXI4 in the forum OSVVM 1 year, 7 months ago
Hi Joseph,
A pro file is tcl plus a procedure abstraction layer that replaces the calls to vlib, vmap, vcom, vlog, and vsim with library, LinkLibrary, analyze, analyze, and simulate (respectively).Sounds like your do file is fairly complicated. Not sure if you can successfully transition it or not. However, here is how to try to do…[Read more]
-
Jim Lewis replied to the topic Learning OSVVM with AXI4 in the forum OSVVM 1 year, 7 months ago
Hi Joseph,
The coverage controls work in a coordinated fashion with the OSVVM scripts that analyze and simulate the design. How about posting your do file – or a representative piece of it and I can suggest how to update it to use the OSVVM script API instead – it is actually quite a bit simpler than using the vendor commands directly.For…[Read more]
-
Jim Lewis wrote a new post 1 year, 8 months ago
OSVVM 2023.05 Release
Summary of 2023.05 Changes Co-simulation updates Added split transaction methods for address bus model independent manager Added […]
-
Jim Lewis replied to the topic Writing a Test Plan, Identifying Transactions, and Documenting BFMs/MIT in the forum OSVVM 1 year, 8 months ago
Hopefully this gets the topic started. Hopefully others will comment too. It is a long topic and I probably missed some things. I may have an entirely different perspective than others.
-
Jim Lewis replied to the topic Writing a Test Plan, Identifying Transactions, and Documenting BFMs/MIT in the forum OSVVM 1 year, 8 months ago
Documenting a Verification Component needs to address
- What does the VC need to do
- How do I use the VC
- What transactions does the VC support
I note that the Axi4_VC_users_guide in OsvvmLibraries/Documentation primarily addresses the last two. Rather than addressing the first one, it assumes that is must support all operations on the AXI4…[Read more]
-
Jim Lewis replied to the topic Writing a Test Plan, Identifying Transactions, and Documenting BFMs/MIT in the forum OSVVM 1 year, 8 months ago
Why Randomize
Our goal is to thoroughly test a design. For some designs, directed testing will get the job done.For some designs, there are too many variations to be able to test every variation in the system. Variations can be a multiplying factor in testing a design. If the design can limit the variations in the system, the system can…[Read more]
-
Jim Lewis replied to the topic Writing a Test Plan, Identifying Transactions, and Documenting BFMs/MIT in the forum OSVVM 1 year, 8 months ago
Implementing Transactions
The behavior of a transaction can either be implemented in a verification component (VC) or in the subprogram body (as SendCmd above suggests). Note the acronym BFM means bus functional model and can refer to either a VC or subprogram body. BFM means the model implements only the interface behavior and not internal…[Read more] -
Jim Lewis replied to the topic Writing a Test Plan, Identifying Transactions, and Documenting BFMs/MIT in the forum OSVVM 1 year, 8 months ago
Lets address, 2. Identifying Transactions:
A transaction is an abstract representation of an atomic action on an interface. For a UART transmitter, it is sending one word on the interface. For an Axi4Lite interface, it is Write and Read operations on the interface.
For the simple interface we look at in our Comprehensive VHDL…[Read more]
-
Jim Lewis replied to the topic Writing a Test Plan, Identifying Transactions, and Documenting BFMs/MIT in the forum OSVVM 1 year, 8 months ago
Hi Dave,
I suspect a proper response to this may end up being a couple of blog posts in length. Lets start with a couple of references:Comprehensive Functional Verification by Bruce Wile, John Goss, and Wolfgang Roesner covers test plans. I have not read the whole book. It is on my some day maybe list.
Peet James Snug 2000 paper on…[Read more]
-
Jim Lewis replied to the topic Configuring the AXI-Lite WSTRB in the forum OSVVM 1 year, 8 months ago
The X”DEADBEUU” you are seeing is due to the masking of the lower byte.
-
Jim Lewis replied to the topic Configuring the AXI-Lite WSTRB in the forum OSVVM 1 year, 8 months ago
Hi Adam,
If you are using the OSVVM Axi4Lite VC, the best way to get word addresses is to just throw away the lower address bits and do full word writes to the interface. Hence, the transaction calls would still use the addresses X”0000″, X”0004″, X”0008″, …, but since you are throwing away the lower two address bits, the memory would see it…[Read more] -
Jim Lewis replied to the topic Configuring the AXI-Lite WSTRB in the forum OSVVM 1 year, 8 months ago
Hi Adam,
Is your question, how do you connect AXI4 up to a memory that only supports word addressing? The memory would ignore the lower bits of address that correspond to the byte addresses and it would ignore strb totally. If there is a write data operation as signified by Valid and Ready, then all 32 bits get written into memory. There is…[Read more] -
Jim Lewis replied to the topic Configuring the AXI-Lite WSTRB in the forum OSVVM 1 year, 8 months ago
Hi Adam,
I am not sure what that means. What are you trying to do? In Axi4Lite, strb is a byte strobe that indicates the corresponding 8 bits is part of the write. The strb will be active when Valid is active. This may be multiple clock cycles if Ready is not also active.Does the dpRAM only accept full 32 bit writes? Maybe this device…[Read more]
-
Jim Lewis replied to the topic Learning OSVVM with AXI4 in the forum OSVVM 1 year, 8 months ago
Hi Adam,
The AxiStreamTransmitter and AxiStreamReceiver both have randomization in them. There is a corresponding test case that has good examples in it, TbStream_SendGetRandom1.vhd. You can find it in OsvvmLibraries/AXI4/AxiStream/TestCases. It was just updated (meaning just before this post) to better show the different use models for…[Read more] - Load More