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.

[opi-5-plus-user]

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

 

[opi-5-plus-user]

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

 

[opi-5-plus-user]

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