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.

Pipeline analyzer tool?

Hi,

I'm using CCS 5.4.0.00091, and about to embark on some assembly language optimization for a C5535 project.

I've got the C55x cycle accurate simulator running, the wiki says I should have a pipeline analyzer available at "CCS menu->Tools->Pipeline Stall Analyzer" to check for stalls... except it's not there. Is this relocated elsewhere in my version of CCS, or is it no longer available?

Secondly, I'm trying to find a cycle count somewhere in the GUI, which would let me single-step through my assembly functions and look for stalls - no luck finding such a thing. Any suggestions?

Thanks!

  • Hi,

    Team will address your request as soon as possible.

    Thanks & regards,

    Sivaraj K

  • Hi,

     Did you try going through options of CCS -> help -> help contents & search for the content you were looking for ?

    With respect to Pipeline stall information,below is the information on pipeline stall analysis ( from CCS help menu)

    The Stall Profiling analysis counts the number of data and program cache stalls. This analysis is typically used for performance optimization. It identifies stalls due to cache-misses or CPU pipeline stalls. It measures the amount of cycles lost due to stalls and identifies the program locations where the stalls occur.

    This configuration is not available for Cortex-M targets.
     
    Running this analysis opens both the Trace Viewer and the Stall Cycle Profiler.
     
    The default analysis configuration traces L1P miss stalls, L1D read miss stalls, L1D write buffer full stalls, and CPU pipeline stalls. You can modify the Advanced Settings to trace other stalls, including L1P wait state stalls, L1D DMA conflicts, and more.
     
    To run this analysis configuration, select the core(s) you want to analyze and choose Tools > Hardware Trace Analyzer > Stall Profiling from the CCS menus in the CCS Debug perspective. You will see the Hardware Trace Analysis Configuration dialog for stall profiling.
     
    This analysis configuration performs an Event Trace using the CPU Trace type (also called PC Trace). If you want to use another configuration that uses the same trace type, you will be prompted to close this analysis

    Hope the above helps. You could also post questions related to CCS in Code composer studio forum.

    Regards

     Vasanth

  • I've gone through the help contents, and haven't found anything useful.

    I'm in the CCS Debug perspective, with a DSP code simulation running, using the C5535 V3.0 cycle accurate simulator. Tools -> Hardware Trace Analyzer gives me the following options:

    Memory Throughtput and... - not applicable on simulators
    Power and clock analysis - not applicable on simulators
    Custom system trace - not applicable on simulators
    Open File...
    Analysis Dashboard
    Open Configuration...

    Nothing particularly useful to be found.

    Opening the trace viewer, I only get a message that says "please select a connected target that supports Trace", so I'm going to assume the C55x simulators doesn't support trace.

  • Hi,

    Moving this post to CCS forum to be better answered.

    Thanks & regards,

    Sivaraj K

  • Hello,

    gmarsh said:
    I've got the C55x cycle accurate simulator running, the wiki says I should have a pipeline analyzer available at "CCS menu->Tools->Pipeline Stall Analyzer" to check for stalls... except it's not there. Is this relocated elsewhere in my version of CCS, or is it no longer available?

    The 55x Pipeline Stall Analyzer was last supported in CCSv3.3. Sorry.

    gmarsh said:
    Secondly, I'm trying to find a cycle count somewhere in the GUI, which would let me single-step through my assembly functions and look for stalls - no luck finding such a thing. Any suggestions?

    All the supported events by the counter is shown in the drop-down list when enabling a counter in the breakpoints view. I don't see anything particular for stalls unfortunately.