• 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. accessing hdl signals in mixed language env

Stats

  • Locked Locked
  • Replies 3
  • Subscribers 64
  • Views 13462
  • 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

accessing hdl signals in mixed language env

archive
archive over 17 years ago

Hi, I have used define statements to acesses dut signals. Worked fine when the entire dut hierarchy was vhdl. Now with vhdl-verilog(netlist) specman says 'signal not found'.(it does exist) Eg:- define sig_a "~/c/b/a";-- where c--vhdl --and all heirachy at b and below is verilog. I am using sig_a inside a TCM which is a member of tb_env. Any solutions. Thanks, pr


Originally posted in cdnusers.org by rprashant
  • Cancel
Parents
  • archive
    archive over 17 years ago

    Sorry the forum mashed my code example!
    Trying again:

    // declare the port
    sig_a : inout simple_port of bit is instance;
    // sig_a is a simulator signal rather than an e-to-e port
    keep bind(sig_a, external);
    // bind the HDL signal name.
    // Can be done in top-level config file for best re-use
    keep sig_a.hdl_path() == "~/c/b/a";


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

    Sorry the forum mashed my code example!
    Trying again:

    // declare the port
    sig_a : inout simple_port of bit is instance;
    // sig_a is a simulator signal rather than an e-to-e port
    keep bind(sig_a, external);
    // bind the HDL signal name.
    // Can be done in top-level config file for best re-use
    keep sig_a.hdl_path() == "~/c/b/a";


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