Delay one clk cycle when driving at posedge
|
|
4
|
26
|
May 14, 2025
|
Parallel sequences for read & write together in axi4 lite protocol
|
|
0
|
53
|
February 13, 2025
|
Multiple sequencers with single driver
|
|
2
|
727
|
June 4, 2023
|
My UVM testbench is stuck at monitor
|
|
2
|
1050
|
November 7, 2021
|
Uvm_driver of Request-ack protocol handshake
|
|
4
|
1753
|
July 4, 2021
|
Ending a Test in Uvm
|
|
1
|
861
|
April 23, 2021
|
Why are we driving the read data after two clocks in driver and monitor of a simple memory design?
|
|
1
|
1088
|
March 29, 2021
|
Passing field_name of the virtual interface to the driver via constructor
|
|
1
|
704
|
December 14, 2020
|
Drive at most N consecutive items to the DUT
|
|
1
|
807
|
September 8, 2020
|
Driver data not getting propagated to the DUT
|
|
5
|
1490
|
May 5, 2020
|
Why function new() is used in derived class in UVM testbench?
|
|
1
|
1124
|
April 20, 2020
|
UVM driver does not drive a component of the interface
|
|
5
|
1974
|
July 20, 2019
|
Sending value from a dynamic array of size 512 to DUT with data width of 32 bit
|
|
3
|
2556
|
August 17, 2017
|
UVM agent topology for request and response interfaces
|
|
3
|
2226
|
January 23, 2017
|
Modeling pipelined out of order transaction driver in UVM for AXI 4.0
|
|
5
|
7030
|
December 23, 2016
|
Variable data lengths in monitor
|
|
0
|
1488
|
March 5, 2015
|
Why UVM driver as non-blocking structure
|
|
0
|
1528
|
July 10, 2014
|