/dev/video[01]?

avaf · April 8, 2024, 10:12pm

I don’t see anything wrong with the dts.

Unfortunately, I can’t help much, my whole setup is based on 5.10 due to using libmali, i can’t just switch kernel as you can with Armbian.

What i know is these guys are actively working on the rockchip media and perhaps they have up-to-date documentation (or they can talk to rockchip directly) and can give you some inside information.
@nyanmisaka @amazingfate

I think you are right.
If you want to debug the kernel: (https://github.com/armbian/linux-rockchip/blob/rk-6.1-rkr1/drivers/media/platform/rockchip/cif/capture.c#L6405)

I will follow the conversation…

Oskar_Enoksson · April 9, 2024, 3:33am

Thanks. Yes amazingfate usually answers on discord armbian-rockchip channel. I’ll try to contact him there too.

Update: since this CIF and ISP driver/sdk software is Rockchips work their staff should be most suited for solving it. I sent an email to someone there.

belveder79 · May 12, 2024, 4:13pm

@avaf @Oskar_Enoksson did you find a solution to the problem? I’m facing the same on a different SBC, however, my overlay for cameras works on 5.1.160 kernel but fails on both 6.1.y kernel from friendlyelec and also 6.1.57 armbian kernel…

avaf · May 12, 2024, 6:41pm

I have reserved my ready-to-fire image with kernel 6.1 to Rock 5C but no sign of the board being delivered any time soon. I am waiting for a few SD card to arrive soon and then i will try on Rock 5B. I think OrangePi has kernel 6.6 , have you tried that kernel version?

Oskar_Enoksson · May 12, 2024, 9:26pm

I still have the same problem. The camera overlay works for me though, it is just the video processing drivers that don’t work (with armbian 6.1 vendor kernel that is, the 5.10 vendor kernel works).

I opened issues here and here but no solution yet.

Note that you must have “vendor” kernel and the only existing versions are 5.10 and 6.1 for all I know. The mainline 6.1 or 6.6 or any other kernel can’t use the MIPI/CSI camera as far as I know because the functionality is not yet implemented there. Collabora has it on their TODO list but I hear that they are not as focused on rockchip development lately.

avaf · May 12, 2024, 9:39pm

Please, disregard this info.

belveder79 · May 13, 2024, 6:35am

thx for the info, at least I’m not alone

avaf · June 11, 2024, 11:50pm

FYI
I don’t know if you have found a solution to the issue with kernel 6.1 but it is working on rock-5c.

rock@rock-5c:~$ ./capture -d /dev/video11 -f NV12 -K 400 -c 500 -s 1920x1080
HDMI-A-1 -> connected
rga_api version 1.10.0_[9]
frameSize: 6220800, srcWidth: 1920, srcHeight: 1080
rock@rock-5c:~$ ls *.png
screenshot_1920x1080.png
rock@rock-5c:~$ ./capture -d /dev/video11 -f NV12 -c 2000 -s 1920x1080
HDMI-A-1 -> connected
rga_api version 1.10.0_[9]
rock@rock-5c:~$ uname -ra
Linux rock-5c 6.1.43-10-rk2312 #eb3b42978 SMP Fri Jun  7 02:38:46 UTC 2024 aarch64 GNU/Linux
rock@rock-5c:~$ v4l2-ctl -d /dev/video11 --get-fmt-video
Format Video Capture Multiplanar:
	Width/Height      : 1920/1080
	Pixel Format      : 'NV12' (Y/UV 4:2:0)
	Field             : None
	Number of planes  : 1
	Flags             : 
	Colorspace        : Default
	Transfer Function : Default
	YCbCr/HSV Encoding: Default
	Quantization      : Full Range
	Plane 0           :
	   Bytes per Line : 1920
	   Size Image     : 3110400
rock@rock-5c:~$

belveder79 · March 19, 2025, 1:47pm

it’s been a while, however I just retried this on 6.1.99 armbian kernel today and found the issue to still be there… @Oskar_Enoksson did you ultimately find a fix?

belveder79 · March 21, 2025, 7:31am

@avaf just to be on the same side - this test captures from HDMI-IN, right? In @Oskar_Enoksson and my case we want to capture from a MIPI CAM…

Oskar_Enoksson · March 21, 2025, 8:38am

I also tried it again a month ago, on latest kernel 6.1, same issue. I’m also trying to capture from a MIPI camera on the Rock5A, and trying to take advantage of the hardware rescaling ISP block in the CPU.

I think @avaf captures video on the device which is directly connected to the camera, i.e. without passing it through the ISP. I’m able to do that too, with the cameras native resolution and output format.

A few things do work, but it’s very shaky. Fiddling with v4l often hangs the system requiring reboot.

avaf · March 21, 2025, 12:26pm

Yes. I mean it works on HDMI-IN as well.

The Kernel 6.1.x is running on Rock 5C, not Rock 5A. I think there are some minor differences regarding the MIPI connection on 5A. My advice is to use vendor kernel 6.1.43, find the correct DTS and then move on to newer kernel.

FYI
Kernel 6.1.x on Rock 5B is using CAMERAOUT_M3 / mipim0_camera3
Kernel 6.1.x on Rock 5C is using CAMERAOUT_M2 / mipim0_camera2

I think Rock 5A is more like Rock 5B than 5C.

belveder79 · March 21, 2025, 1:54pm

@Oskar_Enoksson yes I verified that capturing the native raw data works fine for me as well, but the connection to the ISP is simply not there, so the /dev/v4l-subdev4 is not there…

@avaf I’m on the NanoPC-T6 actually, but it is exactly the same problem that Oskar has described… my setup is just either one single 4-lane OV4689 on csi0, or two 4-lane OV4689 on csi0 and csi1 - DeviceTree works on 5.10.160 fine, does not on 6.1.99

Oskar_Enoksson · March 22, 2025, 7:01am

@avaf not sure I understand you right, but I am running Armbians “6.1.99-vendor-rk35xx” kernel on my Rock-5A (I understand you have Rock-5C and that there are differences, but Armbian has some sort of “unsupported inofficial support” for Rock-5A with a working devicetree). If you talk about mainline kernel I think RKISP support is one of the things that is unfortunately still not implemented there.

But does anyone know: is the idea that the desired connections between the video blocks of this CPU can be changed/configured in the devicetree? If so maybe that is the missing key to success?

avaf · March 22, 2025, 12:10pm

I meant Radxa official OS. (6.1.43)
Interestingly, people with Rock 5A are silent about kernel 6.1 and the camera.

If i recall correctly, i had this issue when i tried rockchip 6.1.57 with the wrong camera engine.

FYI:
According to Rock 5A overlay, it uses CAMARAOUT_M2 and camera2_clk, same as Rock 5C (CSI2), did you try with this configuration?

mark_chang · May 19, 2025, 2:27pm

Hi to all there, I think I’m also facing the exact same question
I am trying to attach a pi-4 compatible tc35874 to capture hdmi via csi input
(I am trying to do streaming hdmi project, RK3566 with radxa zero 3w works but only smooth at 1080p50 with audio, 1080p60 without audio)
here is my current dts i tried, now with armbian and kernel 6.1.99-vendor-rk35xx

markchang@rock-5c:~/dtb$ cat tc358743-hdmi-in.dts
/dts-v1/;
/plugin/;

/ {

    metadata {
        title = "TC358743 HDMI RX";
        compatible = "radxa,zero3";
        description = "Allow use of TC358743 HDMI -> CSI2 input.";
        category = "video";
    };

        fragment@0 {
                target-path = "/";

                __overlay__ {
                        clk_cam_27m: external-camera-clock-27m {
                                status = "okay";
                                compatible = "fixed-clock";
                                clock-frequency = <27000000>;
                                clock-output-names = "clk_cam_27mhz";
                                #clock-cells = <0>;
                        };

                        camera_pwdn_gpio: camera-pwdn-gpio {
                                status = "okay";
                                compatible = "regulator-fixed";
                                regulator-name = "camera_pwdn_gpio";
                                regulator-always-on;
                                regulator-boot-on;
                                enable-active-high;
                                gpio = <&gpio1 27 0>; // <&gpio1 RK_PD3 GPIO_ACTIVE_HIGH>;
                        };
                };
        };

        fragment@1 {
                target = <&i2c3>;

                __overlay__ {
                        status = "okay";
                        pinctrl-names = "default";
                        pinctrl-0 = <&i2c3m0_xfer>;
                        #address-cells = <1>;
                        #size-cells = <0>;

                        camera_tc358743: tc358743@f {
                                status = "okay";
                                compatible = "toshiba,tc358743";
                                reg = <0x0f>;
                                clocks = <&clk_cam_27m>;
                                clock-names = "refclk";
                                rockchip,camera-module-index = <0>;
                                rockchip,camera-module-facing = "back";
                                rockchip,camera-module-name = "tc358743";
                                rockchip,camera-module-lens-name = "default";
                                port {
                                        hdmi_rx_out: endpoint {
                                                remote-endpoint = <&mipi_in_hdmirx0>;
                                                clock-lanes = <0>;
                                                clock-noncontinuous;
                                                link-frequencies = /bits/ 64 <297000000>;
                                                data-lanes = <1 2>;
                                        };
                                };
                        };
                };
        };

        fragment@2 {
                target = <&csi2_dphy0_hw>;

                __overlay__ {
                        status = "okay";
                };
        };

        fragment@3 {
                target = <&csi2_dphy0>;

                __overlay__ {
                        status = "okay";

                        ports {
                                #address-cells = <1>;
                                #size-cells = <0>;

                                port@0 {
                                        reg = <0>;
                                        #address-cells = <1>;
                                        #size-cells = <0>;
                                        mipi_in_hdmirx0: endpoint@2 {
                                                reg = <2>;
                                                remote-endpoint = <&hdmi_rx_out>;
                                                data-lanes = <1 2>;
                                        };
                                };
                                port@1 {
                                        reg = <1>;
                                        #address-cells = <1>;
                                        #size-cells = <0>;

                                        mipi_out_dphy0: endpoint@0 {
                                                reg = <0>;
                                                remote-endpoint = <&mipi2_csi2_input>;
                                        };
                                };
                        };
                };
        };

        fragment@4 {
                target = <&mipi2_csi2>;

                __overlay__ {
                        status = "okay";
                        ports {
                                #address-cells = <1>;
                                #size-cells = <0>;

                                port@0 {
                                        reg = <0>;
                                        #address-cells = <1>;
                                        #size-cells = <0>;

                                        mipi2_csi2_input: endpoint@1 {
                                                reg = <1>;
                                                remote-endpoint = <&mipi_out_dphy0>;
                                        };
                                };
                                port@1 {
                                        reg = <1>;
                                        #address-cells = <1>;
                                        #size-cells = <0>;

                                        mipi2_csi2_output: endpoint@0 {
                                                reg = <0>;
                                                remote-endpoint = <&cif_mipi2_in0>;
                                        };
                                };
                        };
                };

        };

        fragment@5 {
                target = <&rkcif>;

                __overlay__ {
                        status = "okay";
                };
        };

        fragment@6 {
                target = <&rkcif_mipi_lvds2>;

                __overlay__ {
                        status = "okay";
                        port {
                                cif_mipi2_in0: endpoint {
                                        remote-endpoint = <&mipi2_csi2_output>;
                                };
                        };
                };

        };

        fragment@7 {
                target = <&rkcif_mipi_lvds2_sditf>;

                __overlay__ {
                        status = "okay";
                        port {
                                mipi_lvds2_sditf: endpoint {
                                        remote-endpoint = <&isp0_vir0>;
                                };
                        };
                };
        };

        fragment@8 {
                target = <&rkcif_mmu>;

                __overlay__ {
                        status = "okay";
                };
        };

        fragment@9 {
                target = <&isp0_mmu>;

                __overlay__ {
                        status = "okay";
                };
        };

        fragment@10 {
                target = <&rkisp0>;

                __overlay__ {
                        status = "okay";
                };
        };

        fragment@11 {
                target = <&rkisp0_vir0>;

                __overlay__ {
                        status = "okay";
                        port {
                                #address-cells = <1>;
                                #size-cells = <0>;

                                isp0_vir0: endpoint@0 {
                                        reg = <0>;
                                        remote-endpoint = <&mipi_lvds2_sditf>;
                                };
                        };
                };
        };

};

if i try with capturing with video0

[  157.283083] rkisp0-vir0: check rkisp_mainpath link or isp input
[  160.259074] rkisp0-vir0: check rkisp_mainpath link or isp input
[  274.616171] rkisp0-vir0: rkisp_mainpath nonsupport pixelformat:YU12
[  274.618359] rkisp0-vir0: rkisp_mainpath nonsupport pixelformat:YU12
[  274.618380] rkisp0-vir0: rkisp_mainpath nonsupport pixelformat:YV12
[  274.618396] rkisp0-vir0: rkisp_mainpath nonsupport pixelformat:422P
[  274.618410] rkisp0-vir0: rkisp_mainpath nonsupport pixelformat:YUYV
[  274.690757] rkisp0-vir0: check rkisp_mainpath link or isp input
[  278.913394] rkisp0-vir0: rkisp_mainpath nonsupport pixelformat:YU12
[  278.913529] rkisp0-vir0: rkisp_mainpath nonsupport pixelformat:YU12
[  278.913567] rkisp0-vir0: rkisp_mainpath nonsupport pixelformat:YV12
[  278.913600] rkisp0-vir0: rkisp_mainpath nonsupport pixelformat:422P
[  278.913632] rkisp0-vir0: rkisp_mainpath nonsupport pixelformat:YUYV
[  279.005119] rkisp0-vir0: check rkisp_mainpath link or isp input

then i tried with video9 where it goes through rkcif

[  331.728371] rkcif-mipi-lvds2: stream[0] start streaming
[  331.730809] rkcif-mipi-lvds2: Allocate dummy buffer, size: 0x003f5000
[  331.730840] rkcif-mipi-lvds2: can not find output format: 0x32315559
[  331.733805] rockchip-mipi-csi2 mipi2-csi2: stream on, src_sd: 000000006775881a, sd_name:rockchip-csi2-dphy0
[  331.733835] rockchip-mipi-csi2 mipi2-csi2: stream ON
[  331.733895] rockchip-csi2-dphy0: dphy0, data_rate_mbps 620
[  331.733938] rockchip-csi2-dphy csi2-dphy0: csi2_dphy_s_stream stream on:1, dphy1, ret 0
[  336.173206] rkcif-mipi-lvds2: stream[0] start stopping, total mode 0x1, cur 0x1
[  336.173233] rkcif-mipi-lvds2: get vblank fail, vblank_def 0, vblank_curr 0
[  336.688102] rockchip-mipi-csi2 mipi2-csi2: stream off, src_sd: 000000006775881a, sd_name:rockchip-csi2-dphy0
[  336.688128] rockchip-mipi-csi2 mipi2-csi2: stream OFF

is going back to kernel 5.10 vender a good try? or is there a fix?

belveder79 · September 25, 2025, 8:55am

@avaf @Oskar_Enoksson do we know if this is now fixed in the 6 kernel version?

avaf · September 26, 2025, 1:17pm

I can confirm Rock 5B (16GB and 4GB), Rock 5C-lite (2GB), and Rock 5C (4GB) with kernel 6.1.43 work with the camera. Note that it is my custom build image, but I don’t see any impediment with the Radxa Image or Armbian.
I don’t have Rock 5A despite having applied for it on the early bid (reserved one but opted for the Rock 5C due to import tax issues). Perhaps it shares the I2C bus with another device.

belveder79 · September 26, 2025, 8:23pm

… interesting. I’m on a NanoPC T6 but I see exactly the same error all this thread started about…

@mark_chang did you solve that problem?

avaf · September 27, 2025, 12:02am

NanoPC T6 dual ov4689 kernel 6.1.43, video streaming over wifi