* Fwd: omap3isp IRQs [not found] <CAJRKTVoKYyJqP1mE=HTmm2jq9uoSkX9kf0HcMxz7F9wZnD1Y5w@mail.gmail.com> @ 2013-02-13 12:13 ` Adriano Martins 2013-02-13 18:51 ` Adriano Martins 0 siblings, 1 reply; 5+ messages in thread From: Adriano Martins @ 2013-02-13 12:13 UTC (permalink / raw) To: linux-media Hi, Please, help me :-) I trying capture frames from my new sensor, ov5640. I already capture images from a mt9p031 camera, but I have some problems with ov5640. Someone can explain me what are the CCDC_VD0_IRQ and CCDC_VD1_IRQ? In the mt9p031 sensor, I get all interrupts (including HS_VS_IRQ) and I can capture frames. In other sensor, I can't capture any frame. I get many HS_VS_IRQ only, then yavta app hangs and I need stop it. Then I get CCDC stop timeout! Is it necessary get CCDC_VD0_IRQ and CCDC_VD1_IRQ ever to capture a frame? I think all signal from ov5640 sensor are ok. A question about it: vsync may be in high level until the frame is transmitted? On my case I see just a pulse of vsync before hsync pulses. Is it correct? Thanks Regards Adriano Martins ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: omap3isp IRQs 2013-02-13 12:13 ` Fwd: omap3isp IRQs Adriano Martins @ 2013-02-13 18:51 ` Adriano Martins [not found] ` <CAJRKTVpcBfyYfbdC-+DL2UgtDR=KNRO87a+Uch583sU=8h70CQ@mail.gmail.com> 0 siblings, 1 reply; 5+ messages in thread From: Adriano Martins @ 2013-02-13 18:51 UTC (permalink / raw) To: linux-media Hi, 2013/2/13 Adriano Martins <adrianomatosmartins@gmail.com>: > Hi, > > Please, help me :-) > > I trying capture frames from my new sensor, ov5640. I already capture > images from a mt9p031 camera, but I have some problems with ov5640. > > Someone can explain me what are the CCDC_VD0_IRQ and CCDC_VD1_IRQ? > > In the mt9p031 sensor, I get all interrupts (including HS_VS_IRQ) and > I can capture frames. > > In other sensor, I can't capture any frame. I get many HS_VS_IRQ only, > then yavta app hangs and I need stop it. Then I get CCDC stop timeout! > Is it necessary get CCDC_VD0_IRQ and CCDC_VD1_IRQ ever to capture a frame? > > I think all signal from ov5640 sensor are ok. A question about it: > vsync may be in high level until the frame is transmitted? On my case > I see just a pulse of vsync before hsync pulses. Is it correct? I can capture frames now, and get all interrupts. But, The image has only green color. I have configured the CCDC module as V4L2_MBUS_FMT_UYVY8_2X8, and the sensor output format is configured as YUV422 with sequence UYVY. somebody has any idea? Regards Adriano Martins ^ permalink raw reply [flat|nested] 5+ messages in thread
[parent not found: <CAJRKTVpcBfyYfbdC-+DL2UgtDR=KNRO87a+Uch583sU=8h70CQ@mail.gmail.com>]
* Re: omap3isp IRQs [not found] ` <CAJRKTVpcBfyYfbdC-+DL2UgtDR=KNRO87a+Uch583sU=8h70CQ@mail.gmail.com> @ 2013-02-14 19:17 ` Adriano Martins 2013-02-14 20:42 ` Laurent Pinchart 0 siblings, 1 reply; 5+ messages in thread From: Adriano Martins @ 2013-02-14 19:17 UTC (permalink / raw) To: Laurent Pinchart, linux-media 2013/2/13 Adriano Martins <adrianomatosmartins@gmail.com>: > Hi Laurent, > > I think my messages are not sent to linux-media. > can you help? > > 2013/2/13 Adriano Martins <adrianomatosmartins@gmail.com>: >> Hi, >> >> Please, help me :-) >> >> I trying capture frames from my new sensor, ov5640. I already capture >> images from a mt9p031 camera, but I have some problems with ov5640. >> >> Someone can explain me what are the CCDC_VD0_IRQ and CCDC_VD1_IRQ? >> >> In the mt9p031 sensor, I get all interrupts (including HS_VS_IRQ) and >> I can capture frames. >> >> In other sensor, I can't capture any frame. I get many HS_VS_IRQ only, >> then yavta app hangs and I need stop it. Then I get CCDC stop timeout! >> Is it necessary get CCDC_VD0_IRQ and CCDC_VD1_IRQ ever to capture a frame? >> >> I think all signal from ov5640 sensor are ok. A question about it: >> vsync may be in high level until the frame is transmitted? On my case >> I see just a pulse of vsync before hsync pulses. Is it correct? > > I can capture frames now, and get all interrupts. > But, The image has only green color. I solved my problem. The .data_lane_shift and yuv sequence were wrong. > I have configured the CCDC module as V4L2_MBUS_FMT_UYVY8_2X8, and the sensor > output format is configured as YUV422 with sequence UYVY. > > somebody has any idea? > Thanks Regards Adriano Martins ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: omap3isp IRQs 2013-02-14 19:17 ` Adriano Martins @ 2013-02-14 20:42 ` Laurent Pinchart 2013-02-15 10:54 ` Adriano Martins 0 siblings, 1 reply; 5+ messages in thread From: Laurent Pinchart @ 2013-02-14 20:42 UTC (permalink / raw) To: Adriano Martins; +Cc: linux-media Hi Adriano, On Thursday 14 February 2013 17:17:40 Adriano Martins wrote: > 2013/2/13 Adriano Martins <adrianomatosmartins@gmail.com>: > > 2013/2/13 Adriano Martins <adrianomatosmartins@gmail.com>: > >> Hi, > >> > >> Please, help me :-) > >> > >> I trying capture frames from my new sensor, ov5640. I already capture > >> images from a mt9p031 camera, but I have some problems with ov5640. > >> > >> Someone can explain me what are the CCDC_VD0_IRQ and CCDC_VD1_IRQ? Those two interrupts are generated by the CCDC using programmable line counters. The ISP driver programs the CCDC to generate the VD0 interrupt on the last line of the image and the VD1 interrupt at 2/3 of the image. > >> In the mt9p031 sensor, I get all interrupts (including HS_VS_IRQ) and > >> I can capture frames. > >> > >> In other sensor, I can't capture any frame. I get many HS_VS_IRQ only, > >> then yavta app hangs and I need stop it. Then I get CCDC stop timeout! > >> Is it necessary get CCDC_VD0_IRQ and CCDC_VD1_IRQ ever to capture a > >> frame? Yes. A failure to get them usually indicates that the number of lines generated by the sensor doesn't match the number of lines expected by the CCDC (possibly because the HS signal is completely missing). > >> I think all signal from ov5640 sensor are ok. A question about it: > >> vsync may be in high level until the frame is transmitted? On my case > >> I see just a pulse of vsync before hsync pulses. Is it correct? > > > > I can capture frames now, and get all interrupts. > > But, The image has only green color. > > I solved my problem. The .data_lane_shift and yuv sequence were wrong. Glad to know you've solved the problem :-) > > I have configured the CCDC module as V4L2_MBUS_FMT_UYVY8_2X8, and the > > sensor output format is configured as YUV422 with sequence UYVY. > > > > somebody has any idea? -- Regards, Laurent Pinchart ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: omap3isp IRQs 2013-02-14 20:42 ` Laurent Pinchart @ 2013-02-15 10:54 ` Adriano Martins 0 siblings, 0 replies; 5+ messages in thread From: Adriano Martins @ 2013-02-15 10:54 UTC (permalink / raw) To: Laurent Pinchart; +Cc: linux-media Hi Laurent, 2013/2/14 Laurent Pinchart <laurent.pinchart@ideasonboard.com>: > On Thursday 14 February 2013 17:17:40 Adriano Martins wrote: >> 2013/2/13 Adriano Martins <adrianomatosmartins@gmail.com>: >> > 2013/2/13 Adriano Martins <adrianomatosmartins@gmail.com>: >> >> Hi, >> >> >> >> Please, help me :-) >> >> >> >> I trying capture frames from my new sensor, ov5640. I already capture >> >> images from a mt9p031 camera, but I have some problems with ov5640. >> >> >> >> Someone can explain me what are the CCDC_VD0_IRQ and CCDC_VD1_IRQ? > > Those two interrupts are generated by the CCDC using programmable line > counters. The ISP driver programs the CCDC to generate the VD0 interrupt on > the last line of the image and the VD1 interrupt at 2/3 of the image. Ok, I understand now. :-) >> >> In the mt9p031 sensor, I get all interrupts (including HS_VS_IRQ) and >> >> I can capture frames. >> >> >> >> In other sensor, I can't capture any frame. I get many HS_VS_IRQ only, >> >> then yavta app hangs and I need stop it. Then I get CCDC stop timeout! >> >> Is it necessary get CCDC_VD0_IRQ and CCDC_VD1_IRQ ever to capture a >> >> frame? > > Yes. A failure to get them usually indicates that the number of lines > generated by the sensor doesn't match the number of lines expected by the CCDC > (possibly because the HS signal is completely missing). Correct. I had hardware problems. The HS signal was unconnected. >> >> I think all signal from ov5640 sensor are ok. A question about it: >> >> vsync may be in high level until the frame is transmitted? On my case >> >> I see just a pulse of vsync before hsync pulses. Is it correct? >> > >> > I can capture frames now, and get all interrupts. >> > But, The image has only green color. >> >> I solved my problem. The .data_lane_shift and yuv sequence were wrong. > > Glad to know you've solved the problem :-) > >> > I have configured the CCDC module as V4L2_MBUS_FMT_UYVY8_2X8, and the >> > sensor output format is configured as YUV422 with sequence UYVY. >> > >> > somebody has any idea? Thanks Regards Adriano Martins ^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2013-02-15 10:54 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <CAJRKTVoKYyJqP1mE=HTmm2jq9uoSkX9kf0HcMxz7F9wZnD1Y5w@mail.gmail.com>
2013-02-13 12:13 ` Fwd: omap3isp IRQs Adriano Martins
2013-02-13 18:51 ` Adriano Martins
[not found] ` <CAJRKTVpcBfyYfbdC-+DL2UgtDR=KNRO87a+Uch583sU=8h70CQ@mail.gmail.com>
2013-02-14 19:17 ` Adriano Martins
2013-02-14 20:42 ` Laurent Pinchart
2013-02-15 10:54 ` Adriano Martins
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.