c-start9.html

vxworks相关论文

<dl class="margin">

<dd><div class="Indent"><a name="85847"> </a>An Internet address consists of a network number and a host number. There are several different classes of Internet addresses that assign different parts of the 32-bit Internet address to these two parts, but in all cases the network number is given in the most significant bits and the host number is given in the least significant bits. The simple configuration described in this chapter assumes that the host and target are on the same network--they have the same network number. (See <i class="title">VxWorks Network Programmer's Guide: TCP/IP under VxWorks </i>for a discussion of setting up gateways if the host and target are not on the same network.) If the target Internet address is not on the same network as the host, the VxWorks boot program displays the following message:</div>
<br>
<dl class="margin">

<dd><pre class="Code3"><b><a name="85848"></b><tt class="output">Error loading file: errno = 0x33.</tt><b></a></b></pre>
</dl>

<dd><div class="Indent"><a name="85849"> </a>0x33 corresponds to <b class="symbol_lc">errno</b> 51 (decimal) <b class="symbol_UC">ENETUNREACH</b>. (This is one of the POSIX error codes, defined for VxWorks in <b class="file">c:\tornado\target\h\errno.h</b>.)</div>
<br>
<dd><div class="Indent"><a name="85850"> </a>If the target Internet address is not in the appropriate <b class="file">hosts</b> file (or the DNS equivalent), then the host does not know about your target. The VxWorks boot program receives an error message from the host:</div>
<br>
<dl class="margin">

<dd><pre class="Code3"><b><a name="85851"></b><tt class="output">host name for your address unknown 
Error loading file: status = 0x320001.</tt><b></a></b></pre>
</dl>

<dd><div class="Indent"><a name="85853"> </a>0x32 is the VxWorks module number for <b class="library">hostLib</b> 50 (decimal). The digit "1" corresponds to <b class="symbol_UC">S_hostLib_UNKNOWN_HOST</b>. See the <b class="library">errnoLib</b> reference manual entry for a discussion of VxWorks error status values.</div>
<br>
</dl>

<dl class="margin">

<b class="BulletHead"><li><a name="85855"> </a><font face="Helvetica, sans-serif" size="-1" class="sans">Verify FTP server permissions. </font></li></b>
</dl>

<dl class="margin">

<dd><div class="Indent"><a name="85859"> </a>Is the FTP server configured correctly? See <a href="x-wftp.html#83917"><i class="title">F.&nbsp;FTP Server</i></a> for more information on configuring the FTP Server under Windows 95. On Windows NT, consult your system documentation on FTP Server. </div>
<br>
</dl>

<dl class="margin">

<b class="BulletHead"><li><a name="85868"> </a><font face="Helvetica, sans-serif" size="-1" class="sans">Helpful Troubleshooting Tools </font></li></b>
</dl>

<dl class="margin">

<dd><div class="Indent"><a name="85869"> </a>In tracking down configuration problems, the following network tools are helpful:</div>
<br>
</dl>

<dl class="margin">

<dd><div class="Item2"><a name="85870"> </a><b class="command">ping</b></div>
<dl class="margin">

<dd><div class="Indent2"><a name="87262"> </a>This command indicates whether packets are reaching a specified destination. For example, the following indicates this host is successful sending packets to <b class="symbol_lc">venus</b>:</div>
<br>
</dl>

<dl class="margin">

<dd><pre class="Code3"><b><a name="87270"></b><tt class="output">C:\&gt;</tt><b> ping venus 
</b><tt class="output">Pinging venus.wrs.com [91.0.10.1] with 32 bytes data:</tt><b></a></b><dd>
 
<b><a name="87271"></b><tt class="output">Reply from 91.0.10.1: bytes=32 time=10ms TTL=255 
Reply from 91.0.10.1: bytes=32 time&lt;10ms TTL=255 
Reply from 91.0.10.1: bytes=32 time&lt;10ms TTL=255 
Reply from 91.0.10.1: bytes=32 time&lt;10ms TTL=255</tt><b></a></b></pre>
</dl>

<dd><div class="Item2"><a name="85886"> </a><b class="command">arp -a</b></div>
<dl class="margin">

<dd><div class="Indent2"><a name="87263"> </a>This command displays the "address resolution protocol" tables that map Internet addresses to physical (Ethernet) addresses. Your target machine is listed if at least one packet was transferred from your target to your host. The following example shows both the Internet address (91.0.10.1) and physical address (08-00-20-1b-66-e9) of <b class="symbol_lc">venus</b>.</div>
<br>
</dl>

<dl class="margin">

<dd><pre class="Code3"><b><a name="87276"></b><tt class="output">C:\&gt;</tt><b> arp -a 
</b><tt class="output">Interface: 91.0.10.26 
Internet Address      Physical Address      Type 
91.0.10.1           08-00-20-1b-66-e9     dynamic 
91.0.10.20          00-20-af-52-1e-72     dynamic 
91.0.10.254         00-00-ef-01-f1-a0     dynamic</tt><b></a></b></pre>
</dl>

<dd><div class="Item2"><a name="87266"> </a><b class="command">netstat</b></div>
<dl class="margin">

<dd><div class="Indent2"><a name="87267"> </a>This command displays network status reports. The <b class="command">-r</b> option displays the network routing tables. This is useful when gateways are used to access the target.</div>
<br>
</dl>

<dl class="margin">

<dd><pre class="Code3"><b><a name="85905"></b><tt class="output">C:\&gt;</tt><b> netstat -r 
</b><tt class="output">Route Table 
 
Network Address          Netmask  Gateway Address   Interface  Metric 
        0.0.0.0          0.0.0.0      91.0.10.254  91.0.10.26       1 
      127.0.0.0        255.0.0.0        127.0.0.1   127.0.0.1       1 
      91.0.10.0    255.255.255.0       91.0.10.26  91.0.10.26       1 
     91.0.10.26  255.255.255.255        127.0.0.1   127.0.0.1       1 
  91.11.255.255  255.255.255.255       91.0.10.26  91.0.10.26       1 
      224.0.0.0        224.0.0.0       91.0.10.26  91.0.10.26       1 
255.255.255.255  255.255.255.255       91.0.10.26  91.0.10.26       1</tt><b></a></b><dd>
 
<b><a name="85906"></b><tt class="output">Active Connections</tt><b></a></b><dd>
 
<b><a name="85908"></b><tt class="output">  Proto  Local Address          Foreign Address        State 
TCP    mercury:1025           saturn.wrs.com:nbsession  ESTABLISHED 
TCP    mercury:1177           earth.wrs.com:nntp     ESTABLISHED 
TCP    mercury:1259           oak.oakland.edu:ftp    ESTABLISHED</tt><b></a></b></pre>
</dl>

</dl>

</dl>

</dl>

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

<dl class="margin">

<dl class="margin">

<b class="BulletHead"><li><a name="85924"> </a><font face="Helvetica, sans-serif" size="-1" class="sans">Check Back-End Serial Port.</font></li></b>
</dl>

<dl class="margin">

<dd><div class="Indent"><a name="85925"> </a>If you use a WDB Serial connection to the target, make sure you have connected the serial cable to a port on the target system that matches your target-agent configuration. The agent uses serial channel 1 by default, which is different from the channel used by VxWorks as a default console (channel 0). Your board's ports may be numbered starting at one; in that situation, VxWorks channel one corresponds to the port labeled "serial 2."</div>
<br>
</dl>

<dl class="margin">

<b class="BulletHead"><li><a name="85926"> </a><font face="Helvetica, sans-serif" size="-1" class="sans">Verify Path to VxWorks Image.</font></li></b>
</dl>

<dl class="margin">

<dd><div class="Indent"><a name="85927"> </a>The target server requires a host-resident image of the VxWorks run-time system. By default, it obtains a path for this image from the target agent (as recorded in the target boot parameters). In some cases (for example, if the target boots from a local device), this default is not useful. In that situation, use the <b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">Core file</font></b> field in the <b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">Create Target Server</font></b> form (see <a href="c-tools2.html#84296"><i class="title">Core File and Symbols</i></a>) or the equivalent <b class="command">-c</b> option to <b class="command">tgtsvr</b> (<a href="x-toolman.html#83918"><i class="title">C.&nbsp;Tornado Tools Reference</i></a>) to specify the path to a host-resident copy of the VxWorks image. </div>
<br>
</dl>

</dl>

</dl>

<font face="Helvetica, sans-serif" class="sans">
<h4 class="H3"><i><a name="85936">2.9.2  &nbsp;&nbsp;Technical Support</a></i></h4>
</font>
<dl class="margin">

<dl class="margin">

<dd><p class="Body"><a name="85938"> </a>If you have questions or problems with Tornado or with VxWorks after completing the above troubleshooting section, or if you think you have found an error in the software, contact the Wind River Systems customer support organization. Your comments and suggestions are welcome as well. </p>
<dd><p class="Body"><a name="83393"> </a></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-start8.html"><img border="0" alt="[Prev]" src="icons/prev.gif"></a><a href="c-editor.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 --->