• 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. Calling VHDL procedures in SystemVerilog Testbench.

Stats

  • Locked Locked
  • Replies 14
  • Subscribers 64
  • Views 20031
  • 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

Calling VHDL procedures in SystemVerilog Testbench.

archive
archive over 18 years ago

Is there a way to call VHDL procedures in a SV TB without translating them into SV tasks.. ?


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

    DM,

    I don't knew, whether you have tried this or no, but you can go down to the hierarchy, to the module, from which the task is to be called, and map it at the top.

    Like:

    **************** Code Snippet ***************

    `define DUT top.i_module1

    module top();

    // your TB description

    // To invoke the task in module1

    initial begin
    'DUT.task-name; // "task-name" is the name of the task defined in module-1
    ...
    end

    // module instantiation

    mod-name module1 ( //port mapping );

    ******************************************************************

    This should work.

    - Vivek


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

    DM,

    I don't knew, whether you have tried this or no, but you can go down to the hierarchy, to the module, from which the task is to be called, and map it at the top.

    Like:

    **************** Code Snippet ***************

    `define DUT top.i_module1

    module top();

    // your TB description

    // To invoke the task in module1

    initial begin
    'DUT.task-name; // "task-name" is the name of the task defined in module-1
    ...
    end

    // module instantiation

    mod-name module1 ( //port mapping );

    ******************************************************************

    This should work.

    - Vivek


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