Does UVM IEEE supports "uvm_path_e"?

UVM
,
1

Does UVM IEEE supports “uvm_path_e” ?

Iam observing syntax error
rror-[SE] Syntax error
Following verilog source has syntax error :
token ‘uvm_path_e’ should be a valid type. Please declare it virtual
if it is an Interface

2

In reply to abhilash.20:

Does UVM IEEE supports “uvm_path_e” ?
Iam observing syntax error
rror-[SE] Syntax error
Following verilog source has syntax error :
token ‘uvm_path_e’ should be a valid type. Please declare it virtual
if it is an Interface

By looking at the 2017 IEEE code I can see the following:

// Variable -- NODOCS -- default_path
   // Default access path for the registers and memories in this block.
`ifdef UVM_ENABLE_DEPRECATED_API
   uvm_door_e      default_path = UVM_DEFAULT_DOOR;
`else
   local uvm_door_e default_path = UVM_DEFAULT_DOOR;
`endif

So it looks it has been deprecated/replaced by uvm_door_e. This example may help you

HTH,

-R

3

In reply to abhilash.20:

Hey i believe is still supported since ral model does support uvm path as backdoor user and not user and frontdoor

4

In reply to Rsignori92:

In reply to abhilash.20:
Hey i believe is still supported since ral model does support uvm path as backdoor user and not user and frontdoor

I think got changed as mentioned in this presentation slide 65

“uvm_path_e type became uvm_door_e
– UVM_DEFAULT_PATH  UVM_DEFAULT_DOOR”

-R

5

In reply to rgarcia07:

Oh i did not know that, is this uvm 1.2d?

6

In reply to Rsignori92:

It is the for UVM IEEE 2017, and 2020 standards