syslib.html

Vxworks API操作系统和驱动程序设计API。压缩的HTML文件

<b><a href="./sysLib.html#top">sysLib</a></b>, and BSP-specific reference pages for this routine.

<hr>
<a name="sysScsiConfig"></a>
<p align=right>
<a href="rtnIndex.htm"><i>OS Libraries :  Routines</i></a></p>

</blockquote><h1>sysScsiConfig(&nbsp;)</h1> <blockquote></a></blockquote><h4>NAME</h4><blockquote>  
<p><strong>sysScsiConfig(&nbsp;)</strong> - system SCSI configuration</p>

</blockquote><h4>SYNOPSIS</h4><blockquote><p>
<pre>STATUS sysScsiConfig (void)</pre>

</blockquote><h4>DESCRIPTION</h4><blockquote><p>
This is an example SCSI configuration routine.
<p>
Most of the code found here is an example of how to declare a SCSI
peripheral configuration.  You must edit this routine to reflect the
actual configuration of your SCSI bus.
This example can also be found in <b>src/config/usrScsi.c</b>.
<p>
If you are just getting started, you can test your hardware configuration
by defining <b>SCSI_AUTO_CONFIG</b>, which will probe the bus and
display all devices found.  No device should have the same SCSI bus ID as
your VxWorks SCSI port (default = 7), or the same as any other device.
Check for proper bus termination.
<p>
There are three configuration examples here.  They
demonstrate configuration of a SCSI hard disk (any type), an OMTI 3500 floppy 
disk, and a tape drive (any type).
<p>
</blockQuote><h4>Hard Disk</h4><blockQuote>
The hard disk is divided into two 32-Mbyte partitions and a third
partition with the remainder of the disk.  The first partition is initialized
as a dosFs device.  The second and third partitions are initialized as
rt11Fs devices, each with 256 directory entries.
<p>
It is recommended that the first partition (<b>BLK_DEV</b>) on a block device be
a dosFs device, if the intention is eventually to boot VxWorks from the
device.  This will simplify the task considerably.
<p>
</blockQuote><h4>Floppy Disk</h4><blockQuote>
The floppy, since it is a removable medium device, is allowed to have only a
single partition, and dosFs is the file system of choice for this device,
since it facilitates media compatibility with IBM PC machines.
<p>
In contrast to the hard disk configuration, the floppy
setup in this example is more intricate.  Note that the
<b><a href="./scsiLib.html#scsiPhysDevCreate">scsiPhysDevCreate</a>(&nbsp;)</b> call is issued twice.  The first time is merely to get
a "handle" to pass to <b><a href="./scsiLib.html#scsiModeSelect">scsiModeSelect</a>(&nbsp;)</b>, since the default
media type is sometimes inappropriate (in the case of generic
SCSI-to-floppy cards).  After the hardware is correctly configured, the
handle is discarded via <b><a href="./scsiLib.html#scsiPhysDevDelete">scsiPhysDevDelete</a>(&nbsp;)</b>, after which the
peripheral is correctly configured by a second call to <b><a href="./scsiLib.html#scsiPhysDevCreate">scsiPhysDevCreate</a>(&nbsp;)</b>.
(Before the <b><a href="./scsiLib.html#scsiModeSelect">scsiModeSelect</a>(&nbsp;)</b> call, the configuration information was
incorrect.)  Note that after the <b><a href="./scsiLib.html#scsiBlkDevCreate">scsiBlkDevCreate</a>(&nbsp;)</b> call, the
correct values for <i>sectorsPerTrack</i> and <i>nHeads</i> must be set via
<b><a href="./scsiLib.html#scsiBlkDevInit">scsiBlkDevInit</a>(&nbsp;)</b>.  This is necessary for IBM PC compatibility.
<p>
</blockQuote><h4>Tape Drive</h4><blockQuote>
The tape configuration is also somewhat complex because 
certain device parameters need to turned off within VxWorks and the
fixed-block size needs to be defined, assuming that the tape
supports fixed blocks.
<p>
The last parameter to the <b>dosFsDevInit(&nbsp;)</b> call is a pointer to a
<b>DOS_VOL_CONFIG</b> structure.  By specifying NULL, you are asking
<b>dosFsDevInit(&nbsp;)</b> to read this information off the disk in the drive.  This
may fail if no disk is present or if the disk has no valid dosFs
directory.  Should this be the case, you can use the <b>dosFsMkfs(&nbsp;)</b> command to
create a new directory on a disk.  This routine uses default parameters
(see <b><a href="./dosFsLib.html#top">dosFsLib</a></b>) that may not be suitable for your application, in which
case you should use <b>dosFsDevInit(&nbsp;)</b> with a pointer to a valid <b>DOS_VOL_CONFIG</b>
structure that you have created and initialized.  If <b>dosFsDevInit(&nbsp;)</b> is
used, a <b><a href="./usrFsLib.html#diskInit">diskInit</a>(&nbsp;)</b> call should be made to write a new directory on the
disk, if the disk is blank or disposable.
<p>
</blockquote><h4>NOTE</h4><blockquote><p>
The variable <b>pSbdFloppy</b> is global to allow the above calls to be
made from the VxWorks shell, for example:
<p>
<pre>    -&gt; dosFsMkfs "/fd0/", pSbdFloppy
</pre>

