Adding An STM Node to CCSv5 Target Configuration

Overview

If you are using a C66x Device, you have the ability to use System Trace (STM), either through an XDS560v2 Generation emulator or through the device's Embedded Trace Buffer (ETB). However, if you're using an early version of CCSv5, the default CCSv5 target configuration might not have the STM node available. This document will walk you through adding that node if you need it. This article won't discuss how to use System Trace, only how to add the STM node that will be needed. There are other articles on this wiki that will discuss how to use System Trace, such as this one.

Figure 1 - C6678 Target Configuration that is missing the CSSTM node

Identifying whether you need to take these steps

It's pretty simple to tell whether you need to add the STM node to your CCS configuration, or whether you already have it. Open your target configuration in Code Composer Studio 5, and click the "Advanced" tab, as shown in the image. Be sure that DAP node of the target configuration is totally expanded. If it is totally expanded, and the bottom most node is CS_DAP_DebugSS, then the STM node is not present and will need to be added. This is the case in Figure 1. Figure 1 shows a C6678 device, but the C6670 will look identical at the DAP node and below.

If your device shows a CSSTM node somewhere below the CS_DAP_DebugSS node, then you do have the correct node. You can go through the rest of this page and ensure that the value settings are correct, but you shouldn't have to add anything.

Adding the CSSTM Node

If you need to add the CSSTM node in order to use STM, follow these instructions.

• Open the Target Configruation in CCS and click on the Advanced Tab. You should see something similar to what we see in Figure 1.
• DAP Node
  • Click on the DAP node (You should see some Subpath Properties. Ensure that the properties are set as marked below.
    • DAP Properties
    • Port Number = 0x9
    • Initial Configuration = Unchecked
    • Custom Configuration = Unchecked
    • Force Configuration = Checked
    • Pseudo Address = Unchecked
    • Type = Debug

Figure 2 - C6678 Target Configuration with the CSSTM node added

• CS_DAP_DebugSS Node
  • Click on the CS_DAP_DebugSS node. Ensure that the properties are set as below
    • CS_DAP_DebugSS
    • Initialization Script = Leave Blank
    • DAP TAP ID = 0x4B6B902F
• Add a Subpath
  • Right Click on the CS_DAP_DebugSS node and select "Add"
  • A Dialog box will open and you'll only have one choice. Choose Subpath. You can leave the name blank (or name it whatever you want so long as it doesn't conflict with other names in the structure) and the number of copies as 1. Click "Finish"
  • Click on the Subpath you just created and set the properties as noted below.
    • Subpath Properties
    • Port Number = 0x1
    • Initial Configuration = Unchecked
    • Custom Configuration = Unchecked
    • Type = debug
    • Force Configuration = Checked
    • Pseudo = Checked
• Add the CSSTM node
  • Right click on the subpath you just created and select "Add"
  • In the Dialog box that opens, select the Cpus tab
  • From the list of Cpus, find CSSTM. You can leave the name blank (or name it whatever you want so long as it doesn't conflict with other names in the structure) and the number of copies as 1. Click "Finish"
  • Click on the CSSTM node you just added and set the properties as below
    • CSSTM Properties
    • Bypass = Unchecked
    • Initialization Script = <leave blank>
    • Slave Processor = Unchecked
    • Address = 0x02421000
    • TraceDeviceId = 0x0
• Save the target configuration

At this point, your target configuration (Below the DAP) should like like the one in Figure 2.