Stats

  • Locked Locked
  • Replies 3
  • Subscribers 65
  • Views 13663
  • 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

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
Parents
  • archive


    in mixed HDL environments it is important to make sure SPMN knows which interface adapter to use to access specific signals.
    if you only have one HDL language then there is only one interface adapter. In mixed environments SPMN will use several interface adapters. you should read the documentation regarding the agent() attribute of units [e Language Reference - 5.3 Predefined Attributes and Methods for Any Unit]. this will define the correct agent to use and will ensure that the right signal is found.


    Originally posted in cdnusers.org by hannes
Reply
  • archive


    in mixed HDL environments it is important to make sure SPMN knows which interface adapter to use to access specific signals.
    if you only have one HDL language then there is only one interface adapter. In mixed environments SPMN will use several interface adapters. you should read the documentation regarding the agent() attribute of units [e Language Reference - 5.3 Predefined Attributes and Methods for Any Unit]. this will define the correct agent to use and will ensure that the right signal is found.


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