Type; Ubreak - Intel IXP2400 User Manual

index_range
Closing
8.3.38

type

Format:
type file_spec
Definition:
Prints the contents of the specified file to the console.
8.3.39

ubreak

Format:
ubreak break_name |quoted_callback_function||goto_filter|
|uaddr_or_label| ...
Definition:
Creates a microcode breakpoint state. A ubreak breakpoint will unconditionally cause the
simulator to stop when that micro-PC address is reached by a thread that is enabled to respond
to that breakpoint.
The breakpoint is enabled upon creation. The breakpoint can be disabled or re-enabled by
depositing a 0 or 1 respectively via the deposit command.
uaddr_or_label
goto_filter
quoted_callback_function
Development Tools User's Guide
®
Intel
The index_range specification (delimited by []) can be a single C
numeric expression or 2 numeric expressions separated by a ":" to
indicate the inclusive range formed between the two numbers.
A trace file may be closed using the "close" command. All trace files are
automatically closed when the simulator is exited, or when the restore
command is executed. Trace files are automatically reopened whenever
a restore operation is executed which restores simulator state to the time
point when that trace was first opened.
Any number of breakpoint addresses can be related to the breakpoint
state by specifying 1 or more micro-addresses in the form of either
number# or label#.
The goto_filter specification is used to designate which threads of which
micro-sequencers the breakpoint specification should apply to. If the
goto_filter is not specified, the configuration set from the
"set_default_goto_filter" is applied by default.
See set_default_goto_filter for the syntax of the goto_filter.
The quoted_callback_function_name is an optional argument. If it is
specified it is used to conditionalize the ubreak event. It must be a
quoted string specifying the name of a pre-existing C-interpreted
function name or pre-existing imported function name (do not specify
parenthesis, argument types, or return types). When a potential
ubreakpoint is reached this function is called with the current ubreak
state information. If the return value from the function is non-zero, the
ubreak is activated causing the simulation to halt; otherwise it is ignored.
The absence of the quoted_callback_function_name argument causes
IXP2400/IXP2800 Network Processors
Transactor
247