Home |
RTTarget-32 Programming Manual Running Win32 Programs without Win32 Running a Program on the Target Running with or without Paging Installing Hardware Interrupt Handlers Catching NULL Pointer Assignments Running without Run-Time System Configuration for Debug and Release Builds Loading DLLs through a File System Using the MetaWINDOW Graphics Library Custom MP Floating Pointer Structure Device Management Compiling and Linking with On Time RTOS-32 |
Device ManagementPlease consult the Real-Time Hypervisor documentation on how ISA and PCI devices can be assigned to On Time RTOS-32. On Time RTOS-32 can only use a very few devices in all configurations:
The application must ensure that On Time RTOS-32 does not access any ISA or PCI devices in use by other cores. 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!
|