c-start3.html

vxworks相关论文

<h4 class="H3"><i><a name="84596">2.3.3  &nbsp;&nbsp;Networking the Host and Target</a></i></h4>
</font>
<dl class="margin">

<dl class="margin">

<dd><p class="Body"><a name="84598"> </a>IP networking over Ethernet is the most desirable way to connect a development target to your host, because of the high bandwidth it provides. This section describes setting up simple IP connections to a target over Ethernet. To read about other communication strategies, see <a href="c-start4.html#90094"><i class="title">2.4&nbsp;Host-Target Communication Configuration</i></a>.</p>
<dd><p class="Body"><a name="91662"> </a>Before VxWorks can boot an executable image obtained from the host, the network software on the host must be correctly configured. There are three main tasks in configuring the host network software to get started with VxWorks:</p>
</dl>

<dl class="margin">

<ul class="BulletSingle" type="disc"><li><a name="84603"> </a>Initializing the host network software.</li></ul>
<ul class="BulletSingle" type="disc"><li><a name="84604"> </a>Establishing the VxWorks system name and network address on the host.</li></ul>
<ul class="BulletSingle" type="disc"><li><a name="84605"> </a>Giving the VxWorks system appropriate access permissions on the host.</li></ul>
</dl>

<dl class="margin">

<dd><p class="Body"><a name="84606"> </a>The following sections describe these procedures in more detail. </p>
</dl>

</dl>

<font face="Helvetica, sans-serif" class="sans">
<h4 class="H4"><i><a name="84612">Initializing the Host Network Software</a></i></h4>
</font>
<dl class="margin">

<dl class="margin">

<dd><p class="Body"><a name="84614"> </a>The TCP/IP networking package should already be installed on the Windows host where you are configuring Tornado; TCP/IP is generally installed when the operating system is first installed. If TCP/IP is not yet installed on your Tornado host, install it now. Consult your Windows documentation on installing and configuring TCP/IP for your PC.</p>
<dd><p class="Body"><a name="84615"> </a>If you are planning to boot VxWorks over the network (the default VxWorks-target boot configuration), you must have an FTP server running on the host where the VxWorks system image is stored, and the FTP server must have a user ID and password defined that your VxWorks target can use to identify itself. </p>
<dd><p class="Body"><a name="84619"> </a>On Windows 95, Tornado includes an FTP-server application, <b>wftpd32.exe</b>. See <a href="x-wftp.html#83917"><i class="title">F.&nbsp;FTP Server</i></a> for information on configuring this FTP server.</p>
<dd><p class="Body"><a name="84621"> </a>On Windows NT, we recommend that you install the FTP server as an NT service when you install TCP/IP. </p>
</dl>

</dl>

<font face="Helvetica, sans-serif" class="sans">
<h4 class="H4"><i><a name="84626">Establishing the VxWorks Target Name and IP Address</a></i></h4>
</font>
<dl class="margin">

<dl class="margin">

<dd><p class="Body"><a name="84631"> </a>With TCP/IP installed, you can configure the server that provides Domain Name Service (DNS) so that your Windows computer uses that server to translate system names to network IP addresses. Consult your Windows documentation on how to configure your system to take advantage of DNS.</p>
<dd><p class="Body"><a name="84632"> </a>If you do not have a domain name server at your site, you can specify how to map machine names to IP addresses in a file (discussed below) on your machine. Otherwise, you must identify targets by IP address.</p>
<dd><p class="Body"><a name="84634"> </a>Windows uses a file called <b class="file">hosts</b> to record the names and IP network addresses of systems accessible on the network from the local system. The location of this file depends on which version of Windows you use:</p>
</dl>

<dl class="margin">

<p class="listspace">
<ul class="Bullet" type="disc"><li><a name="84635"> </a>Windows 95 and 98: the <b class="file">hosts</b> file is <b class="file">c:\windows\hosts</b></li></ul>
</p>
<p class="listspace">
<ul class="Bullet" type="disc"><li><a name="84636"> </a>Windows NT: the <b class="file">hosts</b> file is <b class="file">c:\winnt\system32\drivers\etc\hosts</b>) </li></ul>
</p>
</dl>

<dl class="margin">

<dd><p class="Body"><a name="84637"> </a>Each line consists of an IP address and the name (or names) of the system at that address.</p>
<dd><p class="Body"><a name="84638"> </a>For example, suppose your host system is called <b class="symbol_lc">mars</b> and has Internet address 90.0.0.1, and you want to name your VxWorks target <b class="symbol_lc">phobos</b> and assign it address 90.0.0.50. The <b class="file">hosts</b> file must then contain the following lines:</p>
<dl class="margin">

<dd><pre class="Code2"><b><a name="84639">90.0.0.1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;mars 
90.0.0.50&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;phobos</a></b></pre>
</dl>

</dl>

</dl>

