|
 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
APIC Mode
Multiprocessor Applications
Custom MP Floating Pointer Structure
RTVmf-32
Device Management
Configuration Files
Compiling and Linking
Run-Time Requirements
Debugging
Release Notes
RTRth-32
Performance Optimizations
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
|
Device Management
Please consult the RTOS32Win documentation on how ISA and PCI devices can be assigned to On Time RTOS-32. By default, On Time RTOS-32 can only use a few virtual devices supplied by RTOS32Win:
- Virtual timer (used by RTTarget-32's Win32 Date and Time Management or RTKernel-32 drivers Clkvmf and Hrtvmf).
- Virtual interrupt controller (used by the Interrupt Handling functions of RTTarget-32, which are replaced by library Rtvmf.lib).
- Virtual real-time clock. Function RTVmfInit uses it to set the date and time of the On Time RTOS-32 application at program startup. It can also be used through the RTOS32Win RTOS Library.
- Virtual network interface. This interface can be used through RTIP-32 driver RTVMF_DEVICE to communicate with the Windows host and by Monvmf for debugging.
- Virtual console interface. This interface can be used to pass screen output or strings to Windows, for example to be displayed by a terminal program. Function RTVmfInit installs RTVmfOutCharDebugConsole as a display handler at program startup. This way, all screen output of the On Time RTOS-32 program will be redirected to the virtual console interface.
The application must ensure that On Time RTOS-32 does not access any ISA or PCI devices in use by Windows. For the interrupt controllers, A20 gate, the PC Timer chip, and the keyboard, this can be achieved with BOOTFLAGS BF_NO_A20, BF_NO_PCTIMER, BF_NO_SLAVE_PIC, BF_NO_MASTER_PIC, BF_NO_KEYBRD.
RTTarget-32 and RTKernel-32's COM port and LPT port drivers will query at run-time whether access to these devices is allowed. All PCI devices in use by Windows are hidden, so no PCI device driver will find them.
RTFiles-32 drivers for ISA devices (floppy, and IDE) do not automatically detect whether access to these devices is allowed. Only devices which have been assigned to On Time RTOS-32 may be specified in the RTFiles-32 device list. Please do not use the default RTFiles-32 device list as it does include entries for floppy and IDE disks!
 RTVmf-32
 Configuration Files
|
