@jossen 不客气。

@nian 不好意思，我们暂时没有计划做raw14bit输出的camera模组。

@sanlu

@veye_xumm i think so. please see screens attached: [image: 1775573271193-1.png] [image: 1775573271002-2.png] when i copied .dts files from veye i saw errors building missing files. i tried to build on: orange pi 5 tablet VM machine with Ubuntu 22.04 installed got the same errors. please check your files.

@乔康 @乔康 said in MV-MIPI-SC130M抓图报错: 驱动正常加载。虽然设备树是4lane的。 问题就在这里，MV-MIPI-SC130M不支持4lane模式配置。 你需要更换设备树为2lane模式。

@乔康 这个问题我们没有遇到。 你可以试试直接用v4l2-ctl抓图，看看效果如何？ https://wiki.veye.cc/index.php/VEYE_CS_Camera_on_Firfly_Boards/zh#.E6.8A.93.E5.8F.96.E5.9B.BE.E7.89.87

@alex_ai First, let me explain the gain configuration logic for the GX-MIPI-IMX662. The IMX662 features 30dB of Analog Gain and supports High Conversion Gain (HCG). The HCG function acts as an amplification during the sensor's analog signal readout, equivalent to 15.3dB. Therefore, when we configure the "Again" parameter, the actual range is [0, 45.3dB]. This means you can set the Analog Gain up to 45dB without enabling Digital Gain (Dgain). Currently, our firmware integrates HCG into the "Again" setting, which may have caused some confusion during your testing. As for the feature to read sensor registers, I have added it to the development roadmap. It will be provided later via a firmware update package.

@veye_xumm said in IMX462+树莓派zero 2w，无法正常控制曝光参数去拍照: @若兮鱼 你使用的是驱动模式，不需要调用camera_i2c_config 核心问题是i2c_write这个可执行文件无法执行。可能是发布的release版本，与你的系统在可执行文件格式方面兼容性不好。你可以进入source目录下，编译一下。然后重新执行。 首先可以通过读取devid来确认你的i2c命令通道，veye_mipi_i2c.sh脚本是否正常了。 你好，谢谢，重新编译source目录里的文件后都正常了。问题已解决。

@ouyangxin 你好，你理解的没错，但是我们现在已经取消了对sda模式的支持，所以这上面的讨论已经没有意义了。

@sheko Sorry, I just got back from the Chinese New Year holiday. Regarding using the RAW-MIPI-SC132M on the Raspberry Pi 5, I suggest you primarily refer to this document. It covers driver installation, how to use the V4L2 mode, and methods for previewing using OpenCV. https://wiki.veye.cc/index.php/Mv_series_camera_appnotes_4_rpi

@nkos Sorry, regarding the attempt to port the camera to the Radxa Zero 3 + 6.x, we tried to set up the standard build environment but were unable to compile successfully. I posted a question on the Radxa forum, but have not yet received a follow-up response. As for the method you mentioned to configure our registers, we recommend that you do not use the driver. Instead, please use our mv_mipi_i2c.sh script. https://wiki.veye.cc/index.php/Mv_mipi_i2c.sh_user_guide

@veye_xumm Thanks for the answer, have a happy holiday!

@veye_xumm That's right. It worked with the lens. Thank you very much for your technical support.

@xlwvu7mx You are welcome.

@d_101 Sorry for the late reply. Based on the current situation, I can only suspect a hardware issue that is causing the I2C path to be unavailable. This could be a problem with your mainboard or with the camera itself. Please return the camera to us, and we will perform testing and inspection.

@ffgemanof The veye_viewer client currently does not support the mono10 and mono12 formats. If you need to use these formats, please configure the data format using mv_mipi_i2c_new.sh, and then acquire the data using v4l2-ctl or the V4L2 API.

Hi @veye_xumm, thank you again for all your help. I found that the VEYE camera you made available with I2C address 0x22 does work on the J401B. And now, after a long series of follow-ups with Seeed Tech Support, I found that i2cdump generates I2C transfer timeouts at address 0x3b (but only 0x3b!). Then Seeed noted that applying the VEYE "compatibility fix" updating the USB Hub firmware to 08C3 removed the timeouts. So I tried that with the VEYE camera and it works! (This with Jetpack 6.1). A weird puzzle remains, I was sure the J401B had USB Hub Firmware version 08C3 as supplied, although with one of the "devices" giving different details to 08C3 on the J401. Hence I did not expect to need the "compatibility fix", and had some concerns that reapplying it could cause a problem. But reapplying the update just now the firmware version was initially 08B3!? It has updated to 08C3, and has fixed camera access to 0x3b. This has been time consuming, but I might now test JetPack 6.2

@veye_xumm Sorry for the late reply. Thank you for the new code! It seems to work partially in the rpi5 standard OS. I was able to compile the read and write files, and some commands work while others don't. The new mgain is stuck at zero, so if i use new exp mode i can set the shutter speed with new mshutter, but not the new mgain, despite changing it returns zero when i probe with the -r parameter. so using the new exp mode i only get a black image. the old mshutter works and i was able go get up to 1 second exposure per frame in streaming mode but the capture mode and capture command don't seem to work. Also i would like to have it work in the rpi archlinux OS that i use for astronomy. The veyecam2m driver works and i get video in the archlinux OS, but i wasn't able to compile the i2c read and write in that system.

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