Configuring System Trace In Code Composer Studio

Configuring System Trace In Code Composer Studio

Overview

The steps provided below are provided in order to configure your target and emulator to capture System Trace. These steps are necessary to prepare the emulator and device to capture the data. In addition to these steps, you must also program a System Trace job through the Breakpoint Manager. Details of those steps will be specific to your data capture scenario.

Procedure

• Launch a debug configuration from within Code Composer Studio and connect to the board. If you need instructions on how to accomplish this piece, please see the Code Composer Studio v5 Getting Started Guide for debugging. At this point, your debug window should look similar to the image marked Debug Window (a). Note: Your image may vary slightly from the one shown in the image, based on the number of cores and the emulator that you are using.

• In order to use System Trace, you need to configure the system trace connection. This connection is configured on the same scan chain as the DSP cores are, but it is typically hidden because it is not a processor. In order to display it, you should right click on anything in the debug window and choose "Show All Cores". When you do this, your debug window should show some additional items under the heading "Non-debuggable Devices". This may be at the top, or the bottom of the debug window, depending on whether your cores are grouped or not. It doesn't matter where they are, as long as they are shown. They should look similar to the image in Debug Window (b).

• This step depends on where the trace output will be routed. Perform ONLY one of the following:
  • If the trace output will be routed to an external System Trace capable emulator, right click on the non-debuggable device ending in the letters CSSTM_0 and choose "Connect"
  • If the trace output will be routed to the on-chip System Trace Embedded Trace Buffer, right click on the non-debuggable device ending in the letters TETB_STM and choose "Connect"

• While the non-debuggable device that you just connected to is still selected, in the CCS Menu, choose Tools->Trace Control. A dialog box should open that looks like the one in the image marked Trace Control Window It is in this window that you will configure the properties of the trace receiver. In the case of trace capture to an external emulator, it is here that you are configuring the external emulator. In the case of trace capture to the system level embedded trace buffer, it is here that you are configuring the embedded trace buffer.

In the trace Control Window, you should ensure that the tab with the STM node is selected as shown in the image. If the trace data is going to be captured by an external emulator, this tab might say CSSTM_0, or something very similar.. If the trace data is going to be captured by the ETB, it might say TETB_STM, or something very similar. The default settings can be used.

• Choose the appropriate receiver by clicking the "Receiver" button on the trace control window. A "Select Receiver" dialog should come up. Choose the appropriate output. For sending Trace to an external emulator, you will choose 560v2 System Trace or Pro Trace depending on whether you are using the XDS560v2 or the XDS560v2 Pro trace. If you are sending the data to the ETB, choose ETB. Once you have done this, select "OK". Then click OK on the Trace Control window. Trace control will now program the trace receiver. This might take a few seconds.

Debug Window (a) - CCSv5

Debug Window (b) - CCSv5 showing Non-debuggable devices

Trace Control Window

Selecting the Trace Receiver

At this point, your the System Trace Receiver has been configured to capture System Trace data.