opi-5-plus-user

I have tried to get the CSI port working on my Radxa Zero 3W with the GEEKOM X1301 HAT, and now I can get the chip to show up in /dev, however there seems to be an issue when I try to access it, as I keep getting ioctl errors. I started by copying over the .dtbo files from the regular radxa official image, and putting them into the overlay-user folder in /boot. Then I enabled the radxa-zero3-tc358743.dtbo overlay, which gets the devices to show up. I am following this guide from GEEKOM https://wiki.geekworm.com/X1300_Software, however, I keep getting ioctl errors when trying to set the EDID file on the Radxa Zero. On the Raspberry Pi, this was not an issue. Here is the output of my media-ctl: media-ctl -d /dev/media0 -p Media controller API version 6.1.115 Media device information ------------------------ driver rkisp-vir0 model rkisp0 serial bus info platform:rkisp-vir0 hw revision 0x0 driver version 6.1.115 Device topology - entity 1: rkisp-isp-subdev (4 pads, 8 links, 0 routes) type V4L2 subdev subtype Unknown flags 0 device node name /dev/v4l-subdev0 pad0: SINK,MUST_CONNECT [stream:0 fmt:UYVY8_2X8/640x480 field:none colorspace:srgb crop.bounds:(0,0)/640x480 crop:(0,0)/640x480] <- "rkisp-csi-subdev":1 [ENABLED] <- "rkisp_rawrd0_m":0 [] <- "rkisp_rawrd2_s":0 [] pad1: SINK <- "rkisp-input-params":0 [ENABLED] pad2: SOURCE [stream:0 fmt:YUYV8_2X8/640x480 field:none colorspace:smpte170m quantization:full-range crop.bounds:(0,0)/640x480 crop:(0,0)/640x480] -> "rkisp_mainpath":0 [ENABLED] -> "rkisp_selfpath":0 [ENABLED] -> "rkisp_iqtool":0 [ENABLED] pad3: SOURCE -> "rkisp-statistics":0 [ENABLED] - entity 6: rkisp-csi-subdev (6 pads, 5 links, 0 routes) type V4L2 subdev subtype Unknown flags 0 device node name /dev/v4l-subdev1 pad0: SINK,MUST_CONNECT [stream:0 fmt:UYVY8_2X8/640x480 field:none colorspace:srgb] <- "rockchip-csi2-dphy0":1 [ENABLED] pad1: SOURCE,MUST_CONNECT [stream:0 fmt:UYVY8_2X8/640x480 field:none colorspace:srgb] -> "rkisp-isp-subdev":0 [ENABLED] pad2: SOURCE -> "rkisp_rawwr0":0 [ENABLED] pad3: SOURCE pad4: SOURCE -> "rkisp_rawwr2":0 [ENABLED] pad5: SOURCE -> "rkisp_rawwr3":0 [ENABLED] - entity 13: rkisp_mainpath (1 pad, 1 link) type Node subtype V4L flags 0 device node name /dev/video0 pad0: SINK <- "rkisp-isp-subdev":2 [ENABLED] - entity 19: rkisp_selfpath (1 pad, 1 link) type Node subtype V4L flags 0 device node name /dev/video1 pad0: SINK <- "rkisp-isp-subdev":2 [ENABLED] - entity 25: rkisp_rawwr0 (1 pad, 1 link) type Node subtype V4L flags 0 device node name /dev/video2 pad0: SINK <- "rkisp-csi-subdev":2 [ENABLED] - entity 31: rkisp_rawwr2 (1 pad, 1 link) type Node subtype V4L flags 0 device node name /dev/video3 pad0: SINK <- "rkisp-csi-subdev":4 [ENABLED] - entity 37: rkisp_rawwr3 (1 pad, 1 link) type Node subtype V4L flags 0 device node name /dev/video4 pad0: SINK <- "rkisp-csi-subdev":5 [ENABLED] - entity 43: rkisp_iqtool (1 pad, 1 link) type Node subtype V4L flags 0 device node name /dev/video5 pad0: SINK <- "rkisp-isp-subdev":2 [ENABLED] - entity 49: rkisp_rawrd0_m (1 pad, 1 link) type Node subtype V4L flags 0 device node name /dev/video6 pad0: SOURCE -> "rkisp-isp-subdev":0 [] - entity 55: rkisp_rawrd2_s (1 pad, 1 link) type Node subtype V4L flags 0 device node name /dev/video7 pad0: SOURCE -> "rkisp-isp-subdev":0 [] - entity 61: rkisp-statistics (1 pad, 1 link) type Node subtype V4L flags 0 device node name /dev/video8 pad0: SINK <- "rkisp-isp-subdev":3 [ENABLED] - entity 67: rkisp-input-params (1 pad, 1 link) type Node subtype V4L flags 0 device node name /dev/video9 pad0: SOURCE -> "rkisp-isp-subdev":1 [ENABLED] - entity 73: rockchip-csi2-dphy0 (2 pads, 2 links, 0 routes) type V4L2 subdev subtype Unknown flags 0 device node name /dev/v4l-subdev2 pad0: SINK,MUST_CONNECT [stream:0 fmt:UYVY8_2X8/640x480@10000/600000 field:none colorspace:srgb] <- "m00_b_tc35874x 2-000f":0 [ENABLED] pad1: SOURCE,MUST_CONNECT -> "rkisp-csi-subdev":0 [ENABLED] - entity 76: m00_b_tc35874x 2-000f (1 pad, 1 link, 0 routes) type V4L2 subdev subtype Sensor flags 0 device node name /dev/v4l-subdev3 pad0: SOURCE [stream:0 fmt:UYVY8_2X8/640x480@10000/600000 field:none colorspace:srgb] [dv.caps:BT.656/1120 min:1x1@0 max:10000x10000@310000000 stds:CEA-861,DMT,CVT,GTF caps:interlaced,progressive,reduced-blanking,custom] [dv.query:no-link] [dv.current:BT.656/1120 640x480p59 (800x525) stds:CEA-861,DMT flags:has-cea861-vic] -> "rockchip-csi2-dphy0":0 [ENABLED] The GEEKOM does seem to require some GPIOs, as shown in the second picture from this link https://geekworm.com/products/x1301, however, these all seem to be for audio functionality, which I have disabled. I currently only have the GEEKOM X1301 connected through the CSI Port to the Radxa Zero, as it physically cannot have the GPIOs and the CSI port connected at the same time. Here is the output of my /dev folder autofs crypto fuse hugepages input loop3 mem port rga stdout tty13 tty20 tty28 tty35 tty42 tty5 tty57 tty7 urandom vcs2 vcsa3 vcsu4 video0 video8 block cuse gpiochip0 hwrng iomux loop4 mmcblk1 ppp rk_cec sw_sync tty14 tty21 tty29 tty36 tty43 tty50 tty58 tty8 v4l vcs3 vcsa4 vcsu5 video1 video9 btrfs-control disk gpiochip1 i2c-0 kmsg loop5 mmcblk1p1 psaux rtc tty tty15 tty22 tty3 tty37 tty44 tty51 tty59 tty9 v4l-subdev0 vcs4 vcsa5 vcsu6 video2 watchdog bus dma_heap gpiochip2 i2c-2 kvm loop6 mmcblk1p2 ptmx rtc0 tty0 tty16 tty23 tty30 tty38 tty45 tty52 tty6 ttyFIQ0 v4l-subdev1 vcs5 vcsa6 vfio video3 watchdog0 cec0 dri gpiochip3 i2c-3 log loop7 mpp_service pts shm tty1 tty17 tty24 tty31 tty39 tty46 tty53 tty60 ttyS1 v4l-subdev2 vcs6 vcsu vga_arbiter video4 zero char fb0 gpiochip4 i2c-6 loop0 loop-control mqueue ram0 snd tty10 tty18 tty25 tty32 tty4 tty47 tty54 tty61 ubi_ctrl v4l-subdev3 vcsa vcsu1 vhci video5 zram0 console fd gpiochip5 iio:device0 loop1 mapper net random stderr tty11 tty19 tty26 tty33 tty40 tty48 tty55 tty62 uhid vcs vcsa1 vcsu2 vhost-net video6 zram1 cpu_dma_latency full hdmi_hdcp1x initctl loop2 media0 null rfkill stdin tty12 tty2 tty27 tty34 tty41 tty49 tty56 tty63 uinput vcs1 vcsa2 vcsu3 vhost-vsock video7 zram2 This is the error that I get when I run the command to set the EDID file. v4l2-ctl -d /dev/v4l-subdev3 --set-edid=file=1080P60EDID.txt VIDIOC_SUBDEV_S_CLIENT_CAP: failed: Inappropriate ioctl for device Is there any way that I can resolve this issue? The HAT's power LED doesn't light up for some reason, and the device also isn't detected when I plug in any other devices HDMI out into the HDMI IN on the HAT.

