lvmc

I have tested GT1 under extremely load cases and it is the best hardware and thermal design I've seen so far. I'm highly interested in helping Armbian support GT1. @tkaiser, can you help me with steps to help it go faster?

@tkaiser, I'm interested in helping in this effort. How Armbian see the possibility to fully support GT1? It is a special hardware!

Enhanced driver for OV5640 and vfe fix are now available on Armbian, thanks to lex and jules! https://github.com/igorpecovnik/lib/commit/05456d07ea78780e17fbfbc0ec9a1e11703ddada

@Max, your camera module is not being recognized at hardware level. [ 2.984892] [OV5640]error at sensor_detect [ 2.984899] [OV5640]chip found is not an target chip. To help you, please provide me with the following information: - datasheet of your board containing the camera interface pinout; - a high resolution photo from the camera conector showing the pins and electrical contacts; - your /boot/script.bin file or converted to fex already.

@Max, can you send me dmesg under two circustances? 1) boot your board with camera attached; 1) boot your board without camera attached;

@tkaiser @lex, @JulesThuillier and @lvmc (me, yeah) worked so hard last 2 weeks to solve most issues on OV5640. It is fully functional now and I will push the Armbian patches today or tomorrow.

I finished all tests on hardware level and it's confirmed that both GC2035 and OV5640 are now fully working! @lex has been doing an incredible job on Linux drivers, now focusing on frame grabbing compatibility.

@Nora Lee, thank you so much for supporting our effort! We are actively working to solve all issues with GC2035 and OV5640 and as soon we finish software stuff, the code will be available for Armbian community. The Armbian project has been doing and incredible job for community and TRUE collaboration is the way to go!

@lex AF pins 23 and 24 need further investigation, it is maybe swapped too... especially on OV5640 AF / SinoVoip... but I will not focus on solving it for now. I think a good idea would be to create a reference/comparison table with camera modules from different factories/brands.

@tkaiser Oranges GC2035 FF/Xulong is working with @lex, already merged on Armbian; From the original gc2035.c driver found typically on Linux, @lex driver provides much better FPS rates and resolutions. modprobe gc2035 modprobe v4l2_vfe fswebcam --Hflip 1 -r 640x480 -p YUV420P - > cam640x480_1.jpg OV5640 AF/SinoVoip is working on Oranges, with the same drawbacks as explained for Bananas (see below). Bananas GC2035 FF/Xulong is working, same comments as for Oranges; OV5640 AF/SinoVoip is working but there are several bugs on ov5640.c driver. To temporaly overcome these bugs, @lex modified fswebcam to retrieve frames bypassing driver missing features. modprobe ov5640 modprobe v4l2_vfe fswebcam --Hflip 1 -r 640x480 -p YUV420P - > cam640x480_1.jpg Fixing all issues ov5640.c is complex and requires a lot of efforts, we don't have a fixed schedule to do it yet... but I report that multiple resolutions are currently working... will keep community updated as we move, if we move in that direction. My personal target would be to have the driver fixed to run a basic OpenCV frame grabbing code... #include <iostream> #include <opencv2/opencv.hpp> using namespace std; int main() { Mat frame; VideoCapture cap; if (!cap.open("/dev/video0")) { cout << "Failed to OPEN /dev/video0" <<endl; return -1; } while(; { cap >> frame; if (frame.empty()) break; cout << "Failed to RETRIEVE frame from /dev/video0" <<endl; return -1; } return 0; } For both OV5640 AF / SinoVoip or GC2035 FF / Xulong, on both Oranges (except Orange Pi One or Orange Pi PC) or Bananas, you can connect modules directly to DVP camera connector (24pin connector), no extension board is required. On the hardware side we discovered that both Oranges and Bananas adopted 180º reversed pins layout, when comparing to most of the camera modules that are available for sale from other suppliers. My guessing is that they have changed it to somehow force customers buy their own cameras. To overcome that I personally partnered with camera factory to develop new GC2035 FF and OV5640 FF modules with the correct pin layout... it is under production right now. As soon I test the new modules next week, I will start selling cameras modules to help me amortize factory custom development costs and help community. Note: FF stands for FIXED FOCUS, while AF stands for AUTO FOCUS. By the way SinoVoip has been extremely supportive with me, proving me hardware as requested. On the other side Steven/Xulong seems to definitely not be interested in solving it... he just told me "It doesn't work, only with our own GC2035 cameras".

OV5640/SinoVoip AF is working on multiple resolutions, check this 640x480 shot on moderate lighting conditions.

@tkaiser: off-topic, create a similar topic about 4th pin header USB on M2+. It is useful as this post!

@lex, accordingly to VVision engineer it doesn't matter AF_VCC and AF_GND on AF modules are inverted... waiting my new v1.1 M2+ board to test...

@tksaiser I'm doing several tests and pinouts comparisons... hope to have the final answer this week.

I'm reporting this issue too, over HDMI the cursor is not being shown.

