c-start5.html

来自「vxworks相关论文」· HTML 代码 · 共 984 行 · 第 1/3 页

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

<td colspan=1 rowspan=1>
<p class="BodyLeft"><a name="87413"> </a>Auto-boot fast (short countdown).</p>

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


</tr>
<tr valign="top">
<td colspan=1 rowspan=1>
<p class="BodyLeft"><a name="87415"> </a><b class="symbol_lc">0x20</b></p>

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

<td colspan=1 rowspan=1>
<p class="BodyLeft"><a name="87417"> </a>=</p>

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

<td colspan=1 rowspan=1>
<p class="BodyLeft"><a name="87419"> </a>Disable login security.</p>

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


</tr>
<tr valign="top">
<td colspan=1 rowspan=1>
<p class="BodyLeft"><a name="87421"> </a><b class="symbol_lc">0x40</b></p>

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

<td colspan=1 rowspan=1>
<p class="BodyLeft"><a name="87423"> </a>=</p>

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

<td colspan=1 rowspan=1>
<p class="BodyLeft"><a name="87425"> </a>Use BOOTP to get boot parameters.</p>

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


</tr>
<tr valign="top">
<td colspan=1 rowspan=1>
<p class="BodyLeft"><a name="87427"> </a><b class="symbol_lc">0x80</b></p>

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

<td colspan=1 rowspan=1>
<p class="BodyLeft"><a name="87429"> </a>=</p>

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

<td colspan=1 rowspan=1>
<p class="BodyLeft"><a name="87431"> </a>Use TFTP to get boot image.</p>

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


</tr>
<tr valign="top">
<td colspan=1 rowspan=1>
<p class="BodyLeft"><a name="87433"> </a><b class="symbol_lc">0x100</b></p>

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

<td colspan=1 rowspan=1>
<p class="BodyLeft"><a name="87435"> </a>=</p>

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

<td colspan=1 rowspan=1>
<p class="BodyLeft"><a name="87437"> </a>Use proxy ARP.</p>

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


</tr>

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

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

<dd><div class="Item"><a name="85006"> </a><b class="symbol_lc">target name (tn)</b></div>
<dl class="margin">

<dd><div class="Indent"><a name="87384"> </a>The name of the target system to be added to the host table (<b class="symbol_lc">phobos</b> in the example).</div>
<br>
</dl>

<dd><div class="Item"><a name="85008"> </a><b class="symbol_lc">startup script (s)</b></div>
<dl class="margin">

<dd><div class="Indent"><a name="87386"> </a>If the target-resident shell is included in the downloaded image, this parameter allows you to pass to it the complete path name of a startup script to execute after the system boots. In the default Tornado configuration, this parameter has no effect, because the target-resident shell is not included.</div>
<br>
</dl>

<dd><div class="Item"><a name="85009"> </a><b class="symbol_lc">other (o)</b></div>
<dl class="margin">

<dd><div class="Indent"><a name="87388"> </a>This parameter is generally unused and available for applications (blank in the example). It can be used when booting from a local SCSI disk to specify a network interface to be included.</div>
<br>
</dl>

</dl>

</dl>

<font face="Helvetica, sans-serif" class="sans">
<h4 class="H3"><i><a name="85011">2.5.5  &nbsp;&nbsp;Booting With New Parameters</a></i></h4>
</font>
<dl class="margin">

<dl class="margin">

<dd><p class="Body"><a name="85013"> </a>Once you have entered the boot parameters, initiate booting by typing the <b class="command">@</b> command at the boot prompt: </p>
<dl class="margin">

<dd><pre class="Code2"><b><a name="85028"></b><tt class="output">[VxWorks Boot]:</tt><b> @ </a></b></pre>
</dl>

<dd><p class="Body"><a name="95305"> </a><div class="frame">
<h4 class="EntityTitle"><a name="85027"><font face="Helvetica, sans-serif" size="-1" class="sans">Figure 2-9:&nbsp;&nbsp;VxWorks Booting Display</font></a></h4>

<dl class="margin">

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



</dl>

</div>
</p>
<dd><p class="Body"><a name="85032"> </a><a href="c-start5.html#85027">Figure&nbsp;2-9</a> shows a typical VxWorks boot display. The VxWorks boot program prints the boot parameters, and the downloading process begins. The following information is displayed during the boot process:</p>
</dl>

<dl class="margin">