Update: It works now, however the power LED doesn't seem to light up, but the video card is detected in /dev

Okay I found out that the previous error was mainly user error, due to an invalid user_overlays=, however I am facing a new issue and it still doesn't seem to work This is the new error Boot script loaded from mmc 1:1 308 bytes read in 2 ms (150.4 KiB/s) 14207910 bytes read in 1182 ms (11.5 MiB/s) 48779776 bytes read in 4043 ms (11.5 MiB/s) 161122 bytes read in 26 ms (5.9 MiB/s) Working FDT set to a100000 3772 bytes read in 4 ms (920.9 KiB/s) Applying user provided DT overlay radxa-zer5028 bytes read in 8 ms (613.3 KiB/s) Applying user provided DT overlay radxa-zero3-tc358743-audio.dtbo Trying kaslrseed command... Info: Unknown command can be safely ignored since ot apply to all boards. Unknown command 'kaslrseed' - try 'help' Moving Image from 0x2080000 to 0x220## Loading init Ramdisk from Legacy Image at 0a200000 ... Imagpe: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 14207846 Bytes = 13.5 MiB Loadoint: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 0a100000 Booting using the fdt blob at 0xa100000 Working FDT set Loading Ramdisk to 7c133000, end 7cebfb66 ... OK I'm not sure why it is saying it is loading radxa-zer5028 when that is clearly not what is listed in armbianEnv.txt This is what is in armbianEnv user_overlays=radxa-zero3-tc358743 radxa-zero3-tc358743-audio

