mastrick

I believe the UVM intent of is to associate the (whole) signal "IP.REG.regout" with the 16 bits starting at offset 16 of the data in the reg model. The start and offset do not affect the signal, and so you do need to provide the bit range as you show to associate a slice of the signal with a slice of the internal data. I agree the documentation does not make that clear, and I have filed a Mantis to improve that documentation.

Thanks for posting this issue Rolko. The "else ret_val = 1" is a bug in 1800.2-2017-0.9. It is removed in 1800.2-2017-1.0, a release which was approved last week by the committee and should be available for download very soon.

Anil, The UVM committee knows of this limitation but our workaround suggestion would be exactly what you are doing with creating duplicate maps. A fix is on our to-do list. Thanks for posting, Mark

Thank you for posting Chintan. I see the 1800.2-2017 standard says in "8.3.1.4.1 set_inst_override_by_type and set_inst_override_by_name": That says to me that when you gave your original commands to override master_base_seq twice with different override types, the first one should be applied, just as you saw. The set_type_override variations include a "replace" argument that controls whether the new or the older override has priority, so it can work either way.

The problem is that your example code has the constraint block c_addr with "addr>=1000" but addr is an 8-bit field and so could not hold a value of 1000 or greater.

When you set the default_sequence in uvm_config_db, you specify the phase in which the driver will start the sequence. Just with that specification, you can run the sequence in any phase. get_starting_phase() and set_starting_phase() refer to a phase that will be objected to by the automatic phase objection feature of uvm_sequence. The default value for that starting_phase is the phase in which the sequence gets started (what you specified to the uvm_config_db).

Strangely enough, we have just encountered this issue for the first time today. Thanks Robert for posting! In our case, the nested class does not use the field macros but rather calls uvm_report_info directly. We use nested class in this case because this class is used as a replacement class in the test, and to allow us to compile all tests in one executable without conflict, we require such classes to be nested within the test class that uses it. Guess I'll file a mantis to see if the implementation can tolerate such usage.

I believe you want your test sequence to object to main_phase so that you will not have the physical sequence ended before the test sequence ends.

Also, you might want to keep your randomize() call outside the assert(). Otherwise, simulators may not call the randomize at all if you disable assertions (e.g. to temporarily work around a problem). You can assign the return from randomize() to a variable and then assert that variable.

Hi Dave, If you just had "c.a = 10; p.c = c;", you would certainly expect c.a (and p.c.a) to be 10 afterwards. I think the question is why p.randomize(c. does not mean that c.a is a state variable, so it is still 10 after the randomize. Mark

I would expect that is an expected usage model and I have filed Mantis 5529 https://accellera.mantishub.com/view.php?id=5529 againstthe current IEEE standardization effort.

You are correct. That is Mantis 4427, whose fix did not get into the UVM 1.2 release.

If you are using run-time phasing, you simply need to have your environment start the init sequence in some phase before main (perhaps the configure phase), holding the objection until that sequence completes, and then tell test developers that they must run their sequences in main phase (which is the intent of main phase).

I have created a Mantis item to clarify the description of uvm_component_name_check_visitor.

Can you describe in more detail what you mean by "pre_reset_phase entering twice"? What are the signs?