@tkaiser What is your board revision? My board is v1.0, while @jernej board revision is v1.1 @tkaiser and @jernej, I'm investigating the OV5640 with @lex... to advance the investigation we need do some tests on more boards with OV5640 from both SinoVoip and VVision {with Auto Focus (AF) and Fixed Focus (FF)} Has anyone found a M2+ and operating system (Linux or Android) combination that is working? SinoVoip claims that OV5640 is working on: BPI-M2_Plus_Android_V1.zip BPI-M2_Plus_Android_V2.zip 2016-05-05-u1510_gpu_vpu_camera_bt_bpi-m2p_beta.img.zip For further investigation I need remote access over SSH connection to M2+ with OV5640 because I got my M2+ from the first pre mass-production batch and it didn't came with Q.C PASSED seal and there are some hand soldered resistors. Could any of you provide me SSH access? We are really working hard to solve it for community benefit!

@tkaiser and m2+ owners, could you please check if on your boards there are 2 resistors that seems to be soldered by hand on pins 3 and 4 of camera connector?

I can provide SSH access to multiple M2+ boards if needed.

Got new libisp blobs from SinoVoip: https://www.dropbox.com/s/ghdcxy16ktim3n0/libisp.zip?dl=0

@tkaiser do you know anything about libisp or how do update Armbian version to the newest one? Me and @lex did a very deep debug and found it is outdated.

I edited /boot/script.fex from vip_dev0_fmt = 0 to vip_dev0_fmt = 1 and camera (OV5640 from SinoVoip) is now being correctly recognized on Linux. [ 140.099421] [VFE]Welcome to Video Front End driver [ 140.099764] [VFE]pdev->id = 0 [ 140.099775] [VFE]dev->mipi_sel = 0 [ 140.099782] [VFE]dev->vip_sel = 0 [ 140.099789] [VFE]dev->isp_sel = 0 [ 140.105923] [VFE_WARN]vfe vpu clock is null [ 140.113251] [VFE]..........................vfe clk open!....................... [ 140.113285] [ISP] isp platform_id = 5! [ 140.113463] [VFE]vfe_init end [ 140.120116] [VFE]probe_work_handle start! [ 140.120142] [VFE]v4l2 subdev register input_num = 0 [ 140.120154] [VFE]vfe sensor detect start! input_num = 0 [ 140.120168] [VFE]Find sensor name is "ov5640", i2c address is 78, type is "YUV" ! [ 140.120180] [VFE]Sub device register "ov5640" i2c_addr = 0x78 start! [ 140.120195] [VFE]v4l2_device_register_subdev return 0 [ 140.120205] [VFE]registered sensor subdev is OK! [ 140.120213] [VFE]Check sensor! [ 140.133563] [VFE]mclk on [ 140.278276] [OV5640]sensor_s_release_af [ 140.290607] [OV5640]disalbe oe! [ 140.290930] [VFE]mclk off [ 140.302989] [VFE]Sub device register "ov5640" is OK! [ 140.303299] [VFE]V4L2 device registered as video0 [ 140.303330] [VFE]..........................vfe clk close!....................... [ 140.303351] [VFE]probe_work_handle end! [ 140.310638] [VFE]vfe_open [ 140.310659] [VFE]..........................vfe clk open!....................... [ 140.310695] [VFE]vfe_open ok [ 140.311109] [VFE]vfe_close [ 140.311121] [VFE]vfe select input flag = 0, s_input have not be used . [ 140.311139] [VFE]..........................vfe clk close!....................... [ 140.311168] [VFE]vfe_close end BUT we have something else to solve. There is a function from H3 SDK (sun8iw7p1_isp_set_table_addr) that is not supported. [ 58.476803] [VFE]vfe_open [ 58.476823] [VFE]..........................vfe clk open!....................... [ 58.476863] [VFE]vfe_open ok [ 58.486403] [VFE]Set vfe core clk = 216000000, after Set vfe core clk = 200000000 [ 58.486421] NOT_SUPPORT_THIS_FUNCTION:sun8iw7p1_isp_set_table_addr, line: 372 [ 58.499735] [VFE]mclk on [ 58.645021] [VFE_WARN]v4l2 sub device queryctrl (null) unsuccess! [ 58.645108] [VFE_ERR]try bayer bus error when pix fmt is bayer rgb at try_fmt_internal! [ 58.649879] [VFE_ERR]pixel format (0x4745504a) width 384 height 288 invalid at vidioc_try_fmt_vid_cap. [ 58.654862] [VFE_ERR]try bayer bus error when pix fmt is bayer rgb at try_fmt_internal! [ 58.659861] [VFE_ERR]pixel format (0x47504a4d) width 384 height 288 invalid at vidioc_try_fmt_vid_cap. [ 58.665093] [VFE_ERR]try bayer bus error when pix fmt is bayer rgb at try_fmt_internal! [ 58.670398] [VFE_ERR]pixel format (0x31363553) width 384 height 288 invalid at vidioc_try_fmt_vid_cap. [ 58.675869] [VFE_ERR]try rgb888 bus error when pix fmt is rgb888/prgb888 at try_fmt_internal! [ 58.681532] [VFE_ERR]pixel format (0x33424752) width 384 height 288 invalid at vidioc_try_fmt_vid_cap. [ 58.687316] [VFE_ERR]try bayer bus error when pix fmt is bayer rgb at try_fmt_internal! [ 58.693114] [VFE_ERR]pixel format (0x33524742) width 384 height 288 invalid at vidioc_try_fmt_vid_cap. [ 58.698969] [VFE_ERR]try rgb888 bus error when pix fmt is rgb888/prgb888 at try_fmt_internal! [ 58.704954] [VFE_ERR]pixel format (0x34424752) width 384 height 288 invalid at vidioc_try_fmt_vid_cap. [ 58.711090] [VFE_ERR]try bayer bus error when pix fmt is bayer rgb at try_fmt_internal! [ 58.717265] [VFE_ERR]pixel format (0x34524742) width 384 height 288 invalid at vidioc_try_fmt_vid_cap. [ 58.915179] [OV5640]s_fmt set width = 640, height = 480 [ 58.915663] [VFE_ERR]bsp_csi_set_fmt error at vidioc_s_fmt_vid_cap! [ 58.993859] [VFE]vfe_close [ 58.993874] [VFE]mclk off [ 59.030031] [VFE]..........................vfe clk close!....................... [ 59.030060] [VFE]vfe_close end Maybe we are missing some .bin files from sun8iw7p1... I have no idea how and where to add this files. Please check from oficial SinoVoip GitHub/repository: https://github.com/BPI-SINOVOIP/BPI-M2P-bsp/tree/master/sunxi-pack/chips/sun8iw7p1/bin

