OrangePi cm5-tablet RAW-MIPI-SC132M

veye_xumm

@mparem
Please post dmesg | grep mvcam output here.

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

:

veye_xumm

@zoldaten I noticed you placed the compiled image onto the SD card. This is likely incorrect. You should refer to the official Orange Pi documentation and flash the compiled image to the eMMC storage that comes with the Orange Pi CM5 core board.

Additionally, you might wonder why we compile the camera's dtsi directly into the main dtb instead of building it separately as an overlay. This approach follows the practice recommended by the Orange Pi manufacturer.

zoldaten

@veye_xumm got it.
but why do you recommend flash eMMC ?
i burned SD with your image provided and there veye presented. what`s the difference ?

veye_xumm

@zoldaten

@zoldaten said in OrangePi cm5-tablet RAW-MIPI-SC132M:

i burned SD with your image provided and there veye presented. what`s the difference ?

Sorry, I misunderstood you earlier. I thought you meant that following the steps to compile wasn't working at all. So, now that you've successfully compiled it, the veyecamera has appeared, correct?

What you should do now is modify the source code of the DTS. For different MIPI interfaces, use different dtsi configurations to set it up for the specific camera or sensor model you want.

zoldaten

@veye_xumm veye appears only on image you provided via download link.
the image i built has no veye on board.

should i change the main dts after decompilation ...tablet.dbt > ...tablet.dts?
or use somehow dtsi (https://github.com/veyeimaging/rk35xx_orangepi/tree/main/linux/drivers/cm5/cm5-mvcam-dts) to link with your ...tablet.dbt ?

veye_xumm

@zoldaten
As long as you follow the steps and place our driver and DTS files into the Orange Pi source tree, then compile the image according to the official Orange Pi instructions and flash this image onto the board, the VEYE camera driver should appear correctly.

Essentially, this operation just adds the driver to the original standard Orange Pi system. No additional steps are required after flashing the image. I suspect that you may not have fully applied the modifications in all the necessary parts of the source code.

zoldaten

@veye_xumm hi. i`m trying to build Kernel itself left alone the full image.
and see this error in compile the veye driver:

so the problem in driver file - [0_1772540181473_veyecam2m.zip](Загрузка 100%)

zoldaten

@veye_xumm and could you check steps it did before start build process:

sudo cp -r rk35xx_orangepi/linux/drivers/cm5/cm5-mvcam-dts orangepi-build/kernel/orange-pi-5.10-rk35xx/arch/arm64/boot/dts/rockchip/
sudo cp rk35xx_orangepi/linux/drivers/cm5/config/linux-rockchip-rk3588-legacy.config orangepi-build/external/config/kernel/linux-rockchip-rk3588-legacy.config
sudo cp -r rk35xx_veye_bsp/linux/drivers/kernel_v5.10 orangepi-build/kernel/orange-pi-5.10-rk35xx/drivers/media/i2c/

sudo nano orangepi-build/kernel/orange-pi-5.10-rk35xx/drivers/media/i2c/Kconfig
config VIDEO_DS90UB954
       tristate "TI FDPLINK III support."
       depends on I2C && VIDEO_V4L2 && VIDEO_V4L2_SUBDEV_API
       help
            Driver for TI FDPLINK III .

config VIDEO_VEYECAM2M
       tristate "VEYE 2M camera support."
       depends on I2C && VIDEO_V4L2 && VIDEO_V4L2_SUBDEV_API
       depends on MEDIA_CAMERA_SUPPORT
       help
               Driver for veye 2m camera.
               
config VIDEO_VEYEMVCAM
       tristate "VEYE MV series camera support."
       depends on I2C && VIDEO_V4L2 && VIDEO_V4L2_SUBDEV_API
       depends on MEDIA_CAMERA_SUPPORT
       help
               Driver for veye mv series camera.

config VIDEO_VEYEVBYONE
       tristate "VEYE V-by-One hs toolkit support."
       depends on I2C && VIDEO_V4L2 && VIDEO_V4L2_SUBDEV_API
       depends on MEDIA_CAMERA_SUPPORT
       help
               Driver for vV-by-One hs toolkit .

sudo nano orangepi-build/kernel/orange-pi-5.10-rk35xx/drivers/media/i2c/Makefile
obj-$(CONFIG_VIDEO_DS90UB954) += ds90ub954.o
obj-$(CONFIG_VIDEO_VEYEVBYONE) += veye_vbyone.o
obj-$(CONFIG_VIDEO_VEYECAM2M) += veyecam2m.o
obj-$(CONFIG_VIDEO_VEYEMVCAM) += veye_mvcam.o

may be i miss something leads to empty image ?