TI E2E Community
CMOS select for 8127
In <Sensor_integration_guide_IPNC_DM812x.pdf>, two CMOS (MN34041 V1.1 and AR0330 V1.2) are listed.
I wonder is there other CMOS supported by 8127, or only those two are supported smoothly?
And, what's the function fo the FPGA? Is there any document that describe it?
The xp2 FPGA(lattice) on MN34041 sensor board is used to convert lvds data to parallel data,then connect to the parallel interface of DM8127
By the way,which version are you using with IPNC812x?
We used RDK V2.0.0.
I see in ISS package, there are four sensor device: ar0331, mn34041, mt9j003, mt9p031, and only ar0331 and mn34041 has FPGA binary file.
But 8127 used mt9j003, does it use the FPGA?
If only those four CMOS are support by 8127?
and how if we use other CMOS except those two(ar0331 mn34041)?
mt9j003 also use lattice FPGA,from Hispi to parallel(AR0331 also use Hispi mode)
The current GA V2.0 release only support these 4 sensors(however,i didn't try mt9p031)
Do you mean adding new sensor driver in GA V2.0 for other sensors?
yes, I mean add other sensor driver.
1. Can we get a list of CMOS that 8127 support smoothly, and is there some limitation of that?
2. What exactly the FPGA does(the exact data format before and after the FPGA)?
3. Where can we get the FPGA code and document? That would help us to deal with the situation of using other CMOS.
Contact with the people who provide you RDK V2.0.
Any other suggestion?
We got no help from them, so we come here.
if your new sensor board have parallel output,then connect with parallel interface of DM812X directly,for Hispi and lvds,basiclly we use lattice xp2 to do the conversion to parallel.
For MIPI interface ,the hardware did have this port,but current release don't support this driver.
Hi Pei Jacky,
(1) 8127 device has 16-bit parallel interface and 4-lane CSI2 MIPI interface. The maximum clock rating for parllel interface is 162Mhz and for MIPI (CSI2) its 1Gbps/lane. Any CMOS sensor that adheres to the above limits can be integrated to the soc. In our RDK we provide with reference drivers for only few sensors but, you should be able to use the reference to create drivers for any sensor that you want to integrate.
(2) MT9J003 or AR331 sensors have a HiSPI interface. Since 8127 does not support HiSPI interface the FPGA is put to convert from HiSPI to parallel bus. We are also planning to offer HiSPI to parallel converter chip as option. Please sync up with a local FAE at your end for more details.
(3) You need to check with local FAE at your end to get the NDA in place before we can share more information on this.
--------------------------------------------------------------------------------------------------------------Please click the Verify Answer button on this post if it answers the question.--------------------------------------------------------------------------------------------------------------
Hi, Pei jacky,
Let me add some more information,
we provided CMOS sensor driver of Mt9j003 AR0331 and MN34041, these code shows you typical way to control
sensor registers through I2C bus, or SPI(now is simulated by GIO) bus, you could take these codes for reference if
you want to add new CMOS sensor support.
For AR0331,MN34041 sensor,We'll provide improved tuned 2A than GA2.0.in next RDK Release
YUV sensor support will be provided in this release too .
Besides parallel convert, does the FPGA do other things, for example, convert RGB to YUV?
That is to say, If the CMOS has parallel interface but out data is RGB, needed FPGA to convert it to YUV?
and which YUVs does the 8127 support？
FPGA is only for HiSPI interface protocol to parallel 16-bit video port interface protocol. It does not do any color conversion.
8127 is capable of capturing RGB, YUV, BAYER formats. In case of DM8127 IPNC example the MT9J003 outputs BAYER format (HiSPI) which is converted into BAYER (parallel port) format - which is captured by parallel port on ISS and then given to ISP for color conversion to YUV.
Thanks for reply.
We saw that 8127 use Vcam but not Vcap, and in MCFW defined
VCAM_MODE_YUV420}; //16-bit Embedded sync YUV422/420 mode.
If we use Vcam, the CMOS should give above format data, others we should use FPGA to do a convert, right?
What's the difference between Vcam and Vcap?
and, What is the data format the MT9J003 gives(If FPGA Do not convert RGB to YUV, the MT9J003 gives YUV?)?
MT9J003 gives our RAW (BAYER RGGB) format of data. The FPGA does not do any data (color) conversion, it simply changes the HiSPI (MIPI) protocol to video port parallel bus.
THe ISS port captures the RAW data and does the color conversion (BAYER to YUV) int he ISP.
I found few information about the ISS and ISP in the RDK.
Where can we find some detailed documents about it?
We need to know the exact data forma that the ISS captured from the 16-bit parallel port and how the ISP convert it.
Thank you very much for help.
The data format that is captured from the 16-bit parallel port is actually dependent on the sensor which is connected.
ISS documentation is released after an NDA. Can you check with local FAE at your end on the NDA and how to get the ISS TRM documentation?
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. 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 respect to these materials. 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.