i tried to build on:

• orange pi 5 tablet
• VM machine with Ubuntu 22.04 installed
  got the same errors.
  please check your files.

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

@zoldaten Sorry, we currently only provide kernel version 5.x images for Orange Pi. If you need version 6.x, you will need to compile it yourself based on our open-source code.

hi. i built kernel 6.1.99 - but the errors almost the same as in start of the spoiler to this topic:

in build progress i saw strange missing packages errors.
could your check your instructions ? may be them got obsolete ?

later i`ll tried to repair broken driver for veye you provided.

thanks for help!

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 ?

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

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.

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 ?

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

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.

:

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 ?

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 ?