vxw_pt2.html

vxworks及tornado常见问题解答

<li>Type <code>vxcopy bootrom.dat d:bootrom.sys</code>.
vxcopy copys &amp; converts the bootrom_uncmp file to the required format.</li>
</ul>
</blockquote>
(From: Ezra Koper, [e-mail])

<p>
<hr WIDTH="50%">
<a NAME="2.3-L"></a>

<p>Q: When booting using the wu_ftpd shipped with RedHat 6.2 the booting
hangs during the download.
<p>A: The system does not hang, if you wait until the connection times-out
you will see that the system boots.
<br>Some more research turned up a plausible explanation of the problem on
the wu ftp web site (the Red Hat Linux ftp server) and the fix was
pretty simple.

<br>Basically, the ftp server has been made more RFC "insistent" and this
caused the VxWorks boot code to break (it also broke Lynx,
Midnight Commander and various other programs so WRS were not alone!).

<br>The patch is to close the data connection immediately after
the read returns EOF (ie the other end has signalled a close). This is
consistent with the FTP RFC 959.

<br>The patch should be safe (the data connection is no longer used), and it
works for me with the ftp daemon (wu ftpd) on Linux Red Hat 6.0, 6.2, as
well as the ftp supplied fom WRS for Windows - wftpd version 2.03.

