• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 53 subscribers
  • Views 1197 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CCS/66AK2G02: Got "Tracing is not supported" in Trace Control

Joshua Wu81
Intellectual 800 points

Part Number: 66AK2G02

Tool/software: Code Composer Studio

I am working on K2GEVM eval board. I try to start trace analyzer in my project. When following the instructions in the following link
e2e.ti.com/.../694502
I got "Tracing is not supported" in Trace Control

Here are the Stpes I followed:
[STM Trace over 560v2]
1.Launch debug session.
2.Conect DSP device and load your target application.
3.Right click in the "Debug" pane and select "Show all cores" to display "Non Debuggable Devices".
4.Expand "Non Debuggable Devices" node and connect CSSTM device.
5.Start Tools->Trace Control
6.From Trace Control select the CSSTM tab, click "Receiver" button, and add "560 V2 Trace".
7.Adjust port width, trace buffer size, etc, and press "Apply".
8.Start Tools->Trace Analyzer->Open Trace Connection In New View->CSSTM
9.Add trace job if necessary (use View->Breakpoints)

My issue starts from Step 5. I don't see "Trace Control" under "Tools" in Munu bar. I entered "Trace Control" in Quick Access field and opened "Trace Control" I found. But I don't see CSSTM tab and inside the window of "Trace Control" shows "Tracing is not supported.   

What step(s) did I miss?

My app is based on the following packages:
 C:\ti\bios_6_46_01_38
 C:\ti\ccsv6\         [CCS  Version: 6.1.3.00034]
 C:\ti\edma3_lld_2_12_02_26
 C:\ti\pdk_k2g_1_0_4
 C:\ti\processor_sdk_rtos_k2g_3_02_00_05
 C:\ti\xdctools_3_32_01_22_core

UIA loggingSetup is added to the configuration of my project. I have been used the on board XDS200 embedded JTAG emulator without really using EMU2 to EMU19 pins of 66AK202 processor. Now I starts to use external emulator: Blackhawk XDS560v2-USB System Trace.

K2GEVM board have been mounted RA17, R18, and RA19 and DNI RA7, RA8, RA9 as specified in Table 3 of EVMK2G TRM(Literature Number: SPRUI65) in order to use MIPI 60-pin JTAG header.

  • 0
    TI__Guru**** 171449 points
    Hi,

    The thread you referenced is quite old and the procedure mentioned by Jason is not current. After CCSv5.3 (or 5.4) the interface improved by a huge margin and it is much easier to work.

    Please check the clip below that covers several Trace topics and has a demonstration that showcases the more updated process - the demo starts at 11:45 on the video.

    www.youtube.com/watch

    Hope this helps,
    Rafael
  • 0 in reply to desouza
    Intellectual 800 points
    Rafael,

    Thanks for point out the clip. The demonstration in the clip shows how to using the PTM. Since I don't have XDS-560v2 Pro I ran an STM example with ETB and my XDS-560v2-USB.

    I first using the on-chip ETB with the selections below in CCS. The transport type is ETB.
    Menu bar -> Tools -> Hardware Trace Analyzer -> Memory Throughput Analysis
    Instrumentation Type: System Trace. Core: CSSTM_0, Transport Type: ETB

    I am able to see activities in "Trace Viewer" and "Memory Throughput" windows in CCS.

    But when I try to take advantage of the bigger buffer size in XDS560v2-USB for running the following selections
    Menu bar -> Tools -> Hardware Trace Analyzer -> Custom System Trace Configuration
    Instrumentation Type: System Trace. Core: CSSTM_0, Transport Type: 560 V2 Trace
    Buffer Type: Stop-on-full
    Buffer Size: 256KB
    Number of pins: 4 pin

    I got error message, "Could not run analyzer. Cause: unable to select receiver: Unintialized error text."

    What is wrong with my setup/selection?
  • 0 in reply to Joshua Wu81
    TI__Guru**** 171449 points

    Hi,

    I have the impression the error message happens due to a few bugs that were fixed in both the Keystone 2 and the TI Emulators component of CCS. Can you update your CCS by going to menu help --> Check for Updates and selecting the two components shown in the screenshot below?

    Unfortunately my K2GEVM board is not fitted with the HW modifications mentioned by you, thus I can't necessarily validate this at this moment. 

    Hope this helps,

    Rafael

  • 0 in reply to desouza
    Intellectual 800 points

    Thanks. I don't have error message when select "560 V2 Trace" under Menu bar -> Tools -> Hardware Trace Analyzer -> Memory Throughput Analysis.

    In "Trace View" window, it shows the Recording: 730.0 Mbits/second: xy% full - Data is shown when recording stops.

    When I stop recording I got something like the following
    19,CPTracer,,0x0,Min. Average Latency (cycles / transaction) = Accumulated wait time / Num Access Granted,CPT,MSMC_0,,,
    19,CPTracer,,0x0,Selected bus throughput(MBytes/s) = ThroughPutCounter0 / Sliding Time Window,CPT,MSMC_0,,,
    9577,CPTracer,,0x0,Bus Throughput(MBytes/s) = ThroughPutCounter1 / Sliding Time Window,CPT,MSMC_0,,,
    9577,CPTracer,,0x0,Average Access Size(bytes/cycle) = ThroughPutCounter1 / Num Access Granted,CPT,MSMC_0,,,
    ...

    My app doesn't include ctoolslib.
    Q1: what is the default 4 EMU pins for STM on K2GEVM? When I probe EMU0, EMU1, EMU2 pins I only see EMU0 running at 50MHz.
    Q2: The Data column in "Trace View" window, it always shows "0". Do I need to do anything in my code or CCS to have meaningful data? I should been able to see non-zero bus throughput.
    The register value under
    Registers -> ARM_VBUSP -> STM_DISABLE
    shows the value "1" which means the STM is disabled.
    But even change it to "0" I still got all zeros in Data column.

    My goal is to make sure EMU pins toggling and check their signal integrity against acceptable waveform. Thanks.