• Home
  • History
  • Annotate
  • Line#
  • Navigate
  • Raw
  • Download
  • only in /asuswrt-rt-n18u-9.0.0.4.380.2695/release/src-rt-6.x.4708/toolchains/hndtools-armeabi-2011.09/share/doc/arm-arm-none-eabi/html/getting-started/
1<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>6.4.�Sourcery CodeBench Debug Sprite Options</title><link rel="stylesheet" href="cs.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.74.0"><link rel="home" href="index.html" title="Sourcery CodeBench Lite"><link rel="up" href="sprite.html" title="Chapter�6.�Sourcery CodeBench Debug Sprite"><link rel="prev" href="sec-sprite-invocation.html" title="6.3.�Invoking Sourcery CodeBench Debug Sprite"><link rel="next" href="debug-sprite-rdi-url.html" title="6.5.�Remote Debug Interface Devices"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">6.4.�Sourcery CodeBench Debug Sprite Options</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="sec-sprite-invocation.html">Prev</a>�</td><th width="60%" align="center">Chapter�6.�Sourcery CodeBench Debug Sprite</th><td width="20%" align="right">�<a accesskey="n" href="debug-sprite-rdi-url.html">Next</a></td></tr></table><hr></div><div class="section" lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="sec-sprite-options"></a>6.4.�Sourcery CodeBench Debug Sprite Options</h2></div></div></div><p>The following command-line options are supported by the 
2    Sourcery CodeBench Debug Sprite:
3
4    </p><div class="variablelist"><dl><dt><span class="term"><code class="option">-b</code></span></dt><dd><p> Print a list of <em class="replaceable"><code>board-file</code></em>
5      files in the board config
6      directory.  </p></dd><dt><span class="term"><code class="option">-h</code></span></dt><dd><p> Print a list of
7      options and their meanings.  A list of
8      <em class="replaceable"><code>device-url</code></em> syntaxes is also
9      shown. </p></dd><dt><span class="term"><code class="option">-i</code></span></dt><dd><p> Print a list of
10      the accessible devices.  If a
11      <em class="replaceable"><code>device-url</code></em> is also specified, only
12      devices for that device type are scanned.  Each supported device
13      type is listed along with the options that can be appended to
14      the <em class="replaceable"><code>device-url</code></em>.  For each discovered
15      device, the <em class="replaceable"><code>device-url</code></em> is printed
16      along with a description of that
17      device.</p></dd><dt><span class="term"><code class="option">-l <em class="replaceable"><code>[host]:port</code></em></code></span></dt><dd><p>
18      Specify the host address and port number to listen for a GDB
19      connection.  If this option is not given, the Debug Sprite
20      communicates with GDB using stdin and stdout.  If you start the
21      Sprite from within GDB using the <code class="literal">target remote |
22      arm-none-eabi-�sprite ...</code> command, you do not need this
23      option.  </p></dd><dt><span class="term"><code class="option">-m</code></span></dt><dd><p> Listen for
24      multiple sequential connections.  Normally the Debug Sprite
25      terminates after the first connection from GDB terminates.  This
26      option instead makes it listen for a subsequent connection.  To
27      terminate the Sprite, open a connection and send the string
28      <code class="literal">END\n</code>.</p></dd><dt><span class="term"><code class="option">-q</code></span></dt><dd><p> Do not print any
29      messages. </p></dd><dt><span class="term"><code class="option">-v</code></span></dt><dd><p> Print additional
30      messages. </p></dd></dl></div><p>
31
32    If any of <code class="option">-b</code>, <code class="option">-i</code> or
33    <code class="option">-h</code> are given, the Debug Sprite terminates after
34    providing the information rather than waiting for a debugger
35    connection.</p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="sec-sprite-invocation.html">Prev</a>�</td><td width="20%" align="center"><a accesskey="u" href="sprite.html">Up</a></td><td width="40%" align="right">�<a accesskey="n" href="debug-sprite-rdi-url.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">6.3.�Invoking Sourcery CodeBench Debug Sprite�</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">�6.5.�Remote Debug Interface Devices</td></tr></table></div></body></html>
36