<html>
<head>
-<title>Breakpoints commands of uCsim</title>
+<title>Breakpoints commands of µCsim</title>
</head>
<body bgcolor="white">
<!-- BREAKPOINTS -->
-<h2>Commands of uCsim to manage breakpoints</h2>
+<h2>Commands of µCsim to manage breakpoints</h2>
-Two kind of breakpoints can be used: fetch and event
+Two kind of breakpoint can be used: fetch and event
breakpoint. <B>Fetch</b> breakpoints are classical breakpoints. They
can be placed at any instruction in the code memory. Breakpoint will
be hit if CPU fetches instruction code from the memory location
breakpoint would be executed.
<p><b>Event</b> breakpoints are special onces. They cause stop of
-execution if event specified by the breakpoint occures. Events are:
-
-<dl><dt><b>wi</b> <dd>writing into internal RAM at specified location;
-
-<dt><b>ri</b> <dd>reading from internal RAM at specified address;
-
-<dt><b>wx</b> <dd>writing into external RAM at specified location
-(MOVX instruction);
-
-<dt><b>rx</b> <dd>reading from external RAM at specified address (MOVX
-instruction);
-
-<dt><b>ws</b> <dd>writing into SFR area at specified location;
-
-<dt><b>rs</b> <dd>reading from SFR area at specified address;
-
-<dt><b>rc</b> <dd>reading from code memory at specified location (MOVC
-instruction).</dl>
-
-Event breakpoint stops execution <i>after</i> specified event occured.
+execution if event specified by the breakpoint occures. Event can be a
+read or a write operation on any address space location. Event
+breakpoint stops execution <i>after</i> specified event occured.
<p>Every breakpoint can be <b>fix</b> (permanent) or <b>dynamic</b>
(temporary). Dynamic breakpoints are automatically removed when they
number specifies how many times the breakpoint must be hit before it
causes the execution to stop. This hit number is 1 by default.
+<hr>
+
-<a name="break"><h3>break addr [hit]
-<br>break memory_type r|w addr [hit]</h3></a>
-<a name="tbreak"><h3>tbreak addr [hit]
-<br>tbreak memory_type r|w addr [hit]</h3></a>
+<a name="break"><h3>break <i>addr [hit]</i>
+<br>break <i>memory_type r|w addr [hit]</i></h3></a>
+<a name="tbreak"><h3>tbreak<i> addr [hit]</i>
+<br>tbreak <i>memory_type r|w addr [hit]</i></h3></a>
Set fetch or event breakpoint. The command specifies if the breakpoint
<dt>Event breakpoint
<dd>First parameter specifies class name of memory where we are going
-to watch for en event. Class names of memories can be checked by
q<a
-href="cmd_general.html#conf">conf</a> command.
+to watch for en event. Class names of memories can be checked by <a
+href="cmd_general.html#info_memory">info memory</a> command.
<br>Second parameter specifies the event. It can be <b>r</b> to
specify <b>read</b> operation or <b>w</b> which means <b>write</b>
operation.
F 000160
> </pre>
+<hr>
-<a name="clear"><h3>clear [addr...]</h3></a>
+
+<a name="clear"><h3>clear <i>[addr...]</i></h3></a>
Delete fetch breakpoint. Parameter specifies address of breakpoint. If
there is no breakpoint specified at given address this command prints
1 event keep 1 1 0x000006 wi
> </pre>
+<hr>
+
-<a name="delete"><h3>delete [number...]</h3></a>
+<a name="delete"><h3>delete <i>[number...]</i></h3></a>
Delete breakpoint(s) by its number.
projects / fw / sdcc / blobdiff