c-tools2.html

vxworks相关论文

</table>
</p callout>



<dl class="margin">

<dd><p class="Body"><a name="85165"> </a>To enable the authorization mechanism, you (and anyone else who wishes to participate in the Tornado authorization scheme from a Windows host) must define an environment variable <b class="symbol_UC">WIND_UID</b> as identification; see <a href="c-tools6.html#84439"><i class="title">Sharing and Reserving a Target Server</i></a>.<div class="frame">
<h4 class="EntityTitle"><a name="85173"><font face="Helvetica, sans-serif" size="-1" class="sans">Figure 5-3:&nbsp;&nbsp;Authorizations Properties</font></a></h4>

<dl class="margin">

<div class="Anchor"><a name="85178"> </a><img class="figure" border="0" src="images/c-toolsa5.gif">
</div>



</dl>

</div>
 </p>
<dd><p class="Body"><a name="84220"> </a>The <b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">Authorizations</font></b> property list (<a href="c-tools2.html#85173">Figure&nbsp;5-3</a>) offers the following controls:</p>
</dl>

<dl class="margin">

<dd><div class="Item"><a name="84221"> </a><b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">Lock on Startup</font></b> </div>
<dl class="margin">

<dd><div class="Indent"><a name="84975"> </a>Turn on this toggle to reserve this target server for your own use. If you do not check this box, any authorized user may use or reserve the server after you launch it.</div>
<br>
</dl>

<dd><div class="Item"><a name="84222"> </a><b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">User ID File</font></b> </div>
<dl class="margin">

<dd><div class="Indent"><a name="84977"> </a>To restrict this target server to a particular set of users, specify the full path and file name of a file of authorized user IDs here. If you do not specify an authorized-users file, any user on your network may connect to the target whenever it is not reserved. See <a href="c-tools6.html#88587"><i class="title">Authorized User File</i></a>.</div>
<br>
</dl>

</dl>

</dl>
<font face="Helvetica, sans-serif" class="sans">
<h4 class="H4"><i><a name="84227">Back End</a></i></h4>
</font>
<dl class="margin">

<dl class="margin">

<dd><p class="Body"><a name="84235"> </a>The <b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">Back End</font></b> property list is used to specify how a target server will communicate with a target (<a href="c-tools2.html#89407">Figure&nbsp;5-4</a>).<div class="frame">
<h4 class="EntityTitle"><a name="89407"><font face="Helvetica, sans-serif" size="-1" class="sans">Figure 5-4:&nbsp;&nbsp;Back End Properties</font></a></h4>

<dl class="margin">

<div class="Anchor"><a name="89412"> </a><img class="figure" border="0" src="images/c-toolsa4.gif">
</div>



</dl>

</div>
 </p>
<dd><p class="Body"><a name="89361"> </a>The fields displayed for the <b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">Back End </font></b>property list vary depending on the communications method you choose from the list labeled <b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">Available Back Ends</font></b>. The default, <b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">wdbrpc</font></b>, is suitable for targets with IP connectivity. </p>
<dd><p class="Body"><a name="89425"> </a>The standard back ends are described in <a href="c-tools2.html#84245">Table&nbsp;5-1</a>. Other back ends may be available separately; contact your nearest Wind River Systems office (see the back cover).<p class="table">
<h4 class="EntityTitle"><a name="84245"><font face="Helvetica, sans-serif" size="-1" class="sans">Table 5-1:&nbsp;&nbsp;Communications Back Ends for Target Server </font></a></h4>

<table border="0" cellpadding="0" cellspacing="0">
<tr>
<td colspan="20">
<hr class="tablerule">
</td>
</tr>
<tr valign="middle">
<th rowspan="1" colspan="1">
<div class="CellHeading"><b><a name="84249"> </a><font face="Helvetica, sans-serif" size="-1" class="sans">Back End Option</font></b></div>

</th>
<td width="10">&nbsp;</td>

<th rowspan="1" colspan="1">
<div class="CellHeading"><b><a name="84251"> </a><font face="Helvetica, sans-serif" size="-1" class="sans">Description</font></b></div>

</th>
<td width="10">&nbsp;</td>


</tr>
<tr>
<td colspan="20">
<hr class="tablerule2">
</td>
</tr>
<tr valign="top">
<td colspan=1 rowspan=1>
<div class="CellBody"><a name="84258"> </a><b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">wdbrpc</font></b></div>

</td>
<td width="10">&nbsp;</td>

<td colspan=1 rowspan=1>
<div class="CellBody"><a name="84260"> </a>WDB RPC back end. This back end is the default. It is the most frequently used back end, and supports any kind of IP connection (for example, Ethernet). Polled-mode Ethernet drivers are available for most BSPs to support system mode debugging for this type of connection.</div>

</td>
<td width="10">&nbsp;</td>