@tkaiser, don't give up! How can I help you?

[ 216.288532] [VFE]cci probe start cci_sel = 0! [ 216.288675] [VFE]cci probe end cci_sel = 0! [ 216.288987] [VFE]cci_init end [ 305.485024] [VFE]Welcome to Video Front End driver [ 305.485366] [VFE]pdev->id = 0 [ 305.485375] [VFE]dev->mipi_sel = 0 [ 305.485383] [VFE]dev->vip_sel = 0 [ 305.485391] [VFE]dev->isp_sel = 0 [ 305.491515] [VFE_WARN]vfe vpu clock is null [ 305.499107] [VFE]..........................vfe clk open!....................... [ 305.499141] [ISP] isp platform_id = 5! [ 305.499292] [VFE]vfe_init end [ 305.500111] [VFE]probe_work_handle start! [ 305.500137] [VFE]v4l2 subdev register input_num = 0 [ 305.500154] [VFE]vfe sensor detect start! input_num = 0 [ 305.500167] [VFE_WARN]Camer detect "YUV" fmt is different from sys_config! [ 305.500179] [VFE_WARN]Apply detect fmt = 0 replace sys_config fmt = 1! [ 305.500191] [VFE]Find sensor name is "ov5640", i2c address is 78, type is "YUV" ! [ 305.500204] [VFE]Sub device register "ov5640" i2c_addr = 0x78 start! [ 305.500221] [VFE]v4l2_device_register_subdev return 0 [ 305.500232] [VFE]registered sensor subdev is OK! [ 305.500240] [VFE]Check sensor! [ 305.513563] [VFE]mclk on [ 305.580334] [VFE CCI_0 ERR] Status error at addr_8bit = 78, wr_flag = 1, val = 1000a30 [ 305.580595] [VFE CCI_0 ERR] Status error at addr_8bit = 78, wr_flag = 1, val = 1000a30 [ 305.580852] [VFE CCI_0 ERR] Status error at addr_8bit = 78, wr_flag = 1, val = 1000a30 [ 305.580869] [OV5640]error at sensor_detect [ 305.580878] [OV5640]chip found is not an target chip. [ 305.580888] [VFE]mclk off [ 305.617004] [VFE]vfe sensor subdev unregister! [ 305.617019] [VFE]Sub device register "ov5640" failed! [ 305.617029] [VFE_ERR]vfe sensor register check error at input_num = 0 [ 305.621776] [VFE]V4L2 device registered as video0 [ 305.621811] [VFE]..........................vfe clk close!....................... [ 305.621833] [VFE]probe_work_handle end! [ 305.626876] [VFE]vfe_open [ 305.626896] [VFE]..........................vfe clk open!....................... [ 305.626935] [VFE]vfe_open ok [ 305.627137] [VFE]vfe_close [ 305.627150] [VFE]vfe select input flag = 0, s_input have not be used . [ 305.627167] [VFE]..........................vfe clk close!....................... [ 305.627196] [VFE]vfe_close end

Use iw command instead of iwconfig.