XDS560 Trace Release Notes  

XDS560 Trace Release Notes
Copyright © 2005-2007 Texas Instruments Incorporated

Supported DSP Platforms

XDS560 Trace is supported on the following DSP Platforms:

  • TNETV3020
  • TMS320TCI6488

Basic Features

CCS Service Release 2 adds the following Trace features

  1. User can Trace DSP using ETB on DSP platforms where ETB is available.
  2. Multiple cores can be traceed simultaneously using ETB.
  3. User can switch between XDS560 Trace Pod and ETB for a given core. Note that XDS560 Trace Pod can only do tracing on single core at any point of time.
For detailed information on supported Trace Features, please refer to the help files in CCS

Basic Steps to use ETB on Supported Platforms

The following steps should be used to configure ETB on supported platforms:

  1. Use CCS Setup for setting up the board.
  2. Once setup is completed, connect the core (or cores) via CCS
  3. Open CCS window and your favorite project
  4. Build your app and load the out file to the target.
  5. Open Trace Control using Tools->XDS560 Trace->Control menu. Focus on the CPU tab (or tabs one by one) and click on the Receiver button. A pop-up dialog box comes up with available Trace receiver choices.
  6. User can select either 560 Trace Pod or ETB or None receiver for a given CPU. None receiver disables tracing for a given CPU.
  7. If user wants to use ETB, select ETB from the pop-up dialog box and press OK. Press OK again on the main dialog box. This is just one time setup step and in the subsequent sessions, this information is reused from previous session settings.
  8. From CCS window, apply Trace triggering jobs. Use Tools->XDS560 Trace->Setup menu to open triggering jobs pane. Following triggering jobs are available for ETB Trace support:
    • Trace ON Trace always ( trace PC and/or Data)
    • Start Trace Trace start at given PC ( trace PC and/or Data)
    • End Trace Trace stop at given PC; used in conjunction with Start Trace ( trace PC and/or Data)
    • Trace In Range Trace In Range gives PCs range (trace PC and/or Data)
    • Dont Trace In range Do not Trace In give PCs range (trace PC and/or Data)
    • Trace Variable Trace given data variable and/or range
  9. Once a job is applied successfully, you can see Trace Display up and running.
  10. Now you can start your execution and Trace will start as per your triggering rules.
  11. Trace would stop when you halt target or when you start trace collection from Trace Display by clicking on "Stop button.
  12. Now the Trace information is available for user in Trace Display.

Known Issues

Identifier

Headline
   SDSCM00014761   
   SDSCM00016071    Did not trace the time of the emulation halt, even though enabled
   SDSCM00016279    When initializing non configured cores, The Trace Display message appeared regarding the out file, but it does not indicate which core is missing the out file
   SDSCM00013944    Wrong receiver status, expected "PC Context Changed", received "Stopped Trace Trigger"
   SDSCM00016277    Unable to swap to Pin Trace after configured ETB trace, other way worked fine
   SDSCM00016070    No good progress indication of a status when Trace Display takes time for decoding
   SDSCM00015594    Unexpected Bad PC trace data with message current export frame processing aborted+++ may be noticed when using "High" export frame size setting from Trace Control and/or enabling timing in Trace Jobs.

Return to Top