From: DSP Hotline

Subject: 320C50 HLL Debugger Bug List

-------------------------------------------------------------------------------
* RELEASE 6.xx BUGLIST                                                        *
* Update - 11/18/94                                                           *
*                                                                             *
* This file contains a list of bugs in the release 6.xx of the 320C50         *
* HLL Debugger                                                                *
*                                                                             *
* All bugs will be fixed in the next production release unless othwerwise     *
* indicated. There will sometimes be references to internal versions in       *
* this list. For that reason you must always refer to the release status      *
* information (published every two weeks) to verify the availability of a     *
* specific revision.                                                          *
*                                                                             *
-------------------------------------------------------------------------------


				Part 1

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

5524     V(current)  will fix next release
  The Sun versions of the debuggers, emulators and simulators, do not support    
the "system", "cd" or "dir" commands.


5579     V4.60  will fix in V4.61
  An alias command with a string longer than 76 characters causes problems.      
For example the following take file:

? pc=0
alias l,"echo This is simply a very, very, very long alias of more than 76
 characters."
echo Error here.
? pc=1
alias

produces the following in the command window :

         0x00000000
        Error here.
        Invalid argument
          Alias          Command
        --------         -------
        L            --> echo This is simply a very, very, very long alias of m
ore than 76 chara
         --- Emulator Memory error

There are two bugs:  first, alias command doesn't get the entire
line, only 80 characters, and yet doesn't complain.  And second, once this
"bad" alias occurs you can no longer use E, eval, ?, reset, nor access memory
with the debugger.  Thus ? pc=1 gives an "Invalid argument" error and then
when the take file is complete and the debugger tries to update the screen,
" --- Emulator memory error".  This second problem, at least, goes away if you
use an alias of less than 77 characters.


5582     V7.00  will fix in V7.01
  When the length of a variable name does not fit completely in the "WATCH" window,
and an attempt is made to change the value of the variable in the "WATCH" window, 
the debugger tools may "crash". 

WORKAROUND
==========
Make the "WATCH" window large enough to fit the entire length of all variable 
names plus the cursor before changing any values in the "WATCH" window.


5636     V7.00  will fix in V7.01
  The OS/2 - version of the emulator does not load source files with 
file names longer than 8 characters. Files stored under the High 
Performance File System in OS/2 may have file names with up to 255 
characters.

TMS320C5X XDS510 PC 'C' SOURCE DEBUGGER
OS/2                  RELEASE 7.00
2617652-1663 REV A           30 SEP 93

The COFF format used with the object files does not support file
names longer than 14 characters.  This is a limitation of the 
COFF format.  Page B-3 in the Assembly Language User's Guide makes
mention of this limitation.  File names less than 14 characters 
should still work so this is a bug; this will be fixed in next release.


5709     V(current)  will fix next release
  1) When using the .def & .ref directives, symbols defined with .set are 
   only visible in the debugger if referenced by .def or .ref.  The 
   program will assemble and run properly.  If .def or .ref are not 
   used, all symbols are visible.
 
   Example:     .def   a
            a   .set   100h
            b   .set   200h
 
            In the debugger, only symbol "a" can be viewed.  If "b" is
            attempted to be viewed, the error message "Name "b" not 
            found" is received.
 
   Note:  The above situation does not occur with rev 5.2 of the 
          assembler.
 
2) The memory display goes to 32-bit mode when accessed by a symbol in
   hexadecimal mode.  The only way to get back to 16-bit mode is to 
   access the memory by value rather than by symbol.
 

WORK AROUND/SOLUTION:
=====================
Both of the above bugs have been corrected in latter releases.


5718     V(current)  will fix next release
  Attempting to watch a variable (WA) that is not defined causes the error
message "Undefined symbol" to be issued.  But if a specification is 
made as to the location (like "wa var@prog" or "wa var@data"), then a 
segmentation fault occurs and the debugger is exited.


XDS
-------------------------------------------------------------------------------

4983     V6.40  will fix next release
  If the address given in a PATCH command in program memory, has a
corresponding address in data memory that is reserved/illegal/unconfigured
memory, the PATCH command will not work.  

e.g.  addresses in the range 035h - 04fh  .

Workaround: Edit the addresses location by using ?/e or editing in
MEM display window.


5599     V7.02  will fix in V7.03
  There is a bug when using the ANALYSIS-menu setting for 
the TI C5x emulator.  A breakpoint, which is ENABLED, 
only works the first time that it is reached.

Product:
     TMS320C5X Debugger Version 7.02 for DOS
     Silicon revision 2.2
     XDS Emulator Revision 3

Problem Sequence:

     1) ANALYSIS
        BREAK
        Set break condition
        OK
        ENABLE

     2) RUN
        Program stops at breakpoint

       3a) RUN
        Program does not stop!

       3b) ANALYSIS
           BREAK
        OK     (just verify the earlier set break condition)
        RUN
        Program stops at breakpoint!

