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.

DSPTOP Error

Moving Average Mode
Average DSP Usage:  0.00% Accuracy 100.00%

>
DSP    %USAGE   RUN TIME+     IDLE TIME+
DSP_0    0.00  00:00:00.000  00:00:00.000
DSP_1    0.00  00:00:00.000  00:00:00.000
DSP_2    0.00  00:00:00.000  00:00:00.000
DSP_3    0.00  00:00:00.000  00:00:00.000
DSP_4    0.00  00:00:00.000  00:00:00.000
DSP_5    0.00  00:00:00.000  00:00:00.000
DSP_6    0.00  00:00:00.000  00:00:00.000
>SP_7    0.00  00:00:00.000  00:00:00.000









dsptop system error: Fatal: Invalid argument: Check for another instance of dsptop running, only one instance per device allowed.
root@k2hk-evm:~#

On running the dsptop command, it is resulting in dsptop system error and exiting. But we are not running any other dsptop instance parallelly.

  • Hi,

    Please confirm if the SoC used is K2HK

    - Keertthy

  • Hi Keerthy,

    Yes, the SoC is TCI6638K2HK

    Regards,

    Sravya Keerthana

  • Hi all,

    root@k2hk-evm:~# dsptop -r 1 -f txt -o log.txt -d 1 -n 100
    dsptop: unrecognized option '--0'

    Usage: dsptop [dhlmnpqrsSvy]
    See "man dsptop" for more details.
     --delay/-d <value>              Set the screen refresh rate in seconds (fractional seconds ok).
     --format/-f <text|csv|gnuplot|gnuplot_wxt>
                                     Set the --output file format for DSP usage data, default is text.
                                     A file extension (.txt, .csv, .gp_cmd & .gp_dat) will be appended
                                     to the filename selected with --output. Selecting gnuplot_wxt will
                                     also launch gnuplot with a wxt terminal to plot DSP usage data.
     --help/-h                       Display help.
     --logging/-l <first|last>       Enable DSP message logging to stdout. DSP messages are captured in a
                                     circular buffer. Selecting "first" will write the DSP messages from
                                     the first full trace buffer to stdout and terminate dsptop. Selecting
                                     "last" forces the trace buffer to operate as a circular buffer in which
                                     case the logging data is written to stdout when dsptop is terminated.
                                     Use --output to select a file for logging rather than stdout.
     --maxoutfile/-m <value>         Set the max size in bytes for --output files (default is 0 - infinite).
     --number/-n <value>             Set the number of screen update iterations (default is 0 - infinite).
     --output/-o <filename>          Select a file for logging (-l) or usage data (-f).
     --resolution/-r <value>         Set plot resolution in seconds (fractional seconds ok).
     --process/-p                    Switch from continuous DSP run/idle time accumulation to
                                     single DSP process run/idle accumulation. Run/idle time
                                     will stop advancing on exit of the current process and
                                     resume when the next process starts.
     --quiet/-q                      Send all stdout to /dev/null except logging data.
     --sample/-s <value>             Set the moving average sample window in seconds (fractional seconds ok).
     --sync/-y                       Enable sync (used by dsptop_sync script).
     --version/-v                    Display version.

                                     Ask a question or report a problem at e2e.ti.com.

    On using the dsptop -r 1 -f txt -o log.txt -d 1 -n 100 command, it is showing unrecognised option, is the syntax which I am using is correct?

    Or is there any issue in the command usage?

    We are facing this issue as well in some of the EVM's

    regards,

    Sravya Keerthana

  • Sravaya,

    Rajarajan is working on your query. He will get back to you soon.

    Thanks for your patience.

    Regards

    Shankari G

  • Hi Sravya,

    There might be an issue with the "arago-base-tisdk-image-xxx.tar.xz" but NOT with the "tisdk-server-rootfs-image-xxx.tar.xz". This is because that the arago-base-tisdk-image does not contain all the packages needed by dsptop.

    Kindly try with "tisdk-server-rootfs-image-xxx.tar.xz". I am also trying in those in parallel.

    Thanks,

    Rajarajan U

  • Hi Sravya,

    I missed pointing out, The "arago-base-tisdk-image" and "tisdk-server-rootfs" were part of TI Processor SDK Linux (URL: https://www.ti.com/tool/PROCESSOR-SDK-K2H , Version: 06.03.00.106 ).

    The files mentioned above were present in the"Filesystem" folder in the SDK.

    Thanks

    Rajarajan

  • Hi Sravya,

    I have tried with "Processor SDK Linux for K2H (Version: 06.03.00.106)" and checked whether the "dsptop" works with the "tisdk-server-rootfs-image" which comes with the SDK (already built).

    My observations are, dsptop command doesn't work, earlier I mentioned "dsptop" command might work, But I could confirm it does not work with "tisdk-server-rootfs-image" too

    Thanks

    Rajarajan

  • Hi Rajarajan,

    Thanks for the reply.But how could we be able to resolve the issue with dsptop command.

    Or is there any other command to check the DSP core utilization?

    Kindly let us know.

    regards,

    Sravya

  • Hi Sravya,

    Will check and update, ASAP.

    Thanks,

    Rajarajan U

  • Hi Sravya,

    I have tried to compile, the "dsptop" from the latest source, "https://git.ti.com/cgit/sdo-emu/dsptop/".

    From this following observation made,

    dsptop -r 1 -f txt -o log.txt -d 1 -n 100 - there was an error in the command line argument, "txt" should be "text", hence this error "dsptop: unrecognized option '--0" showed up.

    1. I have modified the Makefile to keep the compiled binary in "release" folder instead of "/usr/bin" folder, due to error.
    1. "dsptop" depends on "debugss" kernel module. It needs to be enabled.
      1. But, Compiling "debugss" from source throws an error, kernel modules missing "/lib/modules/4.19.94-gbe5389fd85/build" (since the Processor SDK uses this (4.19.94) version of kernel.

    I will update you on the findings further.

    Thanks & Regards,

    Rajarajan U

  • Hi Rajarajan,

    Thanks for the update. Please keep us in your updates on dsptop issue.

    regards,

    Sravya

  • Hi Sravya,

    Could you able to compile the "debugss" kernel module with the kernel version that you have been using?

    I have been using kernel: 4.19.94, One that comes with the SDK Linux. (Just to check whether we were using the same kernel)

    Thanks,

    Rajarajan U