• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Functional Verification
  3. Error when combining AXI UVC and AHB UVC

Stats

  • Locked Locked
  • Replies 2
  • Subscribers 65
  • Views 14232
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Error when combining AXI UVC and AHB UVC

Louis Gao
Louis Gao over 14 years ago

My testbench need both AXI UVC and AHB UVC. I can successfully run each of them. But when I try to integrate both UVCs into one testbench. I got the following error mesage:

irun: *N,OVMW: The use of the -ovm option will automatically suppress the following warnings
        PMBDVX
        BIGWIX
.
Compiling UVC core code. Please wait ....................
Compiling vr_axi 09.20.003-s ...............
Compiling vr_ahb 09.20.003-s
Linking. This may take a few minutes ...............

irun: *E,SNLDRN: A failure occurred while trying to generate internal simulation files using the dynamic specman library
.....

        1 check was modified.
        1 check was modified.
        1 check was modified.
           *** Error: Items used with per_instance option must be gradable. line 1490
        in @vr_axi_coverage

In my top module file, the "vr_axi_top.sv" and "vr_ahb_top.sv" are included.

`include "vr_axi_top.sv"
`include "vr_ahb_top.sv"

module vr_amba_top_tb();
   import ovm_pkg::*;
 ...

endmodule

Here is the content of the UVC top file "vr_axi_top.sv":

`ifndef OIG_VR_AXI_TOP
`define OIG_VR_AXI_TOP

// pragma oig_irun top_e_files = vr_axi/e/api/ovm/sv_generated_api/vr_axi_ovm.e
// pragma oig_irun oig_params = -uvc_name vr_axi -version 08.20.002-s -eexp vr_axi/misc/vr_axi_cb_ovm.eexp -e_file vr_axi/e/api/ovm/vr_axi_ovm_top.e -base_name vr_axi

`include "ovm_macros.svh"
`ifndef OVM_MB_DEFINES_SVH
   `define SN_SV_MP_OVM_OPEN_SOURCE
`endif

`include "vr_axi_defines.sv"
`include "vr_axi_dut_intf.svh"
`include "vr_axi_extensions.svh"
`include "vr_axi_classes.svh"

`endif

Here is the content of "vr_ahb_top.sv":

`ifndef OIG_VR_AHB_TOP
`define OIG_VR_AHB_TOP

// pragma oig_irun top_e_files = vr_ahb/e/api/ovm/sv_generated_api/vr_ahb_ovm.e
// pragma oig_irun oig_params = -uvc_name vr_ahb -version 08.20.002-s -eexp vr_ahb/misc/vr_ahb_cb_ovm.eexp -e_file vr_ahb/e/api/ovm/vr_ahb_ovm_top.e -base_name vr_ahb


`include "ovm_macros.svh"
`ifndef OVM_MB_DEFINES_SVH
   `define SN_SV_MP_OVM_OPEN_SOURCE
`endif

`include "vr_ahb_defines.sv"
`include "vr_ahb_dut_intf.svh"
`include "vr_ahb_extensions.svh"
`include "vr_ahb_classes.svh"

`endif

I guess there might be some conflicts of the pragmas. Who can help me on this issue?

Thanks very much in advance.

  • Cancel
Parents
  • Louis Gao
    Louis Gao over 14 years ago

    Hi Steve,

    You're correct. This problem is really related to the bus ID width VR_AXI_MAX_ID_WIDTH.

    The ID width of my design is 13-bit. So I set VR_AXI_MAX_ID_WIDTH=13. The large number resulted the failure. When I reduce it to VR_AXI_MAX_ID_WIDTH=4, my simulation works.

    But the  "-defineall VR_AXI_LARGE_ID" doesn't work for the VIP version I'm using 09.20.003.

    I plan to upgrade to 09.20.005 or higer version.

    Thank you very much.

    Louis

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • Louis Gao
    Louis Gao over 14 years ago

    Hi Steve,

    You're correct. This problem is really related to the bus ID width VR_AXI_MAX_ID_WIDTH.

    The ID width of my design is 13-bit. So I set VR_AXI_MAX_ID_WIDTH=13. The large number resulted the failure. When I reduce it to VR_AXI_MAX_ID_WIDTH=4, my simulation works.

    But the  "-defineall VR_AXI_LARGE_ID" doesn't work for the VIP version I'm using 09.20.003.

    I plan to upgrade to 09.20.005 or higer version.

    Thank you very much.

    Louis

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
No Data

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information