A hierarchical view of the design provides fast and direct access to the source code; by simply double-clicking on an instance, the corresponding source code will be displayed in a new editor window.
|
|
Variables, signals and quantities can be watched during the simulation for online investigation of “data” and “calculation” design bugs. Local watches are automatically displayed for the instance under investigation and the designer can configure User watches as needed.
|
Placing time, signal or source code breakpoints makes it easier to isolate design bugs and enables step by step simulation. The simulation pauses when a breakpoint is reached and the designer can elect to step over time points, delta cycles, events or instructions.
|
|
The simulation history, or backtrace, keeps track of what has been previously simulated to reduce tedious step by step simulation. It provides online investigation of design “behavior” and “control” bugs by allowing to determine the data change paths in the simulation.
|
Simulation can be run in slow motion or animated mode (per instruction or per simulation cycle) to help identify the cause of a design bug. A marker in the source code shows what will be executed next during slow motion simulation. |
|
The upcoming events viewer helps to understand delta cycle problems in behavioral modeling by making explicit the event execution order. |