@veye_xumm it is resolved now, the image is shown. Before with the steps on the forum the .dtbo file was also missing, I copied it from another folder and it didn't work. The right and supported way of installing drivers is very confusing, I tried installing by wiki guide and then compiling locally (github), since it didn't work. Thank you for your patience.

@nian 不客气

@veye_xumm Thanks! I'll read and reinstall the SO.
Hopefully, I'll be able to show if the problem is resolved in the next few days.

@veye_xumm Thanks
my problem is solved.

@opti
Please check this:
https://github.com/veyeimaging/raspberrypi_v4l2/releases/tag/v1.22

@chenhaoyu
这个实现不了，树莓派只有两个mipi口。

@sqf121
这个问题已经解决，请参考一下github上的更新。
https://github.com/veyeimaging/raspberrypi_v4l2

pi@raspberrypi:~/raspberrypi_v4l2/i2c_cmd/source $ sudo ./make.sh

问题：
i2c_read.c: In function ‘main’:
i2c_read.c:112:42: warning: passing argument 4 of ‘i2c_rd’ from incompatible pointer type [-Wincompatible-pointer-types]
112 | i2c_rd(fd, device_addr,reg_addr, &value, num);
| ^~~~~~
| |
| unsigned char (*)[512]
i2c_read.c:20:68: note: expected ‘unsigned char ’ but argument is of type ‘unsigned char ()[512]’
20 | static int i2c_rd(int fd, uint8_t i2c_addr, uint16_t reg, uint8_t *values, uint32_t n)
5157972e-2e6f-451a-b0df-c2344adf9ed2-001.JPG

pi@raspberrypi:~/raspberrypi_v4l2/i2c_cmd/source $ dmesg | grep veye
[ 2.947096] veyecam2m: loading out-of-tree module taints kernel.
[ 2.957137] veyecam2m 4-003b: Unable to load ds90ub954 driver,will go on
[ 2.984139] rp1-cfe 1f00110000.csi: found subdevice /axi/pcie@120000/rp1/i2c@88000/veyecam2m@3b
[ 2.984914] rp1-cfe 1f00128000.csi: found subdevice /axi/pcie@120000/rp1/i2c@80000/veyecam2m@3b
[ 3.082974] veyecam2m 4-003b: camera id is veyecam2m
[ 3.084546] veyecam2m 4-003b: sensor is IMX385
[ 3.084552] veyecam2m 4-003b: board type is ONE board
[ 3.084970] rp1-cfe 1f00128000.csi: Using sensor veyecam2m 4-003b for capture
[ 3.106635] veyecam2m 4-003b: veyecam2m camera probed
[ 3.113508] veyecam2m 6-003b: Unable to load ds90ub954 driver,will go on
[ 3.229811] veyecam2m 6-003b: probe failed
pi@raspberrypi:~/raspberrypi_v4l2/i2c_cmd/source $ cd
cd raspberrypi_v4l2/rpi5_scripts
./media_setting_rpi5.sh veyecam2mpi@raspberrypi:~ $ cd raspberrypi_v4l2/rpi5_scripts
pi@raspberrypi:~/raspberrypi_v4l2/rpi5_scripts $ ./media_setting_rpi5.sh veyecam2m
This is a Raspberry Pi 5.
camera is YUV type
camera name veyecam2m; width 1920; height 1080; media_fmt UYVY8_1X16; pixel_fmt UYVY
CAM1 probed: media device is /dev/media2
set CAM1 finish, plese get frame from /dev/video0 and use /dev/v4l-subdev2 for camera setting
veyecam2m 6 NOT FOUND
pi@raspberrypi:~/raspberrypi_v4l2/rpi5_scripts $

@veye_xumm Okay, thank you very much for the replies.

LivePushStream_2024-04-21_04.49.41.300_04.49.44.300_流星数1.jpg

http://hainanftp.net/lx/LivePushStream_2024-04-21_04.49.41.300_04.49.44.300_流星数1.mp4

已解决，请访问
https://forum.veye.cc/topic/581/树莓派4b-imx462-ffmpeg-meteor-master-ai-流星监控方案-不断更新

@veye_xumm 楼主，我用的这个微雪的树莓派CM4扩展板，
https://www.waveshare.net/wiki/CM4-IO-BASE-A
能麻烦帮我看看么？

@veye_xumm 好的，已经解决了感谢

@natzguk

Raspberry Pi 5 is special, its i2c bus is 4 and 6. meanwhile, Raspberry Pi need to configure the parameters in advance, please refer to this link below:
https://wiki.veye.cc/index.php/V4L2_mode_for_Raspberry_Pi#Raspberry_Pi_5_Setting

@etale_cohomology said in How to set exposure for IMX-287M?:

It turns out you must manually select the I2C bus number (I also enabled I2C on raspi-config). Since I'm using CAM0 on RPI5, the bus is 6. Example:
./mv_mipi_i2c.sh -r -f manufacturer -b 6
This works.

Yes

@lizi 好的。

@veye_xumm For anyone else. This works perfectly. Note that when recompiling on 64-bit Pi, the following warning is produced. It still builds. Just copy the outputs to bin and the scripts work fine.

./make.sh i2c_read.c: In function ‘main’: i2c_read.c:112:35: warning: passing argument 4 of ‘i2c_rd’ from incompatible pointer type [-Wincompatible-pointer-types] 112 | i2c_rd(fd, device_addr,reg_addr, &value, num); | ^~~~~~ | | | unsigned char (*)[512] i2c_read.c:20:68: note: expected ‘unsigned char *’ but argument is of type ‘unsigned char (*)[512]’ 20 | static int i2c_rd(int fd, uint8_t i2c_addr, uint16_t reg, uint8_t *values, uint32_t n)

@etale_cohomology
080d6fcb-12e7-4338-800a-b7ef90734db4-image.png
I think the FFC cable direction is wrong here.

@natzguk

I believe the code is compatible. You can refer to the following link and try compiling it yourself:

https://wiki.veye.cc/index.php/Build_drivers_from_source_for_rpi

@maifengw2023

@veye_xumm said in MV-MIPI-IMX264M+CM4+CM4-NANO-A 需要怎么配置？:

根据原理图，微雪的CM4-NANO-A所引出的CAMERA接口应该是跟树莓派官方的CMIO4板子的cam0一样的。
树莓派4b实际上引出的是cam1。
问题： 你用微雪的CM4-IO-BASE-A，是不是两个摄像头插口都调通了？ 如果没有，那么，首先调通它。 然后再调CM4-NANO-A就顺理成章了。

现在我们给出的技术建议就是这个方向。在我看来，应该不需要改驱动代码的。

如果你现在放弃，我也没有办法了。