• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 32 subscribers
  • Views 149 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.

AM2634: Profiling tool compatible with AM263x SDK?

Barna Csenteri
Expert 1890 points

Part Number: AM2634

Tool/software:

Hi

Are there any profiling tools compatible with AM2634 SDK or anyone managed to start any of them?

I want to check for bottlenecks in a heavily multitask/multicore firmware and searching for a good tool what was tried and working or at least compatible with the TI SDK.

Right now I am checking the Tools/RTOS Analyzer to see what it provides but I could get only tasklist and some memory addresses with it.

I would need cpu usage broken down to tasks and if possible to functions what I did not managed to make it run (yet) from CC/Tools.

Best Regards,

Barna Csenteri

  • 0
    TI__Guru 55760 points

    Hi Barna,

    I have not had a chance to come across such a tool.

    My best suggestion would be ROV tool that lets you know the tasks current state, lists of task etc.

    software-dl.ti.com/.../ROV_INTRO_PAGE.html

  • 0 in reply to Nilabh Anand
    Expert 1890 points

    Hi

    I already have task-stats and run-time-stats working compiled into the SDK so the cpu usage, task stats, states are known (code is built in FREERTOS code, just enabled it from the config which is not done by default in TI's SDK).

    However they are not 100% accurate and I would need to find out the real values or get a clue of what happening - maybe you can help:

    For example the 1st task (in examples is mostly called freertos_main) has a simple while (1) in it, with vTaskDelay( portTICK_PERIOD_MS ); and a counter increment. The counter is ~950-1000/second which is correct.

    However this process eats around 40% of CPU time while I have other tasks with the same delay and a lot of code in them (canopen stack timers for example). Their counters are also ~950-1000/second which is correct. However those worker threads are eating <2-3% of the CPU.

    I know the priority matters but if I have two processes which are running 1000 times/second, both having the same vTaskDelay, why the main one is eating 40% and the really hard worker thread less than 3%. I can't get my head around this one :)

    The percents and cpu usage is returned by vTaskGetRunTimeStats(  ) from the SDK - no custom code added whatsoever.

    So this is why I am searching for a good profiling tool ...

    Best regards

  • +1 in reply to Barna Csenteri
    TI__Guru 55760 points

    Hi Berna,

    Unfortunately, we do not have such a tool recommendation today.