Breakpoint Items in IO Monitoring

You can add breakpoints in IO monitoring. If you add a breakpoint on an instruction, you cannot use an expression evaluation. However, you can use expression evaluation with breakpoints on the resource IO.

The following topics are discussed:

This page discusses:

Breakpoint on Instruction
Breakpoints on Resource IO

Breakpoint on Instruction

You can add breakpoints on specific instructions, which pause the debugger when the instruction is reached. You cannot apply expression-based conditionality to this type of breakpoint.

An example of using a breakpoint on an instruction follows.

When a simulation is running, open the Logics Monitoring window.
Click an instruction to add a breakpoint. The breakpoint is marked with a red bullet. The effect of adding this breakpoint is that the debugger stops when this instruction is reached.
Open the Signals Monitoring window.
In the Breakpoints tab, the breakpoint instruction appears. However, the Expression Breakpoint field is not available.

Breakpoints on Resource IO

You can create breakpoints on either expressions or on changes.

Breakpoints on Changes

You can create breakpoints on changes, which enable a pause in the debugger execution when the IO has changed.

An example of using a breakpoint on changes follows.

When a simulation is running, open the Signals Monitoring window.
In the Simulation tab, click Status breakpoint to add a breakpoint.

The breakpoint appears as a red bullet. As a result of creating this breakpoint, the debugger will be stopped on changes to the IO.

Breakpoints on an Expression

You can create a breakpoint on an expression that has the same behavior as a standard breakpoint but is only active when the given IO value validates a given expression.

An example of using a breakpoint on an expression follows.

When a simulation is running, open the Signals Monitoring window.
In the Simulation tab, click Expression Breakpoint to add a breakpoint.

In this field, the expression is created from a literal value and an operator that compares the literal value to the IO signal. Adding an expression defines a breakpoint on expression, which is activated once the given comparison between the literal value and the operator is true. A literal value is required. You cannot use expressions on both sides of the comparison operator.

Supported Expressions


	Operator	Literal Value
Double	=	Note: Literal values may be in floating notation (1.0, 3.14) or in exponential notation (1e14).
	>
	<
	>=
	<=
	<>
Boolean	=	true
	=	false
	<>	true
	<>	false
Integer	=	Note: Literal values for integers are in decimal notation (1, 2...).
	>
	<
	>=
	<=
	<>
String	=	Any list of characters starting an ending with double quotation marks, for example, "test."
String	<>	Strings can contain any character, even a new line. A double quotation mark within a string must be written `\"`.

Note: Combined criteria are not supported. An example of combined criteria is:

= 50 or = 100