@veye_xumm sorry for necro-posting, but this method stopped working. on fresh system I have Failed to set I2C address after running make.sh under mv_tools_rpi/sources on rpi5. do you know if something has changed there?

@veye_xumm 对的，所以我感觉很奇怪。 下面是我修改的install_driver.sh
echo "Add cma=128M to /boot/firmware/cmdline.txt "
echo "--------------------------------------"
sudo sed 's/cma=128M//g' -i /boot/firmware/cmdline.txt
sudo sed 's/[[:blank:]]*$//' -i /boot/firmware/cmdline.txt
sudo sed 's/$/& cma=128M/g' -i /boot/firmware/cmdline.txt
echo "Installing the $driver_name.ko driver"
echo "--------------------------------------"
sudo install -p -m 644 ./driver_bin/$(uname -r)/$driver_name.ko /lib/modules/$(uname -r)/kernel/drivers/media/i2c/
sudo install -p -m 644 ./driver_bin/$(uname -r)/$driver_name.dtbo /boot/firmware/overlays/
sudo /sbin/depmod -a $(uname -r)
echo "reboot now?(y/n):"

谢谢！

@阿坎德 你好，有进一步的结果吗？

已私信。已私信。

@zjutony
a5a4e9a6-73d9-4791-be79-2b8d3929796d-image.png
c8d0ee25-5791-4830-baae-bb3c47232379-image.png
你好，我这边freerunning模式跑的，测试没问题。
要不你配置一下sysreset，让模组恢复下默认值，然后再测试试试？

With this fix it seems more reliable but it did crash again last night leaving a veye_raspistill Zombie. Short stack trace:-

Apr 11 23:31:21 allsky kernel: [22053.109872] WARNING: CPU: 3 PID: 20358 at drivers/firmware/raspberrypi.c:64 rpi_firmware_transaction+0xec/0x128
Apr 11 23:31:21 allsky kernel: [22053.109884] Firmware transaction timeout
Apr 11 23:31:21 allsky kernel: [22053.109895] Modules linked in: rpcsec_gss_krb5 8021q garp stp llc spidev brcmfmac brcmutil sha256_generic i2c_mux_pinctrl i2c_mux raspberrypi_hwmon cfg80211 rfkill bcm2835_codec(C) v4l2_mem2mem bcm2835_v4l2(C) bcm2835_isp(C) bcm2835_mmal_vchiq(C) videobuf2_vmalloc snd_bcm2835(C) videobuf2_dma_contig videobuf2_memops videobuf2_v4l2 videobuf2_common snd_pcm snd_timer i2c_bcm2835 snd spi_bcm2835 videodev mc vc_sm_cma(C) uio_pdrv_genirq uio fixed i2c_dev ip_tables x_tables ipv6
Apr 11 23:31:21 allsky kernel: [22053.110362] CPU: 3 PID: 20358 Comm: kworker/3:0 Tainted: G C 5.10.17-v7+ #1403
Apr 11 23:31:21 allsky kernel: [22053.110369] Hardware name: BCM2835
Apr 11 23:31:21 allsky kernel: [22053.110386] Workqueue: events dbs_work_handler

@picantepeperoni You are welcome.

@veye_xumm Hi,
Firmware update does not solve the problem, after software reset auto exposure mode works normal

@seyran Извините, что так долго не отвечал вам. Судя по вашему снимку экрана, похоже, что команда была выполнена правильно. Вы должны видеть изображение при подключении монитора HDMI.

@veye_xumm ok

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

@lighteek 有点奇怪了。你参考3.5.4把Image也换掉试试。

@watchever
I think what you mentioned is mshutter. Yes, of course.
mshutter :
If you use manual mode, the exposure time will be independent of the ambient brightness.

@veye_xumm
Hi,
We are using Orin 32G and we have installed the jetpack on Nvme M.2 ssd. We will remove the ssd and try installing it in emmc storage.

@yongjin
I don't know what your current state of knowledge is. If you don't understand i2C, you don't understand fpdlink, you don't understand registers. I think you should first learn the basics and be able to understand the information and code we provide now, and then proceed to your next work.
Good luck.

@xsw
很好。
硬件是被动的，软件是主动的。
摄像头不能去操作主板的内存，是靠主板上的软件来操作摄像头，把数据放到内存。
树莓派是上我们提供的两种应用模式，都可以由软件获取到摄像头输出的数据。
请参考详细的文档和代码。

@wqeeqweqwwccsd
你这种测试方法是极为模糊和不确切的。请参考我上一个帖子发给你的链接。

@max
lowlight只有在自动曝光模式下生效。你一旦设置mshutter为手动，lowlight就不生效了。

@veye_xumm Can't save? Oh... It's really disappointing.
Anyway... Okay. Thank you.
I'll close this agenda.

@milank
I think it was RF interference on the FFC cable.