Search the Community

Hi Igor, Thanks for your great work with Armbian. I'm currently using your Armbian4.90 for my Hummingboard Edge v2 (dual), as the newest that does not hang on PCIe initialization. Unfortunately, the OV5640 MIPI module is not compiled in this version (it is compiled in all later versions of kernel 3.14.60). Have you kept an archive all the versions of your kernel source? Is there any way to get it so we can add and compile a specific module? Of course, I would prefer if the latest 3.14 kernel could not hang with the PCIe adapter initializing, but this seems to be a pretty difficult issue... I tried the latest one available on the official Armbian site (5.00), and also using your compilation script (which gives me version 5.05 or 5.07 if I remember well). I also tried SolidRun's images. Thanks! Alexandre

Hi again Igor, I just compiled the default branch, and mini-PCIe works well! Thanks again! Unfortunately, it seems that now the OV5640 module is not recognized anymore... Any chance you could "put it back" in the 3.14 kernel? Previous Armbian 3.14 kernels have it enabled. Thanks! Alexandre

Slightly off-topic: A quick look on SinoVoip's Android build: http://forum.banana-pi.org/t/bpi-m2-new-image-android-4-4-vsersion-v1/1429/2 It's Android 4.4 and since Allwinner never provides updates and SinoVoip doesn't develop themselve you won't see Lollipop or Marshmallow on this device. For newbies it will be impossible to use Android at all since SinoVoip does not tell their users to use Phoenix Card or Phoenix Suit to burn the aforementioned Android image to a SD card or directly to the device in FEL mode (you start Phoenix Suit, then the M2+ connected through USB to the USB-OTG port holding down the misnamed 'u-boot' button and can then flash an image directly). But if you can deal with screenshots in chinese, find the relevant Android chapter in their gitbook 'documentation' and are able to deal with broken links then you might succeed. In the link above they write "Bluetooth 4.0 supported" and "Camera ov5640 supported" which is not true since they use the same kernel as with their Raspbian image and there it's clearly written that neither BT nor camera work and at least BT isn't working at all (same applies to WiFi with this Android but you never know: SinoVoip thinks it's a good idea to let people desolder chips from their SBCs to get working WiFi). The kernel shows the usual quirks: when connected to a DVI display you get wrong colors (and unless you switch your display from RGB to YPbPr mode as can be seen below or you are an Linux expert able to play with kernel sources you're already lost when you only have a DVI display), average load is always above 1 since they don't care about problems that could be solved that easily and you're stuck with 720p display resolution (or you are an Linux expert, see link before). Will you be able to tweak kernel stuff with their Android (changing display resolution, switching from HDMI to DVI, adding drivers and so on): the usual SinoVoip answer applies: http://forum.banana-pi.org/t/please-update-specs-of-m3/640/53 (no answer) So in case you have to use their OS images be prepared that everything will remain as already known from M2 and M3, simply look through their forums first to get an impression what you can expect. And since the first retailers here in Germany list the M2+ already (+50€ shipping included) the whole board isn't interesting at all anymore. Wrong colors can be so nice: You would have to change the color mode of your display to fix that: 720p by default: And the typical SinoVoip 'trade mark': Average load above 1 also on Android!

Hi Igor, If I may, it would be greatly appreciated if you could fix this PCI issue on 3.14.60 for HB v2 (I just got one - Edge i2eX), as this kernel supports i2c and the OV5640 camera module via MIPI-CSI (like the Wandcam). The "only" thing missing is the mini PCIe hanging. Unless it is easy to provide these functionalities (i2c and ov5640 MIPI-CSI), as well as GPIO, to kernel 4.4.x? Thanks for your great work. PS. Is there somewhere we can download your kernel based on 3.14.53? Alexandre

Hi! I got back to Jessie_3.4.110. Now, with the same webcams I have: mario@cubieboard:~$ lsmod Module Size Used by gspca_zc3xx 41992 0 cpufreq_userspace 3447 0 gspca_spca561 8131 0 gspca_main 19991 2 gspca_spca561,gspca_zc3xx spi_sunxi 19001 0 sunxi_ir 4029 0 hidp 17744 0 rfcomm 59266 0 hci_uart 25232 0 bluetooth 267297 5 hidp,hci_uart,rfcomm and mario@cubieboard:~$ ls -R /lib/modules/`uname -r`/kernel/drivers/media/video /lib/modules/3.4.110-sun4i/kernel/drivers/media/video: cs53l32a.ko gspca mt9m111.ko ov5642.ko pwc soc_camera_platform.ko tuner.ko videobuf2-core.ko videobuf-vmalloc.ko cx231xx hdpvr mt9t031.ko ov6650.ko rj54n1cb0c.ko soc_mediabus.ko tveeprom.ko videobuf2-memops.ko wm8775.ko cx2341x.ko imx074.ko mt9t112.ko ov772x.ko s2255drv.ko stkwebcam.ko tvp5150.ko videobuf2-vmalloc.ko zr364xx.ko cx25840 ir-kbd-i2c.ko mt9v011.ko ov9640.ko saa7115.ko sun4i_csi tw9910.ko videobuf-core.ko em28xx msp3400.ko mt9v022.ko ov9740.ko sn9c102 tlg2300 usbvision videobuf-dma-contig.ko et61x251 mt9m001.ko ov2640.ko pvrusb2 soc_camera.ko tm6000 uvc videobuf-dvb.ko /lib/modules/3.4.110-sun4i/kernel/drivers/media/video/cx231xx: cx231xx-alsa.ko cx231xx-dvb.ko cx231xx.ko /lib/modules/3.4.110-sun4i/kernel/drivers/media/video/cx25840: cx25840.ko /lib/modules/3.4.110-sun4i/kernel/drivers/media/video/em28xx: em28xx-alsa.ko em28xx-dvb.ko em28xx.ko /lib/modules/3.4.110-sun4i/kernel/drivers/media/video/et61x251: et61x251.ko /lib/modules/3.4.110-sun4i/kernel/drivers/media/video/gspca: gl860 gspca_jeilinj.ko gspca_mr97310a.ko gspca_pac7302.ko gspca_sonixj.ko gspca_spca508.ko gspca_stv0680.ko gspca_vicam.ko gspca_benq.ko gspca_jl2005bcd.ko gspca_nw80x.ko gspca_pac7311.ko gspca_spca1528.ko gspca_spca561.ko gspca_sunplus.ko gspca_xirlink_cit.ko gspca_conex.ko gspca_kinect.ko gspca_ov519.ko gspca_se401.ko gspca_spca500.ko gspca_sq905c.ko gspca_t613.ko gspca_zc3xx.ko gspca_cpia1.ko gspca_konica.ko gspca_ov534_9.ko gspca_sn9c2028.ko gspca_spca501.ko gspca_sq905.ko gspca_topro.ko m5602 gspca_etoms.ko gspca_main.ko gspca_ov534.ko gspca_sn9c20x.ko gspca_spca505.ko gspca_sq930x.ko gspca_tv8532.ko stv06xx gspca_finepix.ko gspca_mars.ko gspca_pac207.ko gspca_sonixb.ko gspca_spca506.ko gspca_stk014.ko gspca_vc032x.ko /lib/modules/3.4.110-sun4i/kernel/drivers/media/video/gspca/gl860: gspca_gl860.ko /lib/modules/3.4.110-sun4i/kernel/drivers/media/video/gspca/m5602: gspca_m5602.ko /lib/modules/3.4.110-sun4i/kernel/drivers/media/video/gspca/stv06xx: gspca_stv06xx.ko /lib/modules/3.4.110-sun4i/kernel/drivers/media/video/hdpvr: hdpvr.ko /lib/modules/3.4.110-sun4i/kernel/drivers/media/video/pvrusb2: pvrusb2.ko /lib/modules/3.4.110-sun4i/kernel/drivers/media/video/pwc: pwc.ko /lib/modules/3.4.110-sun4i/kernel/drivers/media/video/sn9c102: sn9c102.ko /lib/modules/3.4.110-sun4i/kernel/drivers/media/video/sun4i_csi: csi0 csi1 device /lib/modules/3.4.110-sun4i/kernel/drivers/media/video/sun4i_csi/csi0: sun4i_csi0.ko /lib/modules/3.4.110-sun4i/kernel/drivers/media/video/sun4i_csi/csi1: sun4i_csi1.ko /lib/modules/3.4.110-sun4i/kernel/drivers/media/video/sun4i_csi/device: gc0307.ko gc0308.ko gt2005.ko hi253.ko hi704.ko mt9d112.ko mt9m112.ko mt9m113.ko ov2655.ko ov5640.ko ov7670.ko sp0838.ko /lib/modules/3.4.110-sun4i/kernel/drivers/media/video/tlg2300: poseidon.ko /lib/modules/3.4.110-sun4i/kernel/drivers/media/video/tm6000: tm6000-alsa.ko tm6000-dvb.ko tm6000.ko /lib/modules/3.4.110-sun4i/kernel/drivers/media/video/usbvision: usbvision.ko /lib/modules/3.4.110-sun4i/kernel/drivers/media/video/uvc: uvcvideo.ko Specifically: mario@cubieboard:~$ ls -R /lib/modules/`uname -r`/kernel/drivers/media/video/gspca /lib/modules/3.4.110-sun4i/kernel/drivers/media/video/gspca: gl860 gspca_jeilinj.ko gspca_mr97310a.ko gspca_pac7302.ko gspca_sonixj.ko gspca_spca508.ko gspca_stv0680.ko gspca_vicam.ko gspca_benq.ko gspca_jl2005bcd.ko gspca_nw80x.ko gspca_pac7311.ko gspca_spca1528.ko gspca_spca561.ko gspca_sunplus.ko gspca_xirlink_cit.ko gspca_conex.ko gspca_kinect.ko gspca_ov519.ko gspca_se401.ko gspca_spca500.ko gspca_sq905c.ko gspca_t613.ko gspca_zc3xx.ko gspca_cpia1.ko gspca_konica.ko gspca_ov534_9.ko gspca_sn9c2028.ko gspca_spca501.ko gspca_sq905.ko gspca_topro.ko m5602 gspca_etoms.ko gspca_main.ko gspca_ov534.ko gspca_sn9c20x.ko gspca_spca505.ko gspca_sq930x.ko gspca_tv8532.ko stv06xx gspca_finepix.ko gspca_mars.ko gspca_pac207.ko gspca_sonixb.ko gspca_spca506.ko gspca_stk014.ko gspca_vc032x.ko /lib/modules/3.4.110-sun4i/kernel/drivers/media/video/gspca/gl860: gspca_gl860.ko /lib/modules/3.4.110-sun4i/kernel/drivers/media/video/gspca/m5602: gspca_m5602.ko /lib/modules/3.4.110-sun4i/kernel/drivers/media/video/gspca/stv06xx: gspca_stv06xx.ko and mario@cubieboard:~$ ls -R /lib/modules/`uname -r`/kernel/drivers/media/video/uvc /lib/modules/3.4.110-sun4i/kernel/drivers/media/video/uvc: uvcvideo.ko thanks in advance!