If a disk is new, use <b><a href="./usrFsLib.html#diskFormat">diskFormat</a>(&nbsp;)</b> to format it.
<p>
</blockquote><h4>NOTE </h4><blockquote><p>
This is a generic page for a BSP-specific routine; this
description  contains general information only. To determine if this
routine is supported by your BSP, or for information specific to your
BSP's version of this routine, see the reference pages for your BSP.
<p>
</blockquote><h4>RETURNS</h4><blockquote><p>
OK or ERROR.
<p>
</blockquote><h4>SEE ALSO</h4><blockquote><p>
<b><a href="./sysLib.html#top">sysLib</a></b>, and BSP-specific reference pages for this routine.
<p>


<hr>
<a name="sysLocalToBusAdrs"></a>
<p align=right>
<a href="rtnIndex.htm"><i>OS Libraries :  Routines</i></a></p>

</blockquote><h1>sysLocalToBusAdrs(&nbsp;)</h1> <blockquote></a></blockquote><h4>NAME</h4><blockquote>  
<p><strong>sysLocalToBusAdrs(&nbsp;)</strong> - convert a local address to a bus address</p>

</blockquote><h4>SYNOPSIS</h4><blockquote><p>
<pre>STATUS sysLocalToBusAdrs
    (
    int    adrsSpace,         /* bus address space in which busAdrs resides */
    char * localAdrs,         /* local address to convert */
    char * *pBusAdrs          /* where to return bus address */
    )
</pre>

</blockquote><h4>DESCRIPTION</h4><blockquote><p>
This routine gets the bus address that accesses a specified local
memory address.
<p>
</blockquote><h4>NOTE </h4><blockquote><p>
This is a generic page for a BSP-specific routine; this
description  contains general information only. To determine if this
routine is supported by your BSP, or for information specific to your
BSP's version of this routine, see the reference pages for your BSP.
<p>
</blockquote><h4>RETURNS</h4><blockquote><p>
OK, or ERROR if the address space is unknown or not mapped.
<p>
</blockquote><h4>SEE ALSO</h4><blockquote><p>
<b><a href="./sysLib.html#top">sysLib</a></b>, <b><a href="./sysLib.html#sysBusToLocalAdrs">sysBusToLocalAdrs</a>(&nbsp;)</b>,  
and BSP-specific reference pages for this routine.

<hr>
<a name="sysBusToLocalAdrs"></a>
<p align=right>
<a href="rtnIndex.htm"><i>OS Libraries :  Routines</i></a></p>

</blockquote><h1>sysBusToLocalAdrs(&nbsp;)</h1> <blockquote></a></blockquote><h4>NAME</h4><blockquote>  
<p><strong>sysBusToLocalAdrs(&nbsp;)</strong> - convert a bus address to a local address</p>

</blockquote><h4>SYNOPSIS</h4><blockquote><p>
<pre>STATUS sysBusToLocalAdrs
    (
    int    adrsSpace,         /* bus address space in which busAdrs resides */
    char * busAdrs,           /* bus address to convert */
    char * *pLocalAdrs        /* where to return local address */
    )
</pre>

