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.

RTOS/TDA3XEVM: When i send the "System_linkControl" API, sometimes the "GrpxSrcLink_tskMain" received the data late.

Part Number: TDA3XEVM

Tool/software: TI-RTOS

Hi,

When i send the "System_linkControl" API the cycle of 500ms, sometimes the "GrpxSrcLink_tskMain" received the data late.

I send the API as below,

===========================================================

 Vps_printf("Send the System_linkControl !! \r\n");
 System_linkControl(chainsObj.ucObj.GrpxSrcLinkID,
                      GRPX_SRC_LINK_CMD_NO_CAMERA,
                      &GrpxInfo,
                      sizeof(GrpxInfo),
                      TRUE);

===========================================================

In the log, the data received 600ms or 700ms delay.

I must receive the data at regular intervals.

How could i fix this issue ?

Regards,

Lee

  • Hi,
    There is no such command is avaliable in gprx src link.
    Have you added your own command.

    It is possible because of the load of the core.
    Can you please check the load.
    I hope you are adding the log just after you are receiving the command.
    Please add sleep after prints and check the timing.

    Regards,
    Anuj
  • Hi Anuj,

    Thanks for reply.
    First, My test environment is checking in "csi2_cal_sv_standalone" and it is in debug mode.

    1) Yes, I added a new command to display the new grpx for my UI.
    Below is a log of the current system load you requested.
     


    2) I measured the log on "GrpxSrcLink_tskMain" and the delay is still generated.
     
     
    3) My current concept is that the button UI should be displayed immediately for button display.
    No delay should occur.
    I don't understand that you said "Please add sleep after prints and check the timing".
    Do you want to test the code below?
     
     
    Regards,
    Lee

  • Hi,

    Can you try out the same experiment in the below usecase and check whether you are getting the same delay or not?

    vision_sdk\apps\src\rtos\usecases\vip_single_cam_view

    Regards,

    Anuj

  • Hi Anuj,

    Thanks for reply.
    Sorry, The board was made to fit our system. So, the board does not have VIP port.
    Could i try the chains_csi2CalMultiCam ?

    \PROCESSOR_SDK_VISION_03_03_00_00_HD-AVM\vision_sdk\apps\src\rtos\usecases\csi2_cal_multi_cam_view

    Regards,
    Lee
  • Hi Lee,

    Yes you can try that also and chek that delay is observed here or not.

    Regards,
    Anuj
  • Hi Anuj,

    In the "chains_csi2CalMultiCam" Application, the delay isn't observed.
    The message transmission is completed within 20ms.

    However, Although i know that many tasks are used in TI-SV, i think that the delay(600~700ms) takes too long.
    Is there a way to solve this problem ?
    Is it possible to change the priotiry of a Grpx task ?

    Regards,
    Lee

  • Hi,

    You can change the priority by changing the 3rd line of the below api.

            status = Utils_tskCreate(&pObj->tsk,
                                     GrpxSrcLink_tskMain,
                                     GRPX_SRC_LINK_TSK_PRI,
                                     gGrpxSrcLink_tskStack[grpxSrcId],
                                     GRPX_SRC_LINK_TSK_STACK_SIZE, pObj, pObj->name,
                                     UTILS_TSK_AFFINITY_CORE1);

    Regards,

    Anuj

  • Hi Anuj,

    Thanks for reply.


    Regards,
    Lee