Search the Community

Hi! Now that the camera interface has been merged in mainline Kernel, I would like to try to use the OrangePi OV5640 camera module on my OrangePi One. So with the latest Armbian Bionic (20.02.1, kernel 5.4.20), I have been trying to get a device tree overlay. But for now, it fails to compile with: $ sudo armbian-add-overlay sun8i-h3-csi.dts Compiling the overlay Error: sun8i-h3-csi.dts:27.23-24 syntax error FATAL ERROR: Unable to parse input tree Error compiling the overlay My current overlay looks like this: /dts-v1/; /plugin/; / { compatible = "allwinner,sun8i-h3"; fragment@0 { target = <&pio>; __overlay__ { csi_mclk_pin: csi-mclk-pin { pins = "PE1"; function = "csi"; }; }; }; fragment@1 { target = <&i2c2>; __overlay__ { status = "okay"; ov5640: camera@3c { compatible = "ovti,ov5640"; reg = <0x3c>; pinctrl-names = "default"; pinctrl-0 = <&csi_mclk_pin>; clocks = <&ccu CLK_CSI_MCLK>; clock-names = "xclk"; AVDD-supply = <&reg_aldo1>; DOVDD-supply = <&reg_dldo3>; DVDD-supply = <&reg_eldo3>; reset-gpios = <&pio 4 14 GPIO_ACTIVE_LOW>; /* CSI-RST-R: PE14 */ powerdown-gpios = <&pio 4 15 GPIO_ACTIVE_HIGH>; /* CSI-STBY-R: PE15 */ port { ov5640_ep: endpoint { remote-endpoint = <&csi_ep>; bus-width = <8>; data-shift = <2>; /* lines 9:2 are used */ hsync-active = <1>; /* Active high */ vsync-active = <0>; /* Active low */ data-active = <1>; /* Active high */ pclk-sample = <1>; /* Rising */ }; }; }; }; }; fragment@2 { target = <&csi>; __overlay__ { status = "okay"; port { csi_ep: endpoint { remote-endpoint = <&ov5640_ep>; bus-width = <8>; hsync-active = <1>; /* Active high */ vsync-active = <0>; /* Active low */ data-active = <1>; /* Active high */ pclk-sample = <1>; /* Rising */ }; }; }; }; }; So the line 27, which seem to trigger the error is: `clocks = <&ccu CLK_CSI_MCLK>;` Also, according to the documentation, the regulator fields are required but this board does not have much regulators (like AXP209), so I have no idea what to write here. But this is my first time writing a device-tree overlay so I am not sure what is wrong with this line. Could someone guide me to get my overlay right? And, does anyone already got the CSI interface working with OV5460 sensor on a H3 based board? Thank you.

Hi all, I am trying to get an OV5640 camera working on the orangePiOne. I found this thread and was wondering if the overlay (or some overlay) is still required. Without anything extra, the camera is not detected. It says that sun6i-csi and ov5640 kernel modules should be loaded, so I loaded them manually with modprobe but nothing happens and nothing is shown in dmesg. Adding the mentioned overlay with "sudo armbian-add-overlay csi-ov5640.dts" just gives me an error in dmesg at reboot time "failed on fdt_overlay_apply(): FDT_ERR_NOTFOUND Error applying DT overlays, restoring original DT" uname -a Linux orangepione2 6.1.63-current-sunxi #1 SMP Mon Nov 20 10:52:19 UTC 2023 armv7l GNU/Linux boot logs on https://paste.armbian.com/unoqesepov wondering what to try next...

Hi there! I've recently configured the ov5640 camera overlay and was able to capture videos either with mjpg-streamer of ffmpeg. Now on 6.1.34 both causes now a kernel oops. From the stack trace it looks like it happens inside v4l2 "media_pad_remote_pad_first" Unable to handle kernel NULL pointer dereference at virtual address 00000030 ... ... PC is at media_pad_remote_pad_first+0xa/0x58 I don't think v4l2 is the root cause because this may mean it fails alle the time which is unlikely. Looks like a null ptr gets passed in into media_pad_remote_pad_first ffmpeg used like this, but other parameters all resulting in the kernel oops at the same location. sudo media-ctl --device /dev/media1 --set-v4l2 '"ov5640 2-003c":0[fmt:UYVY8_2X8/1280x720@1/15]' ffmpeg -hwaccel_device 0 -framerate 15 -f v4l2 -video_size 1280x720 -i /dev/video1 -r 15 -pix_fmt yuv420p -b:v 1280k test1280-15.mp4 WORKS on 4.14.x (was video0 and media0 here) mjpeg streamer testing ./mjpg_streamer -i "./input_uvc.so -d /dev/video0 -y 1 -r 1920x1080 -f 5 -q 30 -n " -o "./output_http.so -w ./www" Possible root causes: 1) Something is now wrong inside my DT overlay due to kernel changes? I'm thinking about the i2c and spi relationships 2) Something is broken inside ov5640 driver 3) Something is broken inside v4l Maybe someone can provide some hints to point me in the right direction for further investigation? Attached are the dmesg output and overlay source. Thilo mjpg-streamer with camera overlay oops 06.08.2023 output.txt sun8i-h3-ov5640.dts

