invalid overlay_prefix rk35xx

[JIN PRO]

Hi everyone, I need to enable the csi camera and i2c port on my zero3 development board. When I click on the management overlay, an error occurs. Is there any solution?

[Werner]

Overlays can be added manually as well. Check /boot/armbianEnv.txt

[JIN PRO]

This is the default configuration:

verbosity=1
bootlogo=false
console=both
extraargs=cma=256M
overlay_prefix=rk35xx
fdtfile=rockchip/rk3566-radxa-zero3.dtb
rootdev=UUID=526007c3-3a0f-451d-a7a7-6d896d15f910
rootfstype=ext4
usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u

[Werner]

Yes. This is an example of a rk3588 based board of mine:

 

overlay_prefix=rockchip-rk3588
overlays=panthor-gpu opp-oc-24ghz

The overlay names come from /boot/dtb/*/

find an overlay matching your soc and needs and enable by putting its name to overlays=. Then reboot. Having a serial console to read uboot logs can show if it has been loaded properly or in case it did not why.

[JIN PRO]

It works, but I found that the i2c dtbo file I needed was not in the armbian repository, so I manually extracted it from the radxa official image.

[Werner]

Feel free to pr any missing overlay here: https://github.com/armbian/linux-rockchip

[opi-5-plus-user]

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.

[Werner]

Did you make sure they're actually loaded? Like by checking uboot boot logs via serial console?

[opi-5-plus-user]

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.

[Werner]

I wasn't talking about dmesg logs.