<font face="Helvetica, sans-serif" class="sans">
<h4 class="H3"><i><a name="84678">2.3.4  &nbsp;&nbsp;Configuring the Target Hardware</a></i></h4>
</font>
<dl class="margin">

<dl class="margin">

<dd><p class="Body"><a name="84680"> </a><b></b>Configuring the target hardware may involve the following tasks:</p>
</dl>

<dl class="margin">

<ul class="BulletSingle" type="disc"><li><a name="84681"> </a>Setting up a boot mechanism.</li></ul>
<ul class="BulletSingle" type="disc"><li><a name="84682"> </a>Jumpering the target CPU board, and any auxiliary boards (for example, Ethernet).</li></ul>
<ul class="BulletSingle" type="disc"><li><a name="84683"> </a>Installing the boards in a chassis, or connecting a power supply.</li></ul>
<ul class="BulletSingle" type="disc"><li><a name="84684"> </a>Connecting a serial cable.</li></ul>
<ul class="BulletSingle" type="disc"><li><a name="84685"> </a>Connecting an Ethernet cable, if the target supports networking.</li></ul>
</dl>

<dl class="margin">

<dd><p class="Body"><a name="84686"> </a>The following general procedures outline common situations. Select from them as appropriate to your particular target hardware. Refer also to the specific information in the target-information reference entry for your BSP (see <b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">Help</font></b>&gt;<b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">Manuals&nbsp;Contents</font></b>&gt;<b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">BSP&nbsp;Reference </font></b>in the Tornado IDE<b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">; </font></b>the file <b class="file">c:\tornado\docs\BSP_Reference.html</b>).</p>
</dl>

</dl>

<font face="Helvetica, sans-serif" class="sans">
<h4 class="H4"><i><a name="84688">Boot ROMs and Other Boot Media</a></i></h4>
</font>
<dl class="margin">

<dl class="margin">

<dd><p class="Body"><a name="84690"> </a><b></b>Tornado includes one of the following boot media as part of each VxWorks BSP package:</p>
</dl>

<dl class="margin">

<dd><div class="Item"><a name="91593"> </a>Boot ROM</div>
<dl class="margin">

<dd><div class="Indent"><a name="91594"> </a>Most BSPs include boot ROMs.</div>
<br>
</dl>

<dd><div class="Item"><a name="84692"> </a>Floppy Disk</div>
<dl class="margin">

<dd><div class="Indent"><a name="84693"> </a>Some BSPs for systems that include floppy drives use boot diskettes instead of a boot ROM. For example, the BSPs for PC386 or PC486 systems usually boot from diskette.</div>
<br>
</dl>

<dd><div class="Item"><a name="84694"> </a>Flash Memory</div>
<dl class="margin">

<dd><div class="Indent"><a name="84695"> </a>For boards that support flash memory, the BSP may be designed to write the boot program there. In such cases, an auxiliary program is supplied to write the boot program into flash memory.</div>
<br>
</dl>

</dl>

<dl class="margin">

<dd><p class="Body"><a name="84699"> </a>For specific information on a BSP's booting method, see <b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">Help</font></b>&gt;<b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">Manuals&nbsp;Contents</font></b>&gt;<b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">BSP&nbsp;Reference</font></b>.</p>
<dd><p class="Body"><a name="91789"> </a>You may also wish to replace a boot ROM, even if it is available, with a ROM emulator. This is particularly desirable if your target has no Ethernet capability, because the ROM emulator can be used to provide connectivity at near-Ethernet speeds. Tornado includes support for one such device, NetROM.<sup><a href="#foot"><b class="FootnoteMarker">1</b></a></sup>
 For information about how to use NetROM on your target, refer to <a href="c-builder6.html#99151"><i class="title">Configuration for NetROM Connection</i></a>. Contact the nearest Wind River Systems office (see back cover) for information about support for other ROM emulators.</p>
<dd><p class="Body"><a name="84709"> </a>For cases where boot ROMs are used to boot VxWorks, install the appropriate set of boot ROMs on your target board(s). When installing boot ROMs, be careful to:</p>
</dl>

<dl class="margin">

<ul class="BulletSingle" type="disc"><li><a name="84710"> </a>Install each device only in the socket indicated on the label.</li></ul>
<ul class="BulletSingle" type="disc"><li><a name="84711"> </a>Note the correct orientation of pin 1 for each device.</li></ul>
<ul class="BulletSingle" type="disc"><li><a name="84712"> </a>Use anti-static precautions whenever working with integrated circuit devices.</li></ul>
</dl>

<dl class="margin">

<dd><p class="Body"><a name="94075"> </a>See <a href="c-buildera7.html#103278"><i class="title">4.7&nbsp;Configuring and Building a VxWorks Boot Program</i></a> for instructions on creating a new boot program with parameters customized for your site.</p>
</dl>

</dl>

<font face="Helvetica, sans-serif" class="sans">
<h4 class="H4"><i><a name="84717">Setting Board Jumpers</a></i></h4>
</font>
<dl class="margin">

