JulesThuillier

Thanks ! Actually I just shouldn't have disabled LIB64, just change g++/gcc How did you installed it then ? I have the "ERROR: pipeline could not be constructed: no element "rkisp"." error when trying to start gst-launch-1.0. You can't believe how happy I was to read that : GREAT JOB !!!!

How did you managed to build it ? I am trying on the board with Armbian distro but always end with the following message, even thouhg the libraries are there they seem to be incompatible. /usr/bin/ld: skipping incompatible ../ext/rkisp/lib/libcam_engine_cifisp.so when searching for -lcam_engine_cifisp /usr/bin/ld: cannot find -lcam_engine_cifisp /usr/bin/ld: skipping incompatible ../ext/rkisp/lib/libcam_ia.so when searching for -lcam_ia /usr/bin/ld: cannot find -lcam_ia I run the following command : sudo ./config_build.sh # I had to change the gcc g++ toolchain path in the file and set LIB64 to FALSE first. sudo make

Oh yes ! I saw the thread at 2am, and read it way too fast I think Back to the testing !

Yes, the problem is not with changing the config, that I already did. I just can't find the right config that makes Rockchip ISP1 driver work instead of rkisp10.

Just been disabling it in the config file (linux-rk3399-default.config) while building with armbian script. But enabling "CONFIG_VIDEO_ROCKCHIP_ISP1" didn't got it to load apparently... I am going to be looking for extra log. By the way they are some interesting informations here : https://github.com/ayaromenok/test/issues/9 And the Nano Pi M4 just got supported on linux kernel 5.1 : https://github.com/torvalds/linux/commit/6ad63dec9c2c80710896edd1996e56c54a230870

Thanks for the help @chwe ! I have been trying all day to configure the kernel options using armbian (linux-rk3399-default.config file), to get rockchip_isp1 instead of isp10 : # CONFIG_VIDEO_RK_CIF_ISP10 is not set CONFIG_VIDEO_ROCKCHIP_CIF=y CONFIG_VIDEO_ROCKCHIP_ISP1=y I tried disabling the old one to enable the most recent (I still haven't understood what ROCKCHIP_CIF stands for...), but I couldn't get it to load. It never appears in the kernel log. It does work on FriendlyElec however... But I'd rather use Armbian as it runs faster. One thing I don't understand is should I set the camera configuration in the .dts file or this is for the previous driver (isp10) ? If I set the camera in the .dts file it will be a v4l2-i2c-subdev device type and use another driver. I think the v4l2-i2c-subdev is the newer system but I might be wrong, and I am not sure if it changes anything to the ISP control driver. I'll keep you updated of my results here

Hi ! I am also trying to get the camera (OV4689 though) to work on a Nano Pi M4. May I ask how did you get to have the rkisp installed ? (What kernel config option did you use ?) And how did you get the /etc/cam_iq/rk-ov13850.xml file ? Did you add it yourself or was it directly from Armbian sources ? Concerning your question, have you been configuring the ISP module before using the camera ? Check the "Linux" part in the link below. It says http://opensource.rock-chips.com/wiki_Rockchip-isp1 In the gstreamer plugin, it takes care of configuring the media-ctl, before the v4l2-ctl, but if you don't use gstreamer you have to configure it yourself. Also you can look at the PDF I attached, it shows you an example to use gstreamer in cv.VideoCapture. Cheers Jules Rockchip_Linux_OpenCV_开发指南.zh-CN.en.pdf

Hello everyone ! Would anyone have any updates on that ? I am looking to use my Nano Pi M4 with the OV4689 camera, and I want to bring a lot drivers improvements to get to 120-180FPS as the RK3399 and OV4689 are supposed to handle. I just started with the RK3399, and I saw that Armbian just added the drivers for this camera recently, but is unclear why Rockchip seems to want us to go through their own version of GStreamer. To my understanding their gstreamer seems to be an interface to access more low level features like the ISP of the RK, I guess to grab/process frames faster maybe ? Originally I was planning on using V4L2 and IOCTL commands to interact directly with the driver, but I am not even sure I will be able to do that, or if it would be more efficient to go through Gstreamer. So if any of you are used to the Rockchip ecosystem, I'd be great if you could just guide me to avoid doing the wrong choices and get started on that driver quickly ! To sum up in a few questions : - Can I access the camera through V4L2 / IOCTL without Gstreamer ? - Will it be less efficient to do so ? - Has anyone successfully installed their Gstreamer on Armbian 4.4 kernel ? (I always end up with issues). Cheers ! EDIT: I actually find most answers here (http://opensource.rock-chips.com/wiki_Rockchip-isp1), now I guess I have to understand why the camera module gets "probbed successfully" but then fails to initialise at boot [ 1.645902] rk-ov4689.ov_camera_module_write_config(180) ERR: no active sensor configuration [ 1.645906] rk-ov4689.ov_camera_module_write_config(231) ERR: failed with error -14 [ 1.646377] rk-ov4689.pltfrm_camera_module_read_reg(1035) ERR: i2c read from offset 0x0000300a failed with error -6 [ 1.646596] rk-ov4689.pltfrm_camera_module_read_reg(1035) ERR: i2c read from offset 0x0000300b failed with error -6 [ 1.646601] rk-ov4689.ov4689_check_camera_id(860) ERR: register read failed, camera module powered off? [ 1.646606] rk-ov4689.ov4689_check_camera_id(878) ERR: failed with error (-6) [ 1.646622] rk-ov4689.ov_camera_module_attach(254) ERR: failed with error -6 [ 1.646632] cif_isp10_img_src_v4l2_i2c_subdev_to_img_src(59) ERR: failed with error -6 [ 1.646635] cif_isp10_img_src_to_img_src(70) ERR: to_img_src failed! [ 1.646638] cif_isp10_img_src_to_img_src(78) ERR: failed with error -14 [ 1.646642] cif_isp10_img_srcs_init(1101) ERR: failed with error -14 [ 1.646645] cif_isp10_create(5980) ERR: cif_isp10_img_srcs_init failed [ 1.646648] cif_isp10_create(6017) ERR: failed with error -14

Hi, Not if you use the version HDF5640-YC02-V1.0 F S (a mentioned above by @lvmc in post 67), with the expansion board of course

Ok, thanks to @lvmc we fixed this ! Here is how : apt-get install libusb-1.0-0-dev git clone https://github.com/linux-sunxi/sunxi-tools cd sunxi-tools make ==> NOTE : Here I had an error finding libusb, so I udpated the file fec.c nano fec.c And replaced #include <libusb/libusb.h> with #include "/usr/include/libusb-1.0/libusb.h" ==> END NOTE Keep a backup : sudo mv /boot/script.bin /boot/script.bin.old Run : ./bin2fex /boot/script.bin.old script.fex Edit the file script.fex nano script.fex Look for this line (Ctrl+W to search in nano) : vip_dev0_mname = "gc2035" And replace it with : vip_dev0_mname = "ov5640" Now save and create the bin from the fex : ./fex2bin script.fex script.bin sudo mv script.bin /boot/script.bin sudo chmod 777 /boot/script.bin reboot, and you're good to go ! Uses @lex fswebcam : modprobe ov5640 modprobe v4l2_vfe fswebcam --Hflip 1 -r 640x480 -p YUV420P - > cam640x480_1.jpg Thanks to @lvmc

I just tested the OV5640 AF (HDF5640-YC02-V1.0 F S) on Orange Pi PC Plus without success : On 3.4.112 : camera not found when using fswebcam On 4.7.3 : cannot even do a "modprobe ov5640" I'd like some help too on this matter, anyone ?

Hello everyone ! I am currently trying to connect an OV5640 to my Orange Pi PC Plus without success. I have reversed the connector on the expansion board like so : I am running the legacy version not the dev one, last updated about 10 days ago. I was wondering if the changes to use the 0V5640 have been pushed ? Also what is the procedure to use it ? So far I have been using : modprobe ov5640 modprobe vfe_v4l2 and then tried either fswebcam or qv4l2 without success (device not found). But there is a problem with the reversed connector as it causes the expansion board to heat up. I might have fried the sensor some times ago, but I am posting here to get the right procedure before frying another one. BTW, if I can make the OV5640 sensor work on the Orange Pi PC I'll make an expansion board with the good wiring and I'll make all the prod files available Cheers !