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,
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
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
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
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
-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
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
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
-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
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
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
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
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
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
-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
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
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
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
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...
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,
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
пятница, 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
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
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
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
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
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?
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
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.
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
30 matches
Mail list logo
