TDA2P-ACD: Capturing more than 4 image streams over 2 CSI-2 ports
Part Number: TDA2P-ACD
I found the following thread and was wondering if the functionality to run more than 4 sensors at the same time has been added to the PSDK since then.
Currently I try to run and display six sensors (IMX390) simultaneously on the TDA2Px + Fusion Board. Four sensors are connected to CSI2-PHY1 and two to CSI2-PHY2. Unfortunately the PSDK crashes when it reaches the function IssM2mIspLink_drvAllocFrames(). So I just want to make sure if it is possible at all to run these six sensors at the same time.
In reply to Tobias Schulze:
We are glad that we were able to resolve this issue, and will now proceed to close this thread.
If you have further questions related to this thread, you may click "Ask a related question" below. The newly created question will be automatically linked to this question.
In reply to Brijesh Jadav:
Yes, this is the new driver which will be used for the conversion.
Hey Brijesh, could you please tell me which module will process the remaining two channels then? Another CAL or do we use the same CAL and time-share it? I also noticed that capture CAL is named 'CAL_B', is there an 'CAL_A'? Also, could you give me a small guideline on how to use the new driver? The location where I have to add changes to the code, maybe? Thank you! Tobias
You need to set pixel extract config to 12bit mipi (VPS_ISS_CAL_PIX_EXRCT_B12_MIPI) format.
Hi Brijesh, it was already set to VPS_ISS_CAL_PIX_EXRCT_B12_MIPI in IssCaptureLink_drvSetDrvCfg. The first time CalSetPixProcCfg is called, the extract value is correct and I dont get the assertion. But after the driver is created the problem is in vcoreCalm2mApplyConfig() in vpscore_calm2m.c. In the following line the pixel extract config is set to cfg.inPixExtract (also see attached image): calCfg.pixProcCfg.extract = cfg.inPixExtract; All other parameters from cfg are 0, so it seems this config isnt initialized. At least I couldn't find the init function. Do you know how to solve this? Thank you, Tobias
ok, so this is not in iss capture configrations. It seems you are trying to use new m2m path, which internally uses cal.
we need to similarly configure cal even in m2m path. You could look into the example application in ti_components\drivers\pdk_01_10_01_06\packages\ti\drv\vps\examples\iss\m2mIssCal\src\ to understand how to configure it. This example converts 12bit mipi to 12bit linear.
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.