UNSOLVED OrangePi cm5-tablet RAW-MIPI-SC132M

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 ?