UNSOLVED OrangePi cm5-tablet RAW-MIPI-SC132M

mparem

sudo dmesg | grep mvcam
[sudo] password for orangepi: 
[    6.581083] platform csi2-dcphy0: Fixed dependency cycle(s) with /i2c@fec80000/mvcam2@3b

sudo 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: -- -- -- -- -- -- -- --

veye_xumm

@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.

mparem

@veye_xumm
rk3588s-orangepi-cm5-tablet.dts.txt

rk3588s-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

veye_xumm

@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";

mparem

@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

veye_xumm

@mparem https://github.com/veyeimaging/rk35xx_orangepi/releases
please try the latest image or deb packages.

veye_xumm

@mparem
https://github.com/veyeimaging/rk35xx_orangepi/releases/tag/v1.2_mvcam_tablet_cm5
Please try this image file on cm5-tablet.

zoldaten

@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.dtb

and put it back to PC ?
or should i work somehow with rk3588s-orangepi-cm5-tablet-camera2.dtsi as you change it ?

veye_xumm

@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.

zoldaten

@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.

zoldaten

@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 ?

zoldaten

@veye_xumm and i do not see any overlays from here compiled on image

: