


          ******************************************************
          *                                                    *
          *       TMS320C30 HIGH LEVEL LANGUAGE DEBUGGER       *
          *                                                    *
	  *		     RELEASE 4.00		       *
	  *			TMDX			       *
          ******************************************************







     -PC/AT SYSTEMS-

      DIGITAL SIGNAL PROCESSOR PRODUCTS

      TEXAS INSTRUMENTS
      INCORPORATED































						       2547274-9301B



----------------------------------------
TMS320C30 HLL DEBUGGER PACKAGE
Version 4.00 TMDX
MS-DOS, PC-DOS Systems
----------------------------------------

   This package contains release 4.00 of the Texas Instruments TMS320C30
   High-Level Language and Assembly Language Debugging Tools.  The software
   supports both the XDS500/XDS100  and TMS320C30 EVM hardware products.
   This bulletin provides important information about the latest release of
   the tools.

TABLE OF CONTENTS
-----------------
   1.  Hardware Compatibility
   2.  Helpful Hints

HARDWARE COMPATIBILITY
----------------------

   This software package supports both the TMS320C30 XDS500/XDS1000 and
   the TMS320C30 EVM hardware products. Listed below are the files used by
   each product:

       Common Files
       ------------
	 resvct.001		       resvct.002
	 init.clr		       readme.hll

       XDS500/XDS1000 Files
       --------------------
	 c30reset.exe			xreset.exe
	 db30.exe			sample.c
	 sample1.c			sample.cmd
	 c30init.asm			sample.out
	 init.cmd

       TMS320C30 EVM
       -------------
	 evmreset.exe			evm30.exe
	 evm30.cmd

   The files for both products can reside in the same directory.  However you
   can selectively load the files for each product to conserve disk space.

   Included in the XDS500/XDS1000 product is the original debugger (EMU30)
   for the TMS320C30 tools.  In time this debugger will be replaced with the
   TMS320C30 HLL debugger.  The two debuggers are not compatible. If you wish
   to use both debuggers, the files for each debugger must be in seperate
   directories.








                                                       Page 2


HELPFUL HINTS
-------------

   Most users prefer that the debugger initialize the target system memory map
   when the debugger is envoked. However if you have both the XDS500 and the
   EVM in your system they probably have different target memory map
   requirements and are certainly located at different host PC I/O base
   addresses.  Following are a few examples of how you can have both programs
   execute without picking up the wrong host I/O base address or target
   memory map.

   Make a memory map command file for each of your targets.  The memory map
   command files for the XDS500/XDS1000 and EVM are shipped in the C Source
   Debugger Software package;  they are 'init.cmd' and 'evm30.cmd'
   respectively.   Place the corresponding command file in each of the source
   directories and rename the file 'init.cmd'.  If you are in your source
   directory when you invoke the debugger it will look for 'init.cmd' in the
   current directory before searching other directories.

   If you keep all of your source in one directory then the task is a little
   more complicated.  In this case you should give each command file a
   unique name.  Then create a 'init.cmd' file with the following;

      take 'command file name',0

      Example:	take evm30.cmd,0

   When you invoke the debugger it will execute the commands in
   'init.cmd'.  In this case the debugger would load and execute the
   'evm30.cmd' command file.  Echoing is suppressed when  0 is
   appended to the 'take' command.

   If you have multiple XDS500 or EVM cards in your system they must each be
   mapped at a unique host PC I/O base address.  The easiest way to invoke the
   debugger for each card is to supply the PC I/O base address on the command
   line when you invoke the debugger.

   Examples:
	      The following sequence will envoke the EVM debugger and use PC
	      I/O base address 0x0240.

		  evm30 -p 240 <return>

	      The following sequence will envoke the EVM debugger and use PC
	      I/O base address 0x0280, and will ignore options supplied by the
	      D_OPTIONS environment varible.

		  evm30 -p 280 -x











						       Page 3


   You could also create a batch file for each hardware platform so that you
   do not have to remember the I/O base addresses.  The hardware reset
   files 'xreset.exe' and 'evmreset.exe' also support the -p option.

   Examples:
	     Create a file named EVM_1.BAT.  In the file include the
	     following line:

		  evm30 -p 240 -x

	     Create another file named EVM_2.BAT. In the file include the
	     following line:

		  evmreset -p 280
		  evm30 -p 280 -x

	     To enboke the debugger for your second EVM, type the following:

		   EVM_2 <return>

   This batch file will reset the EVM and envoke the debugger.





































						       Page 3
