3 <title>Debugging with GDB
</title>
4 <meta http-equiv=
"Content-Type" content=
"text/html">
5 <meta name=
"description" content=
"Debugging with GDB">
6 <meta name=
"generator" content=
"makeinfo 4.3">
7 <link href=
"http://www.gnu.org/software/texinfo/" rel=
"generator-home">
12 Node:
<a name=
"i960">i960
</a>,
13 Next:
<a rel=
"next" accesskey=
"n" href=
"M32R-D.html#M32R%2fD">M32R/D
</a>,
14 Previous:
<a rel=
"previous" accesskey=
"p" href=
"H8-500.html#H8%2f500">H8/
500</a>,
15 Up:
<a rel=
"up" accesskey=
"u" href=
"Embedded-Processors.html#Embedded%20Processors">Embedded Processors
</a>
19 <h4 class=
"subsection">Intel i960
</h4>
23 <br><dt><code>target mon960
</code><var>dev
</var><code></code>
24 <dd>MON960 monitor for Intel i960.
26 <br><dt><code>target nindy
</code><var>devicename
</var><code></code>
27 <dd>An Intel
960 board controlled by a Nindy Monitor.
<var>devicename
</var> is
28 the name of the serial device to use for the connection, e.g.
29 <code>/dev/ttya
</code>.
33 <p><dfn>Nindy
</dfn> is a ROM Monitor program for Intel
960 target systems. When
34 GDB is configured to control a remote Intel
960 using Nindy, you can
35 tell GDB how to connect to the
960 in several ways:
38 <li>Through command line options specifying serial port, version of the
39 Nindy protocol, and communications speed;
41 <li>By responding to a prompt on startup;
43 <li>By using the
<code>target
</code> command at any point during your GDB
44 session. See
<a href=
"Target-Commands.html#Target%20Commands">Commands for managing targets
</a>.
48 <p>With the Nindy interface to an Intel
960 board,
<code>load
</code>
49 downloads
<var>filename
</var> to the
960 as well as adding its symbols in
53 <li><a accesskey=
"1" href=
"Nindy-Startup.html#Nindy%20Startup">Nindy Startup
</a>: Startup with Nindy
54 <li><a accesskey=
"2" href=
"Nindy-Options.html#Nindy%20Options">Nindy Options
</a>: Options for Nindy
55 <li><a accesskey=
"3" href=
"Nindy-Reset.html#Nindy%20Reset">Nindy Reset
</a>: Nindy reset command