• State TI Thinks Resolved
  • Locked Locked
  • Replies 7 replies
  • Answers 5 answers
  • Subscribers 98 subscribers
  • Views 575 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.

TDA2E: rtos system_linkControl issue

SJay
Expert 1615 points

Part Number: TDA2E

Hi,

My Development environment is below,

vision_sdk302,

4.4.84-00018-gd326d64-dirty,

tda2eg,

i find when my system runs for long time,

my GrpxSrcLink_tskMain will dead,

the dead is mean i print some log,

but at that time the log is disappear,

after trace my code,

i found it stopped at BspOsal_semWait which in links_fw\src\rtos\links_common\system\system_ipc_msgq.c   "function System_ipcMsgQSendMsg",

the code is BspOsal_semWait(gSystem_ipcObj.msgQLock, BSP_OSAL_WAIT_FOREVER);

i want to know that the parameter set to BSP_OSAL_WAIT_FOREVER is reasonable?

Because I have seen some ways to prevent stopping BspOsal_semWait wait forever,

like set 1000( mean 1sec?), if over this time print some error log,

and semStatus = (Bool)TRUE;

so, my quesion is in System_ipcMsgQSendMsg, BspOsal_semWait wait forever is reasonble?

if not, could i change this to wait 1sec?

  • 0
    TI__Guru 55685 points

    Hi,

    BSP_OSAL_WAIT_FOREVER is reasonable as the wait is on a semaphore while doing IPC.

    You need to root cause why GrpxSrcLink_tskMain stops after some time?

    Regards,

    Rishabh

  • 0 in reply to Rishabh Garg
    Expert 1615 points

    Hi Rishabh,

    GrpxSrcLink_tskMain stops just because BspOsal_semWait,

    the flow like below,

    GrpxSrcLink_tskMain

    ->GrpxSrcLink_drvProcessData

    ->GrpxSrcLink_runDisplayStats

    ->GrpxSrcLink_startResetProfiling

    ->System_linkControl(linkId,SYSTEM_COMMON_CMD_CPU_LOAD_CALC_START,NULL,0,TRUE)

    ->System_ipcSendMsg

    ->System_ipcMsgQSendMsg

    ->BspOsal_semWait(gSystem_ipcObj.msgQLock, BSP_OSAL_WAIT_FOREVER)     STOP HERE

     

    Regards,

    SJay

     

  • 0 in reply to SJay
    TI__Guru 55685 points

    Hi SJay,

    GrpxSrcLink is trying to communicate with the next link and waiting for IPC to finish by pending on a semaphore.

    What is the use case that you are running?

    What are the changes that you have made in SDK?

    Can you share the print statistics when hang occurs.

    Regards,

    Rishabh

  • 0 in reply to Rishabh Garg
    TI__Guru 55685 points

    Hi,

    I haven't heard back from you, I'm assuming you were able to resolve your issue.
    If not, just post a reply below (or create a new thread if the thread has locked due to time-out).

    Regards,
    Rishabh

  • 0 in reply to Rishabh Garg
    Expert 1615 points

    Hi,

    My usecase is chains_lvdsVipMultiCam_Sgx3Dsrv on hlos,

    alg_pluging is use objectdetection,

    my customize usecase like below,

    the links that was crossed out by black was taken off,

    because this issue need run a long time to let it occur,

    due to other works,  no extra time to provide statistics info in short time, sorry!

    SJay

  • 0 in reply to SJay
    TI__Guru 55685 points

    Hi SJay,

    Statistics will be helpful in identifying the issue.

    Can you please run the use case for enough time for hang to occur and share the statistics.

    Regards,

    Rishabh

  • 0 in reply to Rishabh Garg
    TI__Guru 55685 points

    Hi,

    I haven't heard back from you, I'm assuming you were able to resolve your issue.
    If not, just post a reply below (or create a new thread if the thread has locked due to time-out).

    Regards,
    Rishabh