</blockquote><h4>DESCRIPTION</h4><blockquote><p>
This routine gets the local address that accesses a specified bus
memory address.
<p>
</blockquote><h4>NOTE </h4><blockquote><p>
This is a generic page for a BSP-specific routine; this
description  contains general information only. To determine if this
routine is supported by your BSP, or for information specific to your
BSP's version of this routine, see the reference pages for your BSP.
<p>
</blockquote><h4>RETURNS</h4><blockquote><p>
OK, or ERROR if the address space is unknown or the mapping is not
possible.
<p>
</blockquote><h4>SEE ALSO</h4><blockquote><p>
<b><a href="./sysLib.html#top">sysLib</a></b>, <b><a href="./sysLib.html#sysLocalToBusAdrs">sysLocalToBusAdrs</a>(&nbsp;)</b>,  
and BSP-specific reference pages for this routine.

<hr>
<a name="sysSerialHwInit"></a>
<p align=right>
<a href="rtnIndex.htm"><i>OS Libraries :  Routines</i></a></p>

</blockquote><h1>sysSerialHwInit(&nbsp;)</h1> <blockquote></a></blockquote><h4>NAME</h4><blockquote>  
<p><strong>sysSerialHwInit(&nbsp;)</strong> - initialize the BSP serial devices to a quiesent state</p>

</blockquote><h4>SYNOPSIS</h4><blockquote><p>
<pre>void sysSerialHwInit (void)</pre>

</blockquote><h4>DESCRIPTION</h4><blockquote><p>
This routine initializes the BSP serial device descriptors and puts the
devices in a quiesent state.  It is called from <b><a href="./sysLib.html#sysHwInit">sysHwInit</a>(&nbsp;)</b> with
interrupts locked.
<p>
</blockquote><h4>NOTE </h4><blockquote><p>
This is a generic page for a BSP-specific routine; this
description  contains general information only. To determine if this
routine is supported by your BSP, or for information specific to your
BSP's version of this routine, see the reference pages for your BSP.
<p>
</blockquote><h4>RETURNS</h4><blockquote><p>
N/A
<p>
</blockquote><h4>SEE ALSO</h4><blockquote><p>
<b><a href="./sysLib.html#top">sysLib</a></b>, and BSP-specific reference pages for this routine.

<hr>
<a name="sysSerialHwInit2"></a>
<p align=right>
<a href="rtnIndex.htm"><i>OS Libraries :  Routines</i></a></p>

</blockquote><h1>sysSerialHwInit2(&nbsp;)</h1> <blockquote></a></blockquote><h4>NAME</h4><blockquote>  
<p><strong>sysSerialHwInit2(&nbsp;)</strong> - connect BSP serial device interrupts</p>

</blockquote><h4>SYNOPSIS</h4><blockquote><p>
<pre>void sysSerialHwInit2 (void)</pre>

</blockquote><h4>DESCRIPTION</h4><blockquote><p>
This routine connects the BSP serial device interrupts.  It is called from
<b><a href="../bsp/ads8260/sysLib.html#sysHwInit2" >sysHwInit2</a>(&nbsp;)</b>.  Serial device interrupts could not be connected in
<b><a href="./sysLib.html#sysSerialHwInit">sysSerialHwInit</a>(&nbsp;)</b> because the kernel memory allocator was not initialized
at that point, and <b><a href="./intArchLib.html#intConnect">intConnect</a>(&nbsp;)</b> calls <b><a href="./memPartLib.html#malloc">malloc</a>(&nbsp;)</b>.
<p>
</blockquote><h4>NOTE </h4><blockquote><p>
This is a generic page for a BSP-specific routine; this
description  contains general information only. To determine if this
routine is supported by your BSP, or for information specific to your
BSP's version of this routine, see the reference pages for your BSP.
<p>
</blockquote><h4>RETURNS</h4><blockquote><p>
N/A
<p>
</blockquote><h4>SEE ALSO</h4><blockquote><p>
<b><a href="./sysLib.html#top">sysLib</a></b>, and BSP-specific reference pages for this routine.

<hr>
<a name="sysSerialReset"></a>
<p align=right>
<a href="rtnIndex.htm"><i>OS Libraries :  Routines</i></a></p>

</blockquote><h1>sysSerialReset(&nbsp;)</h1> <blockquote></a></blockquote><h4>NAME</h4><blockquote>  
<p><strong>sysSerialReset(&nbsp;)</strong> - reset all SIO devices to a quiet state</p>

