• 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. Hierarchical reference not allowed from within a package...

Stats

  • Locked Locked
  • Replies 5
  • Subscribers 64
  • Views 22271
  • 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

Hierarchical reference not allowed from within a package.

archive
archive over 18 years ago

Hi All,
We are trying this kind of example. We are having two files of these. It's giving  "Hierarchical reference  not allowed from within a package." at    class1_instance.class1_function(.....)     class2_instance.class2_function(......)

I tried passing both classes as members of a structure. but it giving same error when accessing member class functions from structure.

What's the solution to access functions of these classes in Program main Blocks.

file1.sv
_______________________

program main;

class1 class1_instance;
class 2 class2_instance;
initial begin
    class1_instance=new;
    class2_instance=new;
    call_task_from_other_file(class1_instance, class2_instance);
end
endprogram


file2.sv
________________________
task call_task_from_other_file(class1 class1_instance, class2 class2_instance);
    class1_instance.class1_function(.....)
    class2_instance.class2_function(......)
endtask




Regards
Mayank


Originally posted in cdnusers.org by mayank
  • Cancel
Parents
  • archive
    archive over 18 years ago

    Hello Mayank,

    I looked at your second code example. IUS does not yet support declaring tasks/functions in the global space but you would be able to declare the forked_task task in the top module, the main program or in a package. The other issue I see with your code example is that the main program must use an initial block to call the forked_task.

    I hope this helps!

    Kathleen Meade

    Here is a modified version of your second code example that works on the IUS5.83-s3 release:

    interface intf1 (input logic clk);
    endinterface

    program main (intf1 intf1_instance);
    initial forked_task();
    endprogram

    module dut (intf1 intf1_instance);
    task dut_task;
    $display("I am in dut_task");
    endtask
    endmodule

    module top;
    reg clk;
    intf1 intf1_instance (clk);
    dut dut_instance (intf1_instance);
    main main_instance (intf1_instance);
    // this task can be declared in the program, the top module or in a package.
    task forked_task();
    dut_instance.dut_task;
    endtask
    endmodule


    Originally posted in cdnusers.org by kameade
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • archive
    archive over 18 years ago

    Hello Mayank,

    I looked at your second code example. IUS does not yet support declaring tasks/functions in the global space but you would be able to declare the forked_task task in the top module, the main program or in a package. The other issue I see with your code example is that the main program must use an initial block to call the forked_task.

    I hope this helps!

    Kathleen Meade

    Here is a modified version of your second code example that works on the IUS5.83-s3 release:

    interface intf1 (input logic clk);
    endinterface

    program main (intf1 intf1_instance);
    initial forked_task();
    endprogram

    module dut (intf1 intf1_instance);
    task dut_task;
    $display("I am in dut_task");
    endtask
    endmodule

    module top;
    reg clk;
    intf1 intf1_instance (clk);
    dut dut_instance (intf1_instance);
    main main_instance (intf1_instance);
    // this task can be declared in the program, the top module or in a package.
    task forked_task();
    dut_instance.dut_task;
    endtask
    endmodule


    Originally posted in cdnusers.org by kameade
    • 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