From: DSP Hotline

Subject: 320C4x HLL Debugger Bug List

-------------------------------------------------------------------------------
* RELEASE 2.xx BUGLIST                                                        *
* Update - 06/04/93                                                           *
*                                                                             *
* This file contains a list of bugs in the release 2.xx of the                *
* 320C4x HLL Debugger                                                         *
-------------------------------------------------------------------------------


				Part 1

HLL
-------------------------------------------------------------------------------

4832     V2.01  will fix next release
  NOTE: This is a problem under OS/2 in full screen mode only!!
There is a problem when using 43 line mode in the emulator when operating
in full screen mode under OS/2.  If you change video mode from 25 line
to 43 line mode, then only the first 25 lines will be shown.  If you switch
from 50 line mode to 43 line mode, then the last 7 lines of the 50 line
mode are left behind unchanged.


Workaround:
1. Run in OS/2 window
2. Run in either 25 or 50 line mode.


4895     V2.01  will fix next release
  If a label that is longer than 18 characters is encountered in executing
code, or in code displayed in the disassembly window, the debugger may
crash.

e.g.

LDI @label_longer_than_18,ar1


Workaround: Make label names less <= 18 chars.


4909     V2.01  will fix next release
  If you have a section  of size 1K and you specify a contigous 1K 
block of memory for allocation in the link command file and then
within the emuinit.cmd file, specify the same range of addresses
but using two ma commands the debugger will give error messages
when loading the file.


e.g.

  Link command has

  Memory
  {
       RAM: 0x2ff800 len = 0x800
       .
       .

  Sections:
  {
     one_k_blk: {} > RAM


   Emuinit has:


   ma 0x2ff800,0x400,ram
   ma 0x2ffc00,0x400,ram


4971     V2.01  will fix next release
  NOTE: This is a new decsription for this bug!
In some case the compiler and or optimizer will optimize out the
function epilogue of a simple function, if that function consists
of an infinite loop.  If this function then calls another within
that loop, the debugger will generate a Corrupt Call Stack message.
And if you continue to C step at this point, it may also cause the 
debugger to hang.

i.e.

   func()
   {

      while (TRUE) {
     call otherfunc();
      }
   }


Workaround:  Compile with -mt option to force generation of
          function epilogue.


5002     V2.01  will fix next release
  Note: PG2 problem only!                                  
Memory save will not work correctly when there is an address range
0x100000-0xffffffff.


5028     V2.01  will fix next release
  When executing EMU40 under OS/2 the sysytem will crash if one of the values
in the watch window is clipped and the highlight moves into the clipped value.


5218     V2.12  will fix next release
  Note: This is a bug on the BETA, SUN release only!
C50reset hangs when you use the "-p" switch to change the default designation 
for the SCSI port.



Workaround:   1. Set the D_OPTIONS environment variable with the -p
           switch:

           i.e.  setenv D_OPTIONS   -p1


              2. edit EMULATOR to associate target 1 with sd 4 instead of sd1


EMULATOR
-------------------------------------------------------------------------------

5143     V2.01  will fix next release
  Setting up C40 to break on emu1 low and signal emu1 low on breakpoint
When you run to a breakpoint and disable analysis and then run again,
the C40 signals emu1 on the second run as well as the first.


5144     V2.01  will fix next release
  Setting up C40 to break on emu1 low and signal emu1 low on breakpoint          
Run to a breakpoint and run again. The second run acts as a "run 1"
instead of running to the second breakpoint.


5325     V2.20  will fix next release
  Note: This is a bug under OS/2 1.XX ONLY !!!!
      It is not a bug under OS/2 2.XX
     
     The "SCONFIG" command hangs the debuggger.                         

Workaround: Create an init.clr file - but swithing config on
         the fly is not supported.


5348     V2.20  will fix next release
  If EMU40 is executed twice from one command prompt, the second 
one's mouse fails.

Solution: Install the OS/2 2.0 service pack


5354     V2.20  will fix next release
  On SUN workstation, emu4x using -p 0 fails, attempts to open device at sd4.


Workaround:  Use a different driver other than sd0.


5357     V2.20  will fix next release
  Note: This is a problem on SUN & PC under SunOS and OS/2

The board configuration path and filename specified after the -f option
is limited to 32 characters including the '\0' end-of-string character.
Longer names are truncated.

This is especially a problem when the OS expands names as in ~user.


Workaround: Don't use long names.


5361     V2.20  will fix next release
  ma command lengths are limited to 0x7FFFFFFF. Anything larger will cause
problems.


Workaround: Break the range into smaller chunks.


5362     V2.20  will fix next release
  The manual (TMS320C4x C Source Debugger Guide rev A) incorrectly states
that the MA command supports memory type IPORT, OPORT, & IOPORT for
simulator only, but these types are also supported by the debugger.
The I/O Ports simply don't cache under the emulator, as opposed to 
being connected to a file as they are for the simulator.


5371     V2.20  will fix next release
  The debugger does not correctly disassemble ADDF3, MPYF3, or SUBF3 
type 1 instructions when R8, R9, R10, or R11 are used as operands.


Solution/Workaround:  The incorrect disassembly does not affect
                execution, so it may be effectively ignored.


5372     V2.20  will fix next release
  The emulator has trouble reading the ROM when LRDY0\ is high.

This bug likely exists because we must read the first 8 words twice
when we read ROM to work around a silicon bug.  Therefore, it also 
will not likely be fixed inthe emulator.


Solution/Workaround: Do not tie LRDY0\ high.


5374     V2.20  will fix next release
  The system command hangs the emulator.


Solution/Workaround:     

       1) Don't use the system command. Use a new command prompt instead.
       2) Upgrade to Os/2 2.x.


5375     V2.20  will fix next release
  The system command , when running under Windows, does nothing.


5376     V2.20  will fix next release
  The system command does nothing.


-------------------------------------------------------------------------------