<br>So, in bootConfig.c, in the 2 places where the connection is terminated
(normal case and error case). Move the close(fd) up after the read. That
is:
<pre>
    /* Empty the Data Socket before close. PC FTP server hangs otherwise */

    while ((read (fd, command, sizeof (command))) &gt; 0);
    /* Close data connection now
    close (fd);
</pre>

See <a href="http://www.wu-ftpd.org/broken-clients.html">
http://www.wu-ftpd.org/broken-clients.html</a> for more info.

<p>(From: [e-mail])

<p>
<hr WIDTH="50%">
<a NAME="2.3-M"></a>

<p>Q: What does the "hostname" field in the boot-parameters mean?
<p>A: The host name field in the boot line refers to the card/machine that
has the host inet address.  This hostname will appear on your 'devs'
list so that you can access the host machine through the target.

<br>There's another field called target name that used for the name of the
card/machine that the image is running on.

<br>Look in Section 13 of the VxWorks Networks Programmer's Guide for an
explanation of all the fields.
<br>(From: Christian Gan, [e-mail])

<p>
<hr WIDTH="50%">
<a NAME="2.3-N"></a>

<p>Q: I boot from my Disk On Chip, but now I get unresolved symbols when I try
to access a symbol.
<p>A: First you have to generate the symbol table. When you include this with
your image you have to copy this (much larger) VxWorks file to your target.
When you create a seperate symbol file you must put the vxworks.sym (the
symbol table ) in the same site of the vxworks image. vxworks.sym is created
when you build the vxworks image.
<br>(From: [e-mail])

<p>
<hr WIDTH="50%">
<a NAME="2.3-O"></a>

<p>Q: After copying the file BOOTROM.SYS to a disk my PC-board does not
start. It only shows <code>VxLd ....... [etc]</code>.
<p>A: Verify that the file BOOTROM.SYS is not fragmented from MS-DOS's point of
view.  You can verify this with
<pre>
chkdsk C:\bootrom.sys
</pre>
(assuming your flash disk has drive letter C)

<br>There will be a line at the end of the output, that tells you whether it is
or not.

<br>If it is fragmented, VxLd loads garbage from disk into memory, 'cause it
only searches for the start of BOOTROM.SYS and reads the following physical
sectors into memory. It's completely random if the system just hangs or
crashes immediately.

<br>(From: Werner Schiendl, [e-mail])

<p>
<hr WIDTH="60%">

<p><h3><a NAME="2.4"><center>2.4 Adding component to your VxWorks configuration</center></a></h3>

<a NAME="2.4-A"></a>
Q: How do I add a new component to my configuration?
<p>A: The component structure is defined in the .cdf files, so study these
first. Before you start to add your component you should answer 3 questions:
<ol TYPE=A>
<li>During which startup routine should the initialization take
place? (see prjConfig.c for startup routines)</li>
<li>Where in the component structure should your component be
defined?</li>
<li>What items should be visible (and editable) to the users
during configuration? Also define a constant that should be used to enable
the component.</li>
</ol>
The following actions should be taken after you answered these questions:
<ol>
<li>Create a CDF file for your component. This file can include
the following item (some of these are required):
<ul TYPE=DISC>
<li>NAME: The name of your component, as it should appear in the component list.</li>
<li>SYNOPSIS: The description of your component.</li> 
<li>MODULES: The object modules to load.</li>
<li>INIT_RTN: The routine that should be called to initialize your component</li>
<li>HDR_FILES: The header file.</li>
<li>CONFIGLETTES: The source files that define your component. This source
file will be included in the prjConfig.c.</li>
<li>CFG_PARAMS: The configuration parameters. These will appear as defines in
the file prjParams.h. For each of the parameters an extra parameter definition
can be given. In this item the name, the type and the default value can
be defined</li>
</ul>
Be sure to place the header and source file in a place that will be searched.
The CDF file should have the name 00&lt;component name&gt;.cdf. If it is a architecture
independent component place it in target\config\comps\vxWorks, otherwise
place it in target\comps\vxWorks\arch\&lt;Architecture&gt;.
<br>For a good example see the item FOLDER_CLOCK, and follow all the items.</li>

<li>Find the right InitGroup item in the file 00VxWorks.cdf.
This file is located in target/config/comps/vxWorks. Now add the line INCLUDE_&lt;component&gt;
at the right place in the list of include statements. Don't forget to add
a backslash to this line (or the one above if the component is added at
the end).</li>

<li>Now find in the file 00VxWorks.cdf or 00BSP.cdf (in the same
directory) the right folder to put your component. Add don't forget the
backslash.</li>
</ol>
For an example look here:
<a href="memDrv.html">Add memDrv as a component</a>
<p>NOTE: there is probably a better way to define new components using extra
tools. I don't have these tools so I had to find another way to include
my new components.

<p>
<hr WIDTH="60%">

<p><h3><a NAME="2.5"><center>2.5 VME problems</center></a></h3>

<a NAME="2.5-A"></a>
Q: How do I implement VME Bus Auto ID on the MVME-2604 Power PC.
The BSP states it supports the VME-64 standard.
<p>A: Andrew Fraser wrote some notes about this. This can be found here:
<a href="vmeAutoId.html">vmeAutoId.html</a>

<p>
<hr WIDTH="50%">
<a NAME="2.5-B"></a>

<p>Q: Is it possible to configure vxWorks so that it makes use of external
VME memory as part of the local memory?
<p>A: Your VME-memory should be accessible via standard VME-setup, if not change
your sysPhysMemDesc[] in sysLib.c and / or your VME-settings parameters.
On boot you may add your memory by a call to memAddToPool(). I would
recommend to insert this call in function sysHwInit2() in sysLib.c.
<br>(From: "Michael Lawnick, [e-mail])

<p>
<hr WIDTH="50%">
<a NAME="2.5-C"></a>

<p>Q: Another card on the VME bus is generating a bus error. How can I avoid 
that my SW will be stoppen by this error?
<p>A: I was able to make my own version of VxMemProbe that's a lot faster and
recovers from bus errors.  Here's what worked for me:
<pre>
jmp_buf myEnv;

void mySigHandler(int sigNum)
{
        longjmp(myEnv, ERROR);
}

//  Call this once before calling the Probe() routine below.
void myByteProbeInit()
{
        struct sigaction newSig, oldSig;

        newSig.sa_handler = mySigHandler;
        newSig.sa_mask    = 0;
        newSig.sa_flags   = 0;

        sigaction(SIGBUS,  &amp;newSig, &amp;oldSig);
        sigaction(SIGSEGV, &amp;newSig, &amp;oldSig);
}

STATUS
myByteProbe(char *addr, int mode, char *data)
{
        if(setjmp(myEnv) == 0)
        {
                if(mode == READ) *data = *addr;
                else *addr = *data;
        }
        else
                return (ERROR);
}
</pre>
(From: Mark A. Naivar, [e-mail])

<p>
<hr WIDTH="60%">

<p><h3><a NAME="2.6"><center>2.6 VxWorks environment</center></a></h3>

<p>
<hr WIDTH="60%">

<p><h4><a NAME="2.6.1"><center>2.6.1 usrSerial.c</center></a></h4>

<a NAME="2.6.1-A"></a>
Q: When I define more than 10 serial lines I only get 10 serial lines.
<p>A: There is an error in usrSerial.c, in the function itos. In this function
there is the following line:
<pre>
	val = val - (val %= 10);
</pre>
This should be changed into:
<pre>
        val = (val - (val % 10))/10;
</pre>

<p>
<hr WIDTH="60%">

<p><h4><a NAME="2.6.2"><center>2.6.2 prj_vxworks.tcl</center></a></h4>
<a NAME="2.6.2-A"></a>
<p>Q: When I create a new bootable project all items in the VxWorks tab are
marked as "not installed". How can I get these back?
<p>A: This is caused by the fact that an extra library has been defined in
your BSP Makefile (LIB_EXTRA = ...). The project is generated only with the
first library to look for the objects needed for the BSP.
<br>It is possible to change this. The file where the project is generated
is <em>prj_vxWorks.tcl</em>. This file can be found in <em>host/resource/tcl/app-config-Project</em>.
In this file the following changes must be made:
<pre>
*** prj_vxWorks.tcl-old Mon Jan 24 12:08:26 2000
--- prj_vxWorks.tcl     Mon Aug  7 14:33:51 2000
*** 895,905 ****
      set wcc [file tail $bspDir]
      wccCreate $hProj $wcc
      wccCdfPathSet $hProj $cdfPath
      foreach lib [bspMakeGet LIBS] {
!       if {[string match *lib[bspMakeGet CPU]*.a $lib]} {
!           set mxrLibs [file tail $lib]
!           break
!       }
      }
      if {![info exists mxrLibs]} {
        set mxrLibs lib[bspMakeGet CPU][bspMakeGet TOOL]vx.a
--- 895,905 ----
      set wcc [file tail $bspDir]
      wccCreate $hProj $wcc
      wccCdfPathSet $hProj $cdfPath
+     set mxrLibs ""
      foreach lib [bspMakeGet LIBS] {
!         if {[string match *lib[bspMakeGet CPU]*.a $lib]} {
!             lappend mxrLibs [file tail $lib]
!         }
      }
      if {![info exists mxrLibs]} {
        set mxrLibs lib[bspMakeGet CPU][bspMakeGet TOOL]vx.a
</pre>

<p>
<hr WIDTH="60%">

<a NAME="2.7-A"></a>
<p><h3><a NAME="2.7"><center>2.7 PCI problems</center></a></h3>

Q: Information about PCI configuration.
<p>A: From James Marshall ([e-mail]):
<br>I've just broken through into a clearing in the jungle of PCI Configuration
&amp; VxWorks on various PC platforms including CompactPCI. Some things I found
useful on the journey:
<ol>
<li>There's a brief WindRiver Technical Note, WTN-49, that talks about some of
these issues - it's on Windsurf. In particular it covers VME window mapping, if
only briefly.</li>

<li>PCI System Architecture by Tom Shanley &amp; Don Anderson, part of the MindShare
series.</li>

<li>Linux source for PCI configuration. I used the source browser at
lxr.linux.no to look at (for example) drivers/pci/pci.c
<a href="http://lxr.linux.no/source/drivers/pci/pci.c?v=2.4.0-test7">
http://lxr.linux.no/source/drivers/pci/pci.c?v=2.4.0-test7</a>. It lets you
click on identifiers to uncover where they are defined and used.</li>
<li>For interpreting PCI Config registers, the PCICFG program might help:
<a href="http://www.cs.cmu.edu/~ralf/pub-files/rbpci119.zip">
http://www.cs.cmu.edu/~ralf/pub-files/rbpci119.zip</a>.</li>

</ol>
The VxWorks PCI show routines aren't included from Project - you need to edit
config.h in your (locally-copied) BSP and define INCLUDE_SHOW_ROUTINES.
Unfortunately, this is very coarse-grained and pulls in several other unrelated
show routines. I guess you could always write a .cdf file to add it to Project.

<p>In your driver you would use PCI routines from sysLib [pcPentium]:
pciFindDevice() to get the config address (bus,device,function) for each
instance of your device, then read the appropriate BAR(s) to get their
address(es). I guess your master/slave window stuff mentioned in WTN-49 comes in
at that point.

<p>Note that the PCI Auto Config Library (src/drv/pci/pciAutoConfigLib.c)
mentioned in WTN-49 isn't supported on x86 targets because the PCI BIOS (a
callable part of the BIOS) is expected to do all PCI configuration before the
OS boots. This is why the default setting for PCI_CFG_TYPE on x86 targets is
PCI_CFG_NONE.
<hr WIDTH="20%">
The abocve is no longer true for all BSP's. For example, the CPV5350 BSP does
support PCI_AUTOCONF. If you enable it then the BSP will re-configure the
bus, overriding what the BIOS did.
<br>(From: Chris Brand)

<hr WIDTH="100%">
<p><h3><a NAME="index"><center>Index</center></a></h3>

<TABLE BORDER=1 CELLSPACING=3>
<TR>
<TD VALIGN=TOP><A HREF="#2.1">2.1</A></TD>
<TD VALIGN=TOP><A HREF="#2.1-A">A</A></TD>
<TD VALIGN=TOP>
Where can I find documentation on how to build a BSP?
</TD></TR>