UNSOLVED radxa zero 3e, yocto linux 6.13, imx287
-
Hi,
I'm trying to follow this instruction to compile veye imx287m for yocto linux 6.13, but it seems it's not fully compatible with this kernel version
https://github.com/veyeimaging/rk35xx_radxa/tree/main/linux/drivers
| SYNC include/config/auto.conf | GEN Makefile | DTC arch/arm64/boot/dts/rockchip/rk3566-radxa-zero-3e.dtb | Error: /home/user/radxa/zero3e/yocto/build/workspace/sources/linux-torvalds-next/arch/arm64/boot/dts/rockchip/rk3566-radxa-zero3-veyemvcam.dtsi:7.1-12 Label or path csi2_dphy0 not found | Error: /home/user/radxa/zero3e/yocto/build/workspace/sources/linux-torvalds-next/arch/arm64/boot/dts/rockchip/rk3566-radxa-zero3-veyemvcam.dtsi:37.1-12 Label or path csi2_dphy1 not found | Error: /home/user/radxa/zero3e/yocto/build/workspace/sources/linux-torvalds-next/arch/arm64/boot/dts/rockchip/rk3566-radxa-zero3-veyemvcam.dtsi:41.1-12 Label or path csi2_dphy2 not found | Error: /home/user/radxa/zero3e/yocto/build/workspace/sources/linux-torvalds-next/arch/arm64/boot/dts/rockchip/rk3566-radxa-zero3-veyemvcam.dtsi:45.1-14 Label or path csi2_dphy_hw not found | Error: /home/user/radxa/zero3e/yocto/build/workspace/sources/linux-torvalds-next/arch/arm64/boot/dts/rockchip/rk3566-radxa-zero3-veyemvcam.dtsi:85.1-11 Label or path mipi_csi2 not found | Error: /home/user/radxa/zero3e/yocto/build/workspace/sources/linux-torvalds-next/arch/arm64/boot/dts/rockchip/rk3566-radxa-zero3-veyemvcam.dtsi:116.1-7 Label or path rkcif not found | Error: /home/user/radxa/zero3e/yocto/build/workspace/sources/linux-torvalds-next/arch/arm64/boot/dts/rockchip/rk3566-radxa-zero3-veyemvcam.dtsi:120.1-17 Label or path rkcif_mipi_lvds not found | Error: /home/user/radxa/zero3e/yocto/build/workspace/sources/linux-torvalds-next/arch/arm64/boot/dts/rockchip/rk3566-radxa-zero3-veyemvcam.dtsi:129.1-23 Label or path rkcif_mipi_lvds_sditf not found | Error: /home/user/radxa/zero3e/yocto/build/workspace/sources/linux-torvalds-next/arch/arm64/boot/dts/rockchip/rk3566-radxa-zero3-veyemvcam.dtsi:133.1-11 Label or path rkcif_mmu not found | Error: /home/user/radxa/zero3e/yocto/build/workspace/sources/linux-torvalds-next/arch/arm64/boot/dts/rockchip/rk3566-radxa-zero3-veyemvcam.dtsi:136.1-7 Label or path rkisp not found | Error: /home/user/radxa/zero3e/yocto/build/workspace/sources/linux-torvalds-next/arch/arm64/boot/dts/rockchip/rk3566-radxa-zero3-veyemvcam.dtsi:140.1-12 Label or path rkisp_vir0 not found | Error: /home/user/radxa/zero3e/yocto/build/workspace/sources/linux-torvalds-next/arch/arm64/boot/dts/rockchip/rk3566-radxa-zero3-veyemvcam.dtsi:144.1-12 Label or path rkisp_vir1 not found | Error: /home/user/radxa/zero3e/yocto/build/workspace/sources/linux-torvalds-next/arch/arm64/boot/dts/rockchip/rk3566-radxa-zero-3e.dts:19.1-12 Label or path rgmii_phy1 not found | FATAL ERROR: Syntax error parsing input treeand I cannot find things like mipi_csi2 in these files:
commit in yocto layer
meta-rockchipsays that radxa 3e requires the latest kernel:https://github.com/radxa/meta-rockchip
git show e0b13fe8 ... NOTE: currently support for this board requires a U-Boot fork for the bootloader, and linux-next for the kernel. Support will probably come in linux kernel 6.11-ish, at which point U-Boot will then use that kernel's device tree which means U-Boot support will come after the release of whichever kernel includes support for this board.this email also says that kernel versions below 6.9 do not support radxa zero 3 devices, so I'm wondering how it is possible to use 5.10 which is mentioned in your instructions
https://lists.yoctoproject.org/g/yocto-patches/topic/kernel_and_u_boot_version/111621524
could please anyone tell if there is an easy way to adopt dtsi for 6.13 kernel version?
thanks
-
We have released a Debian installation package that supports Radxa Zero 3E. Please check the link below. Of course, this is based on the kernel 5.10 version.
https://github.com/veyeimaging/rk35xx_radxa/releases/tag/v1.2
-
@veye_xumm yeah, I know that and I mentioned it in my question
And, as I mentioned, I cannot use it, so the question is not about the list of currently supported kernel versions, but how to use your camera on yocto, especially: how to adopt dtsi for 6.13 or how to use 5.10/6.1 kernels with yocto and radxa zero 3e
-
@nkos Understood, I will arrange to interface with the new version of the kernel. It will take a few days.
-
@veye_xumm that would be great, thank you very much in advance
-
@veye_xumm could you please tell if there are any updates?
-
@nkos Apologies for the delay. I've just returned from the National Day holiday and will follow up on this matter as soon as possible.
-
@nkos Our driver code is developed based on Radxa's BSP, and the BSP development documentation can be found at the following URL:
https://docs.radxa.com/en/zero/zero3/low-level-dev/kernelTo address the issue you raised, we attempted to set up a Yocto development environment for the Radxa ZERO 3. Unfortunately, we were unsuccessful in this endeavor.
Later, we noticed Radxa's documentation regarding building Linux images with Yocto:
https://github.com/radxa/yocto-manifestsIn the "List of Radxa Boards supported" section, the Radxa ZERO 3 is not listed among the supported development boards.
Therefore, we do not recommend using Yocto to build a Linux image for the Radxa ZERO 3.
-
I wonder if there are other options to build newer kernels for radxa zero 3e. Building yocto to adopt the driver to a particular kernel version looks like an overkill and I cannot ask you to do that
Just in case you're interested, I've prepared a small guide showing how to build yocto for radxa zero 3e:
https://kostovsky.me/blog/yocto_qt_on_radxa_zero_3e/
I'll try stock radxa distro
-
@nkos I will attempt to build a 6.x version system based on the original BSP approach.
-
@veye_xumm hi, did you have any chance to take a look at this? it would be nice to have an easy option to modify and build driver with up to date kernel on current radxa debian and/or on yocto
the main goal I'm trying to achieve is to configure any registers that aren't available in your kernel's driver (a lot of them)
for example, the flash delay relative to the input trigger (if it's possible at all, it could be very useful in laser devices; negative or positive - not so important)