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.
Tool/software:
Hi Ti experts:
On our custom boards , SoC is TDA4VEN . There are three deserializers connect to SoC's capture inst0, inst1,inst2.
In this link , I met the ``UDMA open failed `` error when I try to use capture instance 2.
And , TI experts told me that , add the following code to `app_csi.c` . After that , No error shows in Drivers. Sadly after running multi_cam demo , It still stuck at dequeue.
To find out why , I done some tests :
Firstly : using csirx test case provided under mcu_plus_sdk_j722s_09_02_00_41/examples/drivers/csirx/csirx_capture_testapp/j722s-evm/main-r5fss0-0_freertos/csirx_capture_test_main.c
I modified the code to support openning three capture instance simultaneously,
I only connected one camera to one capture instance once a time. And tested three times.
result is :
From the csirx test case , I assume that driver of third capture instance work properly.
=======================================================================================================================================
1. CRC , ECC error existing in drivers is normal ?
2. Where else should TIOVX code be changed to support the third instance ?
======================================================================================================================================
BR
stream
Hi :
Secondly , I try to read the csirx regsters to compare the status between stuck after running multi cam demo and csirx test case running well
- read 0x30141048 whether stuck or running ,value changes which means that Dphy rx is working .
- read 0x30141104
when running :
when stuck : value is 0x00000111, and does not change .
From this block diagram , I learn that : when stuck , stream0 seems not working , So , no data come to memory.
I hope it will help.
It's urgent, looking forwards to your help.
BR
stream
Hi,
From the csirx test case , I assume that driver of third capture instance work properly.
From the pdk test case, you can see that the frame drop count is also seen for all the instances. Hence, the capture is not successful here.
As mentioned in the earlier thread. The third capture instance is not validated.
Regards,
Nikhil
Hi Nikhil :
Thank you for reply.
When I running pdk driver test case, I looked into DPHY lane control and status register , [ 0x30151000 ] ,it kept changing when I kept reading , it means that PHY receiver detects the hs clk signals as i understand.
But when I use the tiovx demo , the register 0x30151000 kept unchanged in 0x44D30000, which indicate that DPHY in common completed but not receive hs clk signal . That make me confused.
By the way , firstly the camera configuration is the same between driver test case and TIOVX demo.
Secondly , In tiovx demo , I also enable the three capture instances at the same time by the following modification in app_capture_module.c
I hope it will help
BR
stream
Hi,
Are you using the single cam demo to validate the 3rd instance?
If not, I would suggest to connect a single cam onto the 3rd instance and validate first.
Since this has not been validated at TI's end, it would require a lot a effort to really debug this and identify the changes.
Regards,
Nikhil