First thing am trying is to store the image data straightly in OMAP memory without frontend and backend processing. After got successful in this i will try for frontend and backend processing.
Please refer the section 12.4.1.1.2. In this section i am planing to use path C. Please let me know whether this is correct option to store directly in memory.
From section 12.4.1.1.1,12.4.1.1.2,12.4.1.1.3 my understanding is all the images must pass through CCDC module in which the sub modules like optical clamping, faulty pixel correction,data formatter,reformatter,LSC can be enabled or disabled individually.Please clarify this.
For storing image data straightly in memory with out video processing, Please clarify the following
1. i must enable(Program) the Timing CTRL, CCDC,SBL,CBUFF modules in Camera ISP
2. Whether i need cam_hs, cam_vs,cam_fld from the camera which is going to interface with Camera ISP.
3.What is the purpose of CCDC_VD0_IRQ,CCDC_VD1_IRQ,CCDC_VD2_IRQ?What may the correspondig interrupt handler do?
4.ISP configuration details
Thanks and Regards,
kathir
To add on to what Kathir has mentioned in his post,
We are working on bringing out RAW data from a DINI-9200K FPGA based board with a Virtex-5 FPGA. The interface on the DINI board is a standard VDI interface that is it comprises of the following signals;
1) cam_d [11:0]
2) cam_hs
3) cam_vs
4) cam_pclk
We are sending out 8-bit data @ 130 MHz from the DINI board through a custom patch board that we have designed in house and that is interfaced to a ZOOM kit (1010047C) from Logic PD Inc.
So the data that is being sent out is in the order 8 bits of R, 8 bits of G, and 8 bits of B respectively. The problem that we are seeing at the OMAP side is that we are missing data (i.e. we are missing one complete byte intermittently) and the data that we see in the OMAP DDR is corrupted. Things seem to get better at lower frequencies say 30 MHz or so. However, at lower frequencies we notice that the cam_d[0] and cam_d[1] bits are corrupted.
Our Custom card is Impedance matched as well as length matched. Where are we going wrong? Could some of you folks out there suggest a solution to this problem?
Thanks,
Kartik.
ALL CONTENT AND MATERIALS ON THIS SITE ARE PROVIDED "AS IS". TI AND ITS RESPECTIVE SUPPLIERS 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.
Content on this site may contain or be subject to specific guidelines or limitations on use. All postings and use of the content on this site are subject to the Terms of Use of the site; third parties using this content agree to abide by any limitations or guidelines and to comply with the Terms of Use of this site. TI and its suppliers reserve the right to make corrections, deletions, modifications, enhancements, improvements and other changes to the content and materials, its products, programs and services at any time or to move or discontinue any content, products, programs, or services without notice.