I have a Configuration locking register field in which writing 1 locks the configuration and writing 0 has no effect until unless a reset is called.
I ran the built-in bit bash sequence on the Register model & this register bit is throwing an error since 0 cannot be written into the field as 1 is already written how to mitigate this issue. since I cannot make changes to the RAL Model.
In reply to vErif_Guy_pxn:
Turn off access with the following example for the ctrl register.
uvm_resource_db#(bit)::set({"REG::", rm.ctrl.get_full_name()},
"NO_REG_TESTS", 1, this);
uvm_resource_db#(bit)::set({"REG::", rm.ctrl.get_full_name()},
"NO_REG_BIT_BASH_TEST", 1, this);