<p class="listspace">
<ul class="Bullet" type="disc"><li><a name="85033"> </a>The boot program first initializes its network interfaces.</li></ul>
</p>
<p class="listspace">
<ul class="Bullet" type="disc"><li><a name="85034"> </a>While VxWorks is booting, you can see the size of each VxWorks section (text, data, and bss) as it is loaded. </li></ul>
</p>
<p class="listspace">
<ul class="Bullet" type="disc"><li><a name="85035"> </a>After the system is completely loaded, the boot program displays the entry address and transfers control to the loaded VxWorks system. </li></ul>
</p>
<p class="listspace">
<ul class="Bullet" type="disc"><li><a name="85036"> </a>When VxWorks starts up, it begins just as the boot ROM did, by initializing its network interfaces; the network-initialization messages appear again, sometimes accompanied by other messages about optional VxWorks facilities.</li></ul>
</p>
<p class="listspace">
<ul class="Bullet" type="disc"><li><a name="85037"> </a>After that point, VxWorks is up and ready to attach to the Tornado tools.</li></ul>
</p>
<p class="listspace">
<ul class="Bullet" type="disc"><li><a name="87439"> </a>The boot display may be useful for troubleshooting. The following hints refer to <a href="c-start5.html#85027">Figure&nbsp;2-9</a>. For more troubleshooting ideas, see <a href="c-start9.html#85814"><i class="title">2.9&nbsp;Troubleshooting</i></a>.</li></ul>
</p>
<p class="listspace">
<ul class="Bullet" type="disc"><li><a name="87446"> </a>The initial "Attaching network interface" is displayed without the corresponding "done," verify that the system controller is configured properly and the Ethernet board is properly jumpered.</li></ul>
</p>
<p class="listspace">
<ul class="Bullet" type="disc"><li><a name="85050"> </a>If "Loading..." is displayed without the size of the VxWorks image, this may indicate problems with the Ethernet cable or connection, or an error in the network configuration (for example, a bad host or gateway Internet address).</li></ul>
</p>
<p class="listspace">
<ul class="Bullet" type="disc"><li><a name="85051"> </a>If the line "Starting at" is printed and there is no further indication of activity from VxWorks, this generally indicates there is a problem with the boot image.</li></ul>
</p>
<p class="listspace">
<ul class="Bullet" type="disc"><li><a name="85052"> </a>If "Attaching network interface" is displayed without the "done," this may indicate there is a problem with the network driver in the newly loaded VxWorks image.</li></ul>
</p>
</dl>

</dl>

<font face="Helvetica, sans-serif" class="sans">
<h4 class="H3"><i><a name="85056">2.5.6  &nbsp;&nbsp;Alternate Boot Methods</a></i></h4>
</font>
<dl class="margin">

<dl class="margin">

<dd><p class="Body"><a name="89843"> </a>To boot VxWorks, you can also use the command line, take advantage of non-volatile RAM, or create new boot programs for your target.</p>
</dl>

</dl>

<dl class="margin">

<dd><font face="Helvetica, sans-serif" size="-1" class="sans">
<h5 class="HU"><i><a name="85058">Command-Line Parameters</a></i></h5>
</font><dl class="margin">

<dd><p class="Body"><a name="85059"> </a>Instead of being prompted for each of the boot parameters, you can supply the boot program with all the parameters on a single line at the boot prompt (<tt class="output">[VxWorks&nbsp;Boot]:</tt>) beginning with a dollar sign character ("<b class="command">$</b>"). For example:</p>
</dl>

</dl>

<pre class="CodeLeft"><b><a name="85061">        $ln(0,0)mars:c:\tornado\target\config\<i class="textVariable">bsp</i>\vxWorks&nbsp;e=90.0.0.50&nbsp;h=90.0.0.1&nbsp;u=fred&nbsp;pw=</a></b></pre>
<dl class="margin">

<dl class="margin">

<dd><p class="Body"><a name="85062"> </a>The order of the assigned fields (those containing equal signs) is not important. Omit any assigned fields that are irrelevant. The codes for the assigned fields correspond to the letter codes shown in parentheses by the <b class="command">p</b> command. For a full description of the format, see the reference entry for <b class="routine"><i class="routine">bootStringToStruct</i></b><b>(</b>&nbsp;<b>)</b> in <b class="library">bootLib</b>. </p>
<dd><p class="Body"><a name="85064"> </a>This method can be useful if your workstation has programmable function keys. You can program a function key with a command line appropriate to your configuration. </p>
</dl>

</dl>

<dl class="margin">

<dd><font face="Helvetica, sans-serif" size="-1" class="sans">
<h5 class="HU"><i><a name="85066">Nonvolatile RAM (NVRAM)</a></i></h5>
</font><dl class="margin">

<dd><p class="Body"><a name="85067"> </a>As noted previously, if your target CPU has nonvolatile RAM (NVRAM), all the values you enter in the boot parameters are retained in the NVRAM. In this case, you can let the boot program auto-boot without having a terminal connected to the target system.</p>
</dl>

<dd><font face="Helvetica, sans-serif" size="-1" class="sans">
<h5 class="HU"><i><a name="85070">Customized Boot Programs</a></i></h5>
</font><dl class="margin">

<dd><p class="Body"><a name="94095"> </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 for your boot media, with parameters customized for your site. With this method, you no longer need to alter boot parameters before booting. </p>
</dl>

<dd><font face="Helvetica, sans-serif" size="-1" class="sans">
<h5 class="HU"><i><a name="92271">BSPs Requiring TFTP on the Host</a></i></h5>
</font><dl class="margin">

