4. APOYO A LA SUPERVISIÓN DE CONTRATOS
4.4. REVISIÓN DE ACTAS
4.4.2. Revisión actas de costos de interventoría
4.4.2.4. Contrato 1586 de 2020
2.2.5 Configuration Tools: Workbench and vxprj
The tools provided for working with both VxWorks image projects (VIPs) and VxWorks source build projects (VSBs) are the Wind River Workbench
development suite and the vxprj command-line configuration facility. Workbench and vxprj can be used to configure and build VxWorks systems, and otherwise manage VIP, VSB, and other sorts of projects.
For information about using Workbench and vxprj, see the Wind River Workbench by Example guide and your Platform user’s guide, respectively.
2.3 VxWorks Image Projects: VIPs
VxWorks image projects are used to configure VxWorks systems with a variety of components. VxWorks components provide units of operating system
functionality based on pre-compiled libraries (archives) that are linked into a system by way of symbolic references. VIPs can be based on a default configuration of VxWorks or configuration profiles. Configuration profiles provide sets of components designed for specific purposes, such as the development environment, DO-178B certification, and so on. In addition, component bundles can be used to configure a system with related sets of components, such as those that provide POSIX support.
During the development cycle you may want to reconfigure and rebuild VxWorks with components specifically selected to support your applications and
development requirements. For example, you may want to include the kernel shell and error detection and reporting facilities, and to exclude other components that are provided in the default system images.
For production systems, you will want to reconfigure VxWorks with only those components needed for deployed operation, and to build it as the appropriate type of system image (see 2.8 VxWorks Image Types, p.28). You will likely want to remove components required for host development support, such as the WDB target agent and debugging components (INCLUDE_WDB and
INCLUDE_DEBUG), as well as to remove any other operating system
components not required to support your application. Other considerations may include reducing the memory requirements of the system, speeding up boot time, and security issues.
Wind River Workbench and the vxprj command-line tool can be used to configure VxWorks based on component selection and de-selection. The Workbench configuration facility displays graphical information about the components included in, and otherwise available to, as system. The vxprj tool can also be used to list various kinds of information about components. In addition, the VxWorks Component Reference provides detailed information about all components and their parameters, bundles, and profiles (for more information, see 2.3.1 VxWorks
2.3.1 VxWorks Components
A VxWorks component is the basic unit of functionality with which VxWorks can be configured. Components are designed for real-time systems, with an emphasis on determinism and performance. Each component provides one or more pre-compiled static library (archive), and often one or more configuration parameters. Components are linked into a system by way of symbolic references.
While some components are autonomous, others may have dependencies on other components, which must be included in the configuration of the operating system for run-time operation. The kernel shell is an example of a component with many dependencies. The symbol table is an example of a component upon which other components depend (the kernel shell and module loader; for more information, see the VxWorks Kernel Shell User’s Guide). Component dependencies are determined automatically by the VxWorks kernel configuration facilities (Wind River Workbench and the vxprj command-line tool).
Component Names
VxWorks components are packaged using component description files (CDFs), which identify components with macro names that begin with INCLUDE_, as well as with user-friendly descriptions. (For information about configuration files, see 19Custom Components and CDFs, p.455.)
The names, descriptions, and configurable features of VxWorks components can be displayed with the GUI configuration facilities in Workbench. Workbench provides facilities for configuring VxWorks with selected components, setting component parameters, as well as automated mechanisms for determining dependencies between components during the configuration and build process.
The command-line operating system configuration tool—vxprj—uses the naming convention that originated with configuration macros to identify individual operating system components. The convention identifies components with names that begin with INCLUDE. For example, INCLUDE_MSG_Q is the message queue component. In addition to configuration facilities, the vxprj tool provides
associated features for listing the components included in a project, configuration parameters, and so on.
! CAUTION: When VxWorks is configured with the WDB target agent, it is enabled on UDP port 17185. This service provides full access to VxWorks memory, and allows for writing to memory as well as for calling routines. Wind River recommends removing WDB from VxWorks for production systems. For information about WDB, see E. WDB Target Agent.
NOTE: In this book, components are identified by their macro name. The GUI configuration facilities provide a search facility for finding individual components in the GUI component tree based on the macro name.
2 VxWorks Configuration 2.3 VxWorks Image Projects: VIPs
Basic VxWorks Components
Some of the commonly used VxWorks components are described in Table 2-1.
Names that end in XXX represent families of components, in which the XXX is replaced by a suffix for individual component names. For example,
INCLUDE_CPLUS_XXX refers to a family of components that includes INCLUDE_CPLUS_MIN and others.
Note that Table 2-1 does not include all components provided in the default configuration of VxWorks. For detailed reference information about all components and their parameters, see the VxWorks Component Reference.
Table 2-1 Key VxWorks Components
Component Default Description
INCLUDE_ANSI_XXX * Various ANSI C library options INCLUDE_BOOTLINE_INIT Parse boot device configuration
information
INCLUDE_BOOTP * BOOTP support
INCLUDE_CACHE_SUPPORT * Cache support
INCLUDE_CPLUS * Bundled C++ support
INCLUDE_CPLUS_XXX Various C++ support options INCLUDE_DEBUG Kernel shell debugging facilities INCLUDE_EDR_XXX Error detection and reporting
facilities.
INCLUDE_DOSFS DOS-compatible file system INCLUDE_FLOATING_POINT * Floating-point I/O INCLUDE_FORMATTED_IO * Formatted I/O
INCLUDE_FTP_SERVER FTP server support
INCLUDE_IO_SYSTEM * I/O system and associated interfaces.
Directory and path manipulation APIs.
INCLUDE_LOADER Target-resident kernel object module loader package
INCLUDE_LOGGING * Logging facility
INCLUDE_MEM_MGR_BASIC * Core partition memory manager INCLUDE_MEM_MGR_FULL * Full-featured memory manager
INCLUDE_MIB2_XXX Various MIB-2 options
INCLUDE_NETWORK * Network subsystem code
INCLUDE_NFS Network File System (NFS)
INCLUDE_NFS_SERVER NFS server
INCLUDE_PIPES * Pipe driver
INCLUDE_POSIX_XXX Various POSIX options
INCLUDE_PROTECT_TEXT Text segment write protection INCLUDE_PROTECT_VEC_TABLE Vector table write protection INCLUDE_PROXY_CLIENT * Proxy ARP client support INCLUDE_PROXY_SERVER Proxy ARP server support
INCLUDE_RAWFS Raw file system
INCLUDE_RLOGIN Remote login with rlogin
INCLUDE_ROMFS ROMFS file system
INCLUDE_RTP Real-time process support.
INCLUDE_SCSI SCSI support (not provided for 64-bit VxWorks with this release)
INCLUDE_SCSI2 SCSI-2 extensions (not provided for 64-bit VxWorks with this release) INCLUDE_SECURITY Remote login security package
INCLUDE_SELECT Select facility
INCLUDE_SEM_BINARY * Binary semaphore support INCLUDE_SEM_COUNTING * Counting semaphore support
INCLUDE_SEM_MUTEX * Mutual exclusion semaphore support
INCLUDE_SHELL Kernel (target) shell
INCLUDE_XXX_SHOW Various system object show facilities INCLUDE_SIGNALS * Software signal facilities
INCLUDE_SM_OBJ Shared memory object support (requires VxMP)
INCLUDE_SNMPD SNMP agent
Table 2-1 Key VxWorks Components (cont’d)
Component Default Description
2 VxWorks Configuration 2.3 VxWorks Image Projects: VIPs
2.3.2 Device Driver Selection
Device drivers are provided as VxWorks components that can be added to or removed from a system using Workbench and vxprj. Some drivers are VxBus-compliant, and others (legacy drivers) are not.
Note that the component names for VxBus drivers do not have the leading
INCLUDE_SPY Task activity monitor
INCLUDE_STDIO * Standard buffered I/O package INCLUDE_SW_FP Software floating point emulation
package
INCLUDE_SYM_TBL Target-resident symbol table support INCLUDE_TASK_HOOKS * Kernel call-out support
INCLUDE_TASK_VARS * Task variable support INCLUDE_IPTELNETS Remote login with telnet INCLUDE_TFTP_CLIENT * TFTP client support
INCLUDE_TFTP_SERVER TFTP server support
INCLUDE_TIMEX * Function execution timer
INCLUDE_TRIGGERING Function execution timer INCLUDE_UNLOADER Target-resident kernel object module
unloader package
INCLUDE_VXEVENTS VxWorks events support.
INCLUDE_WATCHDOGS * Watchdog support
INCLUDE_WDB * WDB target agent
INCLUDE_WDB_TSFS * Target server file system
INCLUDE_WINDVIEW System Viewer command server (see the Wind River System Viewer User’s Guide)
Table 2-1 Key VxWorks Components (cont’d)
Component Default Description
NOTE: Only VxBus-compatible drivers can be used with the symmetric
multiprocessing (SMP) configuration of VxWorks. For general information about VxWorks SMP and about migration, see 23. VxWorks SMP and 23.17 Migrating Code to VxWorks SMP, p.558.
2.3.3 Component Bundles and Configuration Profiles
In addition to basic VxWorks components, component bundles and configuration profiles can be used to configure a VxWorks system.
Component bundles are associated sets of components, which can be added to a system as a unit (for example, BUNDLE_POSIX provides all the components required for POSIX support in the kernel).
Profiles provide a convenient way of providing a base line of operating system functionality that is different from the default configuration available with the VxWorks product installation. The following profiles are available:
PROFILE_SMALL_FOOTPRINT— VxWorks Small Footprint Profile
Provides basic facilities for systems in which minimal kernel functionality is necessary and a small memory footprint is required. See
2.6 Small-Footprint VxWorks Configuration, p.21.
PROFILE_COMPATIBLE—VxWorks 5.5 Compatible Profile
Provides the minimal configuration that is compatible with VxWorks 5.5.
PROFILE_DEVELOPMENT—VxWorks Kernel Development Profile
Provides a VxWorks kernel that includes development and debugging components, including support for real-time processes.
PROFILE_ENHANCED_NET—VxWorks Enhanced Network Profile
Adds components appropriate for typical managed network client host devices to the default profile. The primary components added are the DHCP client and DNS resolver, the telnet server (shell not included), and several command-line-style configuration utilities.
PROFILE_CERT—VxWorks DO-178 Certification Profile
Provides a DO-178B Level A-certifiable API subset of the VxWorks operating system.
PROFILE_BOOTAPP—VxWorks Boot Loader Profile
Provides facilities for a VxWorks boot loader. For more information, see 3.7 Configuring and Building Boot Loaders, p.43.
For detailed reference information about all component bundles and profiles, see the VxWorks Component Reference.
2.3.4 VxWorks Component Reference
For detailed reference information about all VxWorks components and their parameters, component bundles, and profiles, see the VxWorks Component Reference.