uvm_map configure does not add the map

[RasmusGOlsen]

When you configure a uvm_map, it is not added to the block specified as its parent. You must explicitly call add_map, although this is not part of the standard API.

import uvm_pkg::*;


class Reg extends uvm_reg;

    function new(string name, int width=32);
        super.new(name, width, UVM_NO_COVERAGE);
    endfunction

endclass


class Block extends uvm_reg_block;

    Reg a;
    uvm_reg_map map;

    function new(string name);
        super.new(name);
        this.a = new("a");
        this.a.configure(this, null, "");
        // this.map = this.create_map("map", 0, 4, UVM_LITTLE_ENDIAN, 0);
        this.map = new("map");
        this.map.configure(this, 0, 4, UVM_LITTLE_ENDIAN, 0);
        this.map.add_reg(this.a, 0, "RW", 0);
        // this.add_map(this.map);
    endfunction

endclass


module test;

    initial begin
        uvm_reg register;
        automatic Block block = new("block");
        block.lock_model();
        register = block.get_default_map().get_reg_by_offset(0);
        assert(register.get_name() == "a");
    end

endmodule

[mstrickland-mrvl]

We need to document add_map() as part of the LRM or create_map would need to be documented as the only way to do this. We will resolve.

[RasmusGOlsen]

This situation is curious, however.

• uvm_reg_field::configure adds itself to its parent.
• uvm_reg::configure adds itself to its parent.
• uvm_reg_block::configure adds itself to its parent.

None of these methods has the "add_*" function mentioned in the LRM, as everything is handled when you call configure. So, what makes uvm_reg_map different in this regard? It seems logical to follow the established pattern unless I've misunderstood something.
If uvm_reg_map::create_map is the only way to create a map, then the uvm_reg_map::configure method would become obsolete. However, if uvm_reg_map::configure can be used, does it make sense not to add it to its parent?