Verification Martial Arts: A Verification Methodology Blog

Cool Things You Can Do With DVE – Part 4

Posted by Yaron Ilani on April 26th, 2011

Yaron Ilani, Apps. Consultant, Synopsys

If you liked part 2 where I explained how Interactive Rewind could save you precious time during debug, then here’s another one for you. Obviously one of the most powerful methods of debugging interactively is by adding breakpoints at interesting points. You could have a single breakpoint as a starting point and then go on step by step. But in most cases it would be wiser to put multiple breakpoints in your code so that you could have more control over your simulation or even jump from one interesting point to another (remember you can always go backwards in time).

So the process of adding breakpoints and refining them might take some time and ideally you wouldn’t want to repeat that process all over again when you start a new interactive debug session. Wouldn’t it be nice to be able to save your breakpoints so that you or someone else from your team could reuse them in a different simulation? Well, DVE lets you do that! Simply launch the Breakpoints window from the Simulator menu:

In the example above I’ve added 3 breakpoints. In the source code window they are marked in red, but they are also listed in the Breakpoints window where each breakpoint can be enabled or disabled individually. In the bottom left you can see the “Save” button. Clicking on it will save all your breakpoints to a TCL file. You may use this file later on in any other DVE session by clicking on the “Load” button.

Once your test bench code is more or less stable, with this new feature you can actually create a number of useful breakpoints files (a breakpoints library if you will…). Each breakpoints file could be designed to help debugging a different part of your test bench. Or if you’re debugging some unfamiliar verification IP, you can create a breakpoints file and send it to its owner for help.

Happy debugging!

Check out the previous parts of this series to learn more about more cool features available today in DVE.

4 Responses to “Cool Things You Can Do With DVE – Part 4”

  1. Pranita Says:


    Thanks for this series of “Cool Things You Can Do With DVE”.. Those are really very helpful. But for last part, I am not able to see Breakpoint button enabled. It is disabled in simulator. Any different setting do I need to do for enabling that?

  2. Yaron Says:


    Make sure you’re using the interactive mode. Breakpoints are disabled in post processing mode.
    If this doesn’t help please contact VCS support.

  3. Dhananjay Mundravale Says:

    Is it possible to adjust time difference between C1 and C2 by multiplying clock perid to get difference in terms of cycles. for example, if my clock period is 1.66ns then cursors at single clock cycle shows C1 – C2 = 1.66. Is it possible to set difference x 1.66 to get C1 -C2 = 1



  4. Yaron Ilani Says:


    You can set the grid type to “Grid on Cycle” (rather than “Grid on Signals”) and enter a cycle time. The grid will use that as a reference clock for counting.