Hello, with 3.4. kernel I could use my csi-cam on my R1: #5.0 Mega Pixel Banana PI Camera Module for Android #and Linux. OV5640 chipset, CSI connector #Price: US $24.00 / piece from aliexpress sudo modprobe ov5640 sudo modprobe sun4i_csi0 #video stream #mplayer tv:// #snapshot mplayer tv:// -vo png -frames 1 Now I switched to armbian 4.7 with 4.2.6 to use new wifi-usb-drivers but I saw that those modules are not supported in the new kernel. :-( Source of drivers: https://github.com/LeMaker/linux-sunxi/tree/lemaker-3.4/drivers/media/video/sun4i_csi https://github.com/LeMaker/linux-sunxi/blob/lemaker-3.4/drivers/media/video/sun4i_csi/device/ov5640.c Did anyone got this to work with 4.x-kernel? Is there a chance that it will/could be integrated in mainline-based Armbian? regards

I think working on CSI is still "work in progress" in mainline kernel. And regarding the OV5460 it's not worth the efforts. This is a "5MP" camera and I've never seen anyone being able to get more than 640x480 pixels with questionable quality out. I tried to get an idea why and stumbled across a freescale forum (IIRC) where one engineer said that it's hard to write a driver for this module without loading/using BLOBs with tables for conversion (or something like that) on the camera first. In short words: If you don't sign an NDA with Omnivision you won't be able to write a driver for this module that doesn't suck. We still use the RPi (B+) for this purpose. And the difference are just the drivers (for both the VPU -- HW accelerated h.264/1080p@30fps -- and OV5647 -- image quality) Today I stumbled across these links: http://www.arducam.com/camera-modules/raspberrypi-camera/ and http://www.arducam.com/camera-modules/5mp-ov5640/ No idea how to deal with currently (maybe they've drivers that work better, but this still won't help with mainline kernel)

Hi tkaiser 1)IMAGE see: [ the black shadow on the left is from my too small hole in self-made R1-case :-) ] http://www.directupload.net/file/d/4204/pndxoapx_png.htm <a href="http://www.directupload.net"target="_blank"><img src="http://fs5.directupload.net/images/151216/pndxoapx.png" title="Kostenlos Bilder und Fotos hochladen"></a> 2) How can I test max resolution? I didn't config anything, see my first post for what I (only) did. 3) What do you want to say with your link-answer: http://linux-sunxi.org/Mainlining_Effort#Major_drivers "CSI (camera sensor interface) driver (WiP: Yassin Jaffer (ddc))" Nothing is happening? Nothing will ever happen? I hoped anyone here or Igor has modified the code from : https://github.com/LeMaker/linux-sunxi/blob/lemaker-3.4/drivers/media/video/sun4i_csi/device/ov5640.cto/for 4.x-kernel or can do this with minimal effort... regards

http://linux-sunxi.org/Mainlining_Effort#Major_drivers BTW: How does quality look like with OV5640? What's the highest resolution possible?