• 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. xmvlog: *E,NOPBIND (../src/soc_tb_top.sv,46|20): Package...

Stats

  • Locked Locked
  • Replies 6
  • Subscribers 65
  • Views 12856
  • 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

xmvlog: *E,NOPBIND (../src/soc_tb_top.sv,46|20): Package soc_test_pkg could not be bound.

vujaclyn
vujaclyn over 4 years ago

file: soc_tb_top.sv

`include "soc_if.sv"

module soc_tb_top;
  import uvm_pkg::*;
  import soc_test_pkg::*;

....

endmodule

Here is my Makefile:

 xrun -uvmhome $(UVM_LIB_PATH) -uvm -64BIT +incdir+../src +incdir+../sim +incdir+../tests ../src/soc_tb_top.sv -seed $(SEED) -access +rwc ../src/soc_tb_top.sv

Here is my soc_test_pkg.sv

package soc_test_pkg;
  import uvm_pkg::*;
  import soc_env_pkg::*;
  `include "uvm_macros.svh"

  `include "soc_base_test.sv"
  
endpackage

This compilation error shouldn't happened. This is very straight forward testbench flow. Please help as I have been debugging for 3 days now.

  • Cancel
Parents
  • vujaclyn
    vujaclyn over 4 years ago

    @muffi, thank you for your suggestion. I've added as below:

    xrun -uvmhome $(UVM_LIB_PATH) -uvm -64BIT +incdir+../src +incdir+../sim +incdir+../tests ../src/soc_tb_top.sv -seed $(SEED) -access +rwc ../tests/soc_test_pkg.sv ../src/soc_tb_top.sv

     

    Now getting this ERROR:

    TOOL: xrun(64) 20.03-s008: Started on Oct 19, 2020 at 10:58:29 PDT
    file: ../tests/soc_test_pkg.sv
    import uvm_pkg::*;
    |
    xmvlog: *E,NOPBIND (../tests/soc_test_pkg.sv,10|15): Package uvm_pkg could not be bound.
    import soc_env_pkg::*;

    Now it's complaining about uvm_pkg could not be bound. Please help!!

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • vujaclyn
    vujaclyn over 4 years ago in reply to vujaclyn

    Here is the correct xrun cmd:

    xrun -uvmhome $(UVM_LIB_PATH) -uvm -64BIT +incdir+../src +incdir+../sim +incdir+../tests -seed $(SEED) -access +rwc ../tests/soc_test_pkg.sv ../src/soc_tb_top.sv

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • muffi
    muffi over 4 years ago in reply to vujaclyn

    What does ${UVM_LIB_PATH} point to? If you are using the UVM library from the Xcelium installation, you can use the option "-uvmhome CDNS-1.2" or "-uvmhome CDNS-1.1d".

    UNIX> xrun -uvmhome CDNS-1.1d -64BIT +incdir+../src +incdir+../sim +incdir+../tests -seed $(SEED) -access +rwc ../tests/soc_test_pkg.sv ../src/soc_tb_top.sv

    Do take a look at the following article on COS for more information on how to use the UVM library:

    FAQ: Frequently Asked Questions related to the UVM library, methodology, learning resources

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • vujaclyn
    vujaclyn over 4 years ago in reply to muffi

    Thank You for your help, really appreciated. Yes, UVM_LIB_PATH points to CDMS-1.2. I'm able to compile now, I have to add the following code for all packages which import uvm_pkg:

    `ifndef MY_PKG_EXCLUDE

    `define MY_PKG_EXCLUDE

      `include "uvm_pkg.sv"

    `endif

    ........ 

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • vujaclyn
    vujaclyn over 4 years ago in reply to muffi

    Thank You for your help, really appreciated. Yes, UVM_LIB_PATH points to CDMS-1.2. I'm able to compile now, I have to add the following code for all packages which import uvm_pkg:

    `ifndef MY_PKG_EXCLUDE

    `define MY_PKG_EXCLUDE

      `include "uvm_pkg.sv"

    `endif

    ........ 

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
  • muffi
    muffi over 4 years ago in reply to vujaclyn

    You don't need the "`include "uvm_pkg.sv". In fact it will cause checksum issues and DLCSMD error if MY_PKG_EXCLUDE is defined, and you use -uvmhome or -uvm options. Packages are generally compiled and imported where needed. You should avoid tick including them.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

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