• 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. cannot find urm_defines.svh

Stats

  • Locked Locked
  • Replies 8
  • Subscribers 67
  • Views 18280
  • 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

cannot find urm_defines.svh

rashmikant
rashmikant over 16 years ago

Hi all,

I am a little new to Cadence tools and am using ncverilog for my research purpose.

I am trying to compile system verilog files where I have included urm_defines.svh for some purpose.

But I am getting an error saying it cannot open the include file urm_defines.svh.

 can you give a hint as to what I am missing here? I am sure i am missiing something dumb here.

I am using cadence on my university license. Let me know if you want anyother information.

Btw, i am using ncverilog 05.83-s002 (ius-5.8)

 

Another problem I am facing is that I have made some package files and have used them to build the top-level but I am getting error while importing the package files too and gives an error: urm_util_pkg (and some other user-defined packages too) could not be bound.

Thanks a lot,

Rashmikant

  • Cancel
  • Mickey
    Mickey over 16 years ago

    Do you have a -incdir option included on your command line that indicates the directory where the urm_defines.svh file is found?

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • rashmikant
    rashmikant over 16 years ago

    If I add -incdir  option to the command line then I get a set of errors which shows there are errors in declaration of packages along wth other set of errors. for eg:

    package urm_util_pkg;
               |
    ncvlog: *E,EXPMPA (urm_util_pkg.sv,24|6): expecting the keyword 'module', 'macromodule' or 'primitive'[A.1].

    module ab_bus_slave_bfm_m( interface dut_if,
                                                                       |
    ncvlog: *E,EXPRPA (ab_bus_slave_bfm.sv,21|43): expecting a right parenthesis (')') [12.1(IEEE)].

    import urm_util_pkg::*;
                                 |
    ncvlog: *E,EXPLPA (ab_bus_slave_bfm.sv,24|19): expecting a left parenthesis ('(') [12.1.2][7.1(IEEE)].

    import ab_bus_pkg::*;
                               |
    ncvlog: *E,EXPLPA (ab_bus_slave_bfm.sv,25|18): expecting a left parenthesis ('(') [12.1.2][7.1(IEEE)].

     ................

    And I think the declaration and code looks fine..I think from the first error it looks like it didnt recognize the keyword "package".. I still have the empty/illegal list of parameters error if i include -incdir option. But the "compilation unit top scope declaration" error goes away.

     

    I have created a urm_defines.svh file in my folder and have included it while compiling along with other .sv files. Now if I dont include -incdir option, then I get only two kinds of errors:For eg:

    ncvlog: *E,SVNIMP (abc_parameters.vh,314|20): SystemVerilog construct not yet implemented:  compilation unit top scope declaration.
    parameter TJIT_PER         =     100; // tJIT(per)  ps    Period JItter

    ncvlog: *E,NULLPP (abc_port.sv,13|39): empty/illegal list of parameters [12.1(IEEE-2001)].
                        SUB_SYSTEM_INSTANCES = 1,

    These errors are repeated for all parameters I have for one particular compile-time configuratio. And they are not the same set of parameters in both the files.

    Let me know if you need more information. These errors are generated when I use only +sv option in the command line while compiling through ncverilog.

     Thanks,

    Rashmikant

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Mickey
    Mickey over 16 years ago

    Sounds like the problem is that the compiler is not parsing for systemverilog.

    if you are using irun, is the file extension of the systemverilog files .sv, or something else?

    if you are using ncvlog, try adding -sv to your compile command line.

    if you are using ncverilog, try adding +sv to your command line.

    let me know if that helps.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • rashmikant
    rashmikant over 16 years ago

    Thanks for the quick reply..

    I get same set of errors with ncvlog by adding -sv option.

    I already have +sv added to the command line and all my systemverilog files have .sv extension. Parameters file have .svh.

    I am running this command:

    ncverilog +sv $(SIMFILES)

    which gives me my previous post's errors..

     

    Thanks,

    Rashmikant

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Mickey
    Mickey over 16 years ago

    it's hard to determine the problem.  Can you send the code you are trying to compile along with the command line you are using?  feel free to send it to my email address (jrodrig@cadence.com)

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • verifs
    verifs over 14 years ago

    Hi Rashmikant,

    I know this response is very late since the post is from last year, but even i was facing the same problem (SV construct not yet implemented) and so I stumbled upon this post while searching for a solution on the internet.

    I am sure you must have figured it out by now, but I would still like to share my experience here for someone else who might be facing the same problem.

    It was mainly because of the tool version. I was using 6.2 ius004 which didnt support a few SV constructs that I was using. The problem was solved when i switched to version - 8.2 ius - s017 of the tool.

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • susharma
    susharma over 10 years ago
    Hello Team, I am facing the same issue while using the "irun 10.2c". The error i am getting is: file: /home/chandra/uvm-1.2/src/uvm_pkg.sv
    `define uvm_info_begin(ID, MSG, VERBOSITY, RM = __uvm_msg) `uvm_message_begin(UVM_INFO, ID, MSG, VERBOSITY, `uvm_file, `uvm_line, RM)
    |
    ncvlog: *E,EXPRPP (/home/chandra/uvm-1.2/src/macros/uvm_message_defines.svh,295|46): expecting a right parenthesis to close the formal arguments to a macro [16.3.1(IEEE)]. Please help me in this regard. Regards sunil.
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • StephenH
    StephenH over 10 years ago
    Sunil, there is no such version of Incisive as "10.2c" so I'm not sure what you're doing :) It's most likely however that you need to update to a newer Incisive version for better SystemVerilog support. Try using 14.20 for the latest features.
    • 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