• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 53 subscribers
  • Views 675 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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/TM4C129XNCZAD: CCS10 usability comments on SWO trace Event Analysis

Chester Gillon
Guru 92251 points
Part Number: TM4C129XNCZAD

Tool/software: Code Composer Studio

In CCS 10 the SWO trace user interface has been updated to be accessed via Tools -> Code Analysis -> Event Analysis.

Whereas in previous CCS versions (e.g. CCS 9.1.0.00010 with TI Emulators 8.3.0.00003) SWO trace analysis was under Tools -> Hardware Trace Analyzer.

Compared to the previous SWO trace functionality under "Hardware Trace Analyzer", I think the new under interface Event Analysis is worse since:

1. In the Event Analysis "Raw Data" I can't find a way to export the raw data for further processing. With the Hardware Trace Analyzer I found it useful to export the raw data in CSV format for post-processing of large data sets in other tools.

2. In the Event Analysis "Exception Profile" on the "Graphical view of exception (green) and preempted (red) state" I can't find any controls on the graph to adjust the graph axes. While the mouse scroll wheel does allow a zoom / un-zoom, once you have zoomed in I can't find a way of moving the graph exes left/right to scroll through the graph data.

  • 0
    Guru 92251 points

    Some further comments having used the Event Analysis "Statistical Function Profile" in CCS10:

    3. In the Statistical Function Profile view the Function reported against the Count make sense. E.g. for the following capture as expected most of the time was reported as spent in main(), then in UART related functions and then startup functions:

    However, the contents of the File column doesn't correlate with the Function column. E.g.:

    a. The main function is reported as in C:/Jenkins/workspace/TivaWare-Git-Release/DriverLib/build/DriverLib.test/driverlib/interrupt.c, yet it is actually in ../sdram.c.

    b. The __aeabi_uidivmod function is reported as in /home/mr_halfword/ti/TivaWare_C_Series-2.2.0.295/utils/uartstdio.c, yet it is actually in u_divt2.asm.

    4. In the Previous CCS version with Hardware Trace Analyzer, when viewing the Trace Viewer view (raw data) or the Statistical Function Profiling view for a Statistical Function Profile you use be able to click on a PC sample in the trace viewer to navigate to the corresponding source line for the PC sample. In the Event Analysis views it doesn't seem possible to navigate from a PC sample to the corresponding source line.

  • 0 in reply to Chester Gillon
    Guru 92251 points

    Another comment:

    5. With CCS 9.1.0.00010 with TI Emulators 8.3.0.00003, while the target is left running it is possible to start/stop the Hardware Trace Analyser in the Trace Viewer view, and collect a new set of data. While the target is left running it is also possible to re-start the Hardware Trace Analyser and switch between Statistical Function Profiling or Interrupt Profiling.

    Whereas with CCS 10.0.0.00010 if attempt to start a capture while the target is running then get the Configure Event Profile dialogue pop-up with a "Failed to fill CPU info from Channel Server" error (when using a XDS110):

    With CCS 10 SWO trace can only be captured if started automatically when the target is Resumed and stopped automatically when the target is Suspended. Given that SWO trace is useful to diagnose run time behaviour of the target, it would be useful is CCS 10 allowed SWO trace to be started/stopped while the target continues to run.

  • 0 in reply to Chester Gillon
    TI__Guru**** 169344 points

    Chester,

    Thank you for sending the usage suggestions. I will ping someone on the dev team to parse the information here. 

    Regarding items 1) 3) and 4), I suspect there are already requests filed to fix/implement them. 

    Regards,

    Rafael

  • 0 in reply to desouza
    TI__Guru**** 169344 points

    Chester,

    Please check the following enhancement/bug reports:

    1) EXT_EP-9831

    2) EXT_EP-9832

    3) EXT_EP-9833

    4) EXT_EP-9834

    5) filed as EXT_EP-9830 in your other thread. These are linked quite closely, given the start/stop functionality is not working very well. 

    All these can be verified in the link SIR in my signature below. Thank you again for reporting this.

    I apologize for the inconvenience,

    Rafael