</tr>
<tr valign="top">
<td colspan=1 rowspan=1>
<div class="CellBody"><a name="88684"> </a><b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">wdbpipe</font></b></div>

</td>
<td width="10">&nbsp;</td>

<td colspan=1 rowspan=1>
<div class="CellBody"><a name="88686"> </a>WDB Pipe back end. The back end for VxWorks target simulators. It supports either system-level or task-level views of the target, depending on the configuration of the target agent.</div>

</td>
<td width="10">&nbsp;</td>


</tr>
<tr valign="top">
<td colspan=1 rowspan=1>
<div class="CellBody"><a name="84263"> </a><b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">wdbserial</font></b></div>

</td>
<td width="10">&nbsp;</td>

<td colspan=1 rowspan=1>
<div class="CellBody"><a name="84265"> </a>WDB Serial back end. A back end for serial hardware connections; does not require SLIP on the host system. This back end supports either system-level or task-level views of the target, depending on the target-agent configuration.</div>

</td>
<td width="10">&nbsp;</td>


</tr>
<tr valign="top">
<td colspan=1 rowspan=1>
<div class="CellBody"><a name="84268"> </a><b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">netrom</font></b></div>

</td>
<td width="10">&nbsp;</td>

<td colspan=1 rowspan=1>
<div class="CellBody"><a name="84270"> </a>WDB NetRom. A back end that communicates over a proprietary communications protocol for NetROM, a networked ROM emulator. This back end supports either system- or task-level views of the target, depending on target-agent configuration.</div>

</td>
<td width="10">&nbsp;</td>


</tr>

<tr>
<td colspan="20">
<hr class="tablerule">
</td>
</tr>
<tr valign="middle">
<td colspan="20">

</td>
</tr>
</table>
</p>
</p>
</dl>

</dl>

<dl class="margin">
<dd>
<p class="table" callout>
<table border="0" cellpadding="0" cellspacing="0">
<tr valign="top">
<td valign="top" width="40">
<br>
<img border="0" alt="*" src="icons/warning.gif">
</td>

<td>
<hr><div class="CalloutCell"><a name="89899"><b class="symbol_UC"><font face="Helvetica, sans-serif" size="-1" class="sans">WARNING:  </font></b></a>The target server <i class="emphasis">must</i> be configured with the same communication back end as the one built into the VxWorks image. See <a href="c-start4.html#90094"><i class="title">2.4&nbsp;Host-Target Communication Configuration</i></a> and <a href="c-builder6.html#99096"><i class="title">4.6&nbsp;Configuring the Target-Host Communication Interface</i></a>. </div>
</td>


</tr>
<tr valign="top">
<td></td>

<td><hr></td>


</tr>

<tr valign="middle">
<td colspan="20">

</td>
</tr>
</table>
</p callout>



<dl class="margin">

<dd><p class="Body"><a name="84275"> </a>The following <b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">Back End</font></b> properties appear for all standard back ends:</p>
</dl>

<dl class="margin">

<dd><div class="Item"><a name="84276"> </a><b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">Timeout</font></b> </div>
<dl class="margin">

<dd><div class="Indent"><a name="84979"> </a>How many seconds to wait for a response from the agent running on the target system (the default is 3 seconds).</div>
<br>
</dl>

<dd><div class="Item"><a name="84277"> </a><b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">Re-try</font></b> </div>
<dl class="margin">

<dd><div class="Indent"><a name="84981"> </a>How many times to repeat a transaction if the target agent does not appear to respond the first time. </div>
<br>
</dl>

</dl>

<dl class="margin">

<dd><p class="Body"><a name="84288"> </a>The <b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">wdbserial</font></b> back end (see <a href="c-tools2.html#89407">Figure&nbsp;5-4</a>) also has the following properties:</p>
</dl>

<dl class="margin">

<dd><div class="Item"><a name="84289"> </a><b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">Serial Port</font></b> </div>
<dl class="margin">

<dd><div class="Indent"><a name="84988"> </a>The communications port on your PC that is connected to the target. The default serial device is <b class="file">COM2</b>.</div>
<br>
</dl>

<dd><div class="Item"><a name="84290"> </a><b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">Speed (bps)</font></b> </div>
<dl class="margin">

<dd><div class="Indent"><a name="84990"> </a>The line speed (in bits per second) that your target uses over its serial line. If your target is configured to use the default serial speed of 9600 bps, leave the <b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">Speed </font></b>setting at the default. However, it is best to use the fastest available serial line speed available. When you change the line speed, you must also re-compile the target agent (see <a href="c-builder6.html#99096"><i class="title">4.6&nbsp;Configuring the Target-Host Communication Interface</i></a>).</div>
<br>
</dl>

</dl>

<dl class="margin">

<dd><p class="Body"><a name="91224"> </a>All back ends also require:</p>
</dl>

<dl class="margin">