Description We had autofocus patches for ov5640 camera in allwinner current and edge kernel that were disabled due to patch application failure. This PR fixes the patch application failure and re-enables the same How Has This Been Tested? Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration. [X] Checked that patches applies on 6.4 kernel [X] Checked that patches applies on 6.4 kernel [X] Tested that autofocus works with 6.1 kernel on NanoPi Duo2 The following procedure was used to test autofocus with 6.1 kernel Compiled and enabled device tree overlay for ov5640 camera taken from the forum post Took the ov5640_af_2.bin autofocus firmware and placed it in /lib/firmware directory with filename ov5640_af.bin Ran the following commands to start a camera stream # v4l2-ctl --device /dev/video1 --set-fmt-video=width=640,height=480,pixelformat=YUYV # media-ctl --device /dev/media1 --set-v4l2 '"ov5640 0-003c":0[fmt:YUYV8_2X8/640x480]' # ffmpeg -i /dev/video1 -q 10 -pix_fmt yuv420p -video_size 640x480 -r 5 -listen 1 -f avi http://192.168.29.128:8080/stream& # v4l2-ctl --device /dev/v4l-subdev0 -c auto_focus_start=1 Verified that autofocus firmware loaded successfully from dmesg output # dmesg | grep ov5640 [ 8.022346] ov5640 0-003c: supply DOVDD not found, using dummy regulator [ 8.022698] ov5640 0-003c: supply AVDD not found, using dummy regulator [ 8.022928] ov5640 0-003c: supply DVDD not found, using dummy regulator [ 2808.787047] ov5640 0-003c: firmware upload success [ 2808.787609] ov5640 0-003c: fw started after 0 ms verified that camera lens moves to focus when moving the subject Checklist: [ ] My code follows the style guidelines of this project [ ] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [X] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

