ERROR : Object found for name dut.register but language domain is not supported !!

I'm guessing that you're talking about UVM_REG, and that your register in the RTL is in VHDL, correct?

In this case, it would help if you switched to UVM 1.2, because the backdoor access code is written in DPI-C, and in UVM 1.1, that C code didn't support VHDL, it only knew how to access Verilog data types. Starting with UVM 1.2 the DPI C backdoor code can access VHDL data types as well.

If that doesn't answer your question, please reply with more precise details of the setup you have.

Regards,

Steve.

Hello Stephen,

thank you for your message. I tried to change from UVM1.1 to UVM1.2 using -uvmhome option. I get the following compiling error.  

Here are the details:

Compiling UVM packages (uvm_pkg.sv cdns_uvm_pkg.sv) using uvmhome location /opt/comware/share/sv_packages/external/uvm/uvm-1.2
m_handles[stream]=1;
|
ncvlog: *E,UNDIDN (/opt/INCISIV_14.10.011/CEN/tools/methodology/UVM/CDNS-1.1d/additions/sv//cdns_recording.svh,79|16): 'm_handles': undeclared identifier [12.5(IEEE)].
ncvlog: *F,MAXERR: maximum error count reached (1).
irun: *E,VLGERR: An error occurred during parsing. Review the log file for errors with the code *E and fix those identified problems to proceed. Exiting with code (status 2).
irun: *E,UVMCXF: The process to compile the uvm extensions has failed. Add -uvmnocdnsextra to disable the addon package or point to the right version using -uvmexthome.
gmake: *** [execute] Error 1
[INFO] Finished 'execute' with errors! (status = 2)

Could you please help me out here?

Thank you. 

Hi Vidya.

Can you try using the Cadence-supplied version of UVM? "irun -uvmhome CDNS1.2".

What seems to be happening in your case is that you're using UVM 1.2 from another path, and irun is picking up the Cadence add-ons (transaction recording in this case) that are desigend for UVM 1.1d. Using the Cadence 1.2 install would certainly solve this, though if you have to use the other install I'm sure there's a way to tell irun to pick up the add-ons from the 1.2 directory. That would not be my preferred solution though.

Regards.