In particular, I found it helpful to OPKG INSTALL kernel-module-mt9p031 and then insert the line camera=lbcm3m1 into the uEnv.txt file in the boot partition. However, the pictures were all VGA quality whereas the camera is 5M. I tried to use different names for the camera entry in uEnv.txt substituting 5 for 3but when I do that /dev/video0 disappears and the mtp3 entry in lsmod disappears also. How can I take full resolution pictures?
Second question is, how can I install the camera on Ubuntu version given above? I did the same things but got no results.
Thank you, Robert. Are you sure about the camera=lbcm5m1 parameter? The equivalent Angstrom parameter was camera=lbcm3m03 which only seems to provide VGA resolution. I have kernel 3.2.30-x15 but /dev/video0 is not shown and the driver is not listed in response to lsmod. If I want to use the camera with your newest kernel, then do I have to follow the steps descirbe in the previous post by mrne? I am not experienced in cross compiling and all that.
Ahmet
8 Ekim 2012 Pazartesi 15:44:05 UTC+3 tarihinde RobertCNelson yazdı:
Although, i'm tempted to change it to something like "camera=li5m03"
as that is what is actually written on this module... (of course i'll
also patching u-boot to pass the parameter so you could just do
"camera=${camera}" and it'll be taken care of..)
equivalent Angstrom parameter was camera=lbcm3m03 which only seems to
provide VGA resolution.
Sorry, I never looked at the angstrom patchset, for these cameras...
I have kernel 3.2.30-x15 but /dev/video0 is not
shown and the driver is not listed in response to lsmod. If I want to use
What do:
dmesg | grep -i beagle
dmesg | grep -i isp
return?
the camera with your newest kernel, then do I have to follow the steps
descirbe in the previous post by mrne? I am not experienced in cross
compiling and all that.
No, there is no reason to rebuild, as after getting it to work, i
tagged a release and pushed it out..
So it is up to the patch writer to decide what the camera= parameter should say. I didn’t know, I thought it might be in the manufacturer’s device driver. What are the camera regulators? My camera is physically powered on as the green light comes on regardless.
The label on the seller’s package was ‘LI-LBCM5M1’. By silkscreen, do you mean the power-up messages dislpayed by dmesg? I couldn’t find the word Leopard in it.
I discovered that I had changed the camera parameter in uEnv.txt to something to experiment with alternatives. I have now corrected it as shown below. The responses to the grep commands look very similar. The O/S is definitely the one you recommended. I downloaded five files from the directory and ran the shell on BB to install.
The label on the seller's package was 'LI-LBCM5M1'. By silkscreen, do you
mean the power-up messages dislpayed by dmesg? I couldn't find the word
Leopard in it.
I discovered that I had changed the camera parameter in uEnv.txt to
something to experiment with alternatives. I have now corrected it as shown
below. The responses to the grep commands look very similar. The O/S is
definitely the one you recommended. I downloaded five files from the
directory and ran the shell on BB to install.
grep-ing console, would be better to make sure it's enabled..
If memory serves, I downloaded your ubuntu-12.04-r7-minimal-armhf-2012-09-27 and used tar to expand it. Then I inserted a blank sd card and executed setup-sdcard.sh to copy the files. I also found a file named precise-armhf 3.5.5-x7 and used it to set up the latest kernel. Then you said use 3.2.30 instead and I downloaded that. Now uname --all gives Linux arm 3.2.30-x15 #1 SMP Sat Oct 6 05:51:08 UTC 2012 armv7l armv7l armv7l GNU/Linux. Can I do anything else to verify compatibility with the camera?
If memory serves, I downloaded your ubuntu-12.04-r7-minimal-armhf-2012-09-27
and used tar to expand it. Then I inserted a blank sd card and executed
setup-sdcard.sh to copy the files. I also found a file named precise-armhf
to:
expansion_args=setenv expansion buddy=${buddy} buddy2=${buddy2} camera=lbcm5m1
3.5.5-x7 and used it to set up the latest kernel.
Yeah, still working on v3.5/v3.6 fighting the i2c changes, as the
device is failing to init.
Then you said use 3.2.30
instead and I downloaded that. Now uname --all gives Linux arm 3.2.30-x15 #1
SMP Sat Oct 6 05:51:08 UTC 2012 armv7l armv7l armv7l GNU/Linux. Can I do
anything else to verify compatibility with the camera?
8 Ekim 2012 Pazartesi 20:51:28 UTC+3 tarihinde RobertCNelson yazdı:
>
>
> 8 Ekim 2012 Pazartesi 12:06:07 UTC-5 tarihinde RobertCNelson yazdı:
>>
>> > ubuntu@arm:~$ dmesg | grep console
>> > [ 0.000000] Kernel command line: console=ttyO2,115200n8
>> > console=tty0
>> > vram=12e
>> > [ 0.000000] console [tty0] enabled
>> > [ 1.482238] console [ttyO2] enabled
>> >
>> > that's all folks just three lines and no mention of the camera
>>
>> Looks like your in minicom or another serial program that can't
>> word-wrap..
>>
>> Here's my uEnv.txt for reference:
>> http://paste.ubuntu.com/1267766/
>>
>> *Warning, unless your running one of my ubuntu/debian images with
>> zImage/initrd.img support, it probally won't boot with that uEnv.txt
>> as is...
>>
>> Regards,
>>
>> --
>> Robert Nelson
>> http://www.rcn-ee.com/
>
>
> line wrap correction:
> [ 0.000000] Kernel command line: console=ttyO2,115200n8 console=tty0
> vram=12M omapfb.mode=dvi:1280x720MR-16@60 omapdss.def_disp=dvi
> root=/dev/mmcblk0p2 ro rootfstype=ext4 rootwait fixrtc buddy=none
> buddy2=none
> [ 0.000000] console [tty0] enabled
> [ 1.482238] console [ttyO2] enabled
>
> If memory serves, I downloaded your
> ubuntu-12.04-r7-minimal-armhf-2012-09-27
> and used tar to expand it. Then I inserted a blank sd card and executed
> setup-sdcard.sh to copy the files. I also found a file named
> precise-armhf
to:
expansion_args=setenv expansion buddy=${buddy} buddy2=${buddy2}
camera=lbcm5m1
> 3.5.5-x7 and used it to set up the latest kernel.
Yeah, still working on v3.5/v3.6 fighting the i2c changes, as the
device is failing to init.
> Then you said use 3.2.30
> instead and I downloaded that. Now uname --all gives Linux arm
> 3.2.30-x15 #1
> SMP Sat Oct 6 05:51:08 UTC 2012 armv7l armv7l armv7l GNU/Linux. Can I do
> anything else to verify compatibility with the camera?