• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 54 subscribers
  • Views 399 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 to get Profiling to work in Non-project Debug mode?

Lee Holeva
Genius 4615 points


I'm using CCS4.2.3 in non-project debug mode, my DSP code is built using xdc, and in attempting to profile the code I do not get the pop-up window as is stated here:

http://processors.wiki.ti.com/index.php/Profiler

A configuration is created, but no options are presented to set it up.  This is all that I see:

 

Lee Holeva

 

  • 0
    TI__Guru**** 171309 points

    Salve Lee,

    Are you using a Simulator? The profiler only supports the simulator...

    Regards,

    Rafael

  • 0 in reply to desouza
    Genius 4615 points

    desouza said:

    Are you using a Simulator? The profiler only supports the simulator...

    No.  I want to see how many cycles my code is using on the DM8168 EVM.  Alternatively, is there a way to measure the actual time used?  I would like to include everything including the DMA transfers.

    Lee Holeva

     

  • 0 in reply to Lee Holeva
    TI__Guru**** 171309 points

    Lee,

    Due to the heavily intrusive nature of the profiler, the tools only enable lightweight cycle counters in hardware.

    - If you want to perform measurements in the DSP core, the profiler clock (menu Run --> Clock) is the tool to be used. One particular option that is very useful to ease the work is Auto-reset: whenever it reaches a breakpoint it resets the counter when the program is resumed (useful to perform cycle counts between two places in the code).

    - If you want to do the same in the A8, they feature hardware event counters that must be enabled through the breakpoint viewer. Open the breakpoint viewer (menu View --> Breakpoints), click on the small black triangle in the new breakpoint icon (the one with the three blue balls) and select Count Event. It also has the same feature as above to clear the counts (right-click on the event counter and select Breakpoint Properties).

    The inclusion of DMA transfers will only be possible if the code under scrutiny waits for a completion event or an interrupt to occur, as direct measurement is harder to achieve.

    Hope this helps,

    Rafael