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