|
|
|
|
|
|
|
|
|
|
|
|
Directory containing files used to configure and build particular VxWorks systems. It includes system-dependent modules and some user-alterable modules. These files are organized into several subdirectories: the subdirectory all, which contains modules common to all implementations of VxWorks (system- independent modules), and a subdirectory for each port of VxWorks to specific target hardware (system- dependent modules).
|
|
|
|
|
|
Subdirectory containing system configuration modules. Note that this method of configuration has been replaced by the project facility (see 4. Projects). The directory includes the following files:
|
|
|
|
|
|
System-independent boot ROM facilities.
|
|
|
|
|
|
Generic header file used to define configuration parameters common to all targets.
|
|
|
|
usrConfig.c, bootConfig.c
|
|
Source of the configuration module for a VxWorks development system ( usrConfig.c), and a configuration module for the VxWorks boot ROM ( bootConfig.c).
|
|
|
|
|
|
The other subdirectories of config contain system-dependent modules for each port of VxWorks to a particular target CPU. Each of these directories includes the following files:
|
|
|
|
|
|
Makefile for creating boot ROMs and the VxWorks system image for a particular target.
|
|
|
|
|
|
Two source modules of system-dependent routines.
|
|
|
|
|
|
A driver for on-board serial ports.
|
|
|
|
|
|
Header file of hardware configuration parameters.
|
|
|
|
|
|
Header file for the target board.
|
|
|
|
|
|
Assembly language source for initialization code that is the entry point for the VxWorks boot ROMs and ROM-based versions of VxWorks.
|
|
|
|
|
|
Complete, linked VxWorks system binary ( vxWorks), and its symbol table ( vxWorks.sym) created with the supplied configuration files.
|
|
|
|
|
|
VxWorks boot ROM code, as object module ( bootrom) and as an ASCII file ( bootrom.hex) in Motorola S-record format or Intel hex format (i960 targets), suitable for downloading over a serial connection to a PROM programmer.
|
|
|
|
|
|
Directory containing all the header (include) files supplied by VxWorks. Your application modules must include several of them in order to access VxWorks facilities.
|
|
|
|
|
|
Directory containing architecture-dependent header files.
|
|
|
|
|
|
Directory containing a header file for use with inetLib.
|
|
|
|
|
|
Directory containing hardware-specific headers (primarily for drivers). Not all of the subdirectories shown are present for all BSPs.
|
|
|
|
|
|
Directory containing files that describe the rules for the makefiles for each CPU and toolset.
|
|
|
|
|
|
Directory containing all the internal header (include) files used by the VxWorks network. Network drivers will need to include several of these headers, but no application modules should need them.
|
|
|
|
|
|
Directory containing Internet-specific header files.
|
|
|
|
|
|
Directory containing header files for code private to VxWorks.
|
|
|
|
|
|
Directory containing header files that must be included by applications using the Remote Procedure Call library (RPC).
|
|
|
|
|
|
Directory containing header files specified by POSIX.
|
|
|
|
|
|
Directory containing header files used for defining types.
|
|
|
|
|
|
Directory containing the machine-independent object libraries and modules provided by VxWorks.
|
|
|
|
|
|
A directory containing VxWorks object modules as individual files (suitable for loading dynamically to the target).
|
|
|
|
|
|
An archive ( ar) format library containing the object modules that make up VxWorks.
|
|
|
|
|
|
Directory containing all source files for VxWorks.
|
|
|
|
|
|
Directory containing files used to force inclusion of specific VxWorks modules.
|
|
|
|
|
|
Used to include all 5.0 ANSI C library routines.
|
|
|
|
|
|
Used to include the assert ANSI C library routine.
|
|
|
|
|
|
Used to include the ctype ANSI C library routines.
|
|
|
|
|
|
Used to include the locale ANSI C library routines.
|
|
|
|
|
|
Used to include the math ANSI C library routines.
|
|
|
|
|
|
Used to include the stdio ANSI C library routines.
|
|
|
|
|
|
Used to include the stdlib ANSI C library routines.
|
|
|
|
|
|
Used to include the string ANSI C library routines.
|
|
|
|
|
|
Used to include the time ANSI C library routines.
|
|
|
|
|
|
Used to check module dependences for constants defined in configAll.h and config.h.
|
|
|
|
|
|
Used to include extra modules that are needed by VxWorks but not referenced in the VxWorks code.
|
|
|
|
|
|
Used to mount a dosFs file system on a boot diskette (i386/i486 targets only).
|
|
|
|
|
|
Used to configure and initialize the wind kernel.
|
|
|
|
|
|
Used to mount a dosFs file system on a boot IDE hard disk drive (i386/i486 targets only).
|
|
|
|
|
|
Used to load the VxWorks symbol table.
|
|
|
|
|
|
Used to initialize the memory management unit.
|
|
|
|
|
|
Used to configure and initialize networking support.
|
|
|
|
|
|
Used to execute a startup script when VxWorks first boots.
|
|
|
|
|
|
Used to configure and initialize SCSI support.
|
|
|
|
|
|
Used to configure and initialize shared memory object support.
|
|
|
|
|
|
Used to configure and initialize the Tornado target agent.
|
|
|
|
cplusHeap.c, cplusIos.c, cplusTools.c
|
|
Used to configure Rogue Wave C++ utility classes (from optional product: Wind Foundation Classes).
|
|
|
|
|
|
Used to configure VxWorks wrapper classes (from optional product: Wind Foundation Classes).
|
|
|
|
|
|
Used to initialize Rogue Wave C++ utility classes (from optional product: Wind Foundation Classes).
|
|
|
|
|
|
Used to initialize VxWorks wrapper classes (from optional product: Wind Foundation Classes).
|
|
|
|
|
|
Directory containing sample application modules for demonstration purposes, including both the source and the compiled object modules ready to be loaded into VxWorks.
|
|
|
|
|
|
Directory containing a simple introductory demo program as well as a server/client socket demonstration.
|
|
|
|
|
|
Directory containing a simple datagram facility, useful for demonstrating and testing datagrams on VxWorks and/or other TCP/IP systems.
|
|
|
|
|
|
Directory containing the VxColor example application used in 2. A Whirlwind Tour.
|
|
|
|
|
|
Directory containing the program used with the Tornado Getting Started Guide tutorial.
|
|
|
|
|
|
Directory containing source code for supported board device drivers. Not all of the subdirectories shown are present for all BSPs.
|
|
|
|
|
|
Directory containing user-modifiable code.
|
|
|
|
|
|
Library of routines designed for interactive invocation, which can be modified or extended if desired.
|
|
|
|
|
|
Source of the error status table. It contains a symbol table of the names and values of all error status codes in VxWorks. This table is used by the routine printErrno( ) for translating error status codes into meaningful messages.
|
|
|
|
|
|
Pseudo-device driver that allows memory to be accessed as a VxWorks character (non-block) device.
|
|
|
|
|
|
Block device driver that allows memory to be used as a device with VxWorks local file systems.
|
|
The following directories are included only with a VxWorks source license.
|
|
|
|
|
|
Directory containing VxWorks source code for architecture-specific modules.
|
|
|
|
|
|
Directory containing source code for the Wind C++ Foundation Classes.
|
|
|
|
|
|
Directory containing the source files for the ANSI C library.
|
|
|
|
|
|
Directory containing the source files for various math routines (non-ANSI).
|
|
|
|
|
|
Directory containing the source files for the VxWorks network subsystem modules.
|
|
|
|
|
|
Directory containing the source files for Internet network protocols.
|
|
|
|
|
|
Directory containing the source code for VxWorks kernel extensions (for example: I/O, file systems).
|
|
|
|
|
|
Directory containing the source code for VxWorks tools.
|
|
|
|
|
|
Directory containing the source code for RPC that has been modified to run under VxWorks.
|
|
|
|
|
|
Directory containing source code for the VxWorks utilities.
|
|
|
|
|
|
Directory containing source code for the Tornado target agent.
|
|
|
|
|
|
Directory containing source code for the VxWorks kernel.
|
|
|
|
|
|
Directory containing miscellaneous unsupported code such as public domain software, examples, host tools, obsolete BSPs, and BOOTP server.
|
|
|
|