The complete VxWorks operating-system environment is part of Tornado. This includes a multitasking kernel that uses an interrupt-driven, priority-based task scheduling algorithm. Run-time facilities include POSIX interfaces, intertask communication, extensive networking, file system support, and many other features.
Target-based tools analogous to some of the Tornado tools are included as well: a target-resident command shell, symbol table, and dynamic linker. In some situations the target-resident tools are appropriate, or even required, for a final application.
|
CAUTION: When you run the VxWorks target-based tools, avoid concurrent use of the corresponding tools that execute on the host. There is no technical restriction forbidding this, but an environment with--for example--two shells, each with its own symbol table, can be quite confusing. Most users choose either host-based tools or target-based tools, and seldom switch back and forth
|
||||||||||||||||||
In addition to the standard VxWorks offering, Tornado is compatible with the features provided by the optional component VxVMI. VxVMI provides the ability to make text segments and the exception vector table read-only, and includes a set of routines for developers to build their own virtual memory managers. When VxVMI is in use, Tornado's target-server loader/unloader takes account of issues such as page alignment and protection.
Tornado is also compatible with the VxWorks optional component VxMP. VxMP provides shared semaphores for synchronization of tasks on different CPUs, as well as shared message queues and shared memory management.
For detailed information on VxWorks and on its optional components, see the VxWorks Programmer's Guide and the VxWorks Network Programmer's Guide.