Prerequisites for Cross Debugging

To use the debugger, the following conditions must be met:

The RTTarget-32 Debug Monitor must be installed on the target.
Host and target must be connected.
The debugger's Rttarget.ini file must contain the host's communication port configuration and the Monitor's configuration file must contains a COMPort command specifying the target's communication port.
For debugging over serial or parallel ports, the application to be tested must not use the same port as the Monitor. If Ethernet is used, the RTIP-32 driver using the same Ethernet controller as the Debug Monitor cannot be debugged.
The program to be tested must be compiled with full debug information. Please see your compiler documentation for details. It is recommended to disable compiler optimization for debugging. Otherwise, the compiler's elimination of common subexpressions, multiple register allocation to variables, etc., can make debugging difficult.
The program must be located with the same target hardware definition (Region commands) as the Monitor. Usually, this is ensured by using the same configuration file containing all Region commands for the Monitor and the test program.
The configuration file of the test program must contain the command:
```
Reserve Monitor
```
This prevents RTLoc from allocating the same memory to both the Monitor and your test program.
The program must be located using command Locate NTSection rather than Locate Section. This restriction only applies to EXEs and DLLs for which source level debugging is required. CPU level debugging also works with Locate Section.
Both the .EXE/.DLL file(s) and the .RTB file of the application to be tested must reside in the default directory. DLL files may also optionally be on the current path.
If Microsoft Visual Studio is to be used for debugging, it must have been started through program Dbgshell.

Left Cross Debugging

The Debug Monitor

Down Program DbgShell