gettingstarted4.html

vxworks相关论文

<p><ol class="List"><li value="2."><a name="95799"> </a>Edit <b class="file">sysLib.c</b> as described in <a href="gettingStarted4.html#95744"><i class="title">Changing syslib.c</i></a>. </li></ol></p>
<p><ol class="List"><li value="3."><a name="95143"> </a>Change the <b class="file">Makefile</b> as specified in <a href="gettingStarted2.html#85369"><i class="title">Changing the Makefile</i></a>. </li></ol></p>
<p><ol class="List"><li value="4."><a name="95144"> </a>Remake VxWorks. </li></ol></p>
<p><ol class="List"><li value="5."><a name="95145"> </a>Reboot the target. </li></ol></p>
<p><ol class="List"><li value="6."><a name="95146"> </a>Insert a flash card in each PCMCIA socket. </li></ol></p>
<p><ol class="List"><li value="7."><a name="95147"> </a>At the target shell prompt, enter the following commands: </li></ol></p>
<dl class="margin">

<dl class="margin">

<dd><pre class="Code3"><b><a name="95148"></b><tt class="output">-&gt; </tt><b>tffsDevFormat 0,0 
</b><tt class="output">-&gt; </tt><b>tffsDevFormat 1,0 
</b><tt class="output">-&gt; </tt><b>tffsDevFormat 2,0 
</b><tt class="output">-&gt; </tt><b>usrTffsConfig 0,0,"/DOC/" 
</b><tt class="output">-&gt; </tt><b>usrTffsConfig 1,1,"/PCMCIA1/" 
</b><tt class="output">-&gt; </tt><b>usrTffsConfig 2,1,"/PCMCIA2/"</a></b></pre>
</dl>

</dl>

</dl>

</dl>

<font face="Helvetica, sans-serif" class="sans">
<h4 class="H4"><i><a name="95149">Adding Boot Code to the DiskOnChip 2000</a></i></h4>
</font>
<dl class="margin">

<dl class="margin">

<dd><p class="Body"><a name="95150"> </a>The DiskOnChip 2000 uses BIOS extensions to make itself appear to the BIOS as a hard disk. This section outlines the procedures you must follow to make sure that the DiskOnChip 2000 device correctly presents itself to the BIOS as a hard disk. VxWorks can then use the DiskOnChip 2000 as a boot device (just as if it were a floppy driver or a conventional hard disk). </p>
</dl>

</dl>

<dl class="margin">

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

<p><ol class="List"><li value="1."><a name="95152"> </a>Build your VxWorks boot image (usually <b class="file">bootrom_uncmp</b>).</li></ol></p>
<p><ol class="List"><li value="2."><a name="95153"> </a>Boot DOS on your target.</li></ol></p>
<p><ol class="List"><li value="3."><a name="95154"> </a>Run <b class="command">dformat </b>on the DiskOnChip 2000 flash device. </li></ol></p>
<dl class="margin">

<dd><div class="Indent"><a name="95155"> </a>The <b class="command">dformat </b>utility is an M-Systems tool that you should have received with your DiskOnChip 2000 flash device. Running the <b class="command">dformat </b>utility clears the flash medium. </div>
<br>
</dl>

<p><ol class="List"><li value="4."><a name="95156"> </a>Using the <b class="command">/s</b> switch, run the DOS format utility on the flash device. This guarantees that the flash medium has system tracks on it. The VxWorks boot strap installer assumes that you have done this and proceeds to modify the contents of the boot sector.</li></ol></p>
</dl>

<dd><font face="Helvetica, sans-serif" size="-1" class="sans">
<h5 class="HU"><i><a name="95157">Installing the VxWorks Boot Code</a></i></h5>
</font><dl class="margin">

<dd><p class="Body"><a name="95158"> </a>You may install the VxWorks boot code using either DOS or the commands available from a VxWorks target shell. </p>
</dl>

<dl class="margin">

<dd><b class="HU-run"><a name="95159"> </a><font face="Helvetica, sans-serif" size="-1" class="sans">Installing from DOS</font></b>
</dl>

<dl class="margin">

<dd><p class="Body"><a name="95160"> </a>To use this method, you must be able to connect a floppy drive to your target. You must also be able to boot DOS on the target. </p>
</dl>

<dl class="margin">

<p><ol class="List"><li value="1."><a name="95161"> </a>Make a bootable floppy disk to which you must then copy the following files:</li></ol></p>
<dl class="margin">

<ul class="DashSingle2" type="circle"><li><a name="95162"> </a>From <b class="file">host\x86-win32\bin</b>: </li></ul>
<dl class="margin">

<dd><div class="Indent2"><a name="95163"> </a><b class="file">mkboot.bat <br>
vxcopy.exe <br>
vxsys.exe</b></div>
<br>
</dl>

<ul class="DashSingle2" type="circle"><li><a name="95164"> </a>From <b class="file">target\config\pc386</b> or <b class="file">target\config\pc486</b>: </li></ul>
<dl class="margin">

<dd><div class="Indent2"><a name="95165"> </a><b class="file">bootrom_uncmp</b></div>
<br>
</dl>

<ul class="DashSingle2" type="circle"><li><a name="95166"> </a>From the your DOS distribution:</li></ul>
<dl class="margin">

<dd><div class="Indent2"><a name="95167"> </a>chkdsk.exe </div>
<br>
</dl>

</dl>