After checking uboot logs, it shows that it fails to load the dtbo files, although I'm not sure what the error is. ** Booting bootflow 'mmc@fe2b0000.bootdev.part_1' with script Boot script loaded from mmc 1:1 308 bytes read in 2 ms (150.4 KiB/s) 14207910 bytes read in 1182 ms (11.5 MiB/s) 48779776 bytes read in 4043 ms (11.5 MiB/s) 161122 bytes read in 26 ms (5.9 MiB/s) Working FDT set to a100000 Failed to load '/overlay-user/radxa-zero3-tc358743,radxa-zero3-tc358743-audio.dtbo' Trying kaslrseed command... Info: Unknown command can be safely ignored sincelrseed does not apply to all boards. Unknown command 'kaslrseed' - try 'help' Moving Image from 0x20840000 ## Loading init Ramdisk from Legacy Image at 0a200000 ... Image : AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 14207846 Bytes = 13.5 MiB Load Address: 00000int: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 0a100000 Booting using the fdt blob at 0xa100000 Working FDT set to a100000 Loading Ramdisk to 7c133000, end 7cebfb66 ... OK ERROR: reserving fdt memory region failed (addr=0 size=0 flags=0) ERROR: reserving fdt memory region failed (addr=0 size=0 flags=0) Loading Device Tree to 000000007c0a3000, end 000000007c132fff .OK Working FDT set to 7c0a3000

