c-start4.html

vxworks相关论文

</dl>
<font face="Helvetica, sans-serif" class="sans">
<h4 class="H4"><i><a name="90550">Starting the Target Server</a></i></h4>
</font>
<dl class="margin">

<dl class="margin">

<dd><p class="Body"><a name="90552"> </a>Start the target server as in the following example, using the <b class="command">-B</b> option to specify the NetROM back end. </p>
<dl class="margin">

<dd><pre class="Code2"><b><a name="90553"></b><tt class="output">C:\&gt; </tt><b>tgtsvr -V 90.0.0.5 -B netrom </a></b></pre>
</dl>

<dd><p class="Body"><a name="90554"> </a>In this example, <b>90.0.0.5</b> is the IP address of the NetROM. (You can also use the Tornado GUI to configure and start a target server; see <a href="c-tools2.html#84049"><i class="title">5.2&nbsp;Configuring and Starting a Target Server</i></a>.) </p>
<dd><p class="Body"><a name="90555"> </a>If the connection fails, try typing the following command at the NetROM prompt:</p>
<dl class="margin">

<dd><pre class="Code2"><b><a name="90556"></b><tt class="output">NetROM&gt; </tt><b>set debugecho on</a></b></pre>
</dl>

<dd><p class="Body"><a name="90557"> </a>With this setting, all packets sent to and from the NetROM are copied to the console. You may need to hook up a connector to the NetROM serial console to see the <b class="symbol_lc">debugecho</b> output, even if your current console with NetROM is attached through Telnet (later versions of NetROM software may not have this problem). If you see packets sent from the host, but no reply from the target, you must modify the target NetROM configuration parameters described in section <a href="c-start4.html#90856"><i class="title">Configuring the Target Agent for NetROM</i></a>.</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/note.gif">
</td>

<td>
<hr><div class="CalloutCell"><a name="93341"><b class="symbol_UC"><font face="Helvetica, sans-serif" size="-1" class="sans">NOTE:  </font></b></a>With a NetROM connection, you must inform the NetROM when you reboot the target. You can do this as follows at the NetROM prompt: <br>
 <br>
    <b>NetROM&gt; tgtreset &nbsp;</b>&nbsp; <br>
</div>
</td>


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

<td><hr></td>


</tr>

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

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



</dl>
<font face="Helvetica, sans-serif" class="sans">
<h4 class="H4"><i><a name="93547">Troubleshooting the NetROM ROM-Emulator Connection</a></i></h4>
</font>
<dl class="margin">

<dl class="margin">

<dd><p class="Body"><a name="93551"> </a>If the target server fails to connect to the target, the following troubleshooting procedures can help isolate the problem.</p>
</dl>

</dl>

<dl class="margin">

<dd><font face="Helvetica, sans-serif" size="-1" class="sans">
<h5 class="HU"><i><a name="93552">Download Configuration</a></i></h5>
</font><dl class="margin">

<dd><p class="Body"><a name="93553"> </a>It is possible that the NetROM is not correctly configured for downloading code to the target. Make sure you can download and run a simple piece of code (for example, to blink an LED -- this code should be something simpler than a complete VxWorks image).</p>
</dl>

<dd><font face="Helvetica, sans-serif" size="-1" class="sans">
<h5 class="HU"><i><a name="93554">Initialization</a></i></h5>
</font><dl class="margin">

<dd><p class="Body"><a name="93555"> </a>If you can download code and execute it, the next possibility is that the board initialization code is failing. In this case, it never reaches the point of trying to use the NetROM for communication. The code in <b class="file">target/src/config/usrWdb.c</b> makes a call to <b class="routine"><i class="routine">wdbNetromPktDevInit</i></b><b>(&nbsp;)</b>. If the startup code does not get to this point, the problem probably lies in the BSP. Contact the vendor that supplied the BSP for further troubleshooting tips.</p>
</dl>

<dd><font face="Helvetica, sans-serif" size="-1" class="sans">
<h5 class="HU"><i><a name="93556">RAM Configuration</a></i></h5>
</font><dl class="margin">

<dd><p class="Body"><a name="93557"> </a>If the NetROM communication initialization code is being called but is not working, the problem could be due to a mis-configuration of the NetROM. To test this, modify the file <b class="file">wdbNetromPktDrv.c</b>. Change the following line: </p>
<dl class="margin">

<dd><pre class="Code2"><b><a name="93558">int wdbNetromTest = 0;</a></b></pre>
</dl>

<dd><p class="Body"><a name="93559"> </a>to: </p>
<dl class="margin">

<dd><pre class="Code2"><b><a name="93560">int wdbNetromTest = 1;</a></b></pre>
</dl>

</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/note.gif">
</td>

<td>
<hr><div class="CalloutCell"><a name="93666"><b class="symbol_UC"><font face="Helvetica, sans-serif" size="-1" class="sans">NOTE:  </font></b></a>There are two versions of <b class="file">wdbNetromPktDrv.c</b>. The one for the 400 series is located in <b class="file">target/src/drv/wdb</b> and the one for the 500 series is located in <b class="file">target/src/drv/wdb/amc500</b>. Be sure to edit the appropriate one.</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="93570"> </a>When you rerun VxWorks with this modification, the <b class="routine"><i class="routine">wdbNetromPktDevInit</i></b><b>(&nbsp;)</b> routine attempts to print a message to NetROM debug port. The initialization code halts until you connect to the debug port (1235), which you can do by typing:</p>
<dl class="margin">

<dd><pre class="Code2"><b><a name="93571"></b><tt class="output">% </tt><b>telnet <i class="textVariable">NetROM_IPaddress</i> 1235</a></b></pre>
</dl>

