• Locked Locked
  • Replies 3 replies
  • Subscribers 53 subscribers
  • Views 462 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.

How can I do profiling code execution, Must I do profiling on simulator instead of EVM?

zhao sun
Expert 1170 points

Hi,       

         I need to do function profiling of my app with ccs v5.3.0 .But I can not implement

setting up profiling for capturing the functional profiling data when I run my .out file on

C6678 evm. Following the guideline, I do profile setup by select:

Tools -> Profile -> Setup Profile Data Collection menu   And then I get "There is no activity

available for the selected debug session" Nothing can be selected in that page. So How

can I do functiton profiling on my EVM?

 

Sunzhao

  • TI__Guru**** 482571 points

    Hi Sunzhao,

    For C6000, the CCS function profiler and code coverage utilities are limited to simulator only. Sorry.

    There are other tools that you can use. The Profile Clock can be used to count cycles and other events. If you are using BIOS, you may be able to get some statistics. If you are using an emulator that supports trace (XDS560v2), you can generate some profile data from that.

    ki

  • in reply to Ki
    Expert 1170 points

    Hi Ki-soo,

          Thanks for the reply. 

           The profiling result get from the simulator is also OK for me.  Ihave try to run the

    testapp of h264 BPencoder(c6678 platform) on the Cycle Approximate Simulator for

    using the profiler shipped with CCS.  But the test application will always fall into

    The __TI_decompress_rle_core and never reach the main function. While the function

    simulator can run correctly. So can you give me some suggestion to profile my app under

    the Cycle simulator?

    Thanks a lot!

    B.R.

    Sunzhao

     

     

     

  • in reply to zhao sun
    TI__Guru**** 482571 points

    It could be that functional simulator simulates a peripheral that the device cycle approximate simulator does not. Looking at the description, it seems like the modeling of the PCIe subsystem is one difference. is your application dependent on that?

    Thanks

    ki