trying to get the ov5640 camera working on an OrangePiOne. armbianmonitor logs : https://paste.armbian.com/gucenokapa Using this overlay : I get some things working and mostly not at all. What works: the kernel modules load bruno@orangepione2:~$ lsmod | grep ov ov5640 36864 1 v4l2_fwnode 24576 2 ov5640,sun6i_csi v4l2_async 20480 3 ov5640,v4l2_fwnode,sun6i_csi videodev 167936 7 ov5640,sunxi_cedrus,videobuf2_common,sun6i_csi,v4l2_mem2mem,videobuf2_v4l2,v4l2_async mc 40960 8 ov5640,sunxi_cedrus,videobuf2_common,videodev,sun6i_csi,v4l2_mem2mem,videobuf2_v4l2,v4l2_async and the device appears on /dev/video1 I assume this means the camera is accessed through the i2c and detected. I see it on the i2c bus: bruno@orangepione2:~/ustreamer$ cat /sys/class/i2c-dev/i2c-1/device/1-003c/of_node/name camera bruno@orangepione2:~/ustreamer$ ls -l /sys/class/i2c-adapter/ total 0 lrwxrwxrwx 1 root root 0 Jan 1 1970 i2c-0 -> ../../devices/platform/soc/1ee0000.hdmi/i2c-0 lrwxrwxrwx 1 root root 0 Jan 1 1970 i2c-1 -> ../../devices/platform/soc/1c2b400.i2c/i2c-1 bruno@orangepione2:~/ustreamer$ sudo i2cdetect -y 1 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- UU -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- media-ctl sees it bruno@orangepione2:~$ media-ctl -d 1 --print-topology Media controller API version 6.1.63 Media device information ------------------------ driver sun6i-csi model Allwinner A31 CSI Device serial bus info platform:1cb0000.camera hw revision 0x0 driver version 6.1.63 Device topology - entity 1: sun6i-csi (1 pad, 1 link) type Node subtype V4L flags 0 device node name /dev/video1 pad0: Sink <- "ov5640 1-003c":0 [ENABLED] - entity 5: ov5640 1-003c (1 pad, 1 link) type V4L2 subdev subtype Sensor flags 0 device node name /dev/v4l-subdev0 pad0: Source [fmt:JPEG_1X8/640x480@1/30 colorspace:jpeg xfer:srgb ycbcr:601 quantization:full-range crop.bounds:(0,0)/2624x1964 crop:(0,4)/2624x1944] -> "sun6i-csi":0 [ENABLED] I read https://linux-sunxi.org/CSI so I know the format and size must be selected before grabbing frames this for example works correctly media-ctl --device /dev/media1 --set-v4l2 '"ov5640 1-003c":0[fmt:UYVY8_2X8/640x480@1/30]' (no error after executing that command. and I can then verify it has been selected by running media-ctl and see the pad0 Source has the format changed. Tried many other formats and sizes, they are taken correctly. What does not work: everything else. I can not grab frames with anything. For both ustreamer and ffmpeg I tried many sizes and format, always fails the same way. ffmpeg: bruno@orangepione2:~/ustreamer$ ffmpeg -input_format mjpeg -s 640x480 -i /dev/video1 output.mjpg fmpeg version 5.1.4-0+deb12u1 Copyright (c) 2000-2023 the FFmpeg developers built with gcc 12 (Debian 12.2.0-14) configuration: --prefix=/usr --extra-version=0+deb12u1 --toolchain=hardened --libdir=/usr/lib/arm-linux-gnueabihf --incdir=/usr/include/arm-linux-gnueabihf --arch=arm --enable-gpl --disable-stripping --enable-gnutls --enable-ladspa --enable-libaom --enable-libass --enable-libbluray --enable-libbs2b --enable-libcaca --enable-libcdio --enable-libcodec2 --enable-libdav1d --enable-libflite --enable-libfontconfig --enable-libfreetype --enable-libfribidi --enable-libglslang --enable-libgme --enable-libgsm --enable-libjack --enable-libmp3lame --enable-libmysofa --enable-libopenjpeg --enable-libopenmpt --enable-libopus --enable-libpulse --enable-librabbitmq --enable-librist --enable-librubberband --enable-libshine --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libsrt --enable-libssh --enable-libsvtav1 --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvorbis --enable-libvpx --enable-libwebp --enable-libx265 --enable-libxml2 --enable-libxvid --enable-libzimg --enable-libzmq --enable-libzvbi --enable-lv2 --enable-omx --enable-openal --enable-opencl --enable-opengl --enable-sdl2 --disable-sndio --enable-libjxl --enable-pocketsphinx --enable-librsvg --enable-libdc1394 --enable-libdrm --enable-libiec61883 --enable-chromaprint --enable-frei0r --enable-libx264 --enable-libplacebo --enable-librav1e --enable-shared libavutil 57. 28.100 / 57. 28.100 libavcodec 59. 37.100 / 59. 37.100 libavformat 59. 27.100 / 59. 27.100 libavdevice 59. 7.100 / 59. 7.100 libavfilter 8. 44.100 / 8. 44.100 libswscale 6. 7.100 / 6. 7.100 libswresample 4. 7.100 / 4. 7.100 libpostproc 56. 6.100 / 56. 6.100 [video4linux2,v4l2 @ 0xa36470] ioctl(VIDIOC_G_PARM): Inappropriate ioctl for device [video4linux2,v4l2 @ 0xa36470] Time per frame unknown [video4linux2,v4l2 @ 0xa36470] ioctl(VIDIOC_STREAMON): Broken pipe /dev/video1: Broken pipe ustreamer bruno@orangepione2:~/ustreamer$ ustreamer -d /dev/video1 -r 640x480 -m JPEG -- INFO [14503.025 main] -- Using internal blank placeholder -- INFO [14503.027 main] -- Listening HTTP on [127.0.0.1]:8080 -- INFO [14503.027 stream] -- Using V4L2 device: /dev/video1 -- INFO [14503.028 stream] -- Using desired FPS: 0 -- INFO [14503.028 http] -- Starting HTTP eventloop ... ================================================================================ -- INFO [14503.030 stream] -- Device fd=8 opened -- INFO [14503.030 stream] -- Using input channel: 0 -- INFO [14503.030 stream] -- Using resolution: 640x480 -- INFO [14503.030 stream] -- Using pixelformat: JPEG -- INFO [14503.030 stream] -- Querying HW FPS changing is not supported -- ERROR [14503.030 stream] -- Device does not support setting of HW encoding quality parameters -- INFO [14503.030 stream] -- Using IO method: MMAP -- INFO [14503.035 stream] -- Requested 5 device buffers, got 5 -- ERROR [14503.036 stream] -- Unable to start capturing: Broken pipe -- INFO [14503.038 stream] -- Device fd=8 closed -- INFO [14503.038 stream] -- Sleeping 1 seconds before new stream init ... I built ustreamer from source with debug symbols and stepped with gdb, it fails on device.c:328 if (_D_XIOCTL((enable ? VIDIOC_STREAMON : VIDIOC_STREAMOFF), &type) < 0) { which is, afaik, when the video device is opened for grabbing frames. Something else that is very strange, trying to list camera controls returns empty bruno@orangepione2:~$ v4l2-ctl -d 1 --list-ctrls bruno@orangepione2:~$ however using yavta on the video subdevice retrieves controls bruno@orangepione2:~$ yavta --no-query -l /dev/v4l-subdev0 Device /dev/v4l-subdev0 opened. --- User Controls (class 0x00980001) --- control 0x00980901 `Contrast' min 0 max 255 step 1 default 0 current 0 control 0x00980902 `Saturation' min 0 max 255 step 1 default 64 current 64 control 0x00980903 `Hue' min 0 max 359 step 1 default 0 current 0 control 0x0098090c `White Balance, Automatic' min 0 max 1 step 1 default 1 current 1 control 0x0098090e `Red Balance' min 0 max 4095 step 1 default 0 current 0 control 0x0098090f `Blue Balance' min 0 max 4095 step 1 default 0 current 0 control 0x00980911 `Exposure' min 0 max 65535 step 1 default 0 current 0 control 0x00980912 `Gain, Automatic' min 0 max 1 step 1 default 1 current 1 control 0x00980914 `Horizontal Flip' min 0 max 1 step 1 default 0 current 0 control 0x00980915 `Vertical Flip' min 0 max 1 step 1 default 0 current 0 control 0x00980918 `Power Line Frequency' min 0 max 3 step 1 default 1 current 1 0: Disabled 1: 50 Hz (*) 2: 60 Hz 3: Auto --- Camera Controls (class 0x009a0001) --- control 0x009a0901 `Auto Exposure' min 0 max 1 step 1 default 0 current 0 0: Auto Mode (*) 1: Manual Mode control 0x009a090c `Focus, Automatic Continuous' min 0 max 1 step 1 default 0 current 0 control 0x009a091c `Auto Focus, Start' min 0 max 0 step 0 default 0 control 0x009a091d `Auto Focus, Stop' min 0 max 0 step 0 default 0 control 0x009a091e `Auto Focus, Status' min 0 max 7 step 0 default 0 current 0x00000000 --- Image Source Controls (class 0x009e0001) --- control 0x009e0901 `Vertical Blanking' min 24 max 2895 step 1 default 600 current 600 control 0x009e0902 `Horizontal Blanking' min 1256 max 1256 step 1 default 1256 current 1256 control 0x009e0903 `Analogue Gain' min 0 max 1023 step 1 default 0 current 0 --- Image Processing Controls (class 0x009f0001) --- control 0x009f0901 `Link Frequency' min 0 max 22 step 1 default 13 current 13 0: 992000000 1: 888000000 2: 768000000 3: 744000000 4: 672000000 5: 672000000 6: 592000000 7: 592000000 8: 576000000 9: 576000000 10: 496000000 11: 496000000 12: 384000000 13: 384000000 (*) 14: 384000000 15: 336000000 16: 296000000 17: 288000000 18: 248000000 19: 192000000 20: 192000000 21: 192000000 22: 96000000 control 0x009f0902 `Pixel Rate' min 48000000 max 168000000 step 1 default 48000000 current 48000000 control 0x009f0903 `Test Pattern' min 0 max 4 step 1 default 0 current 0 0: Disabled (*) 1: Color bars 2: Color bars w/ rolling bar 3: Color squares 4: Color squares w/ rolling bar 22 controls found. something else that is bothersome: the adapter board for the ov5640 has one component that reaches 90 degrees (c) constantly... not sure it should be that hot all the time ! this is starting to irritate me as it seems everything is configured correctly... grr. Any suggestions ?

