|
 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
 Locate Section or NTSection
Physical or Virtual Regions
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
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
|
Physical or Virtual Regions
The disadvantages of virtual regions are the requirement to use paging, a minimum alignment of 4096 bytes, and the possible need for the page table to be enlarged to accommodate a potentially larger linear address space.
Virtual regions have no advantages if the program is mapped with Locate Section. However, if Locate NTSection is used, there are two circumstances that could make use of a virtual region necessary: if the program is to run completely in RAM and no physical RAM region is large enough to contain the program, or if parts of the program should reside in ROM.
 Choosing a Locate Method
 Locate Section or NTSection
|
