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.

TDA4VM: How to get complete stats with statcol

Part Number: TDA4VM

Goodmorning,

We need to collect data about cores usage, memory usage and bandwidth on our TDA4VMid evaluation board; we saw in the documentation the tool called "statcol" (https://software-dl.ti.com/jacinto7/esd/processor-sdk-linux-jacinto7/latest/exports/docs/linux/How_to_Guides/Target/How_to_visualize_statistics_data.html) that seems to be suitable for this task,but when we launch it, the output data we receive is only partial (no memory information, no A72 cores information, etc.) and the usage values seems not to change accordingly to the actual load. 

More over it print some errors during initialization (here an example of terminal output):

rpmsg-char supported in r5f-mcu-core-0
rproc_device_find_for_name: could not open remoteproc node directory for r5f-mcu-core-0
rpmsg-char supported in r5f-mcu-core-1
rproc_device_find_for_name: could not open remoteproc directory for r5f-mcu-core-1
rpmsg-char supported in r5f-main-0-core-0
    rproc_dev exists
    rproc_char_dev exists
    char_dev endpoint created
>> Created RPMSG endpoint /dev/rpmsg0 for r5f-main-0-core-0 (fd = 4, port = 1025)
rpmsg-char supported in r5f-main-0-core-1
rproc_device_find_for_name: could not open remoteproc node directory for r5f-main-0-core-1
rpmsg-char supported in r5f-main-1-core-0
rproc_device_find_for_name: could not open remoteproc node directory for r5f-main-1-core-0
rpmsg-char supported in r5f-main-1-core-1
rproc_device_find_for_name: could not open remoteproc node directory for r5f-main-1-core-1
rpmsg-char supported in c66-0
    rproc_dev exists
    rproc_char_dev exists
    char_dev endpoint created
>> Created RPMSG endpoint /dev/rpmsg1 for c66-0 (fd = 6, port = 1024)
rpmsg-char supported in c66-1
    rproc_dev exists
    rproc_char_dev exists
    char_dev endpoint created
>> Created RPMSG endpoint /dev/rpmsg2 for c66-1 (fd = 8, port = 1024)
rpmsg-char supported in c7x
    rproc_dev exists
    rproc_char_dev exists
    char_dev endpoint created
>> Created RPMSG endpoint /dev/rpmsg3 for c7x (fd = 10, port = 1024)
WS-cpuload: 4 r5f-main-0-core-0 2.37 c66-0 0.12 c66-1 0.12 c7x 0.16
WS-cpuload: 4 r5f-main-0-core-0 2.37 c66-0 0.12 c66-1 0.12 c7x 0.16
WS-cpuload: 4 r5f-main-0-core-0 2.37 c66-0 0.12 c66-1 0.12 c7x 0.16
WS-cpuload: 4 r5f-main-0-core-0 2.37 c66-0 0.12 c66-1 0.12 c7x 0.16
WS-cpuload: 4 r5f-main-0-core-0 2.37 c66-0 0.12 c66-1 0.12 c7x 0.16
WS-cpuload: 4 r5f-main-0-core-0 2.37 c66-0 0.12 c66-1 0.12 c7x 0.16
WS-cpuload: 4 r5f-main-0-core-0 2.37 c66-0 0.12 c66-1 0.12 c7x 0.16
WS-cpuload: 4 r5f-main-0-core-0 2.37 c66-0 0.12 c66-1 0.12 c7x 0.16
[...]

How can we get all the stats as reported in the documentation?

Thanks,

Federico