Posts made by veye_xumm

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

@sanlu

@zoldaten You can ignore the warning shown in your screenshot. However, your probe information is incomplete; it seems that the mvcam probe function has not been triggered.

@乔康

@乔康 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

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

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

@若兮鱼

1. 你使用的是驱动模式，不需要调用camera_i2c_config
2. 核心问题是i2c_write这个可执行文件无法执行。可能是发布的release版本，与你的系统在可执行文件格式方面兼容性不好。你可以进入source目录下，编译一下。然后重新执行。
   首先可以通过读取devid来确认你的i2c命令通道，veye_mipi_i2c.sh脚本是否正常了。

@alex_ai I used firmware version 1.14 for comparison and did not observe any significant noise changes in gamma mode 1 compared to other modes. Could you provide your specific usage parameters and environment?

@alex_ai Thank you for your feedback; we will look into this issue.

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

@zoldaten looking forward to your good news.

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

@alex_ai OK, the GX series and the VEYE series use completely different ISP solutions, so their parameters do not correspond one-to-one. I look forward to your test results.

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

@zoldaten

@zoldaten said in OrangePi cm5-tablet RAW-MIPI-SC132M:

i burned SD with your image provided and there veye presented. what`s the difference ?

Sorry, I misunderstood you earlier. I thought you meant that following the steps to compile wasn't working at all. So, now that you've successfully compiled it, the veyecamera has appeared, correct?

What you should do now is modify the source code of the DTS. For different MIPI interfaces, use different dtsi configurations to set it up for the specific camera or sensor model you want.

@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

@zoldaten I noticed you placed the compiled image onto the SD card. This is likely incorrect. You should refer to the official Orange Pi documentation and flash the compiled image to the eMMC storage that comes with the Orange Pi CM5 core board.

Additionally, you might wonder why we compile the camera's dtsi directly into the main dtb instead of building it separately as an overlay. This approach follows the practice recommended by the Orange Pi manufacturer.

@zoldaten
My recommended approach is to set up the system compilation environment following the official OrangePi method, then place our provided dtsi files and drivers into it to compile a new deb package.
Your suggested method might work as well, but I haven't personally tried it.

@alex_ai In the current program, HCG will be automatically enabled when the gain is higher than 26 dB — you can give it a try.

Also, please try turning off the 3D noise reduction.