Stats

  • Locked Locked
  • Replies 2
  • Subscribers 64
  • Views 5752
  • 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

ncsim +gui debugging and breakpoints on system-tasks/functions?

cubicle82

Is there an easy way to setup a breakpoint on a system-task, like $finish()?

I'm trying to debug some validation-code (which calls $finish on failure.) And the code is nested inside a bunch of `include files, making it difficult to directly navigate within SourceBrowser.  I thought I might take the reverse-approach, and  simply set a breakpoint on $finish itself, assuming that is even possible.

(Alternatively, I could do a text-substitution on $finish, replace it with a `define macro that calls an arbitrary unique user-task, and put the breakpoint on my task.)

  • I'm not sure about doing this directly, hopefully someone else might know a proper way to do it.

    Sticking with what I do know, I'd use grep or awk to search my Verilog files for $finish, and construct a list of TCL commands to generate the line breakpoints automatically. It's a bit brutal, but should work.
    You can get the line breakpoint syntax by doing "help stop" in the ncsim prompt, or by setting a line breakpoint in SimVision and checking the ncsim console window for the TCL command it generated.

     

  • To set a breakpoint on a line that contains a system task such as $finish, be sure to elaborate with the -linedebug switch. In SimVision, bring up the source code browser and you will see that the line numbers will not be grayed out and you can double-click on the line number that you want to break on. When the simulation reaches this line, it will stop before executing the line of code.

    Tim

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.