<dl class="margin">

<dd><p class="Body"><a name="93997"> </a>Many CPU and Ethernet controller boards still have configuration options that are selected by hardware jumpers, although this is less common than in the past. These jumpers must be installed correctly before VxWorks can boot successfully. You can determine the correct jumper configuration for your target CPU from the information provided in the<i class="acronym_lc"> </i>target-information reference for your BSP (see <b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">Help</font></b>&gt;<b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">Manuals</font></b>&gt;<b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">BSP&nbsp;Reference </font></b>in the Tornado IDE; the file <b class="file">c:\tornado\docs\BSP_Reference.html</b>).</p>
</dl>

</dl>

<font face="Helvetica, sans-serif" class="sans">
<h4 class="H4"><i><a name="84723">Board Installation and Power</a></i></h4>
</font>
<dl class="margin">

<dl class="margin">

<dd><p class="Body"><a name="84725"> </a>For bare-board targets, use the power supply recommended by the board manufacturer.</p>
<dd><p class="Body"><a name="84727"> </a>If you are using a VME chassis, first install the CPU board in the first slot of the backplane (<a href="c-start3.html#84751">Figure&nbsp;2-4</a>). If you are using a separate Ethernet controller board, install it in the second slot of the backplane.<div class="frame">
<h4 class="EntityTitle"><a name="84751"><font face="Helvetica, sans-serif" size="-1" class="sans">Figure 2-4:&nbsp;&nbsp;Assembling VME Targets</font></a></h4>

<dl class="margin">

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



</dl>

</div>
</p>
<dd><p class="Body"><a name="84754"> </a>On a VMEbus backplane, there are several issues to consider:</p>
</dl>

<dl class="margin">

<dd><div class="Item"><a name="84755"> </a>P1 and P2 Connectors</div>
<dl class="margin">

<dd><div class="Indent"><a name="84756"> </a>The P1 connector must be completely bussed across all the boards in the system. </div>
<br>
<dd><div class="Indent"><a name="84757"> </a>Many systems also require the P2 bus. Some boards require power on the P2 connector, and some require the extended address and data lines of row B of the P2 bus.</div>
<br>
</dl>

<dd><div class="Item"><a name="84759"> </a>System Controller</div>
<dl class="margin">

<dd><div class="Indent"><a name="84760"> </a>The VME bus requires a <i class="term">system controller</i> to be present in the first slot. Many CPU boards have a system controller on board that can be enabled or disabled by hardware jumpers. On such boards, enable the system controller in the first slot and disable it in all others. The diagrams in the target-information reference indicate the location of the system controller enable jumper, if any. Alternatively, a separate system controller board can be installed in the first slot and the CPU and Ethernet boards can be plugged into the next two slots.</div>
<br>
</dl>

<dd><div class="Item"><a name="84762"> </a>Empty Slots</div>
<dl class="margin">

<dd><div class="Indent"><a name="84763"> </a>The VME bus has several daisy-chained signals that must be propagated to all the boards on the backplane. If you leave any slot empty between boards on the backplane, you must jumper the backplane to complete the daisy chain for the BUS GRANT and INT ACK signals.</div>
<br>
</dl>

</dl>

</dl>

<font face="Helvetica, sans-serif" class="sans">
<h4 class="H4"><i><a name="84767">Connecting a Serial Cable for Terminal Emulator</a></i></h4>
</font>
<dl class="margin">

<dl class="margin">

<dd><p class="Body"><a name="84768"> </a>Most VxWorks targets include at least one on-board serial port. This serial port must be connected to a terminal emulator (HyperTerminal), at least for the initial configuration of the boot parameters and getting started with VxWorks. Subsequently, VxWorks can be configured to boot automatically without a terminal. Refer to the CPU board hardware documentation for proper connection of the RS-232 signals.</p>
<dd><p class="Body"><a name="91294"> </a>Tornado comes with terminal-emulator configurations already set up for connecting to VxWorks targets on either COM1 or COM2, in the same program folder as other Tornado programs. Use <b>VxWorks COM1</b> if the serial connection from your target is to COM1, or <b>VxWorks COM2</b> if the target is connected to COM2.</p>
</dl>

</dl>

<font face="Helvetica, sans-serif" class="sans">
<h4 class="H4"><i><a name="91292">Connecting a Cable for Ethernet Connection</a></i></h4>
</font>
<dl class="margin">

<dl class="margin">

<dd><p class="Body"><a name="84771"> </a>For the Ethernet connection, a transceiver cable must be connected from the Ethernet controller to an Ethernet transceiver.</p>
</dl>

</dl>


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

<p class="FootnoteNumberMarker">1:&nbsp;
<span class="Footnote"><a name="84704"> </a>NetROM is a trademark of Applied Microsystems Corporation.</span>

<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-start2.html"><img border="0" alt="[Prev]" src="icons/prev.gif"></a><a href="c-start4.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 --->