- 1. What domains are in the environment? What units do they contain?
- 2. What phase is running now?
- 3. Why are we still in this phase? Which activity is still running, and blocking us from proceeding?
- 4. ... and more...
Notice that from the output of this command, we can learn the following:
- The unit env_a is running the blocking thread tf_main_test.
- There is also a blocking sequence: my_seq-@7.
- As you can see, there are also blue hyper links to the sources of the two blocking threads
It may happen that a domain had finished all its current phase activities, but is not proceeding to the next phase, because it waits for a domain it depends on. The show domain command gives this information.
In the following screenshot example, the ENV_B_DOMAIN completed its FINISH_TEST phase activities, but waits for ENV_A_DOMAIN to finish its FINISH_TEST activities before it can proceed to the next phase.
To display all defined dependencies at any time during the test, you use the show dependencies command. The following show dependencies screenshot example lists these dependencies between the three domains defined in this environment:
Read more about Testflow, defining domains activities and domains dependencies, in the UVM e Reference Manual.
Enjoy verification!Efrat Shneydor,
UVM e