WORK AROUND
===========

After the break point is reached, "step" once before running;
this has been used to get passed the problem sometimes--not everytime.


5748     V(current)  will fix next release
  The GREG instruction doesn't activate the BR signal of the processor
when atempting to modify global memory values from the memory window
of the XDS510 debugger.  (When reading/writing to global memory space 
by running a DSP program it works, but the memory window is not 
updated, doesn't relfect the real data in the global memory).

TELRAD using the TMS320C50PQ57 
EFRAT  using the TMS320C51PQ57

WORK AROUN/SOLUTION:
====================
This is a bug in the 6.60 HLL DBR.  This bug was fixed in the 7.02
HLL DBR for 2.x C5x; arrangements for a 1.x C5x version must be
made.


5756     V7.10  will fix next release
  Unable to set hardware break points while using the version
7.10 of the debugger with the C53SX processor.  Hardware
beakpoints were supported under version 7.02, reports the
customer.

WORK AROUND/SOLUTION:
=====================
There is a problem with the HLL Debugger 7.10 using with C53SX parts.
The user will get "register access error" message when they try to
program the analysis register regardless of wheither the register 
exists or not.  The work around for this problem is to use the 
"analysis.cmd" file which is shipped with the software package.
To program the analysis for a program address breakpoint, after 
invoking the C5x HLL Debugger, at the command line the user types in:
1.  take analysis.cmd
2.  asys_on
3.  stop_prog
4.  prog_qual_r  (or prog_qual_w or prog_qual_rw or prog_qual_iaq)
5.  prog_brk_add [address]


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

5356     V7.00  will fix next release
  On SUN workstation, emu5x using -p 0 fails, attempts to open device at sd4.    

Workaround: Use a different driver other than sd0.


5358     V7.00  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.


5468     V7.00  will fix next release
  After approximately 13812 invocations of emu5x on a single C5x 
board without any intervening emurst execution, the debugger 
fails to come up.

The characteristics of the bug imply a direct relationship to the 
size of the SMG database, aka the board.dat file.   Thus C3x shows
no problems.  We must not be freeing the memory used by the SMG 
database.


5488     V7.00  will fix in V7.01
  The debugger comes up, but I can't modify memory or registers, nor run.

    CAUSE : User didn't execute emurst with the correct c?x510ws.out
            since powering-up the XDS510WS, but before invoking the debugger.
 
SOLUTION/WORKAROUND DESCRIPTION :
    Obviously, make sure to execute emurst with the correct c?x510ws.out
    file prior to invoking the debugger, yet after powering-up the XDS510WS.


5489     V7.00  will fix in V7.01
  The XDS510WS hangs if emu5x is executed on it, but it was initialized,
via emurst, with a file other than c5x510ws.out, such as c3x510ws.out.  

SOLUTION/WORKAROUND DESCRIPTION : 
    Cycle the power on the XDS510WS and re-emurst with the correct
    c?x510ws.out file or simply have enough sense not to execute a
    debugger on an XDS510WS that is not set up for that device.


PDM
-------------------------------------------------------------------------------

5383     V1.00  will fix next release
  loop/endloop commands do not function correctly in pdm take 
files that are not in pc style format on a pc.  PC format 
uses cr/lf fro a new line.  Unix uses just lf.


5461     V1.00  will fix next release
  PDM doesn't support the "dlog" command as described in the documentation.
Always returns the error "Cannot open Log file".


EVM
-------------------------------------------------------------------------------

4911     V6.40  will fix next release
  There is an error in the documentation in the TMS320C5x Evaluation Module
Technical Reference Guide on pg. 3-8 in the table describing the
I/O Expansion Connector Pin Assignments

The line which reads


     7 |  XA2     | OUT |  XA2    | OUT


Should read

     7 |  XA2     | OUT |  XA3    | OUT


5742     V1.00  will fix next release
  Cannot seem to get the timer to run properly on the
C5x EVM so that benchmarking can be performed.

A modyfication of the TCR register in the CPU window
not only affects the TCR but also a few other MMR's
and reserved locations.  Resizing the memory window
appears to clear out the erroneous data.

WORK AROUND/SOLUTION:
=====================
The problem is due to 1.x silicon bugs.  This was 
corrected in revision 2.x.  There are no know fixes
for the 1.x silicon and no plans to create a 
version of the software that supports the buggy
silicon.


PORTING KIT
-------------------------------------------------------------------------------

5866     V7.10  will fix next release
  The disk containing the SUN HLL OBJECT code for the C5x Porting Kit
was inadvertently shipped with the OS/2 version of the Parellel Debug 
Manager, PDM.


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