gspmon.obj
-o gspmon.out
-m gspmon.map
-a

MEMORY
{
  RAM:	origin = 0FFFFA500h, length = 2B00h
}

SECTIONS
{
  .data  : {}
  reg    : {}
  .text  : {}
}

/***************************************************************************
  
   The GSP Debugger Monitor is currently located in GSP memory from
   0xFFFFA500 to 0xFFFFD000.  To move the monitor to a differnt
   location, change the address given for the RAM origin.
   Be certain that the area used by the monitor meets the following
   requirements:
      Must be valid RAM
      Must not be used for vector tables or IO Registers
      Must not be used by the program to be debugged
  
   For example, to locate the monitor from 0xFFFF0000 to 0xFFFF2B00,
   change the line in between "MEMORY {" and "}" to read
   RAM:  origin = 0FFFF0000h, length = 2B00h
  
   Then, re-link the GSP Debugger Monitor by entering
   GSPLNK GSPMON.CMD
   This will create the files GSPMON.OUT and GSPMON.MAP.  GSPMON.MAP
   will give the addresses of various routines in the monitor.
   GSPMON.OUT is the executable output module that the GSP Debugger
   will load on the target system.  Copy the newly created GSPMON.OUT
   into the same directory as the GSP Debugger.  It is a wise idea to
   keep a copy of the original GSPMON.OUT under a different name or
   in a different directory.
   
   The length given above includes storage space for the 34082 coprocessor
   registers.  If memory space is critical, and your target system does
   not use a 34082, you may change the line to be  
   RAM:  origin = 0FFFFAA00h, length = 2600h

 ***************************************************************************/