I found the program v4l2-compliance it has one failure : Format ioctls (Input 0): fail: v4l2-test-formats.cpp(263): fmtdesc.description mismatch: was 'Y/UV 4:2:0 (16x16 Linear)', expected 'Y/CbCr 4:2:0 (16x16 Linear)' test VIDIOC_ENUM_FMT/FRAMESIZES/FRAMEINTERVALS: FAIL also very strange, I expected output like this instead I get this bruno@orangepione2:~$ v4l2-ctl -d 1 --list-ctrls --list-formats ioctl: VIDIOC_ENUM_FMT Type: Video Capture [0]: 'BA81' (8-bit Bayer BGBG/GRGR) [1]: 'GBRG' (8-bit Bayer GBGB/RGRG) [2]: 'GRBG' (8-bit Bayer GRGR/BGBG) [3]: 'RGGB' (8-bit Bayer RGRG/GBGB) [4]: 'BG10' (10-bit Bayer BGBG/GRGR) [5]: 'GB10' (10-bit Bayer GBGB/RGRG) [6]: 'BA10' (10-bit Bayer GRGR/BGBG) [7]: 'RG10' (10-bit Bayer RGRG/GBGB) [8]: 'BG12' (12-bit Bayer BGBG/GRGR) [9]: 'GB12' (12-bit Bayer GBGB/RGRG) [10]: 'BA12' (12-bit Bayer GRGR/BGBG) [11]: 'RG12' (12-bit Bayer RGRG/GBGB) [12]: 'YUYV' (YUYV 4:2:2) [13]: 'YVYU' (YVYU 4:2:2) [14]: 'UYVY' (UYVY 4:2:2) [15]: 'VYUY' (VYUY 4:2:2) [16]: 'RGBP' (16-bit RGB 5-6-5) [17]: 'RGBO' (16-bit A/XRGB 1-5-5-5) [18]: 'HM12' (Y/UV 4:2:0 (16x16 Linear)) [19]: 'NV12' (Y/UV 4:2:0) [20]: 'NV21' (Y/VU 4:2:0) [21]: 'YU12' (Planar YUV 4:2:0) [22]: 'YV12' (Planar YVU 4:2:0) [23]: 'NV16' (Y/UV 4:2:2) [24]: 'NV61' (Y/VU 4:2:2) [25]: '422P' (Planar YUV 4:2:2) [26]: 'RGBP' (16-bit RGB 5-6-5) [27]: 'RGBR' (16-bit RGB 5-6-5 BE) [28]: 'JPEG' (JFIF JPEG, compressed) also bruno@orangepione2:~$ media-ctl -d 0 --print-topology Media controller API version 6.1.63 Media device information ------------------------ driver sun6i-csi model Allwinner A31 CSI Device serial bus info platform:1cb0000.camera hw revision 0x0 driver version 6.1.63 Device topology - entity 1: sun6i-csi (1 pad, 1 link) type Node subtype V4L flags 0 device node name /dev/video1 pad0: Sink <- "ov5640 1-003c":0 [ENABLED] - entity 5: ov5640 1-003c (1 pad, 1 link) type V4L2 subdev subtype Sensor flags 0 device node name /dev/v4l-subdev0 pad0: Source [fmt:UYVY8_2X8/640x480@1/30 field:none colorspace:srgb xfer:srgb ycbcr:601 quantization:full-range crop.bounds:(0,0)/2624x1964 crop:(0,4)/2624x1944] -> "sun6i-csi":0 [ENABLED]