Yes. I check the dmesg logs and they aren't loading which is probably why it doesn't work, but I have tried a variety of methods to try and get them to load, however nothing worked.

Would you mind sharing the steps you took to enable csi camera support? I'm trying to enabled the CSI port on the Radxa Zero 3W for the TC358743, but I have been unable to make progress. I'm currently using a Geekom X1301 HAT for the CSI to HDMI adapter which uses the TC358743, but it never shows up. What I have tried so far is extracting the .dtbo files from the official radxa image. Adding them to /boot/overlay-user and enabling the two tc358743 overlays radxa-zero3-tc358743.dtbo radxa-zero3-tc358743-audio.dtbo and finally enabling them in armbianEnv.txt with this line user_overlays=radxa-zero3-tc358743,radxa-zero3-tc358743-audio Is there anything that I missed? The CSI port still doesn't seem to be receiving any power, as the X1301's power LED has been off the whole time.

I have run armbianmonitor and here is the paste: https://paste.armbian.com/oyajulusax

After enabling the rk3588-hdmirx overlay in armbian-config device tree overlays, whenever I boot, I am greeted with multiple hdmirx (fdee0000.hdmirx-controller: hdmirx_wait_lock_and_get_timing HDMI pull out, return!) errors on boot. On a previous install, the hdmirx errors would block the entire boot process and it would just hang forever. I do not know the exact cause, but the issues seemed to arise after I ran this command to disable the X Display Server "systemctl set-default multi-user.target". The errors could only be resolved if I plugged in the sd card into another device and removed rk3588-hdmirx from overlays in /boot/armbianEnv.txt . I have since reinstalled Armbian, but the errors still appear during the boot process, however now they do not block the boot process and I am able to successfully boot into Armbian. Is there any solution to get rid of these errors, or ensure that the "fdee0000.hdmirx-controller: hdmirx_wait_lock_and_get_timing HDMI pull out, return!" error doesn't block the boot process without disabling hdmirx? These are my current device details: .. orangepi@orangepi5-plus `:]x**j-,' ----------------------- .,+t***********z\<" OS: Armbian 25.5.1 noble aarch64 ?******************; Host: Orange Pi 5 Plus '*n` .'`^,;;,^`'. ,cc. Kernel: Linux 6.1.115-vendor-rk35xx -<. .[l Uptime: 30 mins // ^^ ^^ \\ Packages: 1822 (dpkg) !^ ^^ ": Shell: bash 5.2.21 'tt}` !~]rj_ ")t/. Display: 3840x2160 @ 60 Hz Itttt?' ~~]rr] `{tttt, DE: KDE Plasma 6.3.90 \tttttt!""I_]r("""~tttttt1 WM: KWin (Wayland) '_tttttttttttt)ftttttttttttti. WM Theme: Breeze \*ztttttttttttttttttttttttttf**[ Theme: Breeze (Dark) [Qt], Yaru [GTK3] l**c)tttttttttttttttttttttttt(z**, Icons: breeze-dark [Qt], Yaru [GTK3] .z*x.`tttttttttttttttttttttttt.`u*n Font: Noto Sans (10pt) [Qt] >` (tttttttttttttttttttttt] "I Cursor: breeze (24px) ,tttttttttttttttttttttt` Terminal: konsole 25.4.1 ./tttttfttttttttfttttt( CPU: rk3588 (8) @ 2.40 GHz 'I)))(\()(tt))|\()({;' GPU: Mesa Mali-G610 (Panfrost) .~~~~~~~|)~~~~~~~< Memory: 4.34 GiB / 15.58 GiB (28%) '[)))))1|()))))))? Swap: 0 B / 7.79 GiB (0%) ",,," ",,,^ Disk (/): 7.82 GiB / Here is the dmesg log after boot up, the hdmirx errors appear near the end: boot_errors.txt