Description of Problem:
-----------------------
If a C54x application is built containing RTDX, and then the application 
is started from reset without a debugger/emulator connected, execution 
of the initialization code may fail.  The problem is related to an 
interaction between the RTDX initialization routine 
	_RTDX_Init_RT_Monitor
and the reset state of emulation.  This fix consists of two new RTDX 
libraries that check for the presence of an emulator.  If no emulator 
is present, the initialization will quietly succeed.


Correction:
-----------
Copy the supplied library files rtdx.lib and rtdx_ext.lib into the Code 
Composer installation directory
	 C:\ti\c5400\rtdx\lib
Your installation drive may be different.  The supplied libraries replace 
the ones of the same name found in the installation directory.


Other things to check:
---------------------
Successful initialization of the RTDX capability depends upon 3 things:

1. .cinit processing (normal initialization of C static variables)

2. Software Interrupt vector 30  (offset 0x3C) set to the RTDX trap 
   handler, as shown in the example
     	c:\ti\c5400\examples\rtdx\target\intvecs.asm

3. .pinit processing which results in calling of initialization routines 
		_RTDX_Init_RT_Monitor and _RTDX_Buffer_Initialize

If you are using RTDX with DSP/BIOS these considerations are handled 
automatically.

If you are using  RTDX with the standard C startup, the C runtime module 
boot.asm handles .cinit and .pinit processing.  It is your responsibility 
to insure that the SINT30 vector and the IVTP are appropriately set 
before the RTDX initialization routines are called.
