UNSOLVED OrangePi cm5-tablet RAW-MIPI-SC132M
-
This is the decompiled dts, which I modified (set i2c address to 0x3b and changed compatibility to veye,mvcam), compiled, then moved back into /boot/dtb*/rockchip/rk3588s-orangepi-cm5-tablet.dtb (faster than recompiling with orangepi-build)
sudo dmesg | grep ov5647 [ 6.594040] i2c i2c-6: of_i2c: modalias failure on /i2c@fec80000/ov5647-cam2@36 [ 6.594051] i2c i2c-6: Failed to create I2C device for /i2c@fec80000/ov5647-cam2@36 [ 6.594128] platform csi2-dcphy0: Fixed dependency cycle(s) with /i2c@fec80000/ov5647-cam2@3b [ 6.607375] i2c i2c-7: of_i2c: modalias failure on /i2c@fec90000/ov5647-cam3@36 [ 6.607381] i2c i2c-7: Failed to create I2C device for /i2c@fec90000/ov5647-cam3@36 [ 6.607412] platform csi2-dcphy1: Fixed dependency cycle(s) with /i2c@fec90000/ov5647-cam3@3bsudo dmesg | grep csi2-dcphy0 [ 5.600344] platform csi2-dcphy0: Fixed dependency cycle(s) with /mipi0-csi2 [ 6.594128] platform csi2-dcphy0: Fixed dependency cycle(s) with /i2c@fec80000/ov5647-cam2@3b [ 6.824192] rockchip-csi2-dphy csi2-dcphy0: csi2 dphy0 probe successfully!sudo dmesg | grep i2c [ 5.612002] platform fed80000.phy: Fixed dependency cycle(s) with /i2c@fec80000/fusb302@22/connector [ 6.408625] platform fc000000.usb: Fixed dependency cycle(s) with /i2c@fec80000/fusb302@22 [ 6.423672] i2c_dev: i2c /dev entries driver [ 6.584542] platform csi2-dphy0: Fixed dependency cycle(s) with /i2c@fea90000/ov13850-1@10 [ 6.584625] i2c i2c-1: 1 i2c clients have been registered at 0x0c [ 6.584679] platform csi2-dphy0: Fixed dependency cycle(s) with /i2c@fea90000/ov13855-1@36 [ 6.594013] i2c i2c-6: of_i2c: modalias failure on /i2c@fec80000/imx219-cam2@10 [ 6.594028] i2c i2c-6: Failed to create I2C device for /i2c@fec80000/imx219-cam2@10 [ 6.594040] i2c i2c-6: of_i2c: modalias failure on /i2c@fec80000/ov5647-cam2@36 [ 6.594051] i2c i2c-6: Failed to create I2C device for /i2c@fec80000/ov5647-cam2@36 [ 6.594128] platform csi2-dcphy0: Fixed dependency cycle(s) with /i2c@fec80000/ov5647-cam2@3b [ 6.607375] i2c i2c-7: of_i2c: modalias failure on /i2c@fec90000/ov5647-cam3@36 [ 6.607381] i2c i2c-7: Failed to create I2C device for /i2c@fec90000/ov5647-cam3@36 [ 6.607412] platform csi2-dcphy1: Fixed dependency cycle(s) with /i2c@fec90000/ov5647-cam3@3b [ 6.607497] platform csi2-dcphy1: Fixed dependency cycle(s) with /i2c@fec90000/imx219-cam3@10 [ 6.708500] [Awinic] [1-0059]aw87xxx_i2c_probe: succeed, dev_index=[0], g_aw87xxx_dev_cnt= [1] [ 6.709515] [Awinic] [1-005a]aw87xxx_i2c_probe: succeed, dev_index=[1], g_aw87xxx_dev_cnt= [2] -
@mparem
Please postdmesg | grep mvcamoutput here. -
sudo dmesg | grep mvcam [sudo] password for orangepi: [ 6.581083] platform csi2-dcphy0: Fixed dependency cycle(s) with /i2c@fec80000/mvcam2@3bsudo i2cdetect -y 6 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- UU -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- 6a -- -- -- -- -- 70: -- -- -- -- -- -- -- -- -
@mparem said in OrangePi cm5-tablet RAW-MIPI-SC132M:
his is the decompiled dts, which I modified (set i2c address to 0x3b and changed compatibility to veye,mvcam), compiled, then moved back into /boot/dtb*/rockchip/rk3588s-orangepi-cm5-tablet.dtb (faster than recompiling with orangepi-build)
I haven't used this method before, and I didn't quite understand your source code.
Now it seems the issue might still be with the DTS. I suggest you try editing the DTS source code using conventional methods. -
@veye_xumm
rk3588s-orangepi-cm5-tablet.dts.txtrk3588s-orangepi-cm5-tablet-camera2-veyemv.dtsi.txt
sudo dmesg | grep mvcam [ 6.458001] platform csi2-dcphy0: Fixed dependency cycle(s) with /i2c@fec80000/mvcam@3b -
@mparem
Since I don't have the tablet board here, the following is just a suggested approach based on my guess. You can try commenting out the following two lines or modifying them as shown below:clocks = <&ext_cam_ov5647_clk>; clock-names = "xvclk"; -
@veye_xumm
I received the cm5-base board today, attempted to connect the camera, but dmesg does not show any logs when grepping for mvcam -
@mparem https://github.com/veyeimaging/rk35xx_orangepi/releases
please try the latest image or deb packages. -
@mparem
https://github.com/veyeimaging/rk35xx_orangepi/releases/tag/v1.2_mvcam_tablet_cm5
Please try this image file on cm5-tablet. -
@veye_xumm
got it!
should i change in my case rk3588s-orangepi-cm5-tablet.dtb directly like:dtc -I dtb -O dts rk3588s-orangepi-cm5-tablet.dtb -o test.dts dtc -I dts -O dtb test.dts -o rk3588s-orangepi-cm5-tablet.dtband put it back to PC ?
or should i work somehow with rk3588s-orangepi-cm5-tablet-camera2.dtsi as you change it ? -
@zoldaten
My recommended approach is to set up the system compilation environment following the official OrangePi method, then place our provided dtsi files and drivers into it to compile a new deb package.
Your suggested method might work as well, but I haven't personally tried it. -
@veye_xumm ok. i tried method you recommend but when i built new image step-by-step and burn it to sd nothing changed. no veye camera there and no drivers.
-
@veye_xumm hi. i`ve built once again image folowing https://github.com/veyeimaging/rk35xx_orangepi/tree/main/linux
and nothing works:
could you check again instructions you provided ?
moreover, i took rk3588s-orangepi-cm5-tablet.dtb from image with drivers installed you provided above and rk3588s-orangepi-cm5-tablet.dts from original image to compare.
i decompiled `em to .dts and looked for differences.
as far as i see on your image you do not use overlays and put all changes to dts:
i looks like you changes overlap original ov5647, ov138*, etc and they stop working.in addition, i see address drift in program list:
could your explain a bit how to make mixed up cameras working as you changes broke dts ?
-
@veye_xumm and i do not see any overlays from here compiled on image
:
