TDA4VM: Function to get error frames on 4 cameras on TDA4VM

Hi Shine,

Do you mean error frames for individual camera? I think you can call API IOCTL_CSIRX_GET_INST_STATUS to get error status for all camera..

Please refer to tivxCapturePrintStatus API in file ti-processor-sdk-rtos-j721e-evm-08_05_00_11\tiovx\kernels_j7\hwa\capture\vx_capture_target.c for more information.

Regards,

Brijesh

Hi Brijesh,

Thank you very much for your great support.

Is the IOCTL_CSIRX_GET_INST_STATUS function for R core? How to send error frame status to A core? 

Thanks
Regards
Shine

Hi Shine,

Are you using OpenVX framework? Then we can call TIVX_CAPTURE_GET_STATISTICS control command for capture node and can get statistics on A core.

Regards,

Brijesh

Hi Brijesh,

Thank you very much. 

Customer used tivxNodeSendCommandTimed(obj->captureObj.node, 0u, TIVX_CAPTURE_GET_STATISTICS, refs, 1u, 50u); to get tivx_capture_statistics_t.errorFrameCount error frame. At first, the tivxNodeSendCommandTimed returned -99, then it returned -1, how to use it?


Thanks
Regards
Shine

Hi Shine,

Can you please check and confirm that this API is called after graph verification? Control command can only be called after graph verification. 

You can also refer to test in tiovx/kernels_j7/hwa/test/test_capture.c for the usage of this control command.

Regards,

Brijesh

Hi Brijesh,

Thank you very much.

Customer ensured that he called the API after vxVerifyGraph. 

The tivxNodeSendCommandTimed can return correctly after increasing the timeout.  But it only works at the first two interruption recovery. The function returns -1 at the third interruption recovery. 

When recalling the function, is there some special status needing to be reset?

Regards
Shine

Hi Shine,

This API does not do any recovery, it just provides the driver statistics.. 

Can you again try increasing timeout? Because if the capture task is busy doing something else, then this control command may not get the chance to run and could time out. Any specific reason for not using infinite timeout?

Regards,

Brijesh 

Hi Brijesh,

i am the user who ask the question.

when i use  infinite timeout , in streaming off condition , whatever recovery streaming , can not get return value from tivxNodeSendCommand,  may block in this function,

The return -99 behalf timeout.

I think return -1 is nothing to do with timeout  parameter.

I need get error frame , even though in condition streaming off  than recovery in any number of times.

Hi xu fu,

did not get it, what is streaming off condition? Also when exactly do you call this API? 

Please note this API can be called only after vxVerifyGraph is called and only before graph is deleted. It cannot be called after graph delete, because node could be deleted and then it cannot reach the node. 

Regards,

Brijesh

Hi Brijesh,

Streaming off condition  i  mean not generate video stream  such as unplug the camera , and  video stream down is just impacted by hardware , i not delete graph , when i plug camera ,the video stream recover at once. 

When not use function  tivxNodeSendCommand , in condition unplug the camera than plug th camera in any number of times the video streaming is normal.

I am sure when i use tivxNodeSendCommand or tivxNodeSendCommandTimed , i not call  graph delete and use function behind  vxVerifyGraph.

Do you mean every time use tivxNodeSendCommandTimed need every call vxVerifyGraph first?

Hi xu fu,

no verifygraph should be called only once, before starting the graph. No need to call it on every tivxNodeSendCommandTimed.

Do you see this issue only when camera is unplugged? Then this could be because of the timeout in camera node. Camera node will wait for this timeout period for the frame to come, if it doesnot come, then it will send dummy frame. During this time, command may be serviced. Please keep the timeout value to be higher than camera timeout value..   

Regards,

Brijesh

When camera is unplugged the return value is -99 of tivxNodeSendCommand, in the first time unplug camea and than recovery . 

You can see the log in txt ,the value queueCount  dequeueCount get from tivxNodeSendCommandTimed can be increased  and  you can find key word about "-99",in the first time.

In the second time , I unplug camera and recover, the value queueCount  dequeueCount get from tivxNodeSendCommandTimed, not change anymore. You can find key word "-1". The value -1 is tivxNodeSendCommandTimed return value behalf function error.0358.tivxNodeSendCommandTimed.txt

I think when video stream recovery the return value of tivxNodeSendCommandTimed should be normal.

Hi,

What's the timeout value that you are using for tivxNodeSendCommandTimed and also in the capture driver? -1 error code is for invalid parameters in the OpenVX, there is not any error with -99 error code, so wondering from where it has come. 

I think error code -99 is coming due to below error, somehow you have not set enough timeout period. Can you please try increasing it? So that error code -99 error will go away. 

46.534756 s: VX_ZONE_ERROR:[tivxEventWait:224] Event timed-out.
46.534789 s: VX_ZONE_ERROR:[ownContextSendControlCmd:730] tivxEventWait() failed.

But error with -1 error code is most likely due to some invalid parameter that you are passing to this API.

Regards,

Brijesh

When i unplug camer  tivxNodeSendCommandTimed return -99 and i think this return value -99 is normal and than i plug camera the return value is normal, you can see the log is normal, the value queueCount  dequeueCount is increase.

This situation is only in the first condition, but in the second unplug camera than recovery ,the return value is -1 , i use the same parameter for tivxNodeSendCommandTimed , why get -1 return , which parameter usage error.

Hi xu fu,

Bit difficult to tell the exact reason for this API returning -1, can you please add some code in this API implementation in the tiovx/source/framework/vx_node.c file to know where and why it is returning -1 error? 

Regards,

Brijesh

I find function tivxQueueGet return -1 may be queue->count < 0 caused it.  I dont know the reason  about that.

Hi xu fu,

But from where this tivxQueueGet is getting called? If the queue is empty and also if there is a timeout for waiting on the queue, it can also return -1. Does it mean R5F is not responding? Is your graph with capture running fine when you call this API? Can you please try connecting to mcu2_0 and see if it is not crashed and is running fine? 

Regards,

Brijesh

The function tivxNodeSendCommandTimed return -1 is from  ownContextSendControlCmd -> tivxQueueGet  -> queue->count . The video stream is fine in whole time when camera is pluged , why r5f not responding. 

I dont think mcu2_0 crashed because video stream is normal , but in this situation tivxNodeSendCommandTimed return -1 .

I suspect the function tivxNodeSendCommandTimed is flawed,.

You can easily recreate the scene, can you check this function .

If there's nothing wrong with the scene you reproduced , I ask you to tell me how to do it correctly please.

Hi xu fu,

i am not able to, can you please share the example that you have used to recreate this issue? Is it multi-camera application that has been modified to recreate this issue? or other example? For the other example, is it possible to run this example on EVM? 

Also why are you using send command with timeout? Does it work fine if you use send command without timeout?

Regards,

Brijesh