e-cam32, problem during insmod

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

e-cam32, problem during insmod

dani.anto
This post was updated on .
Hi all,
   i'm actually workin' on a Gumstix Overo Air board, with e-cam32 camera.
Following the manual they give me, I have a problem during the insmod operation.
I try both on a 2.6.36 Linux version and on a 2.6.34 with the same results.

These are the environment variables:

bootcmd=if mmc init; then if run loadbootscript; then run bootscript; else if run loaduimage; then run mmcboot; else run nandboot; fi; fi; else run nandboot; fi
bootdelay=5
baudrate=115200
loadaddr=0x82000000
console=ttyS2,115200n8
mpurate=500
vram=12M
dvimode=1024x768MR-16@60
defaultdisplay=dvi
mmcroot=/dev/mmcblk0p2 rw
mmcrootfstype=ext3 rootwait
nandroot=/dev/mtdblock4 rw
nandrootfstype=jffs2
nandargs=setenv bootargs console=${console} mpurate=${mpurate} vram=${vram} omapfb.mode=dvi:${dvimode} omapfb.debug=y omapdss.def_disp=${defaultdisplay} root=${nandroot} rootfstype=${nandrootfstype}
loadbootscript=fatload mmc 0 ${loadaddr} boot.scr
bootscript=echo Running bootscript from mmc ...; source ${loadaddr}
loaduimage=fatload mmc 0 ${loadaddr} uImage
mmcboot=echo Booting from mmc ...; run mmcargs; bootm ${loadaddr}
nandboot=echo Booting from nand ...; run nandargs; nand read ${loadaddr} 280000 400000; bootm ${loadaddr}
dieid#=3a3600020000000004031c130100d01b
mmcargs=setenv bootargs mem=93M@0x80000000 mem=128M@0x88000000 console=ttyS2,115200n8 vram=12M omapfb.mode=dvi:1024x768MR-16@60 omapfb.debug=y omapdss.def_disp=dvi root=/dev/mmcblk0p2 rw rootfstype=ext3 rootwait
stdin=serial
stdout=serial
stderr=serial



After having setted the environment variable in u-boot, I reboot the board, log as root and then I find where the FAT partition is (with fdisk -l): /dev/mmcblk0p1
So, always following the manual:

root@overo:#mount -t vfat /dev/mmcblk0p1 /mnt
root@overo:#cd /mnt
root@overo:/mnt# insmod /home/root/v4l2_driver.ko sens_max_pclk=33000000                                            
Driver Module info : V4l2 driver module                                                                            
Version info : 6.1 Build Time stamp: Fri Feb 11 08:22:00 2011                                                      
                                                                                                                   
Memory overlap detected between camera reserved memory and kernel memory                                            
phy_addr_start  0x85d00000                                                                                          
phy_addr_end    0x862fffff                                                                                          
phys_end_kernel 0x8dd00000                                                                                          
                                                                                                                   
Using Reserved memory for V4l2 driver module                                                                        
From Start address - 0x85d00000                                                                                    
To End address - 0x862fffff                                                                                        
insmod: error inserting '/home/root/v4l2_driver.ko': -1 Operation not permitted

Someone knows where is the problem??
I have already controlled the cable connectivity and it's ok!
Someone also know where I can find a schematic of the camera pin? (just in the happy hypotesis that it will work)

Thanks all,
Daniele
Reply | Threaded
Open this post in threaded view
|

Re: e-cam32, problem during insmod

dani.anto
I also tried to add "i2c_bus=3,100" to the bootarg arguments but it nothing different happened
Reply | Threaded
Open this post in threaded view
|

Re: e-cam32, problem during insmod

Steven
if you type dmesg it'll give you a more informative error message.

Also, did you apply the kernel patches properly?  That's the error i usually get when I forget to do that.

On Mon, May 9, 2011 at 10:55 AM, dani.anto <[hidden email]> wrote:

I also tried to add "i2c_bus=3,100" to the bootarg arguments but it nothing
different happened
--
View this message in context: http://old.nabble.com/e-cam32%2C-problem-during-insmod-tp31575571p31577500.html
Sent from the Gumstix mailing list archive at Nabble.com.


------------------------------------------------------------------------------
WhatsUp Gold - Download Free Network Management Software
The most intuitive, comprehensive, and cost-effective network
management toolset available today.  Delivers lowest initial
acquisition cost and overall TCO of any competing solution.
http://p.sf.net/sfu/whatsupgold-sd
_______________________________________________
gumstix-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gumstix-users


------------------------------------------------------------------------------
WhatsUp Gold - Download Free Network Management Software
The most intuitive, comprehensive, and cost-effective network
management toolset available today.  Delivers lowest initial
acquisition cost and overall TCO of any competing solution.
http://p.sf.net/sfu/whatsupgold-sd
_______________________________________________
gumstix-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/gumstix-users
Reply | Threaded
Open this post in threaded view
|

Re: e-cam32, problem during insmod

dani.anto
This post was updated on .
In reply to this post by dani.anto
We have found the problem: we was using an Overo Air with e-cam32 on a Palo43 board. Substituting this one with a Summit Board we have solved the problem. Insmod install the driver and the camera is able to snap photo and record video.

We think that the problem is releated with the possibility of connect an LCD screen on Palo43 (feature that Summit doesn't have).