UNSOLVED OrangePi cm5-tablet RAW-MIPI-SC132M
-
@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 ? -
@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.
-
@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%)
-
@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.omay be i miss something leads to empty image ?
-
@zoldaten
In the source code of veyecam2m.c, please comment out this function.

Additionally, since you are using the RAW-MIPI-SC132M camera, you only need the mvcam driver and its corresponding dtb. -
@veye_xumm ok. i just del it and remove from Makefile.
and changed in main dts - uncomment camera-1.
build kernel package without full image.
installed to jammy 20.04 via dpkg.
and... my mixed cams start working !later i`ll tried to repair broken driver for veye you provided.
thanks for help!
-
@zoldaten looking forward to your good news.
-
@veye_xumm hi. could you provide link to image kernel 6.* image with cameras integrated ?
as far as i saw there are only kernel 5.10 links... -
@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.
-
@veye_xumm got it. i tried to do that but have segmentation fault - something wrong with mali drivers. at the same time drivers for cameras built correctly.