Hi All,We have an issue in OMAP3530 ISP driver on kernel 2.6.22. We are using MT9V023 sensor to capture the video and display it on LCD. The video image on LCD is getting split after a 2 or 3 hrs run, or if there is any external disturbance. If the mobile phone which is kept nearer to camera, receives the call / SMS, the video is getting split. Following is our observation:If the camera is working fine, without any split screen, we receive 4 interrupts – in the ISP handler.isp: irqstatus = 0x02000100 - Overflow Error, VD0 Done isp: irqstatus = 0x02160000 - Overflow Error, Preview Done, LSC Done, LSC Pre-fetch Completedisp: irqstatus = 0x03000000 - Overflow Error, Resize doneisp: irqstatus = 0x02000200 - Overflow Error, VD1 Done Whenever we see the image split issue, we see an additional interrupt.isp: irqstatus = 0x02080100 - Overflow Error, LSC pre-fetch error isp: irqstatus = 0x82060000 - H-Sync, Overflow Error, LSC done, pre-fetch completed isp: irqstatus = 0x02000200 - Overflow Error and VD1 doneisp: irqstatus = 0x02100000 - Overflow Error and Preview doneisp: irqstatus = 0x03000000 - Overflow Error and Resize doneHow to recover/avoid this image spilt issue? Are there any patch for ISP on 2.6.22 kernel?. Can anybody please help us or suggest to fix this issue? is there any patch to fix this issue?
ThanksSenthil
senthilnathan KS:How to recover/avoid this image spilt issue?
Could you post a picture of the split image issue so we can see the problem more effectively? Since you mention it is seceptable to external disturbance you may want to check your hardware integrity, it could be that the external distrurbance is causing the camera to send in an invalid data stream and it is putting the capture interface in a odd state, the first thing I would try to recover from this is reset the capture interface, though I am not sure there is an option for this in the 2.6.22 driver. The 2.6.22 kernel is a bit old now, you may want to try a newer kernel version, I am not aware of any patches specific to this sort of issue.
Please find the attached split image. I have done the stop and restart the ISP if there is any error ISP isr. Most of the time, the ISP gives LSC pre-fetch error and overflow error. Is there a way on the application side to fix this issue? Please let me know.
Thanks
Senthil
This looks like something that should go away by restarting the driver, these days I would not expect this to be something that should happen so it may be a bug in the driver, however there is no TI support for camera capture drivers on the OMAP35x series, the only driver supported (that is bug reports are accepted) is the TVP5146 capture driver. For the application to fix the issue it would probably have to restart the video stream, as it looks like your buffer is out of sync with the video capture hardware, and I do not see any simpler sort of resync commands in the driver.
It is possible that there is no hardware event generated to indicate that this particular failure has occoured so there may not be a way for the software application to adequately detect the problem so if possible you may be better off finding a way to prevent it instead of repairing it. It seems like your camera is probably not generating a contiguous stream sync signals, in particular it looks like the hsync is off at some point, since you mention this can happen when there is a cell phone near by it is possible that your electrical connections between the camera and the processor are too long or inadequately shielded.
Ok.Thanks.
How about back porting ISP driver (only isp.c) from 2.6.29 to 2.6.22 kernel? will back porting help to solve this issue?. Any idea would help.
senthilnathan KS:How about back porting ISP driver (only isp.c) from 2.6.29 to 2.6.22 kernel? will back porting help to solve this issue?
That may help but it is hard to say, it is possible that the issue still exists in the newer driver and that it is only brought out by your particular hardware. On the positive side the only camera I have tested on the OMAP3 myself was with a 2.6.29 kernel (in particular this module from Leopard Imaging), though I did not do long term or EMI testing.
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.