Previous

Next

RTRth-32

The On Time RTOS-32 add-on component RTRth-32 contains everything required to run On Time RTOS-32 programs under the Real-Time-Systems Hypervisor, a product of Real-Time Systems GmbH (http://www.real-time-systems.com/). The Real-Time Hypervisor can execute several operating system instances on Intel x86 multicore CPUs with VTx (Virtual Technology) support. For example, the Real-Time Hypervisor can execute On Time RTOS-32 on one core while Windows runs on another. RTRth-32 is not included with RTTarget-32 or other On Time RTOS-32 components and must be purchased separately. Currently, the Real-Time Hypervisor version 2.1 and higher is supported.

RTRth-32 contains the following:

• Debug Monitor Monrth.exe. Debug Monitor Monrth.exe must be used instead of Monitor.exe to debug On Time RTOS-32 applications running under the Real-Time Hypervisor.
• Library Rtrth.lib. Rtrth.lib replaces some functions usually present in Rtt32.lib to ensure Real-Time Hypervisor compatibility. It also adds calls to initialize the Hypervisor run-time system and access shared memory partitions (documented in the RTTarget-32 Reference Manual and in header file Include\Rtrth.h). Real-Time Systems' API for shared memory partitions, OS Control, date/time synchronization, Event Management, and a Watchdog is also available through header file Include\libRth.h. Please note that date/time synchronization, the Event System, and the reboot monitor thread are not started automatically. It is thus recommended to call libRth function rthTimeSyncStart after RTKernelInit. The Event Systems can be started by calling function RTRTHEventSystemStart. The reboot monitor thread (required to be able to reboot the On Time RTOS-32 virtual machine from a different OS) can be started by calling function RTRTHOsControlStart.
• RTKernel-32 Clock Driver. Driver Clkrth (libraries Clkrth.lib) is required to make RTKernel-32 compatible with the Real-Time Hypervisor.
• RTIP-32 Driver RTRTH_DEVICE. Driver RTRTH_DEVICE enables RTIP-32 to communicate through the Real-Time Hypervisor's virtual network interface. This driver is located in library Netrth.lib. Please note that RTIP-32 programs can also use real PCI Ethernet interfaces, if they have been assigned to On Time RTOS-32.
• Demo Programs Hellorth and Rthtcp. Hellorth is a simple demo program using RTTarget-32, RTKernel-32, and RTRth-32. It tests a few Real-Time Hypervisor features and displays a list of PCI devices which have been assigned to On Time RTOS-32 rather than to Windows or some other OS. Rthtcp is demo program TCPServer configured for RTRth-32 and Windows.

Programs to run under the Real-Time Hypervisor always need RTTarget-32 and RTRth-32. In addition, optional components RTKernel-32, RTFiles-32, RTUSB-32, RTIP-32, all RTIP-32 add-ons, and RTPEG-32. RTFiles-32, RTUSB-32, and RTIP-32 can only be used with physical devices which have been assigned to On Time RTOS-32 and are thus not available to Windows. If RTPEG-32 is used, the computers screen, keyboard, and mouse must be assigned to On Time RTOS-32.

The following sections describe how On Time RTOS-32 programs for the Real-Time Hypervisor are built.

Advanced Topics

RTVmf-32

Device Management

Configuration Files

Compiling and Linking

Run-Time Requirements

Debugging

Performance Optimizations