TDA2E: Sgx3DsrvLink issue

Hi,

Please make sure that you are freeing each msg after it is received and the mailbox for that link is not full.

If the mailbox has psace and the link is not busy in doing any task then it should be able to receive new msg without any delay.

When your link is receiving msg after long delay , during that time is it busy in doing any task?

Regards,

Anuj

Hi,

After your explanation,

I think that in the part of alg link,

the frequency of transmitting system_linkControl to sgx link is too high,

causing the mailbox to block.

I will check mailbox count when issue occurs.

Waiting for my test results~

SJay 

SJay

Hi,

could i increase UTILS_MBX_ACK_QUE_CNT_MAX?

default value is 4,

if i could  increase it, how many size could i increase?

SJay

Hi,

Originally in alg link each frame will use system_linkControl to send cmd to sgx link,

i tried to change when alg detect something and need to warning,

then just use system_linkControl to send cmd to sgx link,

but the issue has not improved after my system  running overnight.

In addition, I print pTsk->mbxHndl.rcvMbx.count and pTsk->mbxHndl.ackMbx.count in sgx link,

both of them are 0,

it's not same as my thoughts,

In general, I think there will be at least 2 links to send SYSTEM_CMD_NEW_DATA to sgx,

is't not?

SJay

Hi,

I think your usecase is getting hang somewhere .

So you need to debug that.

You can use null link to close your pipeline and check which link is causing hang.

You can also add some prints in all link and check where exactly it is getting hang.

Regards,

Anuj

Hi,

After add  the log information,

Found that the links still with new data when issue occurs are below,

Capture, sync,

and the other with no new data links are alg, sgx, display,

I am currently tracking dup and sync.

Is it possible that a certain video stream has not entered sync link then lead to this issue?

SJay

Hi,

I also confirmed the instId of new data frames in the capture link does continue to have 4 channels instId.

So the problem looks like in the sync link.

SJay

Hi,

As suggested earlier please use null link.

If you doubt sync link is a issue then add a null link after sync and close the usecase there and run that usecase.

Your usecase will be capture -> sync -> null

If this works then issue is somewhere else then add some more link from your original usecase and terminate it using null link and check again.

Regards,

Anuj

Hi,

   i found when issue occur , syncDone is always false,

   the default setting ,syncDelta  is 16, syncThreshold is 33,

  it looks like for 30fps (NTCS), means 33ms per frame,

  this issue is always happend when i use PAL camera,

  PAL s 25fps, 40 ms per frame,

  so  i think i need to set syncDelta  to 20, syncThreshold to 40, when i use PAL camera,

  i will try this setting, wait my testing results!

  Another problem is that usually the last link will send SYSTEM_CMD_NEW_DATA to the next link,

then capture is the first link, who passed SYSTEM_CMD_NEW_DATA to the capture link? Is it displaylink?

By the way use null link to check which link is abnormal is a method i didn't know before,

thanks you for giving me this way! i will try it in the future.

SJay