Re: [linux-sunxi] Re: A20 + OV5640 (parallel) issues
IS it this one, http://dl.linux-sunxi.org/SDK/A20/ ? On Saturday, September 6, 2014 5:20:35 PM UTC-7, Jon Smirl wrote: The CSI source in the sunxi kernel is a couple of years old. First thing I would do is update to the latest source in the Allwinner SDK. On Sat, Sep 6, 2014 at 7:12 PM, George Ioakimedes georg...@gmail.com javascript: wrote: I thought I'd try and resurrect this thread. I've got a new Baseboard with a CSI1 header on it connected to a OV5642 camera module. For initial testing I am running a Cubian distro with a Cubieboard A20 board. I have the following environment: cubie@Cubian:~$ zcat /proc/config.gz | grep -i ov564 CONFIG_SOC_CAMERA_OV5642=m CONFIG_CSI_OV5640=m cubie@Cubian:~$ zcat /proc/config.gz | grep -i v4l CONFIG_VIDEO_V4L2_COMMON=y CONFIG_VIDEO_V4L2=y CONFIG_V4L_USB_DRIVERS=y CONFIG_V4L_PLATFORM_DRIVERS=y # CONFIG_V4L_MEM2MEM_DRIVERS is not set cubie@Cubian:~$ uname -a Linux Cubian 3.4.103-00029-g0c7986b #4 PREEMPT Mon Sep 1 09:30:06 PDT 2014 armv7l GNU/Linux Before I get too involved with trial and error testing I thought I would check here for advice and see if we can get this fully working for everyone. Thanks, George On Tuesday, July 29, 2014 5:28:18 AM UTC-7, Adilson Oliveira wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Em 29-07-2014 09:09, Danny Song escreveu: I have enabled the ov5640 now. it works well. Thanks That's awesome. Is it the code already on the main kernel? -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.14 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBCAAGBQJT15NKAAoJENqn0z1Ab/Bx2TAIAKpd5BrgXpbzl4acPpGOyUSe Zf0iPiGVOJfpqUeLsCJ2ESHplQOkbTzNyRlGXCBI0wA6uU04yQi4dFhHVWz3+qRz G/u+feC7fC3J6XEb6+5uGEpwBjE+jaC/803JG0trHfUqSTXGyrfrnL6aKEs8YIpY ngr34HzFIZmqsCMzOfd2h1h72Pp/gwEiYYA6dLIDFKmZ8qwRDNbmoNF6LrnDdGGC Uv43tzzBz9bBhzddZHKWDTN/01+loa2uL8IPHU24VXLCn/zU6HlCxWF5Xxm+VPbu oCxkv98+CrxUyapw5JJSeha4552kEqw8CKge9Wg7u56r6hAEec+bzuy/aAld72w= =KIfl -END PGP SIGNATURE- -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi...@googlegroups.com javascript:. For more options, visit https://groups.google.com/d/optout. -- Jon Smirl jons...@gmail.com javascript: -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [linux-sunxi] Re: A20 + OV5640 (parallel) issues
On Sun, Sep 7, 2014 at 10:42 AM, George Ioakimedes georgei...@gmail.com wrote: IS it this one, http://dl.linux-sunxi.org/SDK/A20/ ? That one is fairly recent, who knows if it is their current code. Do these instructions work? http://linux-sunxi.org/CedarX/Encoder I just remember when I looked at it last year the old code in sunxi was missing a lot of stuff that was fixed in later Allwinner releases. The old code wasn't broken, it was just missing a bunch of stuff. On Saturday, September 6, 2014 5:20:35 PM UTC-7, Jon Smirl wrote: The CSI source in the sunxi kernel is a couple of years old. First thing I would do is update to the latest source in the Allwinner SDK. On Sat, Sep 6, 2014 at 7:12 PM, George Ioakimedes georg...@gmail.com wrote: I thought I'd try and resurrect this thread. I've got a new Baseboard with a CSI1 header on it connected to a OV5642 camera module. For initial testing I am running a Cubian distro with a Cubieboard A20 board. I have the following environment: cubie@Cubian:~$ zcat /proc/config.gz | grep -i ov564 CONFIG_SOC_CAMERA_OV5642=m CONFIG_CSI_OV5640=m cubie@Cubian:~$ zcat /proc/config.gz | grep -i v4l CONFIG_VIDEO_V4L2_COMMON=y CONFIG_VIDEO_V4L2=y CONFIG_V4L_USB_DRIVERS=y CONFIG_V4L_PLATFORM_DRIVERS=y # CONFIG_V4L_MEM2MEM_DRIVERS is not set cubie@Cubian:~$ uname -a Linux Cubian 3.4.103-00029-g0c7986b #4 PREEMPT Mon Sep 1 09:30:06 PDT 2014 armv7l GNU/Linux Before I get too involved with trial and error testing I thought I would check here for advice and see if we can get this fully working for everyone. Thanks, George On Tuesday, July 29, 2014 5:28:18 AM UTC-7, Adilson Oliveira wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Em 29-07-2014 09:09, Danny Song escreveu: I have enabled the ov5640 now. it works well. Thanks That's awesome. Is it the code already on the main kernel? -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.14 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBCAAGBQJT15NKAAoJENqn0z1Ab/Bx2TAIAKpd5BrgXpbzl4acPpGOyUSe Zf0iPiGVOJfpqUeLsCJ2ESHplQOkbTzNyRlGXCBI0wA6uU04yQi4dFhHVWz3+qRz G/u+feC7fC3J6XEb6+5uGEpwBjE+jaC/803JG0trHfUqSTXGyrfrnL6aKEs8YIpY ngr34HzFIZmqsCMzOfd2h1h72Pp/gwEiYYA6dLIDFKmZ8qwRDNbmoNF6LrnDdGGC Uv43tzzBz9bBhzddZHKWDTN/01+loa2uL8IPHU24VXLCn/zU6HlCxWF5Xxm+VPbu oCxkv98+CrxUyapw5JJSeha4552kEqw8CKge9Wg7u56r6hAEec+bzuy/aAld72w= =KIfl -END PGP SIGNATURE- -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- Jon Smirl jons...@gmail.com -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- Jon Smirl jonsm...@gmail.com -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [linux-sunxi] Re: A20 + OV5640 (parallel) issues
I thought I'd try and resurrect this thread. I've got a new Baseboard with a CSI1 header on it connected to a OV5642 camera module. For initial testing I am running a Cubian distro with a Cubieboard A20 board. I have the following environment: cubie@Cubian:~$ zcat /proc/config.gz | grep -i ov564 CONFIG_SOC_CAMERA_OV5642=m CONFIG_CSI_OV5640=m cubie@Cubian:~$ zcat /proc/config.gz | grep -i v4l CONFIG_VIDEO_V4L2_COMMON=y CONFIG_VIDEO_V4L2=y CONFIG_V4L_USB_DRIVERS=y CONFIG_V4L_PLATFORM_DRIVERS=y # CONFIG_V4L_MEM2MEM_DRIVERS is not set cubie@Cubian:~$ uname -a Linux Cubian 3.4.103-00029-g0c7986b #4 PREEMPT Mon Sep 1 09:30:06 PDT 2014 armv7l GNU/Linux Before I get too involved with trial and error testing I thought I would check here for advice and see if we can get this fully working for everyone. Thanks, George On Tuesday, July 29, 2014 5:28:18 AM UTC-7, Adilson Oliveira wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Em 29-07-2014 09:09, Danny Song escreveu: I have enabled the ov5640 now. it works well. Thanks That's awesome. Is it the code already on the main kernel? -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.14 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBCAAGBQJT15NKAAoJENqn0z1Ab/Bx2TAIAKpd5BrgXpbzl4acPpGOyUSe Zf0iPiGVOJfpqUeLsCJ2ESHplQOkbTzNyRlGXCBI0wA6uU04yQi4dFhHVWz3+qRz G/u+feC7fC3J6XEb6+5uGEpwBjE+jaC/803JG0trHfUqSTXGyrfrnL6aKEs8YIpY ngr34HzFIZmqsCMzOfd2h1h72Pp/gwEiYYA6dLIDFKmZ8qwRDNbmoNF6LrnDdGGC Uv43tzzBz9bBhzddZHKWDTN/01+loa2uL8IPHU24VXLCn/zU6HlCxWF5Xxm+VPbu oCxkv98+CrxUyapw5JJSeha4552kEqw8CKge9Wg7u56r6hAEec+bzuy/aAld72w= =KIfl -END PGP SIGNATURE- -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [linux-sunxi] Re: A20 + OV5640 (parallel) issues
The CSI source in the sunxi kernel is a couple of years old. First thing I would do is update to the latest source in the Allwinner SDK. On Sat, Sep 6, 2014 at 7:12 PM, George Ioakimedes georgei...@gmail.com wrote: I thought I'd try and resurrect this thread. I've got a new Baseboard with a CSI1 header on it connected to a OV5642 camera module. For initial testing I am running a Cubian distro with a Cubieboard A20 board. I have the following environment: cubie@Cubian:~$ zcat /proc/config.gz | grep -i ov564 CONFIG_SOC_CAMERA_OV5642=m CONFIG_CSI_OV5640=m cubie@Cubian:~$ zcat /proc/config.gz | grep -i v4l CONFIG_VIDEO_V4L2_COMMON=y CONFIG_VIDEO_V4L2=y CONFIG_V4L_USB_DRIVERS=y CONFIG_V4L_PLATFORM_DRIVERS=y # CONFIG_V4L_MEM2MEM_DRIVERS is not set cubie@Cubian:~$ uname -a Linux Cubian 3.4.103-00029-g0c7986b #4 PREEMPT Mon Sep 1 09:30:06 PDT 2014 armv7l GNU/Linux Before I get too involved with trial and error testing I thought I would check here for advice and see if we can get this fully working for everyone. Thanks, George On Tuesday, July 29, 2014 5:28:18 AM UTC-7, Adilson Oliveira wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Em 29-07-2014 09:09, Danny Song escreveu: I have enabled the ov5640 now. it works well. Thanks That's awesome. Is it the code already on the main kernel? -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.14 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBCAAGBQJT15NKAAoJENqn0z1Ab/Bx2TAIAKpd5BrgXpbzl4acPpGOyUSe Zf0iPiGVOJfpqUeLsCJ2ESHplQOkbTzNyRlGXCBI0wA6uU04yQi4dFhHVWz3+qRz G/u+feC7fC3J6XEb6+5uGEpwBjE+jaC/803JG0trHfUqSTXGyrfrnL6aKEs8YIpY ngr34HzFIZmqsCMzOfd2h1h72Pp/gwEiYYA6dLIDFKmZ8qwRDNbmoNF6LrnDdGGC Uv43tzzBz9bBhzddZHKWDTN/01+loa2uL8IPHU24VXLCn/zU6HlCxWF5Xxm+VPbu oCxkv98+CrxUyapw5JJSeha4552kEqw8CKge9Wg7u56r6hAEec+bzuy/aAld72w= =KIfl -END PGP SIGNATURE- -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- Jon Smirl jonsm...@gmail.com -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [linux-sunxi] Re: A20 + OV5640 (parallel) issues
I have enabled the ov5640 now. it works well. Thanks 2014-07-13 0:34 GMT+08:00 jonsm...@gmail.com jonsm...@gmail.com: OV5640 is a parallel interface camera sensor. I believe the latest Allwinner A20 camera code is in the A20 SDK 2.0. https://dl.linux-sunxi.org/SDK/A20-SDK-2.0/ I don't have it downloaded on this machine. Maybe someone else has it broken out and can just sent you the relevant files. Inside that 6GB file is the Android tree and a kernel tree. On Sat, Jul 12, 2014 at 12:24 PM, dfson...@gmail.com wrote: Yes, ov5640 is connected with CB2 pins by fly lines. Can you share the camera driver which enables the ov5640? I am trying to enable ov5640 but failed now. Thanks in advance On Saturday, July 12, 2014 1:22:25 AM UTC+8, Jon Smirl wrote: On Fri, Jul 11, 2014 at 1:19 PM, Danny Song dfson...@gmail.com wrote: I attached ov5640 to CB2 CS1 bus. Have you enabled the ov5640 successfully ? Only ov5640 I have is the one in the EU3000. It works with the standard Allwinner Android image. So you build some kind of converter board from a FPC cable to the CB2 pins? 2014-07-12 1:17 GMT+08:00 jonsm...@gmail.com jonsm...@gmail.com: On Fri, Jul 11, 2014 at 12:09 PM, dfson...@gmail.com wrote: Hi, All I am debugging ov5640 on CB2 now. Who have enabled the ov5640 on CB1 or 2 successfully? Hope you to share the experience here. How did you attach the sensor to the CB2? On Friday, July 4, 2014 7:53:17 PM UTC+8, alex simohin wrote: Hi! I've done everything according to the instructions http://docs.cubieboard.org/tutorials/dvk521/documentations/a20/driver_porting_and_configuration . fex file I changed to ov5640. Pay attention to the sections in the manual porting I2C bus driver and porting csi driver. вторник, 1 июля 2014 г., 11:40:54 UTC+4 пользователь zahra...@gmail.com написал:On Thursday, June 26, 2014 10:48:35 AM UTC+4:30, alex simohin wrote: Hello everyone! I want to run on the OV5642 sensor cubieboard2 (A20). First tried to run OV7670. Works well. Ov5642 sensor used in another project, so the working registers I have. Tried to use them in the driver ov5640 and get a green screen with lower stripes, and in the background, the image movement visible. I do not know what the problem is. Maybe the wrong color conversion? Tested through gstreamer rtp on hardware encoder cedar264. Tried to jpeg-encode the same picture. hi alex how did you run ov7670 on A20 could you please share your fex and any other important settings? thanks, вторник, 1 июля 2014 г., 11:40:54 UTC+4 пользователь zahra...@gmail.com написал:On Thursday, June 26, 2014 10:48:35 AM UTC+4:30, alex simohin wrote: Hello everyone! I want to run on the OV5642 sensor cubieboard2 (A20). First tried to run OV7670. Works well. Ov5642 sensor used in another project, so the working registers I have. Tried to use them in the driver ov5640 and get a green screen with lower stripes, and in the background, the image movement visible. I do not know what the problem is. Maybe the wrong color conversion? Tested through gstreamer rtp on hardware encoder cedar264. Tried to jpeg-encode the same picture. hi alex how did you run ov7670 on A20 could you please share your fex and any other important settings? thanks, -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- Jon Smirl jonsm...@gmail.com -- You received this message because you are subscribed to a topic in the Google Groups linux-sunxi group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/linux-sunxi/ijitRnbl8c8/unsubscribe. To unsubscribe from this group and all its topics, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- Jon Smirl jonsm...@gmail.com -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more
Re: [linux-sunxi] Re: A20 + OV5640 (parallel) issues
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Em 29-07-2014 09:09, Danny Song escreveu: I have enabled the ov5640 now. it works well. Thanks That's awesome. Is it the code already on the main kernel? -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.14 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBCAAGBQJT15NKAAoJENqn0z1Ab/Bx2TAIAKpd5BrgXpbzl4acPpGOyUSe Zf0iPiGVOJfpqUeLsCJ2ESHplQOkbTzNyRlGXCBI0wA6uU04yQi4dFhHVWz3+qRz G/u+feC7fC3J6XEb6+5uGEpwBjE+jaC/803JG0trHfUqSTXGyrfrnL6aKEs8YIpY ngr34HzFIZmqsCMzOfd2h1h72Pp/gwEiYYA6dLIDFKmZ8qwRDNbmoNF6LrnDdGGC Uv43tzzBz9bBhzddZHKWDTN/01+loa2uL8IPHU24VXLCn/zU6HlCxWF5Xxm+VPbu oCxkv98+CrxUyapw5JJSeha4552kEqw8CKge9Wg7u56r6hAEec+bzuy/aAld72w= =KIfl -END PGP SIGNATURE- -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [linux-sunxi] Re: A20 + OV5640 (parallel) issues
Yes, ov5640 is connected with CB2 pins by fly lines. Can you share the camera driver which enables the ov5640? I am trying to enable ov5640 but failed now. Thanks in advance On Saturday, July 12, 2014 1:22:25 AM UTC+8, Jon Smirl wrote: On Fri, Jul 11, 2014 at 1:19 PM, Danny Song dfson...@gmail.com wrote: I attached ov5640 to CB2 CS1 bus. Have you enabled the ov5640 successfully ? Only ov5640 I have is the one in the EU3000. It works with the standard Allwinner Android image. So you build some kind of converter board from a FPC cable to the CB2 pins? 2014-07-12 1:17 GMT+08:00 jonsm...@gmail.com jonsm...@gmail.com: On Fri, Jul 11, 2014 at 12:09 PM, dfson...@gmail.com wrote: Hi, All I am debugging ov5640 on CB2 now. Who have enabled the ov5640 on CB1 or 2 successfully? Hope you to share the experience here. How did you attach the sensor to the CB2? On Friday, July 4, 2014 7:53:17 PM UTC+8, alex simohin wrote: Hi! I've done everything according to the instructions http://docs.cubieboard.org/tutorials/dvk521/documentations/a20/driver_porting_and_configuration. fex file I changed to ov5640. Pay attention to the sections in the manual porting I2C bus driver and porting csi driver. вторник, 1 июля 2014 г., 11:40:54 UTC+4 пользователь zahra...@gmail.com написал:On Thursday, June 26, 2014 10:48:35 AM UTC+4:30, alex simohin wrote: Hello everyone! I want to run on the OV5642 sensor cubieboard2 (A20). First tried to run OV7670. Works well. Ov5642 sensor used in another project, so the working registers I have. Tried to use them in the driver ov5640 and get a green screen with lower stripes, and in the background, the image movement visible. I do not know what the problem is. Maybe the wrong color conversion? Tested through gstreamer rtp on hardware encoder cedar264. Tried to jpeg-encode the same picture. hi alex how did you run ov7670 on A20 could you please share your fex and any other important settings? thanks, вторник, 1 июля 2014 г., 11:40:54 UTC+4 пользователь zahra...@gmail.com написал:On Thursday, June 26, 2014 10:48:35 AM UTC+4:30, alex simohin wrote: Hello everyone! I want to run on the OV5642 sensor cubieboard2 (A20). First tried to run OV7670. Works well. Ov5642 sensor used in another project, so the working registers I have. Tried to use them in the driver ov5640 and get a green screen with lower stripes, and in the background, the image movement visible. I do not know what the problem is. Maybe the wrong color conversion? Tested through gstreamer rtp on hardware encoder cedar264. Tried to jpeg-encode the same picture. hi alex how did you run ov7670 on A20 could you please share your fex and any other important settings? thanks, -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- Jon Smirl jonsm...@gmail.com -- You received this message because you are subscribed to a topic in the Google Groups linux-sunxi group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/linux-sunxi/ijitRnbl8c8/unsubscribe. To unsubscribe from this group and all its topics, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- Jon Smirl jonsm...@gmail.com -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [linux-sunxi] Re: A20 + OV5640 (parallel) issues
EU3000 is USB camera. Have you enabled ov5640 by CSI/DVP interface? On Saturday, July 12, 2014 1:22:25 AM UTC+8, Jon Smirl wrote: On Fri, Jul 11, 2014 at 1:19 PM, Danny Song dfson...@gmail.com wrote: I attached ov5640 to CB2 CS1 bus. Have you enabled the ov5640 successfully ? Only ov5640 I have is the one in the EU3000. It works with the standard Allwinner Android image. So you build some kind of converter board from a FPC cable to the CB2 pins? 2014-07-12 1:17 GMT+08:00 jonsm...@gmail.com jonsm...@gmail.com: On Fri, Jul 11, 2014 at 12:09 PM, dfson...@gmail.com wrote: Hi, All I am debugging ov5640 on CB2 now. Who have enabled the ov5640 on CB1 or 2 successfully? Hope you to share the experience here. How did you attach the sensor to the CB2? On Friday, July 4, 2014 7:53:17 PM UTC+8, alex simohin wrote: Hi! I've done everything according to the instructions http://docs.cubieboard.org/tutorials/dvk521/documentations/a20/driver_porting_and_configuration. fex file I changed to ov5640. Pay attention to the sections in the manual porting I2C bus driver and porting csi driver. вторник, 1 июля 2014 г., 11:40:54 UTC+4 пользователь zahra...@gmail.com написал:On Thursday, June 26, 2014 10:48:35 AM UTC+4:30, alex simohin wrote: Hello everyone! I want to run on the OV5642 sensor cubieboard2 (A20). First tried to run OV7670. Works well. Ov5642 sensor used in another project, so the working registers I have. Tried to use them in the driver ov5640 and get a green screen with lower stripes, and in the background, the image movement visible. I do not know what the problem is. Maybe the wrong color conversion? Tested through gstreamer rtp on hardware encoder cedar264. Tried to jpeg-encode the same picture. hi alex how did you run ov7670 on A20 could you please share your fex and any other important settings? thanks, вторник, 1 июля 2014 г., 11:40:54 UTC+4 пользователь zahra...@gmail.com написал:On Thursday, June 26, 2014 10:48:35 AM UTC+4:30, alex simohin wrote: Hello everyone! I want to run on the OV5642 sensor cubieboard2 (A20). First tried to run OV7670. Works well. Ov5642 sensor used in another project, so the working registers I have. Tried to use them in the driver ov5640 and get a green screen with lower stripes, and in the background, the image movement visible. I do not know what the problem is. Maybe the wrong color conversion? Tested through gstreamer rtp on hardware encoder cedar264. Tried to jpeg-encode the same picture. hi alex how did you run ov7670 on A20 could you please share your fex and any other important settings? thanks, -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- Jon Smirl jonsm...@gmail.com -- You received this message because you are subscribed to a topic in the Google Groups linux-sunxi group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/linux-sunxi/ijitRnbl8c8/unsubscribe. To unsubscribe from this group and all its topics, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- Jon Smirl jonsm...@gmail.com -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [linux-sunxi] Re: A20 + OV5640 (parallel) issues
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Em 12-07-2014 13:27, dfson...@gmail.com escreveu: EU3000 is USB camera. Have you enabled ov5640 by CSI/DVP interface? Sure it's USB? I can't see a sign of it. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.14 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBCAAGBQJTwWKNAAoJENqn0z1Ab/BxdkYH/3Sn9h1SkWM88FVMljLCN27b 2Brc1xPVoPF49zJplDg6cIrQ+3z8XJtb6f2utj5VFgUMZLlk3l9C2sdADxeD91Rw 6NspM3WYzK/Z5UR5NIj8BdnU7hzBVKKMnAeDB/Wo9BhljnfbpPDzNMqm34F8qIYV 7Qc1Rd/77wbIoFDX6bYkaplYo2n1SjJnh75XbVvn+dzmeIDAAGoniNElvsr5n9bd RmEU+q3JXy8opmYuXe6F2lwgoS3HfL9QgRU0QEDPug6uf4+kkYctJJIyZrduwg2i WKb7BznFBMVc8gB3wyJrCrb1nYb1Gc8q8SVkWxeXeRSAuTym1IVR+lKCwyQrVQA= =0zjI -END PGP SIGNATURE- -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [linux-sunxi] Re: A20 + OV5640 (parallel) issues
OV5640 is a parallel interface camera sensor. I believe the latest Allwinner A20 camera code is in the A20 SDK 2.0. https://dl.linux-sunxi.org/SDK/A20-SDK-2.0/ I don't have it downloaded on this machine. Maybe someone else has it broken out and can just sent you the relevant files. Inside that 6GB file is the Android tree and a kernel tree. On Sat, Jul 12, 2014 at 12:24 PM, dfson...@gmail.com wrote: Yes, ov5640 is connected with CB2 pins by fly lines. Can you share the camera driver which enables the ov5640? I am trying to enable ov5640 but failed now. Thanks in advance On Saturday, July 12, 2014 1:22:25 AM UTC+8, Jon Smirl wrote: On Fri, Jul 11, 2014 at 1:19 PM, Danny Song dfson...@gmail.com wrote: I attached ov5640 to CB2 CS1 bus. Have you enabled the ov5640 successfully ? Only ov5640 I have is the one in the EU3000. It works with the standard Allwinner Android image. So you build some kind of converter board from a FPC cable to the CB2 pins? 2014-07-12 1:17 GMT+08:00 jonsm...@gmail.com jonsm...@gmail.com: On Fri, Jul 11, 2014 at 12:09 PM, dfson...@gmail.com wrote: Hi, All I am debugging ov5640 on CB2 now. Who have enabled the ov5640 on CB1 or 2 successfully? Hope you to share the experience here. How did you attach the sensor to the CB2? On Friday, July 4, 2014 7:53:17 PM UTC+8, alex simohin wrote: Hi! I've done everything according to the instructions http://docs.cubieboard.org/tutorials/dvk521/documentations/a20/driver_porting_and_configuration. fex file I changed to ov5640. Pay attention to the sections in the manual porting I2C bus driver and porting csi driver. вторник, 1 июля 2014 г., 11:40:54 UTC+4 пользователь zahra...@gmail.com написал:On Thursday, June 26, 2014 10:48:35 AM UTC+4:30, alex simohin wrote: Hello everyone! I want to run on the OV5642 sensor cubieboard2 (A20). First tried to run OV7670. Works well. Ov5642 sensor used in another project, so the working registers I have. Tried to use them in the driver ov5640 and get a green screen with lower stripes, and in the background, the image movement visible. I do not know what the problem is. Maybe the wrong color conversion? Tested through gstreamer rtp on hardware encoder cedar264. Tried to jpeg-encode the same picture. hi alex how did you run ov7670 on A20 could you please share your fex and any other important settings? thanks, вторник, 1 июля 2014 г., 11:40:54 UTC+4 пользователь zahra...@gmail.com написал:On Thursday, June 26, 2014 10:48:35 AM UTC+4:30, alex simohin wrote: Hello everyone! I want to run on the OV5642 sensor cubieboard2 (A20). First tried to run OV7670. Works well. Ov5642 sensor used in another project, so the working registers I have. Tried to use them in the driver ov5640 and get a green screen with lower stripes, and in the background, the image movement visible. I do not know what the problem is. Maybe the wrong color conversion? Tested through gstreamer rtp on hardware encoder cedar264. Tried to jpeg-encode the same picture. hi alex how did you run ov7670 on A20 could you please share your fex and any other important settings? thanks, -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- Jon Smirl jonsm...@gmail.com -- You received this message because you are subscribed to a topic in the Google Groups linux-sunxi group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/linux-sunxi/ijitRnbl8c8/unsubscribe. To unsubscribe from this group and all its topics, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- Jon Smirl jonsm...@gmail.com -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- Jon Smirl jonsm...@gmail.com -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to
[linux-sunxi] Re: A20 + OV5640 (parallel) issues
Hi, All I am debugging ov5640 on CB2 now. Who have enabled the ov5640 on CB1 or 2 successfully? Hope you to share the experience here. On Friday, July 4, 2014 7:53:17 PM UTC+8, alex simohin wrote: Hi! I've done everything according to the instructions http://docs.cubieboard.org/tutorials/dvk521/documentations/a20/driver_porting_and_configuration. fex file I changed to ov5640. Pay attention to the sections in the manual porting I2C bus driver and porting csi driver. вторник, 1 июля 2014 г., 11:40:54 UTC+4 пользователь zahra...@gmail.com написал:On Thursday, June 26, 2014 10:48:35 AM UTC+4:30, alex simohin wrote: Hello everyone! I want to run on the OV5642 sensor cubieboard2 (A20). First tried to run OV7670. Works well. Ov5642 sensor used in another project, so the working registers I have. Tried to use them in the driver ov5640 and get a green screen with lower stripes, and in the background, the image movement visible. I do not know what the problem is. Maybe the wrong color conversion? Tested through gstreamer rtp on hardware encoder cedar264. Tried to jpeg-encode the same picture. hi alex how did you run ov7670 on A20 could you please share your fex and any other important settings? thanks, вторник, 1 июля 2014 г., 11:40:54 UTC+4 пользователь zahra...@gmail.com написал:On Thursday, June 26, 2014 10:48:35 AM UTC+4:30, alex simohin wrote: Hello everyone! I want to run on the OV5642 sensor cubieboard2 (A20). First tried to run OV7670. Works well. Ov5642 sensor used in another project, so the working registers I have. Tried to use them in the driver ov5640 and get a green screen with lower stripes, and in the background, the image movement visible. I do not know what the problem is. Maybe the wrong color conversion? Tested through gstreamer rtp on hardware encoder cedar264. Tried to jpeg-encode the same picture. hi alex how did you run ov7670 on A20 could you please share your fex and any other important settings? thanks, -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [linux-sunxi] Re: A20 + OV5640 (parallel) issues
On Fri, Jul 11, 2014 at 12:09 PM, dfson...@gmail.com wrote: Hi, All I am debugging ov5640 on CB2 now. Who have enabled the ov5640 on CB1 or 2 successfully? Hope you to share the experience here. How did you attach the sensor to the CB2? On Friday, July 4, 2014 7:53:17 PM UTC+8, alex simohin wrote: Hi! I've done everything according to the instructions http://docs.cubieboard.org/tutorials/dvk521/documentations/a20/driver_porting_and_configuration. fex file I changed to ov5640. Pay attention to the sections in the manual porting I2C bus driver and porting csi driver. вторник, 1 июля 2014 г., 11:40:54 UTC+4 пользователь zahra...@gmail.com написал:On Thursday, June 26, 2014 10:48:35 AM UTC+4:30, alex simohin wrote: Hello everyone! I want to run on the OV5642 sensor cubieboard2 (A20). First tried to run OV7670. Works well. Ov5642 sensor used in another project, so the working registers I have. Tried to use them in the driver ov5640 and get a green screen with lower stripes, and in the background, the image movement visible. I do not know what the problem is. Maybe the wrong color conversion? Tested through gstreamer rtp on hardware encoder cedar264. Tried to jpeg-encode the same picture. hi alex how did you run ov7670 on A20 could you please share your fex and any other important settings? thanks, вторник, 1 июля 2014 г., 11:40:54 UTC+4 пользователь zahra...@gmail.com написал:On Thursday, June 26, 2014 10:48:35 AM UTC+4:30, alex simohin wrote: Hello everyone! I want to run on the OV5642 sensor cubieboard2 (A20). First tried to run OV7670. Works well. Ov5642 sensor used in another project, so the working registers I have. Tried to use them in the driver ov5640 and get a green screen with lower stripes, and in the background, the image movement visible. I do not know what the problem is. Maybe the wrong color conversion? Tested through gstreamer rtp on hardware encoder cedar264. Tried to jpeg-encode the same picture. hi alex how did you run ov7670 on A20 could you please share your fex and any other important settings? thanks, -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- Jon Smirl jonsm...@gmail.com -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [linux-sunxi] Re: A20 + OV5640 (parallel) issues
I attached ov5640 to CB2 CS1 bus. Have you enabled the ov5640 successfully ? 2014-07-12 1:17 GMT+08:00 jonsm...@gmail.com jonsm...@gmail.com: On Fri, Jul 11, 2014 at 12:09 PM, dfson...@gmail.com wrote: Hi, All I am debugging ov5640 on CB2 now. Who have enabled the ov5640 on CB1 or 2 successfully? Hope you to share the experience here. How did you attach the sensor to the CB2? On Friday, July 4, 2014 7:53:17 PM UTC+8, alex simohin wrote: Hi! I've done everything according to the instructions http://docs.cubieboard.org/tutorials/dvk521/documentations/a20/driver_porting_and_configuration. fex file I changed to ov5640. Pay attention to the sections in the manual porting I2C bus driver and porting csi driver. вторник, 1 июля 2014 г., 11:40:54 UTC+4 пользователь zahra...@gmail.com написал:On Thursday, June 26, 2014 10:48:35 AM UTC+4:30, alex simohin wrote: Hello everyone! I want to run on the OV5642 sensor cubieboard2 (A20). First tried to run OV7670. Works well. Ov5642 sensor used in another project, so the working registers I have. Tried to use them in the driver ov5640 and get a green screen with lower stripes, and in the background, the image movement visible. I do not know what the problem is. Maybe the wrong color conversion? Tested through gstreamer rtp on hardware encoder cedar264. Tried to jpeg-encode the same picture. hi alex how did you run ov7670 on A20 could you please share your fex and any other important settings? thanks, вторник, 1 июля 2014 г., 11:40:54 UTC+4 пользователь zahra...@gmail.com написал:On Thursday, June 26, 2014 10:48:35 AM UTC+4:30, alex simohin wrote: Hello everyone! I want to run on the OV5642 sensor cubieboard2 (A20). First tried to run OV7670. Works well. Ov5642 sensor used in another project, so the working registers I have. Tried to use them in the driver ov5640 and get a green screen with lower stripes, and in the background, the image movement visible. I do not know what the problem is. Maybe the wrong color conversion? Tested through gstreamer rtp on hardware encoder cedar264. Tried to jpeg-encode the same picture. hi alex how did you run ov7670 on A20 could you please share your fex and any other important settings? thanks, -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- Jon Smirl jonsm...@gmail.com -- You received this message because you are subscribed to a topic in the Google Groups linux-sunxi group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/linux-sunxi/ijitRnbl8c8/unsubscribe. To unsubscribe from this group and all its topics, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [linux-sunxi] Re: A20 + OV5640 (parallel) issues
On Fri, Jul 11, 2014 at 1:19 PM, Danny Song dfson...@gmail.com wrote: I attached ov5640 to CB2 CS1 bus. Have you enabled the ov5640 successfully ? Only ov5640 I have is the one in the EU3000. It works with the standard Allwinner Android image. So you build some kind of converter board from a FPC cable to the CB2 pins? 2014-07-12 1:17 GMT+08:00 jonsm...@gmail.com jonsm...@gmail.com: On Fri, Jul 11, 2014 at 12:09 PM, dfson...@gmail.com wrote: Hi, All I am debugging ov5640 on CB2 now. Who have enabled the ov5640 on CB1 or 2 successfully? Hope you to share the experience here. How did you attach the sensor to the CB2? On Friday, July 4, 2014 7:53:17 PM UTC+8, alex simohin wrote: Hi! I've done everything according to the instructions http://docs.cubieboard.org/tutorials/dvk521/documentations/a20/driver_porting_and_configuration. fex file I changed to ov5640. Pay attention to the sections in the manual porting I2C bus driver and porting csi driver. вторник, 1 июля 2014 г., 11:40:54 UTC+4 пользователь zahra...@gmail.com написал:On Thursday, June 26, 2014 10:48:35 AM UTC+4:30, alex simohin wrote: Hello everyone! I want to run on the OV5642 sensor cubieboard2 (A20). First tried to run OV7670. Works well. Ov5642 sensor used in another project, so the working registers I have. Tried to use them in the driver ov5640 and get a green screen with lower stripes, and in the background, the image movement visible. I do not know what the problem is. Maybe the wrong color conversion? Tested through gstreamer rtp on hardware encoder cedar264. Tried to jpeg-encode the same picture. hi alex how did you run ov7670 on A20 could you please share your fex and any other important settings? thanks, вторник, 1 июля 2014 г., 11:40:54 UTC+4 пользователь zahra...@gmail.com написал:On Thursday, June 26, 2014 10:48:35 AM UTC+4:30, alex simohin wrote: Hello everyone! I want to run on the OV5642 sensor cubieboard2 (A20). First tried to run OV7670. Works well. Ov5642 sensor used in another project, so the working registers I have. Tried to use them in the driver ov5640 and get a green screen with lower stripes, and in the background, the image movement visible. I do not know what the problem is. Maybe the wrong color conversion? Tested through gstreamer rtp on hardware encoder cedar264. Tried to jpeg-encode the same picture. hi alex how did you run ov7670 on A20 could you please share your fex and any other important settings? thanks, -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- Jon Smirl jonsm...@gmail.com -- You received this message because you are subscribed to a topic in the Google Groups linux-sunxi group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/linux-sunxi/ijitRnbl8c8/unsubscribe. To unsubscribe from this group and all its topics, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. -- Jon Smirl jonsm...@gmail.com -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [linux-sunxi] Re: A20 + OV5640 (parallel) issues
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Em 11-07-2014 14:19, Danny Song escreveu: I attached ov5640 to CB2 CS1 bus. Have you enabled the ov5640 successfully ? I was told by the manufacturer of eu3000 board they are moving to the s5k4ec sensor because the OV5640 is been phased out. I'm not 100% sure if this is true because just a design engineer told me that but, worth the heads up I guess. []s Adilson. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.14 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBCAAGBQJTwB3MAAoJENqn0z1Ab/BxT2IH/0mO0sD4Oh0P/hbIKNuR0gPp ejMi5Vc+IE475p/jIsNfUcXGoxuTd8iXLVjEt27UKaa96y2dU16jfC4DTy/nqrqk Vov/IfWtWlbQZOZeu/EWzF2lJIkvNxnOjWaJ491ah9i+w0c4zKSjIEkmr/9XqoAa BjtqjSW5268fMwrH2b2Z+XMEDtV8tByiCwyHDZvanw/tp6lnBc49YHj6pEZxi6lI k49loXlUNPz81yF3xJGpihd29iwn9Tw5d16KuA9R1/CQcLKezVyF1OoBGlV+hgAS dhFmwaoJK/PoybfVnKjUGKz3STr6tNHVAcn0ihmtu2lygwWkoF0UvXm4K2l0emI= =T6Rh -END PGP SIGNATURE- -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[linux-sunxi] Re: A20 + OV5640 (parallel) issues
Hi! I've done everything according to the instructions http://docs.cubieboard.org/tutorials/dvk521/documentations/a20/driver_porting_and_configuration . fex file I changed to ov5640. Pay attention to the sections in the manual porting I2C bus driver and porting csi driver. вторник, 1 июля 2014 г., 11:40:54 UTC+4 пользователь zahra...@gmail.com написал: On Thursday, June 26, 2014 10:48:35 AM UTC+4:30, alex simohin wrote: Hello everyone! I want to run on the OV5642 sensor cubieboard2 (A20). First tried to run OV7670. Works well. Ov5642 sensor used in another project, so the working registers I have. Tried to use them in the driver ov5640 and get a green screen with lower stripes, and in the background, the image movement visible. I do not know what the problem is. Maybe the wrong color conversion? Tested through gstreamer rtp on hardware encoder cedar264. Tried to jpeg-encode the same picture. hi alex how did you run ov7670 on A20 could you please share your fex and any other important settings? thanks, вторник, 1 июля 2014 г., 11:40:54 UTC+4 пользователь zahra...@gmail.com написал: On Thursday, June 26, 2014 10:48:35 AM UTC+4:30, alex simohin wrote: Hello everyone! I want to run on the OV5642 sensor cubieboard2 (A20). First tried to run OV7670. Works well. Ov5642 sensor used in another project, so the working registers I have. Tried to use them in the driver ov5640 and get a green screen with lower stripes, and in the background, the image movement visible. I do not know what the problem is. Maybe the wrong color conversion? Tested through gstreamer rtp on hardware encoder cedar264. Tried to jpeg-encode the same picture. hi alex how did you run ov7670 on A20 could you please share your fex and any other important settings? thanks, -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. script.fex Description: Binary data
[linux-sunxi] Re: A20 + OV5640 (parallel) issues
On Thursday, June 26, 2014 10:48:35 AM UTC+4:30, alex simohin wrote: Hello everyone! I want to run on the OV5642 sensor cubieboard2 (A20). First tried to run OV7670. Works well. Ov5642 sensor used in another project, so the working registers I have. Tried to use them in the driver ov5640 and get a green screen with lower stripes, and in the background, the image movement visible. I do not know what the problem is. Maybe the wrong color conversion? Tested through gstreamer rtp on hardware encoder cedar264. Tried to jpeg-encode the same picture. hi alex how did you run ov7670 on A20 could you please share your fex and any other important settings? thanks, -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[linux-sunxi] Re: A20 + OV5640 (parallel) issues
Hello everyone! I want to run on the OV5642 sensor cubieboard2 (A20). First tried to run OV7670. Works well. Ov5642 sensor used in another project, so the working registers I have. Tried to use them in the driver ov5640 and get a green screen with lower stripes, and in the background, the image movement visible. I do not know what the problem is. Maybe the wrong color conversion? Tested through gstreamer rtp on hardware encoder cedar264. Tried to jpeg-encode the same picture. -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [linux-sunxi] Re: A20 + OV5640 (parallel) issues
Luckily not yet, it goes directly to the screen - this would be the next potential project. However, when I see how many issues disp driver has (and it's somewhat documented), I cannot imagine the issues with the VPU that you're having, knowing that even registers are not documented... Hopefully, it'll be a bit more functional when I get the second project. On Saturday, March 29, 2014 10:56:49 PM UTC+1, Jon Smirl wrote: On Sat, Mar 29, 2014 at 4:34 PM, Ivan Kozic jimm...@gmail.comjavascript: wrote: Hey getting closer :) There's still an issue with the LDO (I don't like this debugfs issue) - check if you actually get sensor voltage first. If no, there's still something funny going on with AXP, so triple-check the Fex file for LDO init. Check with a multimeter whether you really get 2V8. Ok, so the I2C stuff is located in the driver itself - just look at the functions in the mt9d112 driver file (something like sensor_read and sensor_write) - there you should see if the sensor address is correct. Also bear in mind which I2C bus is used for sensor in the fex file for your sensor - mine is twi0, but it can easily be that you've connected the sensor to something else (on Olinuxino twi2 was also close to route for instance so I made assembly options on my interface to either use TWI0 or TWI2, as I didn't really know what is implemented in the kernel and what's not at the time...). If you're using level converters for I2C, check them as well, especially OE's. Are you planning on feeding this into the h.264 compression engine? That's where I got stuck with not enough compression being done - output stream is too many MB/s. On Fri, Mar 28, 2014 at 11:47 PM, rdv...@gmail.com javascript: wrote: пятница, 28 марта 2014 г., 11:41:49 UTC+2 пользователь Ivan Kozic написал: Hi, You haven't given much info about this - take care with Cubieboard 1 2 - as far as I can remember they don't have PIXCLK routed for CSI0 port, so it's completely unusable. You should use CSI1. Regarding the seg fault - not sure how you connected the power supplies to the sensor, but these regulator_enable are for AXP IC - if you connected the sensor to the AXP, you need to use them I guess. I for instance have just connected the sensor supply to fixed LDO's coming from either 3V3 or 5V, which is always alive, so I don't really need them, but nevertheless they aren't commented out in my driver (WiP, so still dirty) and they are working, so maybe the culprit is something else. You didn't say which test application or given any snippets, but if it's the one coming with the driver (app_test_ok or something similar), by Rockie Cheng (this name always amuses me :) ), then it's full of bugs and issues and you should carefully go through every step and clean the crap code out (a lot of it is crap). Better yet, write a much simpler V4L2 test app yourself. Things that also pop is the old kernel (I'm using 3.4.75 and this is already like couple of months old) and this Linaro rootfs (don't know about this - is it fully supported on Cubies?). You should probably use newer kernel just to be sure that something stupid is not breaking. Also take care with drivers - the one for OV5640 is very badly written and full of bugs and I don't think that the supplied sensor settings are usable for anyone (they are all like 3.75 and 7.5 fps, most of them just wrong). Also sun4i_csi driver is bad (you can read some of the issues on this thread, but there are other threads as well). So mostly for a functional system all this needs to be cleaned and rewritten. On Thursday, March 27, 2014 11:54:08 PM UTC+1, rdv...@gmail.com wrote:Hello guys, I want to get camera module mt9d112 working on cubieboard a10 over CSI. I am using ubuntu linaro with kernel version 3.4.61. Test application crashes with seg fault on (regulator_enable+0x4/0x1f8) from [bf010138] (sensor_power+0x190/0x398 [mt9d112]). Could you please help me to figure out where the issue is? How can I debug kernel module? You are right for testing I using app_test_ok. This test application is full of mistakes but for now I did not even successfuly initialized camera module. I have connected VCC of camera module to CSI1_IO_2V8 pin on the board and other pins to the rest of CSI ports. The CSI1_IO_2V8 is actually LDO4 of AXP20 and I finally found in AllWinner documentation that string axp_hdmi should be used in script.fex instead of axp_p11 as described in tutorial. By the way the tutorial from cubieboard is full of such mistakes. So, when I change settings string to axp_hdmi I get new portion of errors: [ 383.721765] [CSI]Welcome to CSI driver [ 383.723657] [CSI]csi_init [
Re: [linux-sunxi] Re: A20 + OV5640 (parallel) issues
Hey getting closer :) There's still an issue with the LDO (I don't like this debugfs issue) - check if you actually get sensor voltage first. If no, there's still something funny going on with AXP, so triple-check the Fex file for LDO init. Check with a multimeter whether you really get 2V8. Ok, so the I2C stuff is located in the driver itself - just look at the functions in the mt9d112 driver file (something like sensor_read and sensor_write) - there you should see if the sensor address is correct. Also bear in mind which I2C bus is used for sensor in the fex file for your sensor - mine is twi0, but it can easily be that you've connected the sensor to something else (on Olinuxino twi2 was also close to route for instance so I made assembly options on my interface to either use TWI0 or TWI2, as I didn't really know what is implemented in the kernel and what's not at the time...). If you're using level converters for I2C, check them as well, especially OE's. On Fri, Mar 28, 2014 at 11:47 PM, rdv0...@gmail.com wrote: пятница, 28 марта 2014 г., 11:41:49 UTC+2 пользователь Ivan Kozic написал: Hi, You haven't given much info about this - take care with Cubieboard 1 2 - as far as I can remember they don't have PIXCLK routed for CSI0 port, so it's completely unusable. You should use CSI1. Regarding the seg fault - not sure how you connected the power supplies to the sensor, but these regulator_enable are for AXP IC - if you connected the sensor to the AXP, you need to use them I guess. I for instance have just connected the sensor supply to fixed LDO's coming from either 3V3 or 5V, which is always alive, so I don't really need them, but nevertheless they aren't commented out in my driver (WiP, so still dirty) and they are working, so maybe the culprit is something else. You didn't say which test application or given any snippets, but if it's the one coming with the driver (app_test_ok or something similar), by Rockie Cheng (this name always amuses me :) ), then it's full of bugs and issues and you should carefully go through every step and clean the crap code out (a lot of it is crap). Better yet, write a much simpler V4L2 test app yourself. Things that also pop is the old kernel (I'm using 3.4.75 and this is already like couple of months old) and this Linaro rootfs (don't know about this - is it fully supported on Cubies?). You should probably use newer kernel just to be sure that something stupid is not breaking. Also take care with drivers - the one for OV5640 is very badly written and full of bugs and I don't think that the supplied sensor settings are usable for anyone (they are all like 3.75 and 7.5 fps, most of them just wrong). Also sun4i_csi driver is bad (you can read some of the issues on this thread, but there are other threads as well). So mostly for a functional system all this needs to be cleaned and rewritten. On Thursday, March 27, 2014 11:54:08 PM UTC+1, rdv...@gmail.comwrote:Hello guys, I want to get camera module mt9d112 working on cubieboard a10 over CSI. I am using ubuntu linaro with kernel version 3.4.61. Test application crashes with seg fault on (regulator_enable+0x4/0x1f8) from [bf010138] (sensor_power+0x190/0x398 [mt9d112]). Could you please help me to figure out where the issue is? How can I debug kernel module? You are right for testing I using app_test_ok. This test application is full of mistakes but for now I did not even successfuly initialized camera module. I have connected VCC of camera module to CSI1_IO_2V8 pin on the board and other pins to the rest of CSI ports. The CSI1_IO_2V8 is actually LDO4 of AXP20 and I finally found in AllWinner documentation that string axp_hdmi should be used in script.fex instead of axp_p11 as described in tutorial. By the way the tutorial from cubieboard is full of such mistakes. So, when I change settings string to axp_hdmi I get new portion of errors: [ 383.721765] [CSI]Welcome to CSI driver [ 383.723657] [CSI]csi_init [ 383.934525] [CSI]registered sub device,input_num = 0 [ 383.939747] axp20_ldo4: Failed to create debugfs directory [ 384.003476] [CSI]V4L2 device registered as video1 [ 385.171443] incomplete xfer (0x20) [ 385.176430] [CSI_ERR][MT9D112]Error -70 on register write [ 385.181925] [CSI_ERR][MT9D112]sensor_read err at sensor_detect! [ 385.194199] [CSI_ERR][MT9D112]chip found is not an target chip. [ 385.199069] [CSI_ERR]sensor initial error when csi open! As I understand these error means that I2C communication is failed. The I2C address might by incorrect. But what is incomplete xfer (0x20) ? -- You received this message because you are subscribed to a topic in the Google Groups linux-sunxi group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/linux-sunxi/ijitRnbl8c8/unsubscribe. To unsubscribe from this group and all its topics, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more
Re: [linux-sunxi] Re: A20 + OV5640 (parallel) issues
On Sat, Mar 29, 2014 at 4:34 PM, Ivan Kozic jimmy...@gmail.com wrote: Hey getting closer :) There's still an issue with the LDO (I don't like this debugfs issue) - check if you actually get sensor voltage first. If no, there's still something funny going on with AXP, so triple-check the Fex file for LDO init. Check with a multimeter whether you really get 2V8. Ok, so the I2C stuff is located in the driver itself - just look at the functions in the mt9d112 driver file (something like sensor_read and sensor_write) - there you should see if the sensor address is correct. Also bear in mind which I2C bus is used for sensor in the fex file for your sensor - mine is twi0, but it can easily be that you've connected the sensor to something else (on Olinuxino twi2 was also close to route for instance so I made assembly options on my interface to either use TWI0 or TWI2, as I didn't really know what is implemented in the kernel and what's not at the time...). If you're using level converters for I2C, check them as well, especially OE's. Are you planning on feeding this into the h.264 compression engine? That's where I got stuck with not enough compression being done - output stream is too many MB/s. On Fri, Mar 28, 2014 at 11:47 PM, rdv0...@gmail.com wrote: пятница, 28 марта 2014 г., 11:41:49 UTC+2 пользователь Ivan Kozic написал: Hi, You haven't given much info about this - take care with Cubieboard 1 2 - as far as I can remember they don't have PIXCLK routed for CSI0 port, so it's completely unusable. You should use CSI1. Regarding the seg fault - not sure how you connected the power supplies to the sensor, but these regulator_enable are for AXP IC - if you connected the sensor to the AXP, you need to use them I guess. I for instance have just connected the sensor supply to fixed LDO's coming from either 3V3 or 5V, which is always alive, so I don't really need them, but nevertheless they aren't commented out in my driver (WiP, so still dirty) and they are working, so maybe the culprit is something else. You didn't say which test application or given any snippets, but if it's the one coming with the driver (app_test_ok or something similar), by Rockie Cheng (this name always amuses me :) ), then it's full of bugs and issues and you should carefully go through every step and clean the crap code out (a lot of it is crap). Better yet, write a much simpler V4L2 test app yourself. Things that also pop is the old kernel (I'm using 3.4.75 and this is already like couple of months old) and this Linaro rootfs (don't know about this - is it fully supported on Cubies?). You should probably use newer kernel just to be sure that something stupid is not breaking. Also take care with drivers - the one for OV5640 is very badly written and full of bugs and I don't think that the supplied sensor settings are usable for anyone (they are all like 3.75 and 7.5 fps, most of them just wrong). Also sun4i_csi driver is bad (you can read some of the issues on this thread, but there are other threads as well). So mostly for a functional system all this needs to be cleaned and rewritten. On Thursday, March 27, 2014 11:54:08 PM UTC+1, rdv...@gmail.com wrote:Hello guys, I want to get camera module mt9d112 working on cubieboard a10 over CSI. I am using ubuntu linaro with kernel version 3.4.61. Test application crashes with seg fault on (regulator_enable+0x4/0x1f8) from [bf010138] (sensor_power+0x190/0x398 [mt9d112]). Could you please help me to figure out where the issue is? How can I debug kernel module? You are right for testing I using app_test_ok. This test application is full of mistakes but for now I did not even successfuly initialized camera module. I have connected VCC of camera module to CSI1_IO_2V8 pin on the board and other pins to the rest of CSI ports. The CSI1_IO_2V8 is actually LDO4 of AXP20 and I finally found in AllWinner documentation that string axp_hdmi should be used in script.fex instead of axp_p11 as described in tutorial. By the way the tutorial from cubieboard is full of such mistakes. So, when I change settings string to axp_hdmi I get new portion of errors: [ 383.721765] [CSI]Welcome to CSI driver [ 383.723657] [CSI]csi_init [ 383.934525] [CSI]registered sub device,input_num = 0 [ 383.939747] axp20_ldo4: Failed to create debugfs directory [ 384.003476] [CSI]V4L2 device registered as video1 [ 385.171443] incomplete xfer (0x20) [ 385.176430] [CSI_ERR][MT9D112]Error -70 on register write [ 385.181925] [CSI_ERR][MT9D112]sensor_read err at sensor_detect! [ 385.194199] [CSI_ERR][MT9D112]chip found is not an target chip. [ 385.199069] [CSI_ERR]sensor initial error when csi open! As I understand these error means that I2C communication is failed. The I2C address might by incorrect. But what is incomplete xfer (0x20) ? -- You received this message because you are subscribed to a
Re: [linux-sunxi] Re: A20 + OV5640 (parallel) issues
пятница, 28 марта 2014 г., 11:41:49 UTC+2 пользователь Ivan Kozic написал: Hi, You haven't given much info about this - take care with Cubieboard 1 2 - as far as I can remember they don't have PIXCLK routed for CSI0 port, so it's completely unusable. You should use CSI1. Regarding the seg fault - not sure how you connected the power supplies to the sensor, but these regulator_enable are for AXP IC - if you connected the sensor to the AXP, you need to use them I guess. I for instance have just connected the sensor supply to fixed LDO's coming from either 3V3 or 5V, which is always alive, so I don't really need them, but nevertheless they aren't commented out in my driver (WiP, so still dirty) and they are working, so maybe the culprit is something else. You didn't say which test application or given any snippets, but if it's the one coming with the driver (app_test_ok or something similar), by Rockie Cheng (this name always amuses me :) ), then it's full of bugs and issues and you should carefully go through every step and clean the crap code out (a lot of it is crap). Better yet, write a much simpler V4L2 test app yourself. Things that also pop is the old kernel (I'm using 3.4.75 and this is already like couple of months old) and this Linaro rootfs (don't know about this - is it fully supported on Cubies?). You should probably use newer kernel just to be sure that something stupid is not breaking. Also take care with drivers - the one for OV5640 is very badly written and full of bugs and I don't think that the supplied sensor settings are usable for anyone (they are all like 3.75 and 7.5 fps, most of them just wrong). Also sun4i_csi driver is bad (you can read some of the issues on this thread, but there are other threads as well). So mostly for a functional system all this needs to be cleaned and rewritten. On Thursday, March 27, 2014 11:54:08 PM UTC+1, rdv...@gmail.com wrote:Hello guys, I want to get camera module mt9d112 working on cubieboard a10 over CSI. I am using ubuntu linaro with kernel version 3.4.61. Test application crashes with seg fault on (regulator_enable+0x4/0x1f8) from [bf010138] (sensor_power+0x190/0x398 [mt9d112]). Could you please help me to figure out where the issue is? How can I debug kernel module? You are right for testing I using app_test_ok. This test application is full of mistakes but for now I did not even successfuly initialized camera module. I have connected VCC of camera module to CSI1_IO_2V8 pin on the board and other pins to the rest of CSI ports. The CSI1_IO_2V8 is actually LDO4 of AXP20 and I finally found in AllWinner documentation that string axp_hdmi should be used in script.fex instead of axp_p11 as described in tutorial. By the way the tutorial from cubieboard is full of such mistakes. So, when I change settings string to axp_hdmi I get new portion of errors: [ 383.721765] [CSI]Welcome to CSI driver [ 383.723657] [CSI]csi_init [ 383.934525] [CSI]registered sub device,input_num = 0 [ 383.939747] axp20_ldo4: Failed to create debugfs directory [ 384.003476] [CSI]V4L2 device registered as video1 [ 385.171443] incomplete xfer (0x20) [ 385.176430] [CSI_ERR][MT9D112]Error -70 on register write [ 385.181925] [CSI_ERR][MT9D112]sensor_read err at sensor_detect! [ 385.194199] [CSI_ERR][MT9D112]chip found is not an target chip. [ 385.199069] [CSI_ERR]sensor initial error when csi open! As I understand these error means that I2C communication is failed. The I2C address might by incorrect. But what is incomplete xfer (0x20) ? -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [linux-sunxi] Re: A20 + OV5640 (parallel) issues
Hello guys, I want to get camera module mt9d112 working on cubieboard a10 over CSI. I am using ubuntu linaro with kernel version 3.4.61. Test application crashes with seg fault on (regulator_enable+0x4/0x1f8) from [bf010138] (sensor_power+0x190/0x398 [mt9d112]). Could you please help me to figure out where the issue is? How can I debug kernel module? -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [linux-sunxi] Re: A20 + OV5640 (parallel) issues
I saw it - it's an interesting driver. Not sure if it's possible to use it on our boards, as it seems to be linked to V4L2 differently. -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [linux-sunxi] Re: A20 + OV5640 (parallel) issues
Hi John, Yeah, that's what I've figured. Are you sure you're using this support library right? Would be much simpler with a snippet of how you use V4L2 in your user app... -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [linux-sunxi] Re: A20 + OV5640 (parallel) issues
Hmm, I think what you've sent is not an app, but a support file for V4L. Either way, I can tell what the issue is: So, V4L2CameraDevice::captureThread is probably called somehow before V4L2CameraDevice::startDevice in the main app. startDevice needs to be called first and initialize the V4L buffers - from what I see in the current A20 driver - you only need to do S_FMT followed by QUERYBUF and then QBUF ioctls. This is a bit dirty, but quick and should work. When V4L2CameraDevice::captureThread is started it basically checks whether the buffer is ready to be dequeued with v4l2WaitCameraReady, and then tries to dequeue a buffer with getPreviewFrame, and fails. Something in this pipeline is not correct. I cannot look more into the code now, but it's quite strange how select() in v4l2WaitCameraReady() passes and then yet DQBUF fails. This is a bit puzzling for me. Please take a look at the following file: https://github.com/allwinner-ics/lichee_linux-3.0/blob/master/drivers/media/video/sun4i_csi/test/app_test_ok.c It has the correct way of how you should use the OV5640 driver - S_FMT, QUERYBUF and QBUF are done in main_test() - you also have a loop there which calls read_frame(), where DQBUF is performed. Check the way V4L is used in this app against your app - I'm pretty sure you have an error somewhere. Regarding the AML8726 kernel - I don't know where you've found ov5640 driver, but I cannot find it in the tar archive. -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [linux-sunxi] Re: A20 + OV5640 (parallel) issues
Hmm, I understand the errors that you've posted, but am not really sure what I'm looking at regarding the faults, as I have no experience with Android. Regarding errors - your buffers are not properly dequeued - maybe they are not ready and you're trying to dequeue them? How do you use V4L? Do you set the ioctl's or is it done somehow under-the-hood in Android? I'm asking because in Linux it's quite easy - you queue a buffer and then wait until it's ready for dequeue. Only then you can dequeue it, not before. And you do everything with V4L ioctl's and display driver ioctls. Basically you have full control of V4L and Display - how is this done in Android - can you post some code of your app? -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [linux-sunxi] Re: A20 + OV5640 (parallel) issues
Hi Jon, Good to have someone to talk to :) I've already previously found your posts about EU3000 - I even downloaded the Fex file to check mine some time ago, so I'm a bit into the subject. I don't have any Android experience except for my phone, so I can't help you much there, but I can tell you what's currently wrong with the sunxi linux driver for ov5640. For me, anything less than 720p is unacceptable. My first problem was that I get like 7fps in 720p (kernel 3.4.75+ from linux-sunxi) - this was driver issue, as the ov5640 driver (part of sun4i_csix driver) is badly written - there is only a tryout of the format, the sensor actually defaults always to sensor_default_regs[], instead of using regs for, let's say, 720p. So it isn't at all configured correctly. This is only the first problem. The second problem is that register settings included in the kernel driver are mostly useless - almost all of them are either 3.75, 7.5 or 15fps, while I need at least 30. So, since I did some development on Freescale's i.MX6, I used some settings from there - I've got 720p @30fps running like this. It works ok, maybe a bit noisey (although this could easily come from my interface board), but my colors are still bad and as you can see I'm currently debugging this (almost certain that it's the display driver issue). Anyway, I'm debugging the display driver - it seems that some things are wrong there, or at least I'm not really configuring it right. What kernel do you have - in which mode are you using 720p (15fps, 30fps?) and what are the errors you see? BR, Ivan -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[linux-sunxi] Re: A20 + OV5640 (parallel) issues
Hi all, One more bump, as I got into it much deeper. It seems that V4L2 is basically more-less functional - the sensor works, albeit with only one set of settings (ov5640.c is quite badly written). Either way, V4L should be good enough with some light code modifications to the OV5640 driver. Display however is another topic. The driver's code is fairly similar to the V4L concept, but with a bit more loose ends - I could not find any documents on how this API is specifically used, so I cannot verify whether the application that I am using (test app for camera) is using display driver in the correct manner. It basically revolves around V4L - when a buffer is dequeued, it's address is forwarded to display driver which initializes the framebuffer and refreshes the display with new content. But there are many ioctl's for display and I am unsure of how to use them properly. Since the color channels are wrong for this default configuration coming from the driver, I am starting to doubt whether it is the proper way to initialize the display. But, as the display API is not documented, I am left with either digging deep in kernel or just plain trial-and-error principle. Basically, as I have figured out V4L almost completely, I would need someone with more knowledge about this Sunxi display driver to continue. Of course, I will continue to dig and tryout different approaches, but it would mean a lot if someone could help. BR, Ivan -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[linux-sunxi] Re: A20 + OV5640 (parallel) issues
Hi all, Ok, I'll bump the post with my own findings, as I see several views but no replies. So, basically, there's something wrong going on in DEFE/DEBE - there is a bit of mess in the drivers (drivers/video/sunxi/disp), so I cannot really say what is causing the issue, but the culprit is that IN_FMT and OUT_FMT registers of DEFE are always initialized to RGB888, instead of YUV. I'm yet to find how to configure the display driver in order for these settings to be in effect, but the abstraction is very high (too many things going on from sunxi display driver up to the V4L structure) and I cannot really find out where exactly DEFE is configured (if at all configured), hence I'll need some time. I'll post back when I find something, but in the meantime all help is welcome. BR, Ivan -- You received this message because you are subscribed to the Google Groups linux-sunxi group. To unsubscribe from this group and stop receiving emails from it, send an email to linux-sunxi+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
