Crossware

Table of Contents        Previous topic       Next topic       

Overview->Location in Target Memory->Data Location

When the debug monitor executes, it uses directly addressable internal ram (data space) for it's workspace, stack and most of it's variables.  When control is passed to the users program, all of the internal ram locations in use by the debug monitor are swapped into xdata space.  Debug monitor variables that need to be accessed when the users program is active are permanently located in xdata space.

Since the debug monitor vacates internal ram when the users program becomes active, all of the internal ram space is available to the users program.  So no precautions are necessary to avoid using certain internal ram locations.  On the other hand, the xdata space being used by the debug monitor should not be used by the users program.

Note that because the debug monitor uses xdata space, it can only be used with systems that have xdata space available (either internal to the microcontroller or externally).