<p><ol class="List"><li value="2."><a name="95168"> </a>Put the floppy in the drive connected to your target.</li></ol></p>
<p><ol class="List"><li value="3."><a name="95169"> </a>Boot the target from the floppy. </li></ol></p>
<p><ol class="List"><li value="4."><a name="95170"> </a>Run <b class="command">mkboot</b> from the floppy:</li></ol></p>
<dl class="margin">

<dl class="margin">

<dd><pre class="Code3"><b><a name="95171">mkboot <i class="textVariable">flash_disk_drive_letter</i>: bootrom_uncmp </a></b></pre>
</dl>

</dl>

<dl class="margin">

<dd><div class="Indent"><a name="95175"> </a>For more information on mkboot, see the mkboot reference entry.<sup><a href="#foot"><b class="FootnoteMarker">3</b></a></sup>
 </div>
<br>
<dd><div class="Indent"><a name="95176"> </a>The 8.3 version of <b class="command">bootrom_uncmp</b> usually lists as <b class="command">bootro~1</b>. It causes no problems for <b class="command">mkboot </b>if you specify <b class="command">bootrom_uncmp</b> as <b class="command">bootro~1</b>.</div>
<br>
</dl>

<p><ol class="List"><li value="5."><a name="95177"> </a>Remove floppy and reboot the target. The target should now boot VxWorks from the DiskOnChip 2000. </li></ol></p>
</dl>

<dl class="margin">

<dd><b class="HU-run"><a name="95178"> </a><font face="Helvetica, sans-serif" size="-1" class="sans">Installing from VxWorks</font></b>
</dl>

<dl class="margin">

<dd><p class="Body"><a name="95179"> </a>To use this method, you need an Ethernet connection to your target. After installing TrueFFS for Tornado and building VxWorks with TrueFFS included, reboot your target. </p>
</dl>

<dl class="margin">

<p><ol class="List"><li value="1."><a name="95180"> </a>Build <b class="file">mkboot.o</b> in the BSP directory. </li></ol></p>
<p><ol class="List"><li value="2."><a name="95181"> </a>Open a target shell and enter the following commands: </li></ol></p>
<dl class="margin">

<dl class="margin">

<dd><pre class="Code3"><b><a name="95182">-&gt; ld &lt; <i class="textVariable">path_to_target_BSP_directory</i>/mkboot.o  
-&gt; mkbootTffs 0,0,"<i class="textVariable">path_to_target_BSP_directory</i>/bootro~1"</a></b></pre>
</dl>

</dl>

<dl class="margin">

<dd><div class="Indent"><a name="95183"> </a>The first zero in the <b class="command">mkbootTffs</b> command shown above is the drive number. The second zero indicates that the flash device is not removable (that is, not a PC flash card). </div>
<br>
</dl>

</dl>

</dl>

<font face="Helvetica, sans-serif" class="sans">
<h4 class="H4"><i><a name="95184">X-86 Pitfalls--CMOS Setup</a></i></h4>
</font>
<dl class="margin">

<dl class="margin">

<p><ol class="List"><li value="1."><a name="95185"> </a>Shadowing must be turned off for the memory region in which DiskOnChip 2000 or any other flash device is located. </li></ol></p>
<p><ol class="List"><li value="2."><a name="95186"> </a>Caching must be turned off (disabled) in the flash disk region. </li></ol></p>
<dl class="margin">

<dd><div class="Indent"><a name="95187"> </a>In some BIOSs, you can specifically disable caching in the following regions: A0000 to F0000. </div>
<br>
</dl>

<p><ol class="List"><li value="3."><a name="95188"> </a>Some BIOSs handle caching in a way that is incompatible with TrueFFS. For these BIOSs, you must disable the external (L2) cache.  You can leave the internal cache enabled. </li></ol></p>
<p><ol class="List"><li value="4."><a name="95189"> </a>Some PnP BIOSs do not load the DiskOnChip 2000 BIOS extension correctly. There is no way to test for this except to plug a DiskOnChip 2000 into the x86 board. The issue is being addressed with the BIOS venders.  There is a special debug version of TFFS BIOS for testing the system. You can get this version from M-Systems. </li></ol></p>
<dl class="margin">

<dl class="margin">

<dd><pre class="Code3"><b><a name="95077"></a></b></pre>
</dl>

</dl>

</dl>

</dl>


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

<p class="FootnoteNumberMarker">1:&nbsp;
<span class="Footnote"><a name="95266"> </a>Support for "hot swapping" means registering a function to handle the interrupt generated when the user removes a device from the PCMCIA socket. </span>
<p class="FootnoteNumberMarker">2:&nbsp;
<span class="Footnote"><a name="96236"> </a>The DiskOnChip 2000 is a "disk on chip" device supplied by M-Systems. </span>
<p class="FootnoteNumberMarker">3:&nbsp;
<span class="Footnote"><a name="95174"> </a>There are two versions of <b class="command">mkboot</b>; one that runs on DOS, and one that runs on VxWorks. The purpose of <b class="command">mkboot</b> is to install the VxWorks boot code on the boot disk. Both versions expect that the system tracks have been installed from DOS's format utility using the <b class="command">/s</b> switch. For more information, see the x86 release notes.</span>

<p class="navbar" align="right"><a href="index.html"><img border="0" alt="[Contents]" src="icons/contents.gif"></a></a><a href="gettingStarted.html"><img border="0" alt="[Top]" src="icons/top.gif"></a><a href="gettingStarted3.html"><img border="0" alt="[Prev]" src="icons/prev.gif"></a><a href="binding.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 --->