|
 On Time RTOS-32 Documentation
 Welcome
 RTTarget-32
RTTarget-32 Programming Manual
 Introduction
Running Win32 Programs without Win32
The i386 Microprocessor
RTLoc: Locating a Program
Running a Program on the Target
Cross Debugging
Using an IDE
The RTTarget-32 API
Demo Programs
Advanced Topics
 Choosing a Locate Method
Running with or without Paging
Running at CPL 0 or 3
Installing Hardware Interrupt Handlers
Catching NULL Pointer Assignments
Catching Stack Overflows
Running without Run-Time System
Avoid Repeated Downloads
Configuration for Debug and Release Builds
Using Data Compression
Using DLLs through RTLoc
Loading DLLs through a File System
RAM File System
Installable File System
Multithread Applications
Using the MetaWINDOW Graphics Library
Using the 387 Emulator
Using Non-Volatile Memory
Running on a Virtual Target
APIC Mode
Multiprocessor Applications
Custom MP Floating Pointer Structure
RTVmf-32
RTRth-32
Device Management
Configuration Files
Compiling and Linking
Run-Time Requirements
Debugging
Compiling and Linking with On Time RTOS-32
Redistributable Components of RTTarget-32
RTLoc Error Messages
RTTarget-32 Reference Manual
RTKernel-32
RTFiles-32
RTIP-32
RTPEG-32
RTUSB-32
|
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, and date/time synchronization is also available through header file Include\libRth.h.
- 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
|