</blockquote><h4>SYNOPSIS</h4><blockquote><p>
<pre>void sysSerialReset (void)</pre>

</blockquote><h4>DESCRIPTION</h4><blockquote><p>
This routine is called from <b><a href="./sysLib.html#sysToMonitor">sysToMonitor</a>(&nbsp;)</b> to reset all SIO device and 
prevent them from generating interrupts or performing DMA cycles.
<p>
</blockquote><h4>NOTE </h4><blockquote><p>
This is a generic page for a BSP-specific routine; this
description  contains general information only. To determine if this
routine is supported by your BSP, or for information specific to your
BSP's version of this routine, see the reference pages for your BSP.
<p>
</blockquote><h4>RETURNS</h4><blockquote><p>
N/A
<p>
</blockquote><h4>SEE ALSO</h4><blockquote><p>
<b><a href="./sysLib.html#top">sysLib</a></b>, and BSP-specific reference pages for this routine.

<hr>
<a name="sysSerialChanGet"></a>
<p align=right>
<a href="rtnIndex.htm"><i>OS Libraries :  Routines</i></a></p>

</blockquote><h1>sysSerialChanGet(&nbsp;)</h1> <blockquote></a></blockquote><h4>NAME</h4><blockquote>  
<p><strong>sysSerialChanGet(&nbsp;)</strong> - get the <b>SIO_CHAN</b> device associated with a serial channel</p>

</blockquote><h4>SYNOPSIS</h4><blockquote><p>
<pre>SIO_CHAN * sysSerialChanGet
    (
    int channel               /* serial channel */
    )
</pre>

</blockquote><h4>DESCRIPTION</h4><blockquote><p>
This routine gets the <b>SIO_CHAN</b> device associated with a specified serial
channel.
<p>
</blockquote><h4>NOTE </h4><blockquote><p>
This is a generic page for a BSP-specific routine; this
description  contains general information only. To determine if this
routine is supported by your BSP, or for information specific to your
BSP's version of this routine, see the reference pages for your BSP.
<p>
</blockquote><h4>RETURNS</h4><blockquote><p>
A pointer to the <b>SIO_CHAN</b> structure for the channel, or ERROR
if the channel is invalid.
<p>
</blockquote><h4>SEE ALSO</h4><blockquote><p>
<b><a href="./sysLib.html#top">sysLib</a></b>, and BSP-specific reference pages for this routine.

<hr>
<a name="sysNanoDelay"></a>
<p align=right>
<a href="rtnIndex.htm"><i>OS Libraries :  Routines</i></a></p>

</blockquote><h1>sysNanoDelay(&nbsp;)</h1> <blockquote></a></blockquote><h4>NAME</h4><blockquote>  
<p><strong>sysNanoDelay(&nbsp;)</strong> - delay for specified number of nanoseconds</p>

</blockquote><h4>SYNOPSIS</h4><blockquote><p>
<pre>void sysNanoDelay
    (
    UINT32 nanoseconds        /* nanoseconds to delay */
    )
</pre>

</blockquote><h4>DESCRIPTION</h4><blockquote><p>
This is an optional API for BSPs to provide.  Some, but not all, drivers do
require the BSP to implement this function.
<p>
When implemented, this function implements a spin loop type delay for at
least the specified number of nanoseconds.  This is not a task delay,
control of the processor is not given up to another task.  The actual delay
must be equal to or greater than the requested number of nanoseconds.
<p>
The purpose of this function is to provide a reasonably accurate time delay
of very short duration.  It should not be used for any delays that are much
greater than two system clock ticks in length.  For delays of a full clock
tick, or more, the use of <b><a href="./taskLib.html#taskDelay">taskDelay</a>(&nbsp;)</b> is recommended.
<p>
This routine should be implemented as interrupt safe.
<p>
</blockquote><h4>NOTE </h4><blockquote><p>
This is a generic page for a BSP-specific routine; this
description  contains general information only. To determine if this
routine is supported by your BSP, or for information specific to your
BSP's version of this routine, see the reference pages for your BSP.
<p>
</blockquote><h4>RETURNS</h4><blockquote><p>
N/A.
<p>
</blockquote><h4>SEE ALSO</h4><blockquote><p>
<b><a href="./sysLib.html#top">sysLib</a></b>, and BSP-specific reference pages for this routine.

</body>
</html>