<dd><p class="Body"><a name="92272"> </a>Some Motorola boards that use Bug ROMs and place boot code in flash require TFTP on the host in order to burn a new VxWorks image into flash. Tornado 2.0 ships with a version of TFTP. See your vendor documentation on how to burn flash for these boards.</p>
</dl>

</dl>

<font face="Helvetica, sans-serif" class="sans">
<h4 class="H3"><i><a name="94118">2.5.7  &nbsp;&nbsp;Booting a Target Without a Network</a></i></h4>
</font>
<dl class="margin">

<dl class="margin">

<dd><p class="Body"><a name="94123"> </a>You can boot a target that is not on a network most easily over a serial line with the Target Server File System (TSFS). The TSFS provides the target with direct access to the host's file system. Using TSFS is simpler than configuring and using PPP or SLIP. </p>
<dd><p class="Body"><a name="94124"> </a>To boot a target using TSFS, you must first reconfigure and rebuild the boot program, and copy it to the boot medium for your target (for example, burn a new boot ROM or copy it to a diskette). See <a href="c-buildera7.html#103278"><i class="title">4.7&nbsp;Configuring and Building a VxWorks Boot Program</i></a>. </p>
<dd><p class="Body"><a name="94129"> </a>Before you boot the target, configure a target server with the TSFS option and start it. See <a href="c-tools2.html#90892"><i class="title">Target Server File System</i></a>.</p>
<dd><p class="Body"><a name="95176"> </a>The only boot parameters required to boot the target are <b class="symbol_lc">boot device</b> and <b class="symbol_lc">file name</b> (see <a href="c-start5.html#84962"><i class="title">2.5.4&nbsp;Description of Boot Parameters</i></a>). The <b class="symbol_lc">boot device</b> parameter should be set to <b class="symbol_lc">tsfs</b>. The <b class="symbol_lc">file name</b> parameter should be set relative to the TSFS root directory that is defined when you configure the target server for the TSFS. You can configure the boot program with these parameters, or enter them at the VxWorks prompt at boot time.</p>
</dl>

</dl>

<font face="Helvetica, sans-serif" class="sans">
<h4 class="H3"><i><a name="85085">2.5.8  &nbsp;&nbsp;Rebooting VxWorks</a></i></h4>
</font>
<dl class="margin">

<dl class="margin">

<dd><p class="Body"><a name="85087"> </a>When VxWorks is running, there are several ways you can reboot VxWorks. Rebooting by any of these means restarts the attached target server on the host as well:</p>
</dl>

<dl class="margin">

<p class="listspace">
<ul class="Bullet" type="disc"><li><a name="85089"> </a>Entering <kbd>CTRL+X</kbd> in the serial terminal window. (This works only if you use the preconfigured terminal emulation icons shipped with Tornado; other terminal emulators do not pass <kbd>CTRL+X</kbd> to the target, because of its standard Windows meaning.)</li></ul>
</p>
<p class="listspace">
<ul class="Bullet" type="disc"><li><a name="85097"> </a>Invoking <b class="routine"><i class="routine">reboot</i></b><b>(</b>&nbsp;<b>)</b> from the Tornado shell.</li></ul>
</p>
<p class="listspace">
<ul class="Bullet" type="disc"><li><a name="85098"> </a>Pressing the reset button on the target system.</li></ul>
</p>
<p class="listspace">
<ul class="Bullet" type="disc"><li><a name="85099"> </a>Turning the target's power off and on.</li></ul>
</p>
</dl>

<dl class="margin">

<dd><p class="Body"><a name="85100"> </a>When you reboot VxWorks in any of these ways, the auto-boot sequence begins again from the countdown.</p>
</dl>

</dl>


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

<p class="FootnoteNumberMarker">1:&nbsp;
<span class="Footnote"><a name="89697"> </a>Unless your target CPU has nonvolatile RAM (NVRAM), you will eventually find it useful to build a new version of the boot loader that includes all parameters required for booting a VxWorks image (see <a href="c-buildera7.html#103278"><i class="title">4.7&nbsp;Configuring and Building a VxWorks Boot Program</i></a>). In the course of your developing an application, you will also build bootable applications (see <a href="c-builder4.html#89245"><i class="title">4.4&nbsp;Creating a Bootable Application</i></a>).</span>
<p class="FootnoteNumberMarker">2:&nbsp;
<span class="Footnote"><a name="84980"> </a>If the same pathname is not suitable for both host and target--for example, if you boot from a disk attached only to the target--you can specify the host path separately to the target server, using the <b class="guiLabel"><font face="Helvetica, sans-serif" size="-1" class="sans">Core file</font></b> field (<b class="command">-c</b> option). See <a href="c-tools6.html#84394"><i class="title">5.6&nbsp;Managing a Target Server</i></a>.</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-start4.html"><img border="0" alt="[Prev]" src="icons/prev.gif"></a><a href="c-start6.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 --->