1<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>6.3.�Invoking Sourcery CodeBench Debug Sprite</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="ch06s02.html" title="6.2.�Debug Sprite Example"><link rel="next" href="sec-sprite-options.html" title="6.4.�Sourcery CodeBench Debug Sprite Options"></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.3.�Invoking Sourcery CodeBench Debug Sprite</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ch06s02.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="sec-sprite-options.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-invocation"></a>6.3.�Invoking Sourcery CodeBench Debug Sprite</h2></div></div></div><p>The Debug Sprite is invoked as follows: 2 3 </p><pre class="screen">> arm-none-eabi-sprite [<em class="replaceable"><code>options</code></em>] <em class="replaceable"><code>device-url</code></em> <em class="replaceable"><code>board-file</code></em></pre><p> 4 </p><p> The <em class="replaceable"><code>device-url</code></em> specifies the 5 debug device to use to communicate with the board. It follows the 6 standard format: 7 8 </p><pre class="screen"><em class="replaceable"><code>scheme</code></em>:<em class="replaceable"><code>scheme-specific-part</code></em>[?<em class="replaceable"><code>device-options</code></em>]</pre><p> 9 10 Most device URL schemes also follow the regular format: 11 12 </p><pre class="screen"><em class="replaceable"><code>scheme</code></em>:[//<em class="replaceable"><code>hostname</code></em>:[<em class="replaceable"><code>port</code></em>]]/<em class="replaceable"><code>path</code></em>[?<em class="replaceable"><code>device-options</code></em>]</pre><p> 13 14 The meanings of <em class="replaceable"><code>hostname</code></em>, 15 <em class="replaceable"><code>port</code></em>, <em class="replaceable"><code>path</code></em> 16 and <em class="replaceable"><code>device-options</code></em> parts depend on the 17 <em class="replaceable"><code>scheme</code></em> and are described below. The 18 following schemes are supported in Sourcery CodeBench Lite for ARM EABI: 19 20 </p><div class="variablelist"><dl><dt><span class="term"><code class="literal">rdi</code></span></dt><dd><p> Use an RDI debugging device. 21 Refer to <a class="xref" href="debug-sprite-rdi-url.html" title="6.5.�Remote Debug Interface Devices">Section�6.5, “Remote Debug Interface Devices”</a>. </p></dd><dt><span class="term"><code class="literal">flashpro</code></span></dt><dd><p> Use a FlashPro debugging device. 22 Refer to <a class="xref" href="debug-sprite-flashpro-url.html" title="6.6.�Actel FlashPro Devices">Section�6.6, “Actel FlashPro Devices”</a>. </p></dd><dt><span class="term"><code class="literal">altera</code></span></dt><dd><p> Use an Altera FPGA. 23 Refer to <a class="xref" href="debug-sprite-altera-url.html" title="6.7.�Altera Devices">Section�6.7, “Altera Devices”</a>.</p></dd></dl></div><p> 24 </p><p>The optional 25 <code class="literal">?<em class="replaceable"><code>device-options</code></em></code> portion is 26 allowed in all schemes. These allow additional device-specific 27 options of the form 28 <code class="literal"><em class="replaceable"><code>name</code></em>=<em class="replaceable"><code>value</code></em></code>. 29 Multiple options are concatenated using 30 <code class="literal">&</code>.</p><p>The <em class="replaceable"><code>board-file</code></em> specifies an XML 31 file that describes how to initialize the target board, as well as 32 other properties of the board used by the debugger. If 33 <em class="replaceable"><code>board-file</code></em> refers to a file (via a 34 relative or absolute pathname), it is read. Otherwise, 35 <em class="replaceable"><code>board-file</code></em> can be a board name, and the 36 toolchain's board directory is searched for a matching file. 37 See <a class="xref" href="sec-sprite-supported-boards.html" title="6.9.�Supported Board Files">Section�6.9, “Supported Board Files”</a> for 38 the list of supported boards, or invoke the Sprite with the 39 <code class="option">-b</code> option to list the available board files. 40 41 You can also write a custom board file; see 42 <a class="xref" href="sec-sprite-board-file.html" title="6.10.�Board File Syntax">Section�6.10, “Board File Syntax”</a> for more information about 43 the file format.</p><p> 44 Both the <em class="replaceable"><code>device-url</code></em> and 45 <em class="replaceable"><code>board-file</code></em> command-line arguments are 46 required to correctly connect the Sprite to a target board. 47 </p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ch06s02.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="sec-sprite-options.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">6.2.�Debug Sprite Example�</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">�6.4.�Sourcery CodeBench Debug Sprite Options</td></tr></table></div></body></html> 48