From: Saravanakrishnan <kri...@gm...> - 2011-05-09 22:59:42
|
Hi, I am trying to interface CaspaVL to overo chestnut board (overo water) running android gingerbread with linux kernel 2.6.32.. I followed the wiki, http://wiki.gumstix.org/index.php?title=Caspa_camera_boards to patch the kernel. When I tried to build after patching, it throws up this error CC arch/arm/mach-omap2/board- overo.o LD arch/arm/mach-omap2/built-in.o LD vmlinux.o MODPOST vmlinux.o GEN .version CHK include/linux/compile.h UPD include/linux/compile.h CC init/version.o LD init/built-in.o LD .tmp_vmlinux1 arch/arm/mach-omap2/built-in.o: In function `mt9v032_sensor_set_xclk': /home/crawford/android/kernel/arch/arm/mach-omap2/board-overo.c:775: undefined reference to `isp_set_xclk' arch/arm/mach-omap2/built-in.o: In function `mt9v032_sensor_set_power': /home/crawford/android/kernel/arch/arm/mach-omap2/board-overo.c:762: undefined reference to `isp_configure_interface' make: *** [.tmp_vmlinux1] Error 1 The two functions are declared in isp.h and the include file is referenced in board-overo.c. I don't know why it is still showing this error. Am I missing something? Any help would be appreciated. Thanks, Krishnan. |
From: Saravanakrishnan <kri...@gm...> - 2011-05-11 22:33:52
|
Hi, I am trying to interface CaspaVL to overo chestnut board (overo water) running android gingerbread(2.3.2) with linux kernel 2.6.32.. I followed the wiki, http://wiki.gumstix.org/index.php?title=Caspa_camera_boards to patch the kernel and it built successfully. Should I have to build any module (mt9v032.ko as specified in the wiki) to use this camera? Or the kernel has already added support for the camera? My Kconfig file looks like this, config SOC_CAMERA_MT9V032 tristate "mt9v032 support" depends on VIDEO_V4L2 && SOC_CAMERA && I2C help This driver supports MT9V032 cameras from Micron So if I enable v4l2 support in kernel, will this camera work? I am not quite aware of Kconfig files. Any help would be appreciated. Thanks, Krishnan. Because, if I try to run make modules in android, it is giving me some errors. Thanks, Krishnan. -- View this message in context: http://old.nabble.com/CaspaVL-for-android-tp31598607p31598607.html Sent from the Gumstix mailing list archive at Nabble.com. |
From: Ash C. <as...@gu...> - 2011-05-11 22:50:38
|
Hi Krishnan, The Android build is actually based off TI 2.6.32 kernel which should already include the isp driver code required for the caspa sensor. The only changes necessary should be adding the capsa i2c declaration to the board-overo.c file and adding the mt0v32.c driver itself (along with any necessary header/Kconfig changes). Maybe there are some changes in 2.6.34 causing the breakage? Prior to releasing Capsa, I actually tried out the sensor with an Android build I had (making the fixes as above) and, once I tweaked the permissions on /dev/video0, it actually came up just fine. -Ash On Tue, May 10, 2011 at 12:59 AM, Saravanakrishnan <kri...@gm...> wrote: > Hi, > > I am trying to interface CaspaVL to overo chestnut board (overo water) > running android gingerbread with linux kernel 2.6.32.. I followed the wiki, > http://wiki.gumstix.org/index.php?title=Caspa_camera_boards to patch the > kernel. When I tried to build after patching, it throws up this error > > CC arch/arm/mach-omap2/board- > overo.o > LD arch/arm/mach-omap2/built-in.o > LD vmlinux.o > MODPOST vmlinux.o > GEN .version > CHK include/linux/compile.h > UPD include/linux/compile.h > CC init/version.o > LD init/built-in.o > LD .tmp_vmlinux1 > arch/arm/mach-omap2/built-in.o: In function `mt9v032_sensor_set_xclk': > /home/crawford/android/kernel/arch/arm/mach-omap2/board-overo.c:775: > undefined reference to `isp_set_xclk' > arch/arm/mach-omap2/built-in.o: In function `mt9v032_sensor_set_power': > /home/crawford/android/kernel/arch/arm/mach-omap2/board-overo.c:762: > undefined reference to `isp_configure_interface' > make: *** [.tmp_vmlinux1] Error 1 > > The two functions are declared in isp.h and the include file is referenced > in board-overo.c. I don't know why it is still showing this error. Am I > missing something? Any help would be appreciated. > > Thanks, > Krishnan. > ------------------------------------------------------------------------------ > Achieve unprecedented app performance and reliability > What every C/C++ and Fortran developer should know. > Learn how Intel has extended the reach of its next-generation tools > to help boost performance applications - inlcuding clusters. > http://p.sf.net/sfu/intel-dev2devmay > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > |
From: Saravanakrishnan <kri...@gm...> - 2011-05-11 23:04:28
|
Hi Ash, Thanks for the reply.. Yes. I figured that out. As, you had mentioned, I modified board-overo.c, added mt9v032 driver files and made changes in Kconfig and Makefile. Hence, the kernel got built successfully. I just want to know whether the module gets built automatically. Will the camera be ready to use if I turn on the v4l, soc and i2c options in the kernel as specified in Kconfig? I don't have the board with me to test whether it is working or not. I will probably get in another 2 days. Thanks, Krishnan. On Wed, May 11, 2011 at 3:50 PM, Ash Charles <as...@gu...> wrote: > Hi Krishnan, > > The Android build is actually based off TI 2.6.32 kernel which should > already include the isp driver code required for the caspa sensor. > The only changes necessary should be adding the capsa i2c declaration > to the board-overo.c file and adding the mt0v32.c driver itself (along > with any necessary header/Kconfig changes). Maybe there are some > changes in 2.6.34 causing the breakage? > > Prior to releasing Capsa, I actually tried out the sensor with an > Android build I had (making the fixes as above) and, once I tweaked > the permissions on /dev/video0, it actually came up just fine. > > -Ash > > On Tue, May 10, 2011 at 12:59 AM, Saravanakrishnan > <kri...@gm...> wrote: > > Hi, > > > > I am trying to interface CaspaVL to overo chestnut board (overo water) > > running android gingerbread with linux kernel 2.6.32.. I followed the > wiki, > > http://wiki.gumstix.org/index.php?title=Caspa_camera_boards to patch the > > kernel. When I tried to build after patching, it throws up this error > > > > CC arch/arm/mach-omap2/board- > > overo.o > > LD arch/arm/mach-omap2/built-in.o > > LD vmlinux.o > > MODPOST vmlinux.o > > GEN .version > > CHK include/linux/compile.h > > UPD include/linux/compile.h > > CC init/version.o > > LD init/built-in.o > > LD .tmp_vmlinux1 > > arch/arm/mach-omap2/built-in.o: In function `mt9v032_sensor_set_xclk': > > /home/crawford/android/kernel/arch/arm/mach-omap2/board-overo.c:775: > > undefined reference to `isp_set_xclk' > > arch/arm/mach-omap2/built-in.o: In function `mt9v032_sensor_set_power': > > /home/crawford/android/kernel/arch/arm/mach-omap2/board-overo.c:762: > > undefined reference to `isp_configure_interface' > > make: *** [.tmp_vmlinux1] Error 1 > > > > The two functions are declared in isp.h and the include file is > referenced > > in board-overo.c. I don't know why it is still showing this error. Am I > > missing something? Any help would be appreciated. > > > > Thanks, > > Krishnan. > > > ------------------------------------------------------------------------------ > > Achieve unprecedented app performance and reliability > > What every C/C++ and Fortran developer should know. > > Learn how Intel has extended the reach of its next-generation tools > > to help boost performance applications - inlcuding clusters. > > http://p.sf.net/sfu/intel-dev2devmay > > _______________________________________________ > > gumstix-users mailing list > > gum...@li... > > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > > > > > > ------------------------------------------------------------------------------ > Achieve unprecedented app performance and reliability > What every C/C++ and Fortran developer should know. > Learn how Intel has extended the reach of its next-generation tools > to help boost performance applications - inlcuding clusters. > http://p.sf.net/sfu/intel-dev2devmay > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: Ash C. <as...@gu...> - 2011-05-11 23:13:09
|
I'm not guaranteeing anything but that sounds about right ;-). I remember having to change permission on the /dev/video0 device node to get it to work in Android too. -ash On Thu, May 12, 2011 at 1:03 AM, Saravanakrishnan <kri...@gm...> wrote: > Hi Ash, > > Thanks for the reply.. Yes. I figured that out. As, you had mentioned, I > modified board-overo.c, added mt9v032 driver files and made changes in > Kconfig and Makefile. Hence, the kernel got built successfully. I just want > to know whether the module gets built automatically. Will the camera be > ready to use if I turn on the v4l, soc and i2c options in the kernel as > specified in Kconfig? I don't have the board with me to test whether it is > working or not. I will probably get in another 2 days. > > Thanks, > Krishnan. > > > > On Wed, May 11, 2011 at 3:50 PM, Ash Charles <as...@gu...> wrote: >> >> Hi Krishnan, >> >> The Android build is actually based off TI 2.6.32 kernel which should >> already include the isp driver code required for the caspa sensor. >> The only changes necessary should be adding the capsa i2c declaration >> to the board-overo.c file and adding the mt0v32.c driver itself (along >> with any necessary header/Kconfig changes). Maybe there are some >> changes in 2.6.34 causing the breakage? >> >> Prior to releasing Capsa, I actually tried out the sensor with an >> Android build I had (making the fixes as above) and, once I tweaked >> the permissions on /dev/video0, it actually came up just fine. >> >> -Ash >> >> On Tue, May 10, 2011 at 12:59 AM, Saravanakrishnan >> <kri...@gm...> wrote: >> > Hi, >> > >> > I am trying to interface CaspaVL to overo chestnut board (overo water) >> > running android gingerbread with linux kernel 2.6.32.. I followed the >> > wiki, >> > http://wiki.gumstix.org/index.php?title=Caspa_camera_boards to patch the >> > kernel. When I tried to build after patching, it throws up this error >> > >> > CC arch/arm/mach-omap2/board- >> > overo.o >> > LD arch/arm/mach-omap2/built-in.o >> > LD vmlinux.o >> > MODPOST vmlinux.o >> > GEN .version >> > CHK include/linux/compile.h >> > UPD include/linux/compile.h >> > CC init/version.o >> > LD init/built-in.o >> > LD .tmp_vmlinux1 >> > arch/arm/mach-omap2/built-in.o: In function `mt9v032_sensor_set_xclk': >> > /home/crawford/android/kernel/arch/arm/mach-omap2/board-overo.c:775: >> > undefined reference to `isp_set_xclk' >> > arch/arm/mach-omap2/built-in.o: In function `mt9v032_sensor_set_power': >> > /home/crawford/android/kernel/arch/arm/mach-omap2/board-overo.c:762: >> > undefined reference to `isp_configure_interface' >> > make: *** [.tmp_vmlinux1] Error 1 >> > >> > The two functions are declared in isp.h and the include file is >> > referenced >> > in board-overo.c. I don't know why it is still showing this error. Am I >> > missing something? Any help would be appreciated. >> > >> > Thanks, >> > Krishnan. >> > >> > ------------------------------------------------------------------------------ >> > Achieve unprecedented app performance and reliability >> > What every C/C++ and Fortran developer should know. >> > Learn how Intel has extended the reach of its next-generation tools >> > to help boost performance applications - inlcuding clusters. >> > http://p.sf.net/sfu/intel-dev2devmay >> > _______________________________________________ >> > gumstix-users mailing list >> > gum...@li... >> > https://lists.sourceforge.net/lists/listinfo/gumstix-users >> > >> > >> >> >> ------------------------------------------------------------------------------ >> Achieve unprecedented app performance and reliability >> What every C/C++ and Fortran developer should know. >> Learn how Intel has extended the reach of its next-generation tools >> to help boost performance applications - inlcuding clusters. >> http://p.sf.net/sfu/intel-dev2devmay >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users > > > ------------------------------------------------------------------------------ > Achieve unprecedented app performance and reliability > What every C/C++ and Fortran developer should know. > Learn how Intel has extended the reach of its next-generation tools > to help boost performance applications - inlcuding clusters. > http://p.sf.net/sfu/intel-dev2devmay > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > |
From: Saravanakrishnan <kri...@gm...> - 2011-05-11 23:28:49
|
Okay. Thanks. I hope it works! Btw, could you tell me which software you used to capture the camera. I guess the default camera app in android is not going to work unless we give some permissions. I have integrated gstreamer in android and when I tried running the pipeline, gst-launch -v v4l2src ! surfaceflingersink it gave me, ERROR: pipeline could not be constructed: no element "v4l2src". I guess there is some problem with gstreamer libraries and I will probably check with gstreamer guys. Did you write your own camera interface program? Thanks, Krishnan. On Wed, May 11, 2011 at 4:12 PM, Ash Charles <as...@gu...> wrote: > I'm not guaranteeing anything but that sounds about right ;-). > > I remember having to change permission on the /dev/video0 device node > to get it to work in Android too. > -ash > > On Thu, May 12, 2011 at 1:03 AM, Saravanakrishnan > <kri...@gm...> wrote: > > Hi Ash, > > > > Thanks for the reply.. Yes. I figured that out. As, you had mentioned, I > > modified board-overo.c, added mt9v032 driver files and made changes in > > Kconfig and Makefile. Hence, the kernel got built successfully. I just > want > > to know whether the module gets built automatically. Will the camera be > > ready to use if I turn on the v4l, soc and i2c options in the kernel as > > specified in Kconfig? I don't have the board with me to test whether it > is > > working or not. I will probably get in another 2 days. > > > > Thanks, > > Krishnan. > > > > > > > > On Wed, May 11, 2011 at 3:50 PM, Ash Charles <as...@gu...> wrote: > >> > >> Hi Krishnan, > >> > >> The Android build is actually based off TI 2.6.32 kernel which should > >> already include the isp driver code required for the caspa sensor. > >> The only changes necessary should be adding the capsa i2c declaration > >> to the board-overo.c file and adding the mt0v32.c driver itself (along > >> with any necessary header/Kconfig changes). Maybe there are some > >> changes in 2.6.34 causing the breakage? > >> > >> Prior to releasing Capsa, I actually tried out the sensor with an > >> Android build I had (making the fixes as above) and, once I tweaked > >> the permissions on /dev/video0, it actually came up just fine. > >> > >> -Ash > >> > >> On Tue, May 10, 2011 at 12:59 AM, Saravanakrishnan > >> <kri...@gm...> wrote: > >> > Hi, > >> > > >> > I am trying to interface CaspaVL to overo chestnut board (overo water) > >> > running android gingerbread with linux kernel 2.6.32.. I followed the > >> > wiki, > >> > http://wiki.gumstix.org/index.php?title=Caspa_camera_boards to patch > the > >> > kernel. When I tried to build after patching, it throws up this error > >> > > >> > CC arch/arm/mach-omap2/board- > >> > overo.o > >> > LD arch/arm/mach-omap2/built-in.o > >> > LD vmlinux.o > >> > MODPOST vmlinux.o > >> > GEN .version > >> > CHK include/linux/compile.h > >> > UPD include/linux/compile.h > >> > CC init/version.o > >> > LD init/built-in.o > >> > LD .tmp_vmlinux1 > >> > arch/arm/mach-omap2/built-in.o: In function `mt9v032_sensor_set_xclk': > >> > /home/crawford/android/kernel/arch/arm/mach-omap2/board-overo.c:775: > >> > undefined reference to `isp_set_xclk' > >> > arch/arm/mach-omap2/built-in.o: In function > `mt9v032_sensor_set_power': > >> > /home/crawford/android/kernel/arch/arm/mach-omap2/board-overo.c:762: > >> > undefined reference to `isp_configure_interface' > >> > make: *** [.tmp_vmlinux1] Error 1 > >> > > >> > The two functions are declared in isp.h and the include file is > >> > referenced > >> > in board-overo.c. I don't know why it is still showing this error. Am > I > >> > missing something? Any help would be appreciated. > >> > > >> > Thanks, > >> > Krishnan. > >> > > >> > > ------------------------------------------------------------------------------ > >> > Achieve unprecedented app performance and reliability > >> > What every C/C++ and Fortran developer should know. > >> > Learn how Intel has extended the reach of its next-generation tools > >> > to help boost performance applications - inlcuding clusters. > >> > http://p.sf.net/sfu/intel-dev2devmay > >> > _______________________________________________ > >> > gumstix-users mailing list > >> > gum...@li... > >> > https://lists.sourceforge.net/lists/listinfo/gumstix-users > >> > > >> > > >> > >> > >> > ------------------------------------------------------------------------------ > >> Achieve unprecedented app performance and reliability > >> What every C/C++ and Fortran developer should know. > >> Learn how Intel has extended the reach of its next-generation tools > >> to help boost performance applications - inlcuding clusters. > >> http://p.sf.net/sfu/intel-dev2devmay > >> _______________________________________________ > >> gumstix-users mailing list > >> gum...@li... > >> https://lists.sourceforge.net/lists/listinfo/gumstix-users > > > > > > > ------------------------------------------------------------------------------ > > Achieve unprecedented app performance and reliability > > What every C/C++ and Fortran developer should know. > > Learn how Intel has extended the reach of its next-generation tools > > to help boost performance applications - inlcuding clusters. > > http://p.sf.net/sfu/intel-dev2devmay > > _______________________________________________ > > gumstix-users mailing list > > gum...@li... > > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > > > > > > ------------------------------------------------------------------------------ > Achieve unprecedented app performance and reliability > What every C/C++ and Fortran developer should know. > Learn how Intel has extended the reach of its next-generation tools > to help boost performance applications - inlcuding clusters. > http://p.sf.net/sfu/intel-dev2devmay > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: Ash C. <ash...@gm...> - 2011-05-12 07:10:54
|
Hi Krishnan, On Thu, May 12, 2011 at 1:28 AM, Saravanakrishnan <kri...@gm...> wrote: > Btw, could you tell me which software you used to capture the camera I just did the quick smoke test with the default camera app (on froyo). -ash |
From: Saravanakrishnan <kri...@gm...> - 2011-05-12 23:54:03
|
Hi Ash, I got the board today and tried to interface the CaspaVL camera after configuring the kernel. But, I ended up facing this problem i2c /dev entries driver Linux video capture interface: v2.00 mt9v032 3-005c: color sensor mt9v032 3-005c: hflip=0 vflip=0 auto_gain=1 auto_exp=1 hdr=1 low_light=0 omap-iommu omap-iommu.0: isp: version 1.1 ........................... ........................ mt9v032 3-005c: unable to detect mt9v032 sensor mt9v032 3-005c: unable to detect mt9v032 sensor mt9v032 3-005c: unable to detect mt9v032 sensor mt9v032 3-005c: unable to detect mt9v032 sensor omap_vout omap_vout: probed for an unknown device I tried modifying the board-overo.c to i2c_bus=*3*,100 (as mentioned in http://old.nabble.com/Caspa-camera-expansion-td31046776.html), but it didn't work either. Do you have any suggestions? Thanks, Krishnan. On Thu, May 12, 2011 at 12:10 AM, Ash Charles <ash...@gm...> wrote: > Hi Krishnan, > > On Thu, May 12, 2011 at 1:28 AM, Saravanakrishnan > <kri...@gm...> wrote: > > Btw, could you tell me which software you used to capture the camera > > I just did the quick smoke test with the default camera app (on froyo). > -ash > > > ------------------------------------------------------------------------------ > Achieve unprecedented app performance and reliability > What every C/C++ and Fortran developer should know. > Learn how Intel has extended the reach of its next-generation tools > to help boost performance applications - inlcuding clusters. > http://p.sf.net/sfu/intel-dev2devmay > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: Ash C. <ash...@gm...> - 2011-05-13 05:58:31
|
Hi Krisnan, Does the camera device work with the kernel and modules given on the Caspa wiki page ( http://wiki.gumstix.org/index.php?title=Caspa_camera_boards )? Also, make sure the camera is attached properly---the cables can be a bit of a pain to correctly align. -Ash On Fri, May 13, 2011 at 1:53 AM, Saravanakrishnan <kri...@gm...> wrote: > Hi Ash, > > I got the board today and tried to interface the CaspaVL camera after > configuring the kernel. But, I ended up facing this problem > > i2c /dev entries driver > Linux video capture interface: v2.00 > mt9v032 3-005c: color sensor > mt9v032 3-005c: hflip=0 vflip=0 auto_gain=1 auto_exp=1 hdr=1 low_light=0 > omap-iommu omap-iommu.0: isp: version 1.1 > ........................... > ........................ > mt9v032 3-005c: unable to detect mt9v032 sensor > mt9v032 3-005c: unable to detect mt9v032 sensor > mt9v032 3-005c: unable to detect mt9v032 sensor > mt9v032 3-005c: unable to detect mt9v032 sensor > omap_vout omap_vout: probed for an unknown device > > > I tried modifying the board-overo.c to i2c_bus=3,100 (as mentioned in > http://old.nabble.com/Caspa-camera-expansion-td31046776.html), but it didn't > work either. Do you have any suggestions? > > Thanks, > Krishnan. > > On Thu, May 12, 2011 at 12:10 AM, Ash Charles <ash...@gm...> wrote: >> >> Hi Krishnan, >> >> On Thu, May 12, 2011 at 1:28 AM, Saravanakrishnan >> <kri...@gm...> wrote: >> > Btw, could you tell me which software you used to capture the camera >> >> I just did the quick smoke test with the default camera app (on froyo). >> -ash >> >> >> ------------------------------------------------------------------------------ >> Achieve unprecedented app performance and reliability >> What every C/C++ and Fortran developer should know. >> Learn how Intel has extended the reach of its next-generation tools >> to help boost performance applications - inlcuding clusters. >> http://p.sf.net/sfu/intel-dev2devmay >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users > > > ------------------------------------------------------------------------------ > Achieve unprecedented app performance and reliability > What every C/C++ and Fortran developer should know. > Learn how Intel has extended the reach of its next-generation tools > to help boost performance applications - inlcuding clusters. > http://p.sf.net/sfu/intel-dev2devmay > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > |
From: Saravanakrishnan <kri...@gm...> - 2011-05-13 22:42:49
|
Hi Ash, I tried using the prebuilt image as you had suggested. I think the camera cable is the problem. Is the camera LED supposed to glow red to tell us that it got powered? The cable is very fragile and moreover I broke the flap :(.. I once noticed that the led turned red and I infact was able to see video0 after doing "modprobe mt9v032". But, after that my luck ran out. I have been fighting with this cable from morning!! I guess I have to order another camera.. Thanks, Krishnan. On Thu, May 12, 2011 at 10:58 PM, Ash Charles <ash...@gm...> wrote: > Hi Krisnan, > > Does the camera device work with the kernel and modules given on the > Caspa wiki page ( > http://wiki.gumstix.org/index.php?title=Caspa_camera_boards )? Also, > make sure the camera is attached properly---the cables can be a bit of > a pain to correctly align. > > -Ash > > On Fri, May 13, 2011 at 1:53 AM, Saravanakrishnan > <kri...@gm...> wrote: > > Hi Ash, > > > > I got the board today and tried to interface the CaspaVL camera after > > configuring the kernel. But, I ended up facing this problem > > > > i2c /dev entries driver > > Linux video capture interface: v2.00 > > mt9v032 3-005c: color sensor > > mt9v032 3-005c: hflip=0 vflip=0 auto_gain=1 auto_exp=1 hdr=1 low_light=0 > > omap-iommu omap-iommu.0: isp: version 1.1 > > ........................... > > ........................ > > mt9v032 3-005c: unable to detect mt9v032 sensor > > mt9v032 3-005c: unable to detect mt9v032 sensor > > mt9v032 3-005c: unable to detect mt9v032 sensor > > mt9v032 3-005c: unable to detect mt9v032 sensor > > omap_vout omap_vout: probed for an unknown device > > > > > > I tried modifying the board-overo.c to i2c_bus=3,100 (as mentioned in > > http://old.nabble.com/Caspa-camera-expansion-td31046776.html), but it > didn't > > work either. Do you have any suggestions? > > > > Thanks, > > Krishnan. > > > > On Thu, May 12, 2011 at 12:10 AM, Ash Charles <ash...@gm...> > wrote: > >> > >> Hi Krishnan, > >> > >> On Thu, May 12, 2011 at 1:28 AM, Saravanakrishnan > >> <kri...@gm...> wrote: > >> > Btw, could you tell me which software you used to capture the camera > >> > >> I just did the quick smoke test with the default camera app (on froyo). > >> -ash > >> > >> > >> > ------------------------------------------------------------------------------ > >> Achieve unprecedented app performance and reliability > >> What every C/C++ and Fortran developer should know. > >> Learn how Intel has extended the reach of its next-generation tools > >> to help boost performance applications - inlcuding clusters. > >> http://p.sf.net/sfu/intel-dev2devmay > >> _______________________________________________ > >> gumstix-users mailing list > >> gum...@li... > >> https://lists.sourceforge.net/lists/listinfo/gumstix-users > > > > > > > ------------------------------------------------------------------------------ > > Achieve unprecedented app performance and reliability > > What every C/C++ and Fortran developer should know. > > Learn how Intel has extended the reach of its next-generation tools > > to help boost performance applications - inlcuding clusters. > > http://p.sf.net/sfu/intel-dev2devmay > > _______________________________________________ > > gumstix-users mailing list > > gum...@li... > > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > > > > > > ------------------------------------------------------------------------------ > Achieve unprecedented app performance and reliability > What every C/C++ and Fortran developer should know. > Learn how Intel has extended the reach of its next-generation tools > to help boost performance applications - inlcuding clusters. > http://p.sf.net/sfu/intel-dev2devmay > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: Saravanakrishnan <kri...@gm...> - 2011-05-18 21:36:13
|
Hi Ash, I am working on another board right now. (ordered another CaspaVL camera ;( ) I got an analog camera to work using gstreamer for this board. I would like to open it using the camera app in android. I get the following error when I try to access the camera from the app, "Sorry. the application Camera(process com.andoid.camera) has stopped unexpectedly.Please try again." Between, you had mentioned that you need to change permission for /dev/video0. Do you mean chmod 777? I am not sure whether it is the permission problem since I could see in the command prompt that it is trying to access the camera.. # clock: Could not find divisor for target rate 0 for clock dpll4_m5_ck parent dpll4_ck omap3isp omap3isp: clk_set_rate for dpll4_m5_ck failed tvp514x 3-005c: tvp5146m2 found at 0xb8 (OMAP I2C adapter) Any ideas?? Thanks, Krishnan. On Fri, May 13, 2011 at 3:42 PM, Saravanakrishnan < kri...@gm...> wrote: > Hi Ash, > > I tried using the prebuilt image as you had suggested. I think the camera > cable is the problem. Is the camera LED supposed to glow red to tell us that > it got powered? The cable is very fragile and moreover I broke the flap :(.. > I once noticed that the led turned red and I infact was able to see video0 > after doing "modprobe mt9v032". But, after that my luck ran out. I have been > fighting with this cable from morning!! I guess I have to order another > camera.. > > Thanks, > Krishnan. > > > On Thu, May 12, 2011 at 10:58 PM, Ash Charles <ash...@gm...>wrote: > >> Hi Krisnan, >> >> Does the camera device work with the kernel and modules given on the >> Caspa wiki page ( >> http://wiki.gumstix.org/index.php?title=Caspa_camera_boards )? Also, >> make sure the camera is attached properly---the cables can be a bit of >> a pain to correctly align. >> >> -Ash >> >> On Fri, May 13, 2011 at 1:53 AM, Saravanakrishnan >> <kri...@gm...> wrote: >> > Hi Ash, >> > >> > I got the board today and tried to interface the CaspaVL camera after >> > configuring the kernel. But, I ended up facing this problem >> > >> > i2c /dev entries driver >> > Linux video capture interface: v2.00 >> > mt9v032 3-005c: color sensor >> > mt9v032 3-005c: hflip=0 vflip=0 auto_gain=1 auto_exp=1 hdr=1 low_light=0 >> > omap-iommu omap-iommu.0: isp: version 1.1 >> > ........................... >> > ........................ >> > mt9v032 3-005c: unable to detect mt9v032 sensor >> > mt9v032 3-005c: unable to detect mt9v032 sensor >> > mt9v032 3-005c: unable to detect mt9v032 sensor >> > mt9v032 3-005c: unable to detect mt9v032 sensor >> > omap_vout omap_vout: probed for an unknown device >> > >> > >> > I tried modifying the board-overo.c to i2c_bus=3,100 (as mentioned in >> > http://old.nabble.com/Caspa-camera-expansion-td31046776.html), but it >> didn't >> > work either. Do you have any suggestions? >> > >> > Thanks, >> > Krishnan. >> > >> > On Thu, May 12, 2011 at 12:10 AM, Ash Charles <ash...@gm...> >> wrote: >> >> >> >> Hi Krishnan, >> >> >> >> On Thu, May 12, 2011 at 1:28 AM, Saravanakrishnan >> >> <kri...@gm...> wrote: >> >> > Btw, could you tell me which software you used to capture the camera >> >> >> >> I just did the quick smoke test with the default camera app (on froyo). >> >> -ash >> >> >> >> >> >> >> ------------------------------------------------------------------------------ >> >> Achieve unprecedented app performance and reliability >> >> What every C/C++ and Fortran developer should know. >> >> Learn how Intel has extended the reach of its next-generation tools >> >> to help boost performance applications - inlcuding clusters. >> >> http://p.sf.net/sfu/intel-dev2devmay >> >> _______________________________________________ >> >> gumstix-users mailing list >> >> gum...@li... >> >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> > >> > >> > >> ------------------------------------------------------------------------------ >> > Achieve unprecedented app performance and reliability >> > What every C/C++ and Fortran developer should know. >> > Learn how Intel has extended the reach of its next-generation tools >> > to help boost performance applications - inlcuding clusters. >> > http://p.sf.net/sfu/intel-dev2devmay >> > _______________________________________________ >> > gumstix-users mailing list >> > gum...@li... >> > https://lists.sourceforge.net/lists/listinfo/gumstix-users >> > >> > >> >> >> ------------------------------------------------------------------------------ >> Achieve unprecedented app performance and reliability >> What every C/C++ and Fortran developer should know. >> Learn how Intel has extended the reach of its next-generation tools >> to help boost performance applications - inlcuding clusters. >> http://p.sf.net/sfu/intel-dev2devmay >> _______________________________________________ >> gumstix-users mailing list >> gum...@li... >> https://lists.sourceforge.net/lists/listinfo/gumstix-users >> > > |
From: Ash C. <ash...@gm...> - 2011-05-27 18:13:24
|
Hi, On Wed, May 18, 2011 at 2:35 PM, Saravanakrishnan <kri...@gm...> wrote: > "Sorry. the application Camera(process com.andoid.camera) has stopped > unexpectedly.Please try again." logcat/adb is probably the best tool for actually determining why the application is crashing. > > Between, you had mentioned that you need to change permission for > /dev/video0. Do you mean chmod 777? I am not sure whether it is the > permission problem since I could see in the command prompt that it is trying > to access the camera.. Yes, iirc, I did a chmod 777 on /dev/video0 (admittedly a dirty hack). Do you see messages in the boot log/dmesg showing the camera being initialized (e.g. something about mt9v032 and i2c)? -Ash |