testbench | Laravel Testing Helper for Packages Development | Build Tool library

What you are asking for is exactly how the UVM sequence/driver mechanism works. The generator does not do any randomization until the driver is ready and asks for an item to drive.

But you can get close to what the UVM does simply by constructing your mailbox with a bound of 1. Then the put(trans) in the main loop blocks until after the driver has performed a get(). Then there will always be one transaction in the mailbox waiting for the next drive cycle.

You can use WebDriver Manager API. -It downloads the driver.exe to your /m2/repository/webdriver folder(while using Maven). It also automatically checks your browser version and download the matching version of driver.exe.

To use Webdriver Manager API, Include below lines in your pom.xml file:

In the testbench, you declared the result signal, but it is not connected to anything. You probably intended it to be driven by the alu output of the same name. In that case, you should connect it to the instance:

Change:

You have to convert datatypes. The simplest way that should work:

Instead of using force, a more conventional approach is to add a tristate buffer to the testbench, just like you have in the design.

For SDA, create a buffer control signal (drive_sda) and a testbench data signal (sda_tb). Use a task to drive a byte and wait for the ACK.

Since SCL is not an inout, there is no need for a pullup, and it can be directly driven by clk.

The decoder module has undriven output ports and unconnected input ports. Since your testbench uses bus signals for these, you might as well use bus ports:

I added $time to the $display statement, and this clearly showed that SDA was changing, but it was changing all at the same time (10):

In verilog, modules are not called, but instantiated. Unlike traditional programming, verilog is a hardware descriptive language; meaning it is code describing hardware, not specifying instructions to be run by a cpu as you do in typically programming languages. Hardware doesn't materialize and dematerialize when signals take on different values; the control signals simply define which of many different data paths is connected between input and output.

In your case, you wouldnt write something like this:

Are you only running mvn azure-webapp:deploy?

Make sure you run mvn package first, or mvn package azure-webapp:deploy. Otherwise it will just re-deploy the same WAR file. Include the -Pproduction flag if you want to run it in production mode.

Edit:

I set up a project myself and could reproduce your issue. After running mvn azure-webapp:config again twice and updating both Application and Runtime, it seems to work.

This did two changes to the pom.xml, try these out:

1. Add war under in the azure-webapp-maven-plugin.
2. Change jre8 to TOMCAT 9.0.