<dd><p class="Body"><a name="93572"> </a>If the debug port successfully connects, the following message is displayed in the <b class="symbol_lc">telnet</b> window:</p>
<dl class="margin">

<dd><pre class="Code2"><b><a name="93573"></b><tt class="output">WDB NetROM communication ready</tt><b> </a></b></pre>
</dl>

<dd><p class="Body"><a name="93574"> </a>If you do not see this message, the NetROM dual-port RAM has not been configured correctly. Turn off the processor cache; if that does not solve the problem, contact AMC for further trouble shooting tips:</p>
</dl>

<dl class="margin">

<dd><div class="Item"><a name="93575"> </a>AMC web page: </div>
<dl class="margin">

<dl class="margin">

<dl class="margin">

<dl class="margin">

<dl class="margin">

<dd><div class="Indent5"><a name="93576"> </a><b class="file"><a href="http://www.amc.com/">http://www.amc.com/</a> </b></div>
<br>
</dl>

</dl>

</dl>

</dl>

</dl>

<dd><div class="Item"><a name="93577"> </a>AMC tech-support: </div>
<dl class="margin">

<dl class="margin">

<dl class="margin">

<dl class="margin">

<dl class="margin">

<dd><div class="Indent5"><a name="93578"> </a><b>1-800-ask-4amc</b> </div>
<br>
<dd><div class="Indent5"><a name="93579"> </a><b class="file"><a href="mailto:[e-mail]">[e-mail]</a> </b></div>
<br>
</dl>

</dl>

</dl>

</dl>

</dl>

</dl>

<dl class="margin">

<dd><p class="Body"><a name="93580"> </a>If everything has worked up to this point, reset <b class="symbol_lc">wdbNetromTest</b> back to zero and end your <b class="symbol_lc">telnet</b> session.</p>
</dl>

</dl>
<dl class="margin">

<dd><font face="Helvetica, sans-serif" size="-1" class="sans">
<h5 class="HU"><i><a name="93581">Communication</a></i></h5>
</font><dl class="margin">

<dd><p class="Body"><a name="93582"> </a>Type the following at the NetROM prompt:</p>
<dl class="margin">

<dd><pre class="Code2"><b><a name="93583"></b><tt class="output">NetROM&gt; </tt><b>set debugecho on</a></b></pre>
</dl>

<dd><p class="Body"><a name="93584"> </a>This causes data to be echoed to the NetROM console when packets are transmitted between the host and target. If you have a VxWorks console available on your target, edit<b class="file"> wdbNetromPktDrv.c </b>by changing the following line: </p>
<dl class="margin">

<dd><pre class="Code2"><b><a name="93585">int wdbNetromDebug = 0;</a></b></pre>
</dl>

<dd><p class="Body"><a name="93586"> </a>to: </p>
<dl class="margin">

<dd><pre class="Code2"><b><a name="93587">int wdbNetromDebug = 1;</a></b></pre>
</dl>

<dd><p class="Body"><a name="93588"> </a>This causes messages to be echoed to the VxWorks console when packets are transmitted between the host and target.</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/note.gif">
</td>

<td>
<hr><div class="CalloutCell"><a name="93687"><b class="symbol_UC"><font face="Helvetica, sans-serif" size="-1" class="sans">NOTE:  </font></b></a>You may need to hook up a connector to the NetROM serial console to see the <b class="symbol_lc">debugecho</b> output, even if your current console with NetROM is attached through <b class="symbol_lc">telnet</b>.</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="93598"> </a>Retry the connection:</p>
</dl>

<dl class="margin">

<p><ol class="List"><li value="1)"><a name="93599"> </a>Kill the target server.</li></ol></p>
<p><ol class="List"><li value="2)"><a name="93600"> </a>Type <b class="command">tgtreset</b> at the NetROM prompt.</li></ol></p>
<p><ol class="List"><li value="3)"><a name="93601"> </a>Reboot your target.</li></ol></p>
<p><ol class="List"><li value="4)"><a name="93602"> </a>Start the target server using the <b class="operator">-Bd</b> option to log transactions between the target server and the agent to a log file. Use the target server <b class="operator">-Bt</b> option to increase the timeout period. (This is necessary whenever the NetROM debug echo feature is enabled, because <b class="command">debugecho</b> slows down the connection.) </li></ol></p>
</dl>

<dl class="margin">

<dd><p class="Body"><a name="93603"> </a>At this point, you have debugging output on three levels: the target server is recording all transactions between it and the NetROM box; the NetROM box is printing all packets it sees to its console; and the WDB agent is printing all packets it sees to the VxWorks console. If this process does not provide enough debug information to resolve your problems, contact WRS technical support for more troubleshooting assistance.</p>
</dl>

</dl>

<a name="foot"><hr></a>


<p class="navbar" align="right"><a href="index.html"><img border="0" alt="[Contents]" src="icons/contents.gif"></a><a href="GuideIX.html"><img border="0" alt="[Index]" src="icons/index.gif"></a><a href="c-start.html"><img border="0" alt="[Top]" src="icons/top.gif"></a><a href="c-start3.html"><img border="0" alt="[Prev]" src="icons/prev.gif"></a><a href="c-start5.html"><img border="0" alt="[Next]" src="icons/next.gif"></a></p>

</body>

</html>
<!---
by WRS Documentation (), Wind River Systems, Inc.
    conversion tool:  Quadralay WebWorks Publisher 4.0.11
    template:         CSS Template, Jan 1998 - Jefro --->