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.

The time spending by remote_debug_client.out

Hi sir:

I works on TI8148 evm board, my PSP is 4.04.00.01 and I have a question below.

When I run load.sh, the scripts below take a long time to be ready.

/opt/bin/fw_load.out startup VPSS-M3 /opt/firmware/dvr_rdk_fw_m3vpss.xem3

/opt/bin/fw_load.out startup VIDEO-M3 /opt/firmware/dvr_rdk_fw_m3video.xem3

/opt/bin/fw_load.out startup DSP /opt/firmware/dvr_rdk_fw_c6xdsp.xe674

rm -f /dev/dev_dma
insmod /opt/kermod/osa_kermod.ko
echo 'insmod osa_kermod end'
if [ ! -f /dev/dev_dma ]
then
    major=$(awk '$2=="dev_dma" {print $1}' /proc/devices)
    mknod /dev/dev_dma c ${major} 0
fi

/opt/bin/remote_debug_client.out ${REMOTE_DEBUG_ADDR} --waitch s m3vpss // especially when running this script

/opt/bin/remote_debug_client.out ${REMOTE_DEBUG_ADDR} --waitch s m3video

/opt/bin/remote_debug_client.out ${REMOTE_DEBUG_ADDR} --waitch s c6xdsp

I have tried to trace the source code about remote_debug_client and it looks like that remote_debug_client.out waits character 's' to be read.

I guess when m3vpss,m3video and c6xdsp task are ready, they will send the character 's', am I right?

Could you give me some suggestion how to eliminate time spending when running these scripts?

Best regards,

Marcus

  • Hi sir:

    Could anyone give me some suggestion?

    If you have no idea about my question, please let me know.

    Best regards,

    Marcus

     

  • Hi sir:

    I think I select wrong tag, so no one can answer me, so I post it again!

    I works on TI8148 evm board, my PSP is 4.04.00.01 and I have a question below.

    When I run load.sh, the scripts below take a long time to be ready.

    /opt/bin/fw_load.out startup VPSS-M3 /opt/firmware/dvr_rdk_fw_m3vpss.xem3

    /opt/bin/fw_load.out startup VIDEO-M3 /opt/firmware/dvr_rdk_fw_m3video.xem3

    /opt/bin/fw_load.out startup DSP /opt/firmware/dvr_rdk_fw_c6xdsp.xe674

    rm -f /dev/dev_dma
    insmod /opt/kermod/osa_kermod.ko
    echo 'insmod osa_kermod end'
    if [ ! -f /dev/dev_dma ]
    then
        major=$(awk '$2=="dev_dma" {print $1}' /proc/devices)
        mknod /dev/dev_dma c ${major} 0
    fi

    /opt/bin/remote_debug_client.out ${REMOTE_DEBUG_ADDR} --waitch s m3vpss // especially when running this script

    /opt/bin/remote_debug_client.out ${REMOTE_DEBUG_ADDR} --waitch s m3video

    /opt/bin/remote_debug_client.out ${REMOTE_DEBUG_ADDR} --waitch s c6xdsp

    I have tried to trace the source code about remote_debug_client and it looks like that remote_debug_client.out waits character 's' to be read.

    I guess when m3vpss,m3video and c6xdsp task are ready, they will send the character 's', am I right?

    Could you give me some suggestion how to eliminate time spending when running these scripts?

    Best regards,

    Marcus

  • The wait for ack from remote core (wait for 's' character) is intentional is done to ensure the remote slave core is initialized. The wait should not be eliminated.I understand your issue is you are seeing long wait time when loading VPSS_M3 core. What is the wait time you are seeing,Can you share logs with timestamps

    after completion of each step in load.sh

    [timestamp]

    /opt/bin/fw_load.out startup VPSS-M3 /opt/firmware/dvr_rdk_fw_m3vpss.xem3

    [timestamp]
    /opt/bin/fw_load.out startup VIDEO-M3 /opt/firmware/dvr_rdk_fw_m3video.xem3

    [timestamp]
    /opt/bin/fw_load.out startup DSP /opt/firmware/dvr_rdk_fw_c6xdsp.xe674

    [timestamp]
    rm -f /dev/dev_dma
    insmod /opt/kermod/osa_kermod.ko
    echo 'insmod osa_kermod end'
    if [ ! -f /dev/dev_dma ]
    then
        major=$(awk '$2=="dev_dma" {print $1}' /proc/devices)
        mknod /dev/dev_dma c ${major} 0
    fi

    [timestamp]
    /opt/bin/remote_debug_client.out ${REMOTE_DEBUG_ADDR} --waitch s m3vpss // especially when running this script

    [timestamp]
    /opt/bin/remote_debug_client.out ${REMOTE_DEBUG_ADDR} --waitch s m3video

    [timestamp]
    /opt/bin/remote_debug_client.out ${REMOTE_DEBUG_ADDR} --waitch s c6xdsp

  • Hi Badri Narayanan:

    can we disable remote debug functions for speed up our booting time in release version, if it is possible how should we do??

    and  

    [timestamp]
    /opt/bin/remote_debug_client.out ${REMOTE_DEBUG_ADDR} --waitch s m3vpss // especially when running this script

    [timestamp]
    /opt/bin/remote_debug_client.out ${REMOTE_DEBUG_ADDR} --waitch s m3video

    [timestamp]
    /opt/bin/remote_debug_client.out ${REMOTE_DEBUG_ADDR} --waitch s c6xdsp

    are these three steps  necessary  to do? if i comment out these three steps , there are some fail occur, like FB_DEVICE OPEN FAIL...etc

    how can we disable them , if we dont need ??


    THX for reply

  • remote debug client does not add to boot time. It is waiting for the slave core to get initialized and the wait is necessary before proceeding with other operations. It should not be disabled.

  • hi,

         unluckly, I meet this question too. 

         My version is DM8168, DVRRDK_04.00.

         After I type load.sh,  output:

    [m3vpss ]  7378: MEM: Shared Region 1: Base = 0x90000000, Length = 0x07100000 (113 MB)
    [c6xdsp ]  22: SYSTEM: ListElem Shared Addr = 0xbf31b700
    [m3video]  7380: SYSTEM  : System Common Init Done !!!
    [m3vpss ]  7379: SYSTEM  : System Common Init Done !!!
    [c6xdsp ] !!WARNING.Resource already registered:2
    [c6xdsp ]  16: SYSTEM  : Initializing Links !!!
    [m3video]  7380: SYSTEM  : System Video Init in progress !!!
    [m3vpss ]  7380: SYSTEM  : System VPSS Init in progress !!!
    [m3vpss ]  7380: SYSTEM: All VPDMA Free !!!
    [c6xdsp ]  22: SYSTEM  : FREE SPACE : System Heap      = 10391168 B, Mbx = 10240 msgs)
    [m3vpss ] === HDVPSS Clocks are enabled ===
    [m3vpss ] === HDVPSS is fully functional ===
    [m3vpss ] === HDVPSS module is not in standby ===
    [m3vpss ] === I2C1 Clk is active ===
    [c6xdsp ] Remote Debug Shared Memory @ 0xbf000000
    [m3video] Remote Debug Shared Memory @ 0xbf010820
    [m3vpss ] Remote Debug Shared Memory @ 0xbf021040


    What can I to solve it, give a hand, Thanks!

  • What is the issue you are seeing. Is load.sh not completing or is it taking time