• 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. Usage of verilog compiler directive in TCL

Stats

  • Locked Locked
  • Replies 5
  • Subscribers 65
  • Views 17535
  • 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

Usage of verilog compiler directive in TCL

usiciliani
usiciliani over 15 years ago

I'm using TCL scripts to stimulate a verilog database (based on task - schedule statement).

Is there a way to use verilog compiler directive (like `define) in TCL?

  • Cancel
  • StephenH
    StephenH over 15 years ago

     I don't think there's a way to do this directly. Normally you would use the TCL command "describe" to get information on a simulation object (net, module, class etc).However, a `define is a compiler macro, and in Verilog isused as a simple text substitution.
    Thus by the time the simulator ges to execute the code, it doesn't really have any idea that the macro even exists, it will have been substituted for some text long before.

    I am loathe to recommend doing any kind of etstbench in TCL when there are so many better ways to do it.
    Still, if you really must use TCL, then I would recommend that you extend your Verilog testbench, and copy the important `define values into some parameters or other such object that can be used with the describe command.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • usiciliani
    usiciliani over 15 years ago

    ... that's the way I'm using, define parameters in Verilog to drive the simulation, so the question is: can I recall these parameters in TCL?

    about the usage of TCL: i like it because you can change everything you want with no elaborate time, you can't do so in Verilog of course!

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • StephenH
    StephenH over 15 years ago

    I think we're confusing each other with the terminology! :-)

    You initially asked about `defines, such as:
        `define BUS_WIDTH 32
    These cannot (as far as I know) be seen from TCL.

     When I said parameters, I specifically meant Verilog parameters, such as:
      module foo (...);
        parameter BUS_WIDTH = `BUS_WIDTH;

    These ARE accesible from TCL, so you can do things like:
      ncsim> describe tb.dut.BUS_WIDTH
    And ncsim will tell you the value as a text string that you can manipulate in TCL.

    Does that help clarify things?

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • usiciliani
    usiciliani over 15 years ago

    Yes, you're right we've made some confusion, it's my mistake!

    Ok, I'll try with describe command. Thanks

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • NineLights
    NineLights over 6 years ago in reply to StephenH

    Hi StephenH,

    I tried using following command in ncsim:
    ncsim> describe tb.dut.BUS_WIDTH

    And I am getting following result:
    tb.dut.BUS_WIDTH...parameter logic [31:0] = 32'h00000001

    I want to assign this value to tcl variable. Do you know how to assign it?
    I have tried following:

    set prm_bus tb.dut.BUS_WIDTH

    But when I print the value using
    puts $prm_bus
    It prints tb.dut.BUS_WIDTH, not 1.

    • 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