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.
I encounter a question about tiovx resource release.
Original capture framework:
capture framework after modify:
we modify like this for Improving camera flexibility,different camera is in different graph.
Because the tiovx capture kernel is implemented based on the R-core fvid2 driver interface, which is encapsulated based on CSI hardware.
a CSI hardware has four virtual data channels, creating multiple graphs based on the current framework will lead to fvid2_create is called many times, so the same csirx hardware will be initialized many times lead to generate exceptions.
when we call a camera demo and kill it repeat 8 times,we encounter a error like figure below:
187.776160 s: VX_ZONE_ERROR:[tivxObjDescQueueDequeue:218] Invalid parameters
187.776178 s: VX_ZONE_ERROR:[tivxObjDescQueueDequeue:218] Invalid parameters
Hi,
In order to understand your usecase better could you address my below queries?
1. You are running a multicam scenario where you have 4 different cameras and you have 1 graph for each camera (i.e. one capture node per camera). Is my understanding correct?
2. Could you tell me what is FVID_proxy?
3. Could you share the full logs and please elaborate on what do you mean by "kill it repeat 8 times"?
Regards,
Nikhil