·VxMP use over (C)PCI and VME busesThe WRS shared memory product VxMP, and for that matter any multi-CPU card proprietary shared memory utilization, requires a participating CPU card to be able to perf
·VME bus access and control via Tundra Universe IIHow do I go out on the bus? That’s the first question most customers ask after getting their VME single board computer (SBC) up and running the VxWorks
·Slave booting, backplane booting and headless booting procedures for a VxWorks targetMany customers have remote booting requirements. VxWorks supports three remote booting scenarios: slave booting ove
·Using Wind Web Server 2.0 with Off-the-Shelf WEB Design Tools for Embedded Device ConfigurationThis tutorial is intended for users who want to design software which uses a WEB browser to control an em
·Building a Personal JWorks JVM into a single object file that can be dynamically loaded onto a VxWorks targetThis document contains instructions about how to build the Personal JWorks 3.0.2 JVM into a
·Configuring Personal JWorks for Network- and Graphics-Intensive Applications: Espial Escape Case StudyJava applications, especially network- and graphics-intensive ones like the Espial Escape Web brow
·Establishing a PPP Session between VxWorks and Windows NTThis tech note outlines how to establish a simple PPP session between VxWorks and a Window NT host. “Simple” is intended to be interpreted as a
·A Discussion of the implementation of PCI support on Tornado/vxWorks BSPs.WRS provides support for the Peripheral Component Interconnect (PCI) bus in many of its newer Board Support Packages (BSPs). I
·A discussion of the implementation of interrupt controllers under vxWorks.This Tech Note defines a common API for an architecture independent interrupt model. One advantage will be simplified architec
·Invoking a User Routine as Part of the VxWorks Startup SequenceThis technical note describes the latter method of initializing and invoking user applications in the VxWorks system initialization routi
·The configuration macro LOCAL_MEM_AUTOSIZE enables or disables dynamic memory sizing for a BSP. Dynamic memory sizing is determining the amount of main RAM available at run time. Fixed memory sizing u
·Reserving some portion of memory for a user’s purpose via a configuration macro.The configuration macro, USER_RESERVED_MEM, allows the user to reserve memory for special purposes. The reserved memory
·Issues and solutions for host file access from a vxWorks target.VxWorks, in cooperation with the remote file host, uses any of three different underlying protocols to provide transparent remote file a
·This technical note discusses the shared memory network (backplane network) configuration and troubleshooting procedures for debugging a network configuration, as well as trouble shooting procedures f
·WTN26(Wind Tech Notes):Using SCSI devices with VxWorks。This document is for users who wish to use SCSI devices with VxWorks. VxWorks supports SCSI-I and SCSI-II devices. SCSI-III is not supported.