• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 54 subscribers
  • Views 949 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.

Cycle Profiling on TI using CCS4.0

Deepak Joshi52929
Prodigy 130 points

Hi,

I have got the Idea of doing cycle profiling using the forum

http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/35754.aspx

But when i have started doing the cycle profiling on CCS4.2.09000 I am facing some problem ( same for TIC6482 Device cycle accurate simulator and xxxxxx cycle accurate simulator)

1) If i use the compiler option --symdebug:none -O3 -mf5 the profiler doesnot show even the main function cycles(CPU and total ).

2) If i Change the compiler option --symdebug:skeletal then the profiler starts showing cycles for both main and other dummy project.

In CCS3.3 profiler , The profiler used to generate cycle result on both of the debug level. In ours actual traget we have symbolic debug as none with -o3 and -mf5 as compiler option.

Since the compiler would be generating diiferent code and might result in diff behaviour I want to see the cycles on CC4.0 with --symdeg:none.

I am attaching a dummy project for refernce.

Also is there is any errata sheet for pdk_xxxxx_1_0_0_9 as for this i can do profiling if i restart my CCS after every execution :)

Regards

Deepak Joshi

+91-9999030812

PS: Current configuration on attached Project is for 6482 but you can change it for xxxxx and can see same behaviour. How can i share my dummy project?

  • 0
    TI__Guru**** 163035 points

    Deepak,

    The CCS profiler needs at least minimal symbol information to do function profiling.  This applies to both 3.3 and 4.x.  The skeletal debug option is the minimum that is required by the profiler.  The attachment didn't come through.  Your CCSv3.3 project may have -gp set which is very similar.

    John

  • 0 in reply to JohnS
    Prodigy 130 points

    Hi John,

    I am Attaching two project link one for CCS3.3 and CC4.0 in the attached zip DemoProject.zip

    CCS3.3 is toTICC3.3.zip

    CCS4.0 is ToTIDemo_CCS4.0.zip  

    On CCS3.3 I am using build options as -o3 -fr"$(Proj_dir)\Debug" -d"_DEBUG" -mv6400+ under this option i am able to see and do the function level cycle profiling.
    But on CCS4.0 Iam using -mv64+ --symdebug:none -O3 --define=CHIP_6482 --include_path="C:/Program Files (x86)/Texas Instruments/C6000 Code Generation Tools 7.1.0B2/include" --diag_warning=225 --opt_for_speed=5.
    how will i be able to generate the profiling figure on CCS4.0 as i need profiling using no symbolic debug as in CCS3.3.
    Regards
    Deepak Joshi