Home |
RTTarget-32 Programming Manual Running Win32 Programs without Win32 Running a Program on the Target The Debug Monitor Prerequisites for Cross Debugging Compiling and Linking with On Time RTOS-32 |
The Debug MonitorThe Debug Monitor implements the target side of the cross debugger. It receives downloaded programs from the host and executes the test program under the control of the host debugger. At startup, the Monitor will initialize the port on the target according to the parameters specified in the COMPort command in a configuration file used to build the Monitor. Three different Monitors are shipped with RTTarget-32: Monitor.exe is the default Monitor used by all demo programs except ExLED, HelloSc400, and NSHello (which use Monser.exe). Monitor.exe contains all available drivers to communicate with the host debugger (serial ports, parallel ports, Ethernet). Monser.exe contains only the driver for serial ports while Monpar.exe contains only the driver for parallel ports. Owners of the RTTarget-32 source code can compile a custom Monitor which contains an arbitrary subset of the 15 available drivers (1 serial, 1 parallel, 11 Ethernet, RTVmf-32 virtual, RTRth-32 virtual). For details on how a custom Monitor is built, please see files Bin\Makemon.bc and Bin\Makemon.ms Two additional Monitors called Monvmf.exe and Monrth.exe are shipped with RTVmf-32 and RTRth-32, respectively. In addition to the drivers included in Monitor.exe, they also contain a driver for the Virtual Network interface, which can be selected with configuration file command "COMPort Ethernet ...". With this driver, host and target can reside on the same physical computer. Instructions on how the Monitor is best located are given in the Monitor.cfg file included with each On Time RTOS-32 demo. Prerequisites for Cross Debugging
|