thanks, I tried that overlay now and there is some progress. A new device appeared in /dev/video, and I can see with lsmod that sun6i-csi and ov5640 kernel modules were loaded. However, trying ustreamer (https://github.com/pikvm/ustreamer) which I have used on the same board with a usb camera, unfortunately fails bruno@orangepione2:~$ sudo ustreamer --device=/dev/video0 --host=0.0.0.0 --port=8080 --resolution 1920x1080 -- INFO [680.044 main] -- Using internal blank placeholder -- INFO [680.045 main] -- Listening HTTP on [0.0.0.0]:8080 -- INFO [680.046 stream] -- Using V4L2 device: /dev/video0 -- INFO [680.046 stream] -- Using desired FPS: 0 -- INFO [680.047 http] -- Starting HTTP eventloop ... ================================================================================ -- INFO [680.049 stream] -- Device fd=8 opened -- INFO [680.049 stream] -- Using input channel: 0 -- INFO [680.049 stream] -- Using resolution: 1920x1080 -- INFO [680.049 stream] -- Using pixelformat: YUYV -- INFO [680.050 stream] -- Querying HW FPS changing is not supported -- INFO [680.050 stream] -- Using IO method: MMAP -- INFO [680.075 stream] -- Requested 5 device buffers, got 5 -- ERROR [680.076 stream] -- Unable to start capturing: Broken pipe -- INFO [680.081 stream] -- Device fd=8 closed -- INFO [680.081 stream] -- Sleeping 1 seconds before new stream init ... ================================================================================ I am going to try other formats, sizes and fps, see if it makes any difference...

Description Bumped Allwinner kernels. legacy - 5.15.137 -> 5.15.139 current - 6.1.62 -> 6.1.63 edge - 6.6.1 -> 6.6.2 Updated ov5640 camera patches to fix patch application failure. Also rebased the config files. How Has This Been Tested? Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration. [X] Both 32-bit and 64-bit kernel builds fine. [X] Tested 32-bit kernel on NanoPi Duo2(H3). All 3 kernels seems to work fine. [X] Tested ov5640 camera with current and edge kernels. Autofocus didn't worked for me, but its possible that I might have damaged my camera by placing something on it. Have to retest with an older kernel later to make sure. But video capture worked fine. Checklist: [ ] My code follows the style guidelines of this project [ ] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [ ] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Did further play around with ffmpeg and v4l pipeline. This now WORKS also 6.4.8-sunxi (Armbian_23.08.0-trunk_Nanopiduo2_jammy_edge_6.4.8_minimal build from 07-Aug) v4l2-ctl --device /dev/video1 --set-fmt-video=width=1280,height=720,pixelformat=YUYV media-ctl --device /dev/media1 --set-v4l2 '"ov5640 2-003c":0[fmt:YUYV8_2X8/1280x720]' ffmpeg -i /dev/video1 -q 10 -pix_fmt yuv420p -video_size 1280x720 -r 5 -listen 1 -f avi http://192.168.179.55:8080/stream VLC http://192.168.179.55:8080/stream ffmpeg is version 4.4.2-0ubuntu0.22.04.1 This means, there was a problem "behind the scenes" in 6.1x which is now fixed. Other parameters which did work in the past and now failing might be a side effect of internal improvments. I'll figure out anyway because this kernel now also contains the cedrus video engine and I want to use that for encoding and decoding. So from my point of view the issue is solved. @going the highest resolution 2592x1944 did work in friendlycore xenial 4.14 so the driver WAS able to do so. Don't know yet if something is now broken - but as said above need to play around anyways. Thanks @all! Thilo

Progress still on nanopiduo2 6.4.8-sunxi Meaniwhile i tried ustreamer which now WORKS at least with 640x480 like so: v4l2-ctl --device /dev/video1 --set-fmt-video=width=640,height=480,pixelformat=YUYV media-ctl --device /dev/media1 --set-v4l2 '"ov5640 2-003c":0[fmt:YUYV8_2X8/640x480]' ./ustreamer -d /dev/video1 --host 192.168.179.55 -r 640x480 and VLC plays http://192.168.179.55:8080/stream will now go ahead trying ffmpeg and will test ustreamer on 6.1.x (But I'd prefer using latest build anyway!) Thanks! Thilo

Did build 'edge' have now Linux nanopiduo2 6.4.8-sunxi #1 SMP Thu Aug 3 08:26:15 UTC 2023 armv7l armv7l armv7l GNU/Linux No more crashes 😀 but now no video🙄. mjpg_streamer says "cant enable video" dmesg shows sun6i-csi 1cb0000.camera: invalid input/output format combination tried sveral params which did work in the past, no luck as yet. Will do further testing later on. v4l2-ctl -d /dev/video1 --all Driver Info: Driver name : sun6i-csi Card type : sun6i-csi-capture Bus info : platform:1cb0000.camera Driver version : 6.4.8 Capabilities : 0xa4200001 Video Capture Streaming Extended Pix Format Device Capabilities Device Caps : 0x24200001 Video Capture Streaming Extended Pix Format Media Driver Info: Driver name : sun6i-csi Model : Allwinner A31 CSI Device Serial : Bus info : platform:1cb0000.camera Media version : 6.4.8 Hardware revision: 0x00000000 (0) Driver version : 6.4.8 Interface Info: ID : 0x0300000e Type : V4L Video Entity Info: ID : 0x0000000c (12) Name : sun6i-csi-capture Function : V4L2 I/O Pad 0x0100000d : 0: Sink, Must Connect Link 0x02000010: from remote pad 0x1000003 of entity 'sun6i-csi-bridge' (Video Interface Bridge): Data, Enabled, Immutable Priority: 2 Video input : 0 (sun6i-csi-capture: ok) Format Video Capture: Width/Height : 640/480 Pixel Format : 'YUYV' (YUYV 4:2:2) Field : None Bytes per Line : 1280 Size Image : 614400 Colorspace : sRGB Transfer Function : Default (maps to sRGB) YCbCr/HSV Encoding: Default (maps to ITU-R 601) Quantization : Default (maps to Limited Range) Flags : looks good but that "sun6i-csi-bridge" seems to be different!?! also i have spi-spidev overlay enabled but there is no /dev/spi* Maybe I made something wrong when building the image!?!? ov5640 load shows root@nanopiduo2:~# dmesg | grep ov5640 [ 8.767826] ov5640 2-003c: supply DOVDD not found, using dummy regulator [ 8.768164] ov5640 2-003c: supply AVDD not found, using dummy regulator [ 8.768320] ov5640 2-003c: supply DVDD not found, using dummy regulator [ 8.775980] ov5640 2-003c: Consider updating driver ov5640 to match on endpoints The last line is new i think. Need to figure out what that means... Thilo

Interesting. I think it might have something to do with the driver for ov5640. Will get one for testing, but it will take about a week to get delivered. Will update once the driver arrives.

Update: after boot simple v4l2-ctl -d /dev/video1 --all also causes the crash. Output ends here in the middle: Driver Info: Driver name : sun6i-csi Card type : sun6i-csi Bus info : platform:1cb0000.camera Driver version : 6.1.34 Capabilities : 0x84200001 Video Capture Streaming Extended Pix Format Device Capabilities Device Caps : 0x04200001 Video Capture Streaming Extended Pix Format Media Driver Info: Driver name : sun6i-csi Model : Allwinner A31 CSI Device Serial : Bus info : platform:1cb0000.camera Media version : 6.1.34 Hardware revision: 0x00000000 (0) Driver version : 6.1.34 Interface Info: ID : 0x03000003 Type : V4L Video Entity Info: ID : 0x00000001 (1) Name : sun6i-csi Function : V4L2 I/O Pad 0x01000002 : 0: Sink, Must Connect Link 0x02000007: from remote pad 0x1000006 of entity 'ov5640 2-003c' (Camera Sensor): Data, Enabled Priority: 2 Video input : 0 (Camera: ok) Format Video Capture: Width/Height : 1280/720 Pixel Format : 'BA81' (8-bit Bayer BGBG/GRGR) Field : None Bytes per Line : 1280 Size Image : 921600 Colorspace : sRGB Transfer Function : Default (maps to sRGB) YCbCr/HSV Encoding: Default (maps to ITU-R 601) Quantization : Default (maps to Full Range) Flags : Thilo

Did you ever solve this? Maybe try this: media-ctl --device /dev/media1 --set-v4l2 '"ov5640 1-003c":0[fmt:UYVY8_2X8/1920x1080]' note the _2X8 (I found this while searching for latest DT overlay) T.

Hello. I am using Nano pi duo2 2 as a sip video door bell. I will use baresip. But i cant do hardware acceleration with OV5640 camera in baresip. I have found that repo https://github.com/twdragon/FFmpeg - with this ffmpeg and i have working acceleration. But i dont understand how i can integrate this acceleration with baresip. I using Ubuntu 18.04.6 LTS with kernel Linux NanoPi-Duo2 3.4.39-h3, because only on this kernel 3.4 works Video OUT on Nano PI Duo 2. Can i integrate hardware acceleration Cedrus to baresip , when compiling baresip?

I have same Problem. Ich habe camera ov5640 on bpim2z. Kernel 6.1. Make for camera overlay. Comera Work. I can use gsteamer. But will use Cedrus. Und load cedrus Modelle. Have new /Dev/video2. how to set up gsteamer to use the accelerator?

didn't want to create a new topic. There is a tutorial on how to enable the camera ov5640 when building a new kernel. There are kernel modules - but no camera. there is no camera in the dts files. Thank you. Andrew.

First off, thanks to everyone who has figured this all out. Much of this is over my head I think I've nearly got my camera working with Armbian 22.08.6 Jammy on Linux 5.15.69-sunxi which is running on an Orange Pi PC. I've gotten /dev/media1 and /dev/video1 nodes after using the following device tree overlay. It is just a combination of @rreignier's overlay with @gsumner's regulator nodes but I haven't seen anyone post a combined overlay yet so I hope this makes it clear for anyone trying to get this to work on the same platform. /dts-v1/; /plugin/; / { compatible = "allwinner,sun8i-h3"; }; &ccu { assigned-clocks = <&ccu 107>; assigned-clock-parents = <&osc24M>; assigned-clock-rates = <24000000>; }; &pio { csi_mclk_pin: csi-mclk-pin { pins = "PE1"; function = "csi"; }; }; &i2c2_pins { bias-pull-up; }; &i2c2 { status = "okay"; ov5640: camera@3c { compatible = "ovti,ov5640"; reg = <0x3c>; pinctrl-names = "default"; pinctrl-0 = <&csi_mclk_pin>; clocks = <&ccu 107>; clock-names = "xclk"; AVDD-supply = <&reg_vcc_af_csi>; DOVDD-supply = <&reg_vdd_1v5_csi>; DVDD-supply = <&reg_vcc_csi>; reset-gpios = <&pio 4 14 1>; /* CSI-RST-R: PE14 */ powerdown-gpios = <&pio 4 15 0>; /* CSI-STBY-R: PE15 */ port { ov5640_ep: endpoint { remote-endpoint = <&csi_ep>; bus-width = <8>; data-shift = <2>; /* lines 9:2 are used */ hsync-active = <1>; /* Active high */ vsync-active = <0>; /* Active low */ data-active = <1>; /* Active high */ pclk-sample = <1>; /* Rising */ }; }; }; }; &csi { status = "okay"; port { #address-cells = <1>; #size-cells = <0>; csi_ep: endpoint { remote-endpoint = <&ov5640_ep>; bus-width = <8>; hsync-active = <1>; /* Active high */ vsync-active = <0>; /* Active low */ data-active = <1>; /* Active high */ pclk-sample = <1>; /* Rising */ }; }; }; &{/} { reg_vdd_1v5_csi: vdd-1v5-csi { compatible = "regulator-fixed"; regulator-name = "vdd1v5-csi"; regulator-min-microvolt = <1500000>; regulator-max-microvolt = <1500000>; gpio = <&pio 6 13 0>; /* PG13 */ enable-active-high; regulator-boot-on; regulator-always-on; }; reg_vcc_csi: vcc-csi { compatible = "regulator-fixed"; regulator-name = "vcc-csi"; regulator-min-microvolt = <2800000>; regulator-max-microvolt = <2800000>; gpio = <&pio 6 11 0>; /* PG11 */ enable-active-high; regulator-boot-on; regulator-always-on; }; reg_vcc_af_csi: vcc-af-csi { compatible = "regulator-fixed"; regulator-name = "vcc-af-csi"; regulator-min-microvolt = <2800000>; regulator-max-microvolt = <2800000>; gpio = <&pio 0 17 0>; /* PA17 */ enable-active-high; regulator-boot-on; regulator-always-on; }; }; After applying the overlay and rebooting, I can use lsmod to see the camera driver: lsmod | grep "ov5640" ov5640 28672 1 v4l2_fwnode 24576 2 ov5640,sun6i_csi v4l2_async 20480 3 ov5640,v4l2_fwnode,sun6i_csi And I can use the media-ctl command to check the topology: media-ctl --device /dev/media1 --print-topology Media controller API version 5.15.69 Media device information ------------------------ driver sun6i-csi model Allwinner Video Capture Device serial bus info platform:1cb0000.camera hw revision 0x0 driver version 5.15.69 Device topology - entity 1: sun6i-csi (1 pad, 1 link) type Node subtype V4L flags 0 device node name /dev/video1 pad0: Sink <- "ov5640 0-003c":0 [ENABLED] - entity 5: ov5640 0-003c (1 pad, 1 link) type V4L2 subdev subtype Sensor flags 0 device node name /dev/v4l-subdev0 pad0: Source [fmt:UYVY8_2X8/640x480@1/30 field:none colorspace:srgb xfer:srgb ycbcr:601 quantization:full-range] -> "sun6i-csi":0 [ENABLED] However, when I try to use the command to set 1920x1080, it fails: media-ctl --device /dev/media1 --set-v4l2 '"ov5640 1-003c":0[fmt:UYVY8/1920x1080]' Unable to setup formats: Invalid argument (22) I've been staring at the help output for media-ctl but I'm in over my head with this one. I also tried poking around with v4l2-ctl but nothing there seems to be working. Here is the result of a v4l2-ctl --info command: Driver Info: Driver name : cedrus Card type : cedrus Bus info : platform:cedrus Driver version : 5.15.74 Capabilities : 0x84208000 Video Memory-to-Memory Streaming Extended Pix Format Device Capabilities Device Caps : 0x04208000 Video Memory-to-Memory Streaming Extended Pix Format Media Driver Info: Driver name : cedrus Model : cedrus Serial : Bus info : platform:cedrus Media version : 5.15.74 Hardware revision: 0x00000000 (0) Driver version : 5.15.74 Interface Info: ID : 0x0300000c Type : V4L Video Entity Info: ID : 0x00000001 (1) Name : cedrus-source Function : V4L2 I/O Pad 0x01000002 : 0: Source Link 0x02000008: to remote pad 0x1000004 of entity 'cedrus-proc' (Video Decoder): Data, Enabled, Immutable What am I still missing?

Hello, I am using armbian on banana pi m2 zero uname -a Linux bananapim2zero 5.16.11-sunxi #22.02.1 SMP Sun Feb 27 09:17:03 UTC 2022 armv7l armv7l armv7l GNU/Linux I want to rebuild kernel, but i cannot find kernel source. Where I can find it? This code from https://wvthoog.nl/nanopi-ov5640-camera/#OV5640_sensor doesn`t work sudo apt update sudo apt upgrade sudo apt install build-essential uname -r # check your current kernel version sudo apt install linux-source-<your current kernel version> In my case: sudo apt install linux-source-5.8.6-current-sunxi cd /usr/src sudo tar xf linux-source-5.8.6-sunxi.tar.xz