• State TI Thinks Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 98 subscribers
  • Views 347 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.

Original question:

Linux/TDA2PXEVM: which tool can be used to observe the memory bandwidth usage

how to analysize the result of glsdkstatcoll bandwidth tool.

SimonChan
Intellectual 900 points
Part Number: TDA2PXEVM

Tool/software: Linux

Hi,

Per thread https://e2e.ti.com/support/processors/f/791/t/772953, I have made glsdkstatcoll bandwidth tool work properly with TDA2X VSDK. Below is the snapshot of the statcoll_plot output in the host. I wonder how should I calculate the total Average BW and peak BW , is it just to sum each column in the table?

Also for Rishabh's nice comments, "Vision SDK default configuration already enables a BIOS Task that is also reading the statistics block of the SoC. Make sure that you disable that before using the glsdkstatcoll, otherwise the results from both will be wrong." Is the change needed even when Apps.out is not launched? And Can you help indicate how to make the change?

  • 0
    TI__Guru** 113810 points
    Hi Simon,

    The total bandwidth is the sum of the EMIF1_SYS and EMIF2_SYS. If you add up the rest of the items below it, it should be very close to that total. Ofcourse, the assumption here is that you have all the initiators configured. Please do this only for the column of average traffic. The peaks can occur at different times and hence it is not advisable to add this column.

    The average bandwidth is the average of traffic (in the sampling period) across all samples.

    The peak bandwidth is the highest sample across all the samples.

    Regarding the question about the apps.out - as indicated the BIOS Task is responsible for reading the statistics block of the SoC. Therefore, even if you do not run the apps.out, the firmware is already loaded into the M4 and the BIOS Task is running as part of the firmware, is reading the statistics block.

    Hope that answers your question.

    Regards
    Karthik
  • 0 in reply to Karthik Ramanan
    Intellectual 900 points

    Hi Karthik,

    Thanks for your nice explanation. But can you kindly share how I can disable BIOS Task that is also reading the statistics block of the SoC. When running use cases based on VSDK, I notice the BW result from glsdkstatcoll is obviously not correct. Thanks!

    Regards,

    Simon

  • 0 in reply to SimonChan
    TI__Guru 55685 points
    Hi Simon,

    You can update Utils_statCollectorInit() API in PROCESSOR_SDK_VISION_03_06_00_00\vision_sdk\links_fw\src\rtos\utils_common\src\utils_stat_collector.c to disable the BIOS task.

    Regards,
    Rishabh
  • 0 in reply to Rishabh Garg
    Intellectual 900 points
    Hi Rishabn,

    Thanks for your immediate reply. I will have